Re: [FFmpeg-user] Problem with pixel format and/or missing constant
Am Do., 12. März 2020 um 00:28 Uhr schrieb Reindl Harald : > > That's apart from the fact that we don't have the manpower to support > > releases apart from security issues. > > irreleavent in the context "only latest git is supported on this list" > which is *users list* and so y*you* can decide not actively support any > question with a build from yesterday but telling "not supported on this > list" is nonsense So you do believe that time is not a limiting factor? Let me clarify for you that time is the only limiting factor for FFmpeg development. 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] Problem with pixel format and/or missing constant
Am 12.03.20 um 00:23 schrieb Carl Eugen Hoyos: > Am Do., 12. März 2020 um 00:17 Uhr schrieb Reindl Harald > : >> >> Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos: >>> Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald >>> : Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: > Why do you want to use a newer x264? > why do you always answer "only current GIT of ffmpeg is supported here" >>> >>> Because the development of the two projects is nowadays very different, >>> monochrome encodings (for example) are not supported by most decoders. >> >> either the latest or greatest tarball of whatever is the best or it's not > > In the case of x264 (where development was practically finished a long time > ago) and which has a very small number of reported bugs, it will not make a > difference unless you need monochrome encoding or an optimization for a > particular platform. > For FFmpeg (where development will never be finished) with its myriad > of known (and unknown) bugs, every day brings a version that is better > than the version of the day before (for any usage). and it will introduce new bugs not present in the version the day before as it's common and happens for every sort of software development on planet earth > That's apart from the fact that we don't have the manpower to support > releases apart from security issues. irreleavent in the context "only latest git is supported on this list" which is *users list* and so y*you* can decide not actively support any question with a build from yesterday but telling "not supported on this list" is nonsense ___ 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] Problem with pixel format and/or missing constant
Am Do., 12. März 2020 um 00:17 Uhr schrieb Reindl Harald : > > > > Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos: > > Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald > > : > >> > >> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: > >>> Why do you want to use a newer x264? > >>> > >> why do you always answer "only current GIT of ffmpeg is supported here" > > > > Because the development of the two projects is nowadays very different, > > monochrome encodings (for example) are not supported by most decoders. > > either the latest or greatest tarball of whatever is the best or it's not In the case of x264 (where development was practically finished a long time ago) and which has a very small number of reported bugs, it will not make a difference unless you need monochrome encoding or an optimization for a particular platform. For FFmpeg (where development will never be finished) with its myriad of known (and unknown) bugs, every day brings a version that is better than the version of the day before (for any usage). That's apart from the fact that we don't have the manpower to support releases apart from security issues. 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] Problem with pixel format and/or missing constant
Am 11.03.20 um 22:48 schrieb Carl Eugen Hoyos: > Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald > : >> >> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: >>> Why do you want to use a newer x264? >>> >> why do you always answer "only current GIT of ffmpeg is supported here" > > Because the development of the two projects is nowadays very different, > monochrome encodings (for example) are not supported by most decoders. either the latest or greatest tarball of whatever is the best or it's not ___ 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] Problem with pixel format and/or missing constant
Am 11.03.20 um 21:04 schrieb Ted Park: Hi, Is it thinkable that libx264 could encode with constrained_baseline profile some day? Currently it only can decode it. IIRC, contained baseline is no different from the original baseline bitstream profile, except it has a flag set (or unset). Does your decoder refuse to decode baseline profile media? I don't really know what is refused. But in the end I was able to create a "constrained baseline" without setting it explicitly. Please see my other thread: "How to compress .MOV file compatible to Canon camera" -Ulf ___ 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] Problem with pixel format and/or missing constant
On 03/11/2020 06:45 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak : On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak : For what it's worth, though the MPEG encoder specs support full, 16-bit monochrome (black-&-white) that, theoretically, would better render I didn't know and I am mildly surprised (16bit video is very uncommon). Otoh, "MPEG encoder spec" is not very precise... monochrome video, all of the modern DVDs that I've encountered use YCbCr 4:2:0 for black-&-white movies. Because that is what the DVD specification requires. Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the $5-thousand for the DVD spec. This is part of the publicly known, non-secret part of the specification. By the way, of course, I made a silly mistake. I should have written "full, 24-bit monochrome". I am curious: Which MPEG specification defines 24-bit monochrome encoding? Edit: Now that I think about it more, maybe I was right in the first place: 16-bit monochrome. Like I 'said', since it (16-bit/24-bit) isn't used for DVD, I didn't commit it to documentation. I'll try harder. Oh, gosh, I ran across that long, long ago. Since it's not used for DVDs, I just noted it but didn't document it. I'll be on the lookout for it and get back to you, but don't hold your breath. :-) Regards, 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] Problem with pixel format and/or missing constant
On 03/11/2020 06:45 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak : On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak : For what it's worth, though the MPEG encoder specs support full, 16-bit monochrome (black-&-white) that, theoretically, would better render I didn't know and I am mildly surprised (16bit video is very uncommon). Otoh, "MPEG encoder spec" is not very precise... monochrome video, all of the modern DVDs that I've encountered use YCbCr 4:2:0 for black-&-white movies. Because that is what the DVD specification requires. Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the $5-thousand for the DVD spec. This is part of the publicly known, non-secret part of the specification. By the way, of course, I made a silly mistake. I should have written "full, 24-bit monochrome". I am curious: Which MPEG specification defines 24-bit monochrome encoding? Oh, gosh, I ran across that long, long ago. Since it's not used for DVDs, I just noted it but didn't document it. I'll be on the lookout for it and get back to you, but don't hold your breath. :-) Regards, 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 23:17 Uhr schrieb Ted Park : > > All features specific to "baseline" (which do not exist in main and > > high) are neither > > supported by any available H.264 encoder nor decoder (including libavcodec). > > All this features were removed for "constrained baseline" which is > > supported by > > all H.264 encoders and all H.264 decoders (even if they call it "baseline”). > > Can you elaborate (i.e. on the features removed)? Flexible macroblock ordering Arbitrary slice ordering Redundant slices 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] Problem with pixel format and/or missing constant
On 03/11/2020 06:41 PM, Ted Park wrote>> haven't spent the $5-thousand for the DVD spec Isn’t that just to be a subscriber/member?? I think it’s a bit more than that if you want the whole DVD specs… DVD has been reverse engineered pretty extensively though, shouldn’t be too difficult to find documentation, even if its not official. There are inconsistencies in the hacked specs (implying errors) which I've partially reconciled, but the inconsistencies are all rather minor. ___ 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 23:15 Uhr schrieb Mark Filipak : > > On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote: > > Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak > > : > >> For what it's worth, though the MPEG encoder specs support full, 16-bit > >> monochrome (black-&-white) that, theoretically, would better render > > > > I didn't know and I am mildly surprised (16bit video is very uncommon). > > Otoh, "MPEG encoder spec" is not very precise... > > > >> monochrome video, all of the modern DVDs that I've encountered > >> use YCbCr 4:2:0 for black-&-white movies. > > > > Because that is what the DVD specification requires. > > Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the > $5-thousand for the DVD spec. This is part of the publicly known, non-secret part of the specification. > By the way, of course, I made a silly mistake. I should have written > "full, 24-bit monochrome". I am curious: Which MPEG specification defines 24-bit monochrome encoding? 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] Problem with pixel format and/or missing constant
Hello, >> Because that is what the DVD specification requires. >> Carl Eugen > > Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the > $5-thousand for the DVD spec. > > By the way, of course, I made a silly mistake. I should have written "full, > 24-bit monochrome". Ooops. Senior moment. Just thought the context might be mentioning... When DVD was gaining traction many people still had crts. Nobody was going to watch black and white movies on super expensive grayscale monitors, so it makes sense. (Unless you could convince someone in radiology to lend you a cart I guess :P) > haven't spent the $5-thousand for the DVD spec Isn’t that just to be a subscriber/member?? I think it’s a bit more than that if you want the whole DVD specs… DVD has been reverse engineered pretty extensively though, shouldn’t be too difficult to find documentation, even if its not official. Regards, Ted Park ___ 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] Problem with pixel format and/or missing constant
Hi, > All features specific to "baseline" (which do not exist in main and > high) are neither > supported by any available H.264 encoder nor decoder (including libavcodec). > All this features were removed for "constrained baseline" which is supported > by > all H.264 encoders and all H.264 decoders (even if they call it "baseline”). Can you elaborate (i.e. on the features removed)? I had been under the impression that baseline and constrained baseline didn’t specify any encoding feature restrictions and basically a name change for non-technical reasons. I just went back to read this from the ITU spec to read: > NOTE – This specification of the Constrained Baseline profile is technically > identical to specification of the use of the Baseline profile with > constraint_set1_flag equal to1. Thus, any existing specifications (in other > documents that reference this Recommendation | International Standard) that > have referred to the use of the Baseline profile with constraint_set1_flag > equal to 1 should thus be interpreted as continuing in force as being > technically identical to referring to the use of the Constrained Baseline > profile (without any need for revision of these existing specifications to > instead refer explicitly to the use of the Constrained Baseline profile). > And sure enough it doesnt really say what I originally thought, I think when I go through the profile requirements, basically weighted prediction and entropy coding of any kind is not allowed in constrained baseline and no random slice order, as opposed to the original definition for baseline, is that correct? Regards, Ted Park ___ 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] Problem with pixel format and/or missing constant
On 03/11/2020 06:09 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak : On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald : Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: Why do you want to use a newer x264? why do you always answer "only current GIT of ffmpeg is supported here" Because the development of the two projects is nowadays very different, monochrome encodings (for example) are not supported by most decoders. For what it's worth, though the MPEG encoder specs support full, 16-bit monochrome (black-&-white) that, theoretically, would better render I didn't know and I am mildly surprised (16bit video is very uncommon). Otoh, "MPEG encoder spec" is not very precise... monochrome video, all of the modern DVDs that I've encountered use YCbCr 4:2:0 for black-&-white movies. Because that is what the DVD specification requires. Carl Eugen Ah! Well, that explains it. Thanks Carl Eugen. I haven't spent the $5-thousand for the DVD spec. By the way, of course, I made a silly mistake. I should have written "full, 24-bit monochrome". Ooops. Senior moment. ___ 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 23:05 Uhr schrieb Mark Filipak : > > On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote: > > Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald > > : > >> > >> Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: > >>> Why do you want to use a newer x264? > >>> > >> why do you always answer "only current GIT of ffmpeg is supported here" > > > > Because the development of the two projects is nowadays very different, > > monochrome encodings (for example) are not supported by most decoders. > > For what it's worth, though the MPEG encoder specs support full, 16-bit > monochrome (black-&-white) that, theoretically, would better render I didn't know and I am mildly surprised (16bit video is very uncommon). Otoh, "MPEG encoder spec" is not very precise... > monochrome video, all of the modern DVDs that I've encountered use YCbCr > 4:2:0 for black-&-white movies. Because that is what the DVD specification requires. 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] Problem with pixel format and/or missing constant
On 03/11/2020 05:48 PM, Carl Eugen Hoyos wrote: Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald : Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: Why do you want to use a newer x264? why do you always answer "only current GIT of ffmpeg is supported here" Because the development of the two projects is nowadays very different, monochrome encodings (for example) are not supported by most decoders. For what it's worth, though the MPEG encoder specs support full, 16-bit monochrome (black-&-white) that, theoretically, would better render monochrome video, all of the modern DVDs that I've encountered use YCbCr 4:2:0 for black-&-white movies. ___ 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 22:44 Uhr schrieb Reindl Harald : > > Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: > > Why do you want to use a newer x264? > > > why do you always answer "only current GIT of ffmpeg is supported here" Because the development of the two projects is nowadays very different, monochrome encodings (for example) are not supported by most decoders. > to *any* question on this and then come up with a dumb "why to you want > to use a recent dependency of ffmpeg" > > you have some sort of split brain Please consider this a last warning. 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] Problem with pixel format and/or missing constant
Am 11.03.20 um 20:02 schrieb Carl Eugen Hoyos: > Why do you want to use a newer x264? > > Carl Eugen why do you always answer "only current GIT of ffmpeg is supported here" to *any* question on this and then come up with a dumb "why to you want to use a recent dependency of ffmpeg" you have some sort of split brain ___ 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] Problem with pixel format and/or missing constant
On 03/11/2020 03:21 PM, Lou Logan wrote: On Wed, Mar 11, 2020, at 10:51 AM, Ulf Zibis wrote: Does John van Sickle's binary use a current version? See the build info / readme for a list of external library versions: https://johnvansickle.com/ffmpeg/git-readme.txt How can I use a more current version with the ffmpeg git version? You can compile it: https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu Thanks for the link, Lou. 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 21:27 Uhr schrieb Ted Park : > > Hi, > > > Is it thinkable that libx264 could encode with constrained_baseline > > profile some day? Currently it only can decode it. > > IIRC, contained baseline is no different from the original baseline bitstream > profile All features specific to "baseline" (which do not exist in main and high) are neither supported by any available H.264 encoder nor decoder (including libavcodec). All this features were removed for "constrained baseline" which is supported by all H.264 encoders and all H.264 decoders (even if they call it "baseline"). 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] Problem with pixel format and/or missing constant
Hi, > Is it thinkable that libx264 could encode with constrained_baseline > profile some day? Currently it only can decode it. IIRC, contained baseline is no different from the original baseline bitstream profile, except it has a flag set (or unset). Does your decoder refuse to decode baseline profile media? Regards, Ted Park ___ 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] Problem with pixel format and/or missing constant
On Wed, Mar 11, 2020, at 11:50 AM, Ulf Zibis wrote: > > Is it thinkable that libx264 could encode with constrained_baseline > profile some day? "-profile:v baseline" is Constrained Baseline. You can always refer to the output of the ffmpeg command to see which profile is being used. > Currently it only can decode it. x264 is only an encoder, not a decoder. ___ 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] Problem with pixel format and/or missing constant
Am 11.03.20 um 20:13 schrieb Carl Eugen Hoyos: To elaborate: The main differences are: Unified support for >8 bit Monochrome encoding XAVC encoding The first is really useful but only if you need 10 bit support, the others should have less relevance. x264 development has slowed down over time since the encoder already was the best-in-class. Thanks for your appraisal. So I think I can live with the 152 version. But maybe that's the reason for this Problem: https://forum.ubuntuusers.de/topic/video-ruckelt-mit-totem-nicht-aber-mit-vlc Is it thinkable that libx264 could encode with constrained_baseline profile some day? Currently it only can decode it. John's version is: [libx264 @ 0x769d500] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - http://www.videolan.org/x264.html -Ulf ___ 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] Problem with pixel format and/or missing constant
On Wed, Mar 11, 2020, at 10:51 AM, Ulf Zibis wrote: > > Does John van Sickle's binary use a current version? See the build info / readme for a list of external library versions: https://johnvansickle.com/ffmpeg/git-readme.txt > How can I use a more current version with the ffmpeg git version? You can compile it: https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu ___ 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 20:02 Uhr schrieb Carl Eugen Hoyos : > > Am Mi., 11. März 2020 um 19:52 Uhr schrieb Ulf Zibis : > > It seems I'm using a very old version of libx264: > > Why do you think so? To elaborate: The main differences are: Unified support for >8 bit Monochrome encoding XAVC encoding The first is really useful but only if you need 10 bit support, the others should have less relevance. x264 development has slowed down over time since the encoder already was the best-in-class. 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 19:52 Uhr schrieb Ulf Zibis : > $ sudo apt policy libx264* > libx264-148: >Installiert: (keine) >Installationskandidat: (keine) >Versionstabelle: > libx264-152: >Installiert: 2:0.152.2854+gite9a5903-2 >Installationskandidat: 2:0.152.2854+gite9a5903-2 >Versionstabelle: > *** 2:0.152.2854+gite9a5903-2 500 > 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 > Packages > 100 /var/lib/dpkg/status > libx264-dev: >Installiert: 2:0.152.2854+gite9a5903-2 >Installationskandidat: 2:0.152.2854+gite9a5903-2 >Versionstabelle: > *** 2:0.152.2854+gite9a5903-2 500 > 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 > Packages > 100 /var/lib/dpkg/status > It seems I'm using a very old version of libx264: Why do you think so? > https://packages.ubuntu.com/search?suite=default§ion=all&arch=any&keywords=libx264&searchon=names > > Does John van Sickle's binary use a current version? Most likely, the console output will tell you. > How can I use a more current version with the ffmpeg git version? Compile a static x264 and force FFmpeg to use, needs either pkg-config magic or --extra-cflags and --extra-ldflags. Why do you want to use a newer x264? 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] Problem with pixel format and/or missing constant
Am 11.03.20 um 18:55 schrieb Carl Eugen Hoyos: mov defaults to mpeg4 if no h264 encoder is present (you did not specify --enable-libx264), for mpeg4 "profile baseline" is not defined. Thanks, it works with: $ sudo apt install libx264-dev $ ./configure --enable-libx264 --enable-gpl $ make But this makes me thinking: $ sudo apt policy libx264* libx264-148: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libx264-152: Installiert: 2:0.152.2854+gite9a5903-2 Installationskandidat: 2:0.152.2854+gite9a5903-2 Versionstabelle: *** 2:0.152.2854+gite9a5903-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status libx264-dev: Installiert: 2:0.152.2854+gite9a5903-2 Installationskandidat: 2:0.152.2854+gite9a5903-2 Versionstabelle: *** 2:0.152.2854+gite9a5903-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status It seems I'm using a very old version of libx264: https://packages.ubuntu.com/search?suite=default§ion=all&arch=any&keywords=libx264&searchon=names Does John van Sickle's binary use a current version? How can I use a more current version with the ffmpeg git version? Please use a wider console window when running ffmpeg for us, Carl Eugen I'll try to remember this. Which width is ideal? -Ulf ___ 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] Problem with pixel format and/or missing constant
Am Mi., 11. März 2020 um 18:32 Uhr schrieb Ulf Zibis : > I have build ffmpeg from the latest sources and get this warning and error: > > $ ~/Projects/ffmpeg/dev_2/ffmpeg -i MVI_1324.MOV -c:a copy -profile:v > baseline -level 4.1 -map_metadata 0 -movflags +faststart MVI_1324.mov > ffmpeg version N-96935-g34d7c8d942 Copyright (c) 2000-2020 the FFmpeg > developers > built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) > configuration: mov defaults to mpeg4 if no h264 encoder is present (you did not specify --enable-libx264), for mpeg4 "profile baseline" is not defined. Please use a wider console window when running ffmpeg for us, 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] Problem with pixel format and/or missing constant
Hello, > I have build ffmpeg from the latest sources and get this warning and error: > > $ ~/Projects/ffmpeg/dev_2/ffmpeg -i MVI_1324.MOV -c:a copy -profile:v > baseline -level 4.1 -map_metadata 0 -movflags +faststart MVI_1324.mov ... > File 'MVI_1324.mov' already exists. Overwrite? [y/N] y > Stream mapping: > Stream #0:0 -> #0:0 (h264 (native) -> mpeg4 (native)) > Stream #0:1 -> #0:1 (copy) > Using the same command line with the binary from John van Sickle works fine: > > $ ~/Projects/ffmpeg/ffmpeg-git-20200211-amd64-static/ffmpeg -i > MVI_1324.MOV -c:a copy -profile:v baseline -level 4.1 -map_metadata 0 > -movflags +faststart MVI_1324.mov ... > File 'MVI_1324.mov' already exists. Overwrite? [y/N] y > Stream mapping: > Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264)) > Stream #0:1 -> #0:1 (copy) The static build you downloaded has libx264 to use for h264 as default encoder in mov files, but your build doesn’t seem to have anything other than the native encoders, so it chooses mpeg4 encoder, which apparently doesn’t take profile parameter. Regards, Ted Park ___ 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".
