On Thu, 15 Jun 2017 18:17:37 +0530 Gyan <gyando...@gmail.com> wrote: > On Thu, Jun 15, 2017 at 4:44 PM, wm4 <nfx...@googlemail.com> wrote: > > > > Forcing the "High" or maybe "Main" profile is enough to ensure > > compatibility. > > > > Result of encoding a PNG sequence, forcing High profile, but without > -pix_fmt > > ----------------- > No pixel format specified, yuv444p for H.264 encoding chosen. > Use -pix_fmt yuv420p for compatibility with outdated media players. > x264 [error]: high profile doesn't support 4:4:4 > [libx264 @ 0000000002b02b40] Error setting profile high. > [libx264 @ 0000000002b02b40] Possible profiles: baseline main high high10 > high422 high444 > Error initializing output stream 0:0 -- Error while opening encoder for > output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, > width or height > Conversion failed! > -----------------
So that's fine and the message is not needed. Where is the problem? Other than ffmpeg not doing the obvious thing, and converting to yuv420p (no, the discussed message has absolutely nothing to do with this). I'm fairly sure this is the fault of the libavcodec encoding API having no format negotiation API, though. Didn't dig into it further. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
