Separate Fields: Off

[Kevin Camp]

you must be using file type that is normally interlaced, so ae by default is set to separate fields (.dv files, for instance will do this). you can edit a file that tells ae how to automatically interpret different file types.

this page, from the manual describes how to edit the file:
https://livedocs.adobe.com/en_US/AfterEffects/8.0/help.html?content=WS3878526689cb91655866c1103906c6dea-7f82.html

the section you want is at the bottom under ‘edit interpretation rules…’

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[James Orlowski]

Thanks. Found the file, and I think I found the line(s) I’d need to change, but I’m unclear what to change them to.

The “key” at the top of the text file doesn’t do a very good job explaining, and I took programming in college.

I think this is the area I’d need to make a modification:

—
# NTSC rules
720, 480, 29.97, *, * ~ 648/720, L, *, *, *, *
720, 480, *, *, * ~ 648/720, *, *, *, *, *
720, 486, *, *, * ~ 648/720, *, *, *, *, *
720, 480, *, *, “dvc ” ~ *, *, *, *, “r6nf”, *
720, 486, *, *, “v210” ~ *, *, *, *, “r6nf”, *
720, 486, *, *, “UYVY” ~ *, *, *, *, “r6nf”, *
720, 486, *, *, “2vuy” ~ *, *, *, *, “r6nf”, *
720, 480, *, *, “dv5n” ~ *, *, *, *, “r6nf”, *
—

The ‘L’ on the first line represents lower field first, but if I change it to an ‘F’ (for “Frame,” which I assume is the same as “Off”), it either doesn’t work or I get a syntax error when I launce AE3.

Specifically, I think the line I need to change is this one:

—
720, 486, *, *, “2vuy” ~ *, *, *, *, “r6nf”, *
—

If I change the first ‘~ *’ after “2vuy” to a “= F”, I get the syntax error.

This really should be an easily-changable setting in the preferences panel.

—
James Orlowski
RYNO Production, Inc.
http://www.rynoproduction.com
800-860-7966

[James Orlowski]

Great! That worked perfectly. I never would have found that workaround on my own.

I did make a backup of that .txt file (I have two for some reason, once called ‘interpretation rules.txt’ and one called ‘interpretation rules 802.txt’), and I will restore it to factory settings now.

(But I’d still like to have AE default to Separate Fields: Off.)

—
James Orlowski
RYNO Production, Inc.
http://www.rynoproduction.com
800-860-7966

[Kevin Camp]

[James Orlowski]
“720, 486, *, *, “2vuy” ~ *, *, *, *, “r6nf”, *
—
If I change the first ‘~ *’ after “2vuy” to a “= F”, I get the syntax error. “

rather than = F try just a plain oldF or ~ F (soft rule). so the line would be like this:

720, 486, *, *, “2vuy” ~ F, *, *, *, “r6nf”, *

and yes, i think the file handling should also be accessed within the preferences, and should have a reset button in case things really get messed up.

dave’s method is quite effective though, and if this is not something you do every day, then it may be a better way to go…

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[James Orlowski]

Thanks for the information. This whole lower fields, upper fields, no fields thing does make my head spin, but this is what I found out works for me:

If I leave the footage as “separate Fields: Lower” in the project, the video looks “stepped” on my SDI output monitor (I use an AJA Xena HS card for capture/output BetaCam SP footage).

If I change that same footage to “none,” it looks perfect.

I then render my output to an uncompressed AJA Quicktime file with lower fields first–especially if there is a lot of horizontal motion.

But if I want a more “film” motion look with over-exaggerated motion blurs, I render my output with full frames.

This workflow method may not be “correct,” but it appears to work well in my projects.

—
James Orlowski
RYNO Production, Inc.
http://www.rynoproduction.com
800-860-7966

[Kevin Camp]

if you are working with progressive footage (and by your description it sounds like you are), then you are correct to want to change the settings to off for separate fields… if you work with interlaced footage this way, then, as dave says, you may end up with a big mess on your hands.

i actually have the reverse issue with my decklink card… anything i capture ae interprets as progressive, yet i’m almost always capturing from interlaced sources… so i’d rather have those files interpreted separating fields.

hacking the rules file should ultimately work for you if you are changing the rule for the correct file/codec code.

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW

[Kevin Camp]

also, the 802 version is the file your want to hack, it was created with the 8.02 update (i’m not sure why…)

fyi, here is the code i added for any blackmagic uncompressed YUV 10 bit footage taht gets imported to ae:

# Blackmagic Decklink Uncompressed YUV 10 bit is lower-field
720, 486, 29.97, “MOoV”, “v210” = 648/720, L, *, *, *, *

the ‘moov’ is the file type (.mov) and the ‘v210’ is the codec code from ae for bm uncompressed 10bit. the 648/720 is just the .9 pixel aspect ratio.

Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW