This content has been marked as final. Show 4 replies
Describe what the corruption looks like, please. Or you could post a link to a screenshot of what you are seeing.
> Makes "Frame Hold" essentially useless
Yep. I know. I filed a bug report on this back when CS3 came out. The image is being deinterlaced without your permission, right? :)
Indeed, it does look like a deinterlacer (that doesn't really work) is being applied to the held frame. Certain diagonal edges become jagged. I was wondering if that was it, even though the project is progressive and all the footage is progressive.
Thanks for the quick response Dan! Very helpful.
> even though the project is progressive and all the footage is progressive
But this is really only the tip of the iceberg.
The project settings apparently do not matter. The problem is that Premiere makes some very silly assumptions (with no way to override them) about which sources are interlaced and which are progressive.
Along with frame holds, there are also issues with (certain?) effects and choosing TFF/BFF/progressive in the export dialog options. Here are some examples:
In a 720x480 interlaced project, applying effects to a video clip and then choosing a progressive output format will deinterlace your footage -- whether "deinterlace footage" is checked or not, and regardless of whether your footage was progressive to begin with.
In a 720x480 progressive project, applying effects to a video clip will cause instant deinterlacing: with no regard to output settings or whether the clip is progressive.
More things I've posted about this here ... #1 ... #2 ... # 3 ...and on the Matrox forums.