06.08.2022, 11:29
Quote: Wrote:Internally mkv always saves interlaced content separated by field (in the container structure) and the actual way the content is saved in the container does differ with the field-order selection on muxing. It's not just a tag.I'm still confused on this one. I get that it can be stored differently. That makes sense.
But FFmpeg is quite clearly just "going with the flow" and processing the file/outputting using the storage order from the source file, but then Hybrid is overwriting that when writing the tags because it doesn't know the original storage order. Otherwise, the output file would have actually changed storage order, right? The output file is still the original storage order just tagged wrong.
Can't Hybrid read the field order tag from the input file and then make a decision like "if input field order is is 1 or 9 && input/processing is bff, write field order tag as 9, else 1. If input field order is is 6 or 14 && input/processing is tff, write field order tag as 14, else 6"?
Quote:ARGH,... do !not! post links I send via PM (edited your post) or I will delete your account.
Sorry, figured dead links were permissible.
Is there no way to get older dev versions of Hybrid?
Quote:Personally I would bob the content and save it as progressive and not interlaced as more and more newer formats drop support for interlaced content altogether.
People were saying that way more than 12 years ago before QTGMC existed...yet algorithms seem to keep getting better!
(QTGMC just turned 12 a couple days ago apparently!)