Support for v210/v410 input

[GoogleCodeExporter]

I have a silly question.

Why I can see some 10-bits colorspace (like v210) in the [Output Formats] on 
the decoder settings page?
In case, if I want to decode a v210 movie, what should I do?

Best regards,

Original issue reported on code.google.com by cabet...@gmail.com on 1 Feb 2012 at 4:11

[GoogleCodeExporter]

v210 input is not supported at this time.
Its technically not a codec, its just a special pixel format to store raw video.

Original comment by h.lepp...@gmail.com on 1 Feb 2012 at 11:13

[GoogleCodeExporter]

Original comment by h.lepp...@gmail.com on 1 Feb 2012 at 1:06

• Changed title: Support for v210/v410 input
• Changed state: Accepted
• Added labels: Component-DirectShow, Filter-Video, Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

LAV 0.46 will support v210 and v410 input, but it'll be off by default. You can 
activate it and then play such files.

Original comment by h.lepp...@gmail.com on 2 Feb 2012 at 3:57

• Changed state: Fixed

[GoogleCodeExporter]

I love LAV!
arigatou !!

If you support 2vuy in the future, it would be great.
2vuy pixel format is similar to v210. (it's only 8-bit)
http://developer.apple.com/quicktime/icefloe/dispatch019.html#2vuy

Original comment by cabet...@gmail.com on 3 Feb 2012 at 1:08

[GoogleCodeExporter]

2vuy is exactly the same as UYVY just with a different FourCC, leave it to 
Apple to re-invent a standard with a different name.

v210 is special, because ffmpeg actually implements it as a "decoder", which is 
why it was trivial to support. All other raw formats will either not be added 
or at a much later time - sorry.

Original comment by h.lepp...@gmail.com on 3 Feb 2012 at 9:14

[GoogleCodeExporter]

Ok, I've understood.
Thanks for supporting v210.

Original comment by cabet...@gmail.com on 3 Feb 2012 at 9:20