Quote:
Originally Posted by Katie Boundary
The original question remains: what are the algorithm details? Does DGIndex drop the 3rd field in a non-progressive frame and then every 5th field in a non-progressive frame afterward? Or what?
|
As I said in post #11 two weeks ago, when I tried force film on interlaced content it dropped every fifth frame. Why don't you try it?
If alternate fields consist of odd and even scan lines, and if you removed every fifth field and replaced it with the following one... effectively:
SeparateFields().SelectEvery(5,0,1,2,3).Weave()
wouldn't fields end up on the wrong scan lines?
A deinterlacer could probably still produce progressive frames if the section was interlaced and it could cope with the constant alternating between top field first and bottom field first, but "force film" is generally used under the assumption no deinterlacing is required.
Maybe I'm looking at it the wrong way but I'm not sure dropping fields makes sense.