19.04.2022, 08:33
(19.04.2022, 07:27)Selur Wrote: Problem is probably that FFV1 does not specifically support interlaced content, iirc. FFV1 can save interlaced content while maintaining the interlaced structure, but everything is flagged as progressive.
-> I'll look into skipping that check for ffv1 after work today.
Side note: "disable de-interlacing" is probably the wrong approach, normally one would overwrite the scan type.
Cu Selur
Thanks for the fast reply as always! Sounds good. I wouldn't have an issue if there is a "support interlace on unsupported formats" checkbox or setting if that would be a good compromise.
Interesting to note FFV1 doesn't have interlaced content in it's specs. I've been using it with Hybrid for (literally) years with no issues playing back on programs like MPC-HC. Do you believe it's a bad format to use for lossless archival of interlaced content?
Also, thanks for the note regarding "disable de-interlacing." I figured I should disable it and let it follow the scan order defined in the input file. Is it better to define the scan order for a reason other than to ensure an input file with a bad header wouldn't be considered progressive?