Quote:
Originally Posted by poisondeathray
A) (vdfm 40716 x64 and x86) - Video => Decode format for pixel format isn't respected for 10bit 422
e.g
1) load a prores 10bit422 source
2) file => file information will say yuv422p10le using caching input driver (so far so good)
3) video => fast recompress will say using conversion yuv422p16-709 ; so you cannot encode yuv422p10le directly (e.g. you won't be able to export v210 or cineform 10bit422 without other conversions with normal or full recompress ). Video compression menu will also report yuv422p16-709 . This is unexpected because yuv422p10le should be direct from decode => encode . If you select video=> compression => uncompressed I would expect v210 out, but you dont get v210.
4) forcing video=>decode format to v210 doesn't "stick"
|
I do not implement formats exactly as in FFMpeg. yuv422p16 in VDFM is perfect match format for everything from yuv422p9le to yuv422p16le with one caveat: instead of locking bitdepth I keep it as a per-frame metadata. If you feed yuv422p10le in and take yuv422p10le out of the pipeline, there is no scaling applied to pixel values. Except when this is needed for some filter. It is also possible to see the YUV values in filter preview through color picker so you can make sure it looks like 10-bit data (crop filter is good to access this feature because crop itself does not change pixels).
yuv422p10le -> yuv422p16 -> yuv422p10le is as direct as possible, there is nothing to worry about in this conversion.
yuv422p10le to uncompressed as v210: if you mean it should be auto-selected/default I agree. Uncompressed output setup needs some improvement. But you can select "v210" manually.
> forcing video=>decode format to v210 doesn't "stick"
This menu only triggers something when the option actually exists in the decoder.
Same if you open png image and select v210 as decoding format: this is not supported.
v210 decoding is implemented by VFW codecs and also by CineForm sdk.