(20.08.2020, 20:03)Selur Wrote: Okay, that makes no sense to me.
If your source is interlaced and deinterlace is set to auto, Hybrid should deinterlaced and produce progressive output which should then work fine if the selected DNxHD profile support progressive content.
If this fails then it's a bug.
Cu Selur
It is a bug indeed.
The only way the encode starts without error is overwriting the input scan order to progressive, but then the source obviously is not deinterlaced despite the deinterlace is set to auto.