Why is AE making text from a .mov jaggedy?

[Kevin Camp]

my best guess is that you’re working with a frame size and frame rate that is commonly interlaced, but you are working with it as progressive and you are exporting/rendering to a codec that does not contain the data on whether the footage is progressive or interlaced and ae is taking a guess… and guessing wrong.

you can override ae’s guess by selecting the footage in the project window and chooseing file>interpret footage>main and setting the ‘separate fields’ option to ‘none’.

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[Danny Mulen]

You’re absolutely right, that fixed it. Thanks!

How can I export from Premiere next time to avoid this issue? I was selecting Quicktime from Premiere with the Apple ProRes LT codec.

[Ben G unguren]

AE has default rules for interpretation of imported files. I believe one of those rules is that if footage comes in at 29.97fps, 720×480 pixels (for instance), it will assume the footage originated as DV, and thus has fields, lower-field first. There are a number of these interpretation rules.

There is a file called “interpretation rules.txt” — I can’t remember off hand where it is located. Either with your app, or with your preference files. You can alter this to your heart’s delight! (But make a copy first…..)

Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.com

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.