On 19 July 2015 at 15:13, Carl Eugen Hoyos <ceho...@ag.or.at> wrote:
> Chris Spencer <spencercw <at> gmail.com> writes:
>
>> + This option is deprecated, use
>> + <at> option{pixel_format=yuv422p10} instead.
>
> I just remembered this mail:
> http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/190657
>
> v4l2 has an option input_format that accepts both
> (for decklink) "v210" and "uyvy422" as strings
> and the option has an alias "pixel_format". If
> nobody (including you) has a better suggestion,
> please copy this behaviour, because using the
> pix_fmt alias for v210 is not very intuitive and
> does not work well for mjpeg.
I'm not sure where that user was seeing MJPEG; I can't find any
reference to it in the SDK. Here is the full list of available pixel
formats:
bmdFormat8BitYUV
This is the default and maps to the uyvy422 pixel format in ffmpeg.
bmdFormat10BitYUV
This is currently controlled by bm_v210 and uses the v210 codec.
bmdFormat8BitARGB
bmdFormat8BitBGRA
This patch adds these pixel formats.
bmdFormat10BitRGB ('r210')
bmdFormat12BitRGB ('R12B')
bmdFormat12BitRGBLE ('R12L')
bmdFormat10BitRGBXLE ('R10l')
bmdFormat10BitRGBX ('R10b')
I guess the first one can be handled by the r210 codec, but I'm not
sure how to deal with the others.
I worry that input_format might create some confusion with the
unrelated list_formats option which deals with resolution and frame
rate, and should probably have been called 'list_modes' IMO.
Chris
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
