Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 23-08-2020 11:07 am, Hans Carlson wrote: On Sat, 22 Aug 2020, Carl Zwanzig wrote: On 8/22/2020 2:03 AM, Nicolas George wrote: There is no duplication, only multiple outputs. Would you also remove the man pages because they are "duplicate" of the HTML pages? Multiple outputs is not duplicative? If the same info in the same format is in two places, that rather sounds like duplication. I can't say this with certainty, but I believe the man pages (and other docs) are auto-generated. ie, there is one central source for the docs (texinfo ?) and all other docs (man, html, etc) are generated from that source. Likewise for the "ffmpeg-all" man page. It's not a separately maintained page, it's auto-generated from all the other man pages. Again, I might be wrong, but I **think** that's the case. Someone more knowledgeable really should confirm this. Re man pages- last time I checked, those are not considered web pages and have a different format & usage, therefore not the same. (OTOH, I don't use the man pages, so. see below.) Many people DO use the man pages, so please don't consider removing them. Again though, I believe they are auto-generated based on other doc sources, so there's no need to maintain separate docs. Yes, there's only one source repository for the documentation text, and the format is texinfo. Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On Sat, 22 Aug 2020, Carl Zwanzig wrote: On 8/22/2020 2:03 AM, Nicolas George wrote: There is no duplication, only multiple outputs. Would you also remove the man pages because they are "duplicate" of the HTML pages? Multiple outputs is not duplicative? If the same info in the same format is in two places, that rather sounds like duplication. I can't say this with certainty, but I believe the man pages (and other docs) are auto-generated. ie, there is one central source for the docs (texinfo ?) and all other docs (man, html, etc) are generated from that source. Likewise for the "ffmpeg-all" man page. It's not a separately maintained page, it's auto-generated from all the other man pages. Again, I might be wrong, but I **think** that's the case. Someone more knowledgeable really should confirm this. Re man pages- last time I checked, those are not considered web pages and have a different format & usage, therefore not the same. (OTOH, I don't use the man pages, so. see below.) Many people DO use the man pages, so please don't consider removing them. Again though, I believe they are auto-generated based on other doc sources, so there's no need to maintain separate docs. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On Friday, 21 August 2020 19:39:07 ACST Gyan Doshi wrote: > On 21-08-2020 02:36 pm, Michael Koch wrote: > > Am 21.08.2020 um 10:50 schrieb Paul B Mahol: > >> On 8/21/20, Michael Koch wrote: > >>> Please add this to the documentation (for example in chapter 20.9 > >>> image2) > >>> > >>> FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, > >>> PGM (binary P5 files are read/write, ascii P2 files are read-only), > >>> PGMYUV, PNG, PPM, TGA, TIFF. > >> > >> Sorry but that list is incomplete. > > > > Then please add what's missing. > > FFmpeg's documentation is very incomplete. I had a rough roadmap at the > start of the year for plugging the gaps, but other events transpired. > > I hope to start a systematic effort in September. > > Gyan > > P.S. ffmpeg supports roughly a few dozen image formats. I'll add the > missing ones to https://ffmpeg.org/general.html#Image-Formats Hi Gyan. I'm not a developer by any stretch of the imagination, but I've a pretty good command of the English language and experience in writing user documentation, as well as a rudimentary understanding of ffmpeg as it applies to stuff that I've needed to do with it. I'd be happy to assist with proof-reading/editing/style checks as appropriate (and I'm sure I'll learn lots along the way by doing so). For a long time I've been of the opinion that ffmpeg documentation has (to date) been written by developers, for developers, with lots of inherent assumptions about what the users of the documentation should know, instead of being written for users with little-to-no technical background or knowledge of the inner workings of ffmpeg and its associated libraries, filters etc, and that this would be addressed by a dedicated "documentation team" working with the developers (those who are willing) to produce and maintain user-level documentation to supplement the dev-level documentation. I think what you're proposing is a good step in that direction, and I'll be happy to help where I can. Regards, Rodney. -- == Rodney Baker VK5ZTV rodney.ba...@iinet.net.au CCNA #CSCO12880208 == ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
One of the things about man pages is that users invariably lack the man command under windows, and you don't get the man pages with most windows builds of ffmpeg anyway. The executable emits messages about man pages, which I've always viewed as practically a bug on Windows builds which will invariably not have them available. P On Saturday, 22 August 2020, 22:19:40 BST, Carl Zwanzig wrote: On 8/22/2020 2:03 AM, Nicolas George wrote: > There is no duplication, only multiple outputs. Would you also remove > the man pages because they are "duplicate" of the HTML pages? Multiple outputs is not duplicative? If the same info in the same format is in two places, that rather sounds like duplication. Re man pages- last time I checked, those are not considered web pages and have a different format & usage, therefore not the same. (OTOH, I don't use the man pages, so. see below.) It's obviously easy for anyone adverse to change to find examples of "it's not like that!!". It should also be obvious that different styles of documentation work for different people- some always go to a man-page style doc, some find topic/area-based html pages easier to use. Don't like one of those? Don't use it. But also don't denigrate those who do. And... how many questions on this list wouldn't need to be asked if the docs provided the answer _to_the_questioner_? Half? Two-thirds? If the docs were really great, we probably wouldn't be having this discussion. Later, z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/22/2020 2:03 AM, Nicolas George wrote: There is no duplication, only multiple outputs. Would you also remove the man pages because they are "duplicate" of the HTML pages? Multiple outputs is not duplicative? If the same info in the same format is in two places, that rather sounds like duplication. Re man pages- last time I checked, those are not considered web pages and have a different format & usage, therefore not the same. (OTOH, I don't use the man pages, so. see below.) It's obviously easy for anyone adverse to change to find examples of "it's not like that!!". It should also be obvious that different styles of documentation work for different people- some always go to a man-page style doc, some find topic/area-based html pages easier to use. Don't like one of those? Don't use it. But also don't denigrate those who do. And... how many questions on this list wouldn't need to be asked if the docs provided the answer _to_the_questioner_? Half? Two-thirds? If the docs were really great, we probably wouldn't be having this discussion. Later, z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am Fr., 21. Aug. 2020 um 18:34 Uhr schrieb Michael Koch : > > Am 21.08.2020 um 17:06 schrieb Gyan Doshi: > > What concerns do you have about using git? > > I don't understand how git works. Have tried it some time ago, > but didn't work, so I gave up. No good instructions available. It is not necessary to completely understand git, I only use it to produce patch files with commit messages that I attach to emails. > A second computer with Linux seems to be required. This is not true. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Michael Koch (12020-08-22): > I agree that it's useful to have one file which contains _all_ > documentation. Searching in one file is easier than searching at multiple > places. But the content of general.html is missing in ffmpeg-all.html (and > also in ffplay-all.html and ffprobe-all.html). Thanks for noticing this. I have made a patch to include the contents of general in the -all pages. Regards, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 22.08.2020 um 11:03 schrieb Nicolas George: Carl Zwanzig (12020-08-21): IMHO, it would make more sense to remove the -all file as it's unweildly and doesn't seem to contain to contain everything anyway. It does contain everything, or there is a bug somewhere. And it is useful precisely because it contains everything: it stays. I agree that it's useful to have one file which contains _all_ documentation. Searching in one file is easier than searching at multiple places. But the content of general.html is missing in ffmpeg-all.html (and also in ffplay-all.html and ffprobe-all.html). Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Carl Zwanzig (12020-08-21): > IMHO, it would make more sense to remove the -all file as it's unweildly and > doesn't seem to contain to contain everything anyway. It does contain everything, or there is a bug somewhere. And it is useful precisely because it contains everything: it stays. > I might go so far as > to start carving things up so there's little to no duplication at all (is > there much? I don't know, that bears checking. One example is stream > selection/specifiers.) There is no duplication, only multiple outputs. Would you also remove the man pages because they are "duplicate" of the HTML pages? Regards, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 08/21/2020 11:08 AM, Gyan Doshi wrote: On 21-08-2020 07:12 pm, Mark Filipak wrote: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? Sure. Do you already have a set of tasks / actions in mind? How about this? Until we get to know each other and you gauge my capabilities, I'll research and document whatever's important to you. I think that initially my most important role would be as an editor -- mostly grammar checking. I hope to also add some user perspective and I trust that you will not reject what I suggest without thinking about it. This will be a long journey during which the path will unfold before us. I can be patient. My experience has been to give users many, many examples having consistent structures with faith that they will see the important patterns. You know, humans are reported to be very good at seeing patterns. Remember a while ago when I asked folks to post working ffmpeg command lines no matter the task or format? My request was rebuffed, but what I was trying to do was gain experience by looking for patterns -- Sort of a Krell mind boost. That's all I needed and I'm convinced that's all most people need. Mark. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/21/2020 3:33 AM, Michael Koch wrote: I never found that "General Documentation" file because I thought "ffmpeg-all" contains what the filename implies: All. This is obviously not the case. The filename is misleading, if the file doesn't contain all documentation. Wouldn't it be better to combine these two files into one file, which contains really all? IMHO, it would make more sense to remove the -all file as it's unweildly and doesn't seem to contain to contain everything anyway. I might go so far as to start carving things up so there's little to no duplication at all (is there much? I don't know, that bears checking. One example is stream selection/specifiers.) Later, z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 21:38 schrieb Gyan Doshi: Git mystifies me, too. I also did a lot of reading but it was written my Martians. For the purposes of only generating doc patches, you only need to know and apply a handful of git commands. Most of the supposed difficulties of working with git revolves around nonlinear histories. I see very little potential for that with pure docs work. You aren't tied to linux either. ffmpeg is perfectly compile-able and testable on Windows. I do it regularly, but even that's not needed here. It's nice to know help is available, and that's appreciated. But let me first look around at my old notes and see what all needs to be done. What can be done in the meantime is for someone to start a wiki or blog or forum and solicit, collect & curate requests for documentation changes. What do users most want answered or documented first? I have collected some things in chapter 2.115 of my book: http://www.astro-electronic.de/FFmpeg_Book.pdf An important first step would be to re-write git-howto.html and explain the git commands more detailed, the whole workflow step by step with many examples. Only the handfull of commands that we really need. Also the new introduced terms should be explained (cloning, push back, remote repository, checkout, tracked branch, rebasing, local branches, commit, master tree, merge commits, patchset). Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 21-08-2020 11:27 pm, Mark Filipak wrote: On 08/21/2020 12:34 PM, Michael Koch wrote: Am 21.08.2020 um 17:06 schrieb Gyan Doshi: On 21-08-2020 07:30 pm, Michael Koch wrote: Am 21.08.2020 um 15:42 schrieb Mark Filipak: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? I'm also ready to help, if it can be done without git. It would be cumbersome, having someone else merge the changes in a git repo. What concerns do you have about using git? I don't understand how git works. Have tried it some time ago, but didn't work, so I gave up. No good instructions available. A second computer with Linux seems to be required. Too complicated. I have no experience with Linux. I know C and C# programming, but I'm not a professional programmer. The page https://www.ffmpeg.org/git-howto.html was obviously not written for beginners. Many terms are introduced without explaining them, and examples are missing. Michael Git mystifies me, too. I also did a lot of reading but it was written my Martians. For the purposes of only generating doc patches, you only need to know and apply a handful of git commands. Most of the supposed difficulties of working with git revolves around nonlinear histories. I see very little potential for that with pure docs work. You aren't tied to linux either. ffmpeg is perfectly compile-able and testable on Windows. I do it regularly, but even that's not needed here. It's nice to know help is available, and that's appreciated. But let me first look around at my old notes and see what all needs to be done. What can be done in the meantime is for someone to start a wiki or blog or forum and solicit, collect & curate requests for documentation changes. What do users most want answered or documented first? Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On Friday, 21 August 2020, 15:01:00 BST, Michael Koch wrote: > I'm also ready to help, if it can be done without git. I feel much the same way. P ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
> Re pointers- consider them an assembly language address. The concept is simple enough; I always thought that the C syntax for them was unnecessarily opaque. P ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/21/2020 10:59 AM, Paul B Mahol wrote: I think git usage is far less complicated than ffmpeg. Also git should be better documented too. Both of those are true :), but still can be mystifying. For those on windoze, there are git GUIs available that take some of the pain out; I generally use "Tortoise GIT". (Otherwise, I really don't like git/hg/svn/cvs/etc (the no-server SCMS's), but those are what too many people use.) Re pointers- consider them an assembly language address. z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/21/20, Michael Koch wrote: > Am 21.08.2020 um 18:41 schrieb Nicolas George: >> Michael Koch (12020-08-21): >>> The page https://www.ffmpeg.org/git-howto.html was obviously not written >>> for beginners. Many terms are introduced without explaining them, and >>> examples are missing. >> I think it was written for people who were familiar with subversion. >> Have you considered following a general-purpose Git tutorial? > > yes, I did read that some time ago, without success. I think git usage is far less complicated than ffmpeg. Also git should be better documented too. Please consider trying again and report where you fail. > > Michael > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 08/21/2020 12:34 PM, Michael Koch wrote: Am 21.08.2020 um 17:06 schrieb Gyan Doshi: On 21-08-2020 07:30 pm, Michael Koch wrote: Am 21.08.2020 um 15:42 schrieb Mark Filipak: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? I'm also ready to help, if it can be done without git. It would be cumbersome, having someone else merge the changes in a git repo. What concerns do you have about using git? I don't understand how git works. Have tried it some time ago, but didn't work, so I gave up. No good instructions available. A second computer with Linux seems to be required. Too complicated. I have no experience with Linux. I know C and C# programming, but I'm not a professional programmer. The page https://www.ffmpeg.org/git-howto.html was obviously not written for beginners. Many terms are introduced without explaining them, and examples are missing. Michael Git mystifies me, too. I also did a lot of reading but it was written my Martians. Also, pointers in 'C' confound me; that's what stops me reading source. 'C' programmers tell me they are like assembly language, and I know 4 or 5 assembly languages (in addition to about 7 HLLs), but "like assembly language" doesn't work with me. It doesn't make sense to me that authors should need to remember which variables are pointers to variables and which are actual variables. I don't know why anyone would think that two references with two different names is useful. I know that 'C' has '.h' files but I don't see why those '.h' files don't fix-up the pointer references automatically. Mark. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 18:41 schrieb Nicolas George: Michael Koch (12020-08-21): The page https://www.ffmpeg.org/git-howto.html was obviously not written for beginners. Many terms are introduced without explaining them, and examples are missing. I think it was written for people who were familiar with subversion. Have you considered following a general-purpose Git tutorial? yes, I did read that some time ago, without success. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Michael Koch (12020-08-21): > The page https://www.ffmpeg.org/git-howto.html was obviously not written > for beginners. Many terms are introduced without explaining them, and > examples are missing. I think it was written for people who were familiar with subversion. Have you considered following a general-purpose Git tutorial? Regards, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 17:06 schrieb Gyan Doshi: On 21-08-2020 07:30 pm, Michael Koch wrote: Am 21.08.2020 um 15:42 schrieb Mark Filipak: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? I'm also ready to help, if it can be done without git. It would be cumbersome, having someone else merge the changes in a git repo. What concerns do you have about using git? I don't understand how git works. Have tried it some time ago, but didn't work, so I gave up. No good instructions available. A second computer with Linux seems to be required. Too complicated. I have no experience with Linux. I know C and C# programming, but I'm not a professional programmer. The page https://www.ffmpeg.org/git-howto.html was obviously not written for beginners. Many terms are introduced without explaining them, and examples are missing. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 21-08-2020 07:12 pm, Mark Filipak wrote: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? Sure. Do you already have a set of tasks / actions in mind? Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 21-08-2020 07:30 pm, Michael Koch wrote: Am 21.08.2020 um 15:42 schrieb Mark Filipak: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? I'm also ready to help, if it can be done without git. It would be cumbersome, having someone else merge the changes in a git repo. What concerns do you have about using git? Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 15:42 schrieb Mark Filipak: On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? I'm also ready to help, if it can be done without git. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 12:44 schrieb Gyan Doshi: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. Gyan P.S. ffmpeg supports roughly a few dozen image formats. I'll add the missing ones to https://ffmpeg.org/general.html#Image-Formats That's very interesting. I never found that "General Documentation" file because I thought "ffmpeg-all" contains what the filename implies: All. This is obviously not the case. The filename is misleading, if the file doesn't contain all documentation. Wouldn't it be better to combine these two files into one file, which contains really all? ffmpeg-all consolidates the documentation for all component options and the options of the ffmpeg core binary. tool. Start exploring at https://ffmpeg.org/documentation.html It would be helpful if you add a link in ffmpeg-all.html, chapter 20.9 (image2) which points to general.html, chapter 2.2 where the supported image formats are listed. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 08/21/2020 06:44 AM, Gyan Doshi wrote: On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. May I assist you? Mark. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 21-08-2020 04:03 pm, Michael Koch wrote: Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. Gyan P.S. ffmpeg supports roughly a few dozen image formats. I'll add the missing ones to https://ffmpeg.org/general.html#Image-Formats That's very interesting. I never found that "General Documentation" file because I thought "ffmpeg-all" contains what the filename implies: All. This is obviously not the case. The filename is misleading, if the file doesn't contain all documentation. Wouldn't it be better to combine these two files into one file, which contains really all? ffmpeg-all consolidates the documentation for all component options and the options of the ffmpeg core binary. tool. Start exploring at https://ffmpeg.org/documentation.html Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 12:09 schrieb Gyan Doshi: On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. Gyan P.S. ffmpeg supports roughly a few dozen image formats. I'll add the missing ones to https://ffmpeg.org/general.html#Image-Formats That's very interesting. I never found that "General Documentation" file because I thought "ffmpeg-all" contains what the filename implies: All. This is obviously not the case. The filename is misleading, if the file doesn't contain all documentation. Wouldn't it be better to combine these two files into one file, which contains really all? Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 21-08-2020 02:36 pm, Michael Koch wrote: Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. FFmpeg's documentation is very incomplete. I had a rough roadmap at the start of the year for plugging the gaps, but other events transpired. I hope to start a systematic effort in September. Gyan P.S. ffmpeg supports roughly a few dozen image formats. I'll add the missing ones to https://ffmpeg.org/general.html#Image-Formats ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 21.08.2020 um 10:50 schrieb Paul B Mahol: On 8/21/20, Michael Koch wrote: Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. Then please add what's missing. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/21/20, Michael Koch wrote: > Please add this to the documentation (for example in chapter 20.9 image2) > > FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, > PGM (binary P5 files are read/write, ascii P2 files are read-only), > PGMYUV, PNG, PPM, TGA, TIFF. Sorry but that list is incomplete. > > Michael > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Please add this to the documentation (for example in chapter 20.9 image2) FFmpeg supports the following image formats: BMP, DNG, GIF, JPG, PAM, PGM (binary P5 files are read/write, ascii P2 files are read-only), PGMYUV, PNG, PPM, TGA, TIFF. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am Mi., 19. Aug. 2020 um 22:48 Uhr schrieb Nicolas George : > > Carl Eugen Hoyos (12020-08-19): > > (I'd like to add that the extremely important information about automatic > > scale filter insertion was originally shown with default verbosity, I always > > wanted to restore this behaviour and wonder now who changed it...) > > commit 1a49a169eb74a978eb7b2a4f2caf3520b7741ee5 > Author: Anton Khirnov > Date: 2012-06-25 06:31:38 +0200 > > lavfi: make filters less verbose. > > [...] > diff --git a/libavfilter/avfilter.c b/libavfilter/avfilter.c > index b550169468..dc828153f9 100644 > --- a/libavfilter/avfilter.c > +++ b/libavfilter/avfilter.c > @@ -101,7 +101,7 @@ int avfilter_insert_filter(AVFilterLink *link, > AVFilterContext *filt, > int ret; > unsigned dstpad_idx = link->dstpad - link->dst->input_pads; > > -av_log(link->dst, AV_LOG_INFO, "auto-inserting filter '%s' " > +av_log(link->dst, AV_LOG_VERBOSE, "auto-inserting filter '%s' " > "between the filter '%s' and the filter '%s'\n", > filt->name, link->src->name, link->dst->name); How unsurprising. Sorry for being right, Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Carl Eugen Hoyos (12020-08-19): > (I'd like to add that the extremely important information about automatic > scale filter insertion was originally shown with default verbosity, I always > wanted to restore this behaviour and wonder now who changed it...) commit 1a49a169eb74a978eb7b2a4f2caf3520b7741ee5 Author: Anton Khirnov Date: 2012-06-25 06:31:38 +0200 lavfi: make filters less verbose. [...] diff --git a/libavfilter/avfilter.c b/libavfilter/avfilter.c index b550169468..dc828153f9 100644 --- a/libavfilter/avfilter.c +++ b/libavfilter/avfilter.c @@ -101,7 +101,7 @@ int avfilter_insert_filter(AVFilterLink *link, AVFilterContext *filt, int ret; unsigned dstpad_idx = link->dstpad - link->dst->input_pads; -av_log(link->dst, AV_LOG_INFO, "auto-inserting filter '%s' " +av_log(link->dst, AV_LOG_VERBOSE, "auto-inserting filter '%s' " "between the filter '%s' and the filter '%s'\n", filt->name, link->src->name, link->dst->name); Restoring the verbosity would probably be a good idea. You may want to review the rest of the changes in this patch. Regards, -- Nicolas George signature.asc Description: PGP signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am Mi., 19. Aug. 2020 um 19:59 Uhr schrieb Paul B Mahol : > > 1. Insert a showinfo filter after maskedmerge and check the pixel format. > > Just use -v debug, it will show whenever scale/format filter is auto inserted. Luckily, -v verbose is sufficient. (I'd like to add that the extremely important information about automatic scale filter insertion was originally shown with default verbosity, I always wanted to restore this behaviour and wonder now who changed it...) Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/19/20, Michael Koch wrote: > Am 19.08.2020 um 16:34 schrieb Paul B Mahol: >> On 8/19/20, Michael Koch wrote: >>> Am 18.08.2020 um 14:35 schrieb Michael Koch: Hello all, I have a question about this script: rem Create red and yellow videos 300x300 c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 c:\ffmpeg\ffmpeg -f lavfi -i color=yellow:size=300x300:duration=5 -y yellow.mp4 rem Create a mergemap file 600x300 c:\ffmpeg\ffmpeg -f lavfi -i nullsrc=size=300x300 -vf "format=gray8,geq='clip(128-128/10*(180-200/150*hypot(X-150,Y-150)),0,255)',v360=input=fisheye:output=e:ih_fov=200:iv_fov=200,format=rgb24" -frames 1 -y mergemap.png rem Stitch two fisheye videos together to an equirectangular video, with merging at the border c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" -y out.mp4 This works fine and the output video looks as expected. My question is why "format=rgb24" is required between "maskedmerge" and "format=yuv422p". Normally two consecutive format conversions should be unnecessary. But it doesn't work when I omit "format=rgb24". The colors become wrong. >>> It seems that v360 and maskedmerge change the pixel format from rgb24 to >>> the planar gbrp pixel format. >>> But why isn't it possible to convert gbrp directly to yuv422p, without >>> an intermediate conversion to rgb24? Is this a bug? >>> >>> I suggest to add to the documentation that v360 and maskedmerge (and >>> possibly also other filters) change the pixel format to gbrp. As a user >>> I was assuming that the pixel format remains the same, unless noted >>> otherwise in the documentation. >> You are deeply confused about our filters. >> Any filter can change pixel formats to one that they accepts thus gbrp >> is picked instead of packed rgb, this is already documented >> implicitly. > > It would be very helpful to find in the documentation for each filter a > list of the accepted input pixel formats, and it's also a useful > information if a filter is capable of changing the pixel format. Or can > all filters change the pixel format? > >> Your mergemap is produced in rgb24 pixel format and it only work with >> rgb pixel formats otherwise you get wrong output from maskedmerge. > > OK, understood. I converted the mergemap to gbrp and now it works fine. > In my opinion the whole thing is badly documented. If input is in yuv422p that you want to be filtered than mergemap needs to be in yuv422p too. > On one hand, the filter does automatically change the first two inputs > to a format that it accepts, in this case gbrp. > On the other hand, the filter is unable to automatically change the > third input to the same pixel format, which is the only pixel format > that works. > > Do you agree that this is the correct workflow? > 1. Insert a showinfo filter after maskedmerge and check the pixel format. Just use -v debug, it will show whenever scale/format filter is auto inserted. It may be to spammy with unrelated messages from other components. There is patch in preparation to disable all auto conversions in filtergraph, than you are on your own to fix any issues if you enable such flag. > 2. Insert a format conversion in the filter chain that converts the > mergemap to the same pixel format as found in step 1. That is useful only when you disable auto conversion with flag that gonna be added (I hope soon) to lavfi. > > Michael > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am Di., 18. Aug. 2020 um 14:44 Uhr schrieb Michael Koch : > c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi > "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" > -y out.mp4 > > > This works fine and the output video looks as expected. My > question is why "format=rgb24" is required I believe it was already explained why it really is required in this case. Also important to mention imo is that in general, the automatic pix_fmt conversion cannot always succeed, the system as a whole is not and cannot be clairvoyant. Therefore, for a sufficiently complex filter-chain, you have to force conversions with format because without it, the conversion decisions may be wrong (or at least not optimal). Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 19.08.2020 um 16:34 schrieb Paul B Mahol: On 8/19/20, Michael Koch wrote: Am 18.08.2020 um 14:35 schrieb Michael Koch: Hello all, I have a question about this script: rem Create red and yellow videos 300x300 c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 c:\ffmpeg\ffmpeg -f lavfi -i color=yellow:size=300x300:duration=5 -y yellow.mp4 rem Create a mergemap file 600x300 c:\ffmpeg\ffmpeg -f lavfi -i nullsrc=size=300x300 -vf "format=gray8,geq='clip(128-128/10*(180-200/150*hypot(X-150,Y-150)),0,255)',v360=input=fisheye:output=e:ih_fov=200:iv_fov=200,format=rgb24" -frames 1 -y mergemap.png rem Stitch two fisheye videos together to an equirectangular video, with merging at the border c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" -y out.mp4 This works fine and the output video looks as expected. My question is why "format=rgb24" is required between "maskedmerge" and "format=yuv422p". Normally two consecutive format conversions should be unnecessary. But it doesn't work when I omit "format=rgb24". The colors become wrong. It seems that v360 and maskedmerge change the pixel format from rgb24 to the planar gbrp pixel format. But why isn't it possible to convert gbrp directly to yuv422p, without an intermediate conversion to rgb24? Is this a bug? I suggest to add to the documentation that v360 and maskedmerge (and possibly also other filters) change the pixel format to gbrp. As a user I was assuming that the pixel format remains the same, unless noted otherwise in the documentation. You are deeply confused about our filters. Any filter can change pixel formats to one that they accepts thus gbrp is picked instead of packed rgb, this is already documented implicitly. It would be very helpful to find in the documentation for each filter a list of the accepted input pixel formats, and it's also a useful information if a filter is capable of changing the pixel format. Or can all filters change the pixel format? Your mergemap is produced in rgb24 pixel format and it only work with rgb pixel formats otherwise you get wrong output from maskedmerge. OK, understood. I converted the mergemap to gbrp and now it works fine. In my opinion the whole thing is badly documented. On one hand, the filter does automatically change the first two inputs to a format that it accepts, in this case gbrp. On the other hand, the filter is unable to automatically change the third input to the same pixel format, which is the only pixel format that works. Do you agree that this is the correct workflow? 1. Insert a showinfo filter after maskedmerge and check the pixel format. 2. Insert a format conversion in the filter chain that converts the mergemap to the same pixel format as found in step 1. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
On 8/19/20, Michael Koch wrote: > Am 18.08.2020 um 14:35 schrieb Michael Koch: >> Hello all, >> >> I have a question about this script: >> >> rem Create red and yellow videos 300x300 >> >> c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 >> c:\ffmpeg\ffmpeg -f lavfi -i color=yellow:size=300x300:duration=5 -y >> yellow.mp4 >> >> rem Create a mergemap file 600x300 >> >> c:\ffmpeg\ffmpeg -f lavfi -i nullsrc=size=300x300 -vf >> "format=gray8,geq='clip(128-128/10*(180-200/150*hypot(X-150,Y-150)),0,255)',v360=input=fisheye:output=e:ih_fov=200:iv_fov=200,format=rgb24" >> >> -frames 1 -y mergemap.png >> >> rem Stitch two fisheye videos together to an equirectangular video, >> with merging at the border >> >> c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi >> "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" >> >> -y out.mp4 >> >> >> This works fine and the output video looks as expected. My question is >> why "format=rgb24" is required between "maskedmerge" and >> "format=yuv422p". Normally two consecutive format conversions should >> be unnecessary. But it doesn't work when I omit "format=rgb24". The >> colors become wrong. > > It seems that v360 and maskedmerge change the pixel format from rgb24 to > the planar gbrp pixel format. > But why isn't it possible to convert gbrp directly to yuv422p, without > an intermediate conversion to rgb24? Is this a bug? > > I suggest to add to the documentation that v360 and maskedmerge (and > possibly also other filters) change the pixel format to gbrp. As a user > I was assuming that the pixel format remains the same, unless noted > otherwise in the documentation. You are deeply confused about our filters. Any filter can change pixel formats to one that they accepts thus gbrp is picked instead of packed rgb, this is already documented implicitly. Your mergemap is produced in rgb24 pixel format and it only work with rgb pixel formats otherwise you get wrong output from maskedmerge. If it does not work with yuv444p pixel formats either than you have bigger problem, otherwise it is giving bad output as yuv422p is subsampled pixel format and thus you need to create different mergemap equation per plane. As for 3rd and 2nd plane of yuv422p pixel format have half of width and same height as first plane. > > Michael > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Am 18.08.2020 um 14:35 schrieb Michael Koch: Hello all, I have a question about this script: rem Create red and yellow videos 300x300 c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 c:\ffmpeg\ffmpeg -f lavfi -i color=yellow:size=300x300:duration=5 -y yellow.mp4 rem Create a mergemap file 600x300 c:\ffmpeg\ffmpeg -f lavfi -i nullsrc=size=300x300 -vf "format=gray8,geq='clip(128-128/10*(180-200/150*hypot(X-150,Y-150)),0,255)',v360=input=fisheye:output=e:ih_fov=200:iv_fov=200,format=rgb24" -frames 1 -y mergemap.png rem Stitch two fisheye videos together to an equirectangular video, with merging at the border c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" -y out.mp4 This works fine and the output video looks as expected. My question is why "format=rgb24" is required between "maskedmerge" and "format=yuv422p". Normally two consecutive format conversions should be unnecessary. But it doesn't work when I omit "format=rgb24". The colors become wrong. It seems that v360 and maskedmerge change the pixel format from rgb24 to the planar gbrp pixel format. But why isn't it possible to convert gbrp directly to yuv422p, without an intermediate conversion to rgb24? Is this a bug? I suggest to add to the documentation that v360 and maskedmerge (and possibly also other filters) change the pixel format to gbrp. As a user I was assuming that the pixel format remains the same, unless noted otherwise in the documentation. Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Why is format=rgb24 required after maskedmerge?
Hello all, I have a question about this script: rem Create red and yellow videos 300x300 c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 c:\ffmpeg\ffmpeg -f lavfi -i color=yellow:size=300x300:duration=5 -y yellow.mp4 rem Create a mergemap file 600x300 c:\ffmpeg\ffmpeg -f lavfi -i nullsrc=size=300x300 -vf "format=gray8,geq='clip(128-128/10*(180-200/150*hypot(X-150,Y-150)),0,255)',v360=input=fisheye:output=e:ih_fov=200:iv_fov=200,format=rgb24" -frames 1 -y mergemap.png rem Stitch two fisheye videos together to an equirectangular video, with merging at the border c:\ffmpeg\ffmpeg -i red.mp4 -i yellow.mp4 -i mergemap.png -lavfi "[0]format=rgb24,v360=input=fisheye:output=e:ih_fov=200:iv_fov=200[a];[1]format=rgb24,v360=input=fisheye:output=e:yaw=180:ih_fov=200:iv_fov=200[b];[a][b][2]maskedmerge,format=rgb24,format=yuv422p" -y out.mp4 This works fine and the output video looks as expected. My question is why "format=rgb24" is required between "maskedmerge" and "format=yuv422p". Normally two consecutive format conversions should be unnecessary. But it doesn't work when I omit "format=rgb24". The colors become wrong. The console output is copied below. After I pasted the console output to this mail, I did make a test with the latest download from Zeranoe, but it's the same problem. Thanks, Michael C:\Users\astro\Desktop\Ricoh_Theta>rem Create red and yellow videos C:\Users\astro\Desktop\Ricoh_Theta>c:\ffmpeg\ffmpeg -f lavfi -i color=red:size=300x300:duration=5 -y red.mp4 ffmpeg version git-2020-06-20-29ea4e1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.3.1 (GCC) 20200523 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf libavutil 56. 55.100 / 56. 55.100 libavcodec 58. 93.100 / 58. 93.100 libavformat 58. 47.100 / 58. 47.100 libavdevice 58. 11.100 / 58. 11.100 libavfilter 7. 86.100 / 7. 86.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc 55. 8.100 / 55. 8.100 Input #0, lavfi, from 'color=red:size=300x300:duration=5': Duration: N/A, start: 0.00, bitrate: N/A Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 300x300 [SAR 1:1 DAR 1:1], 25 tbr, 25 tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264)) Press [q] to stop, [?] for help [libx264 @ 011f173614c0] using SAR=1/1 [libx264 @ 011f173614c0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 [libx264 @ 011f173614c0] profile High, level 1.3, 4:2:0, 8-bit [libx264 @ 011f173614c0] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=9 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 Output #0, mp4, to 'red.mp4': Metadata: encoder : Lavf58.47.100 Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 300x300 [SAR 1:1 DAR 1:1], q=-1--1, 25 fps, 12800 tbn, 25 tbc Metadata: encoder : Lavc58.93.100 libx264 Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A [Parsed_color_0 @ 011f17310b40] EOF timestamp not reliable frame= 125 fps=0.0 q=-1.0 Lsize= 5kB time=00:00:04.88 bitrate= 8.5kbits/s speed=91.2x video:3kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 83.759773% [libx264 @ 011f173614c0] frame I:1 Avg QP: 9.00 size: 71 [libx264 @ 011f173614c0] frame P:31 Avg QP: 9.23 size: 23 [libx264 @ 011f173614c0] frame B:93 Avg QP:12.67 size
