Re: Separate Fields: Off by Kevin Camp on Nov 19, 2008 at 4:33:15 pm
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.
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:
Re: Separate Fields: Off by Dave LaRonde on Nov 19, 2008 at 4:58:38 pm
[James Orlowski]"...is there a way to mass-change all clips in your bin to 'Separate Fields: Off'?"
I think this is by far the safest way to go about doing what you want to do.
Highlight the first clip and go File>Interpret>Main. Change clip interpretation as necessary. Then go File>Interpret>Remember Interpretation.
Highlight the rest of the clips and go File>Interpret>Apply Interpretation. You're done.
Changing the text document that stores the interpretation rules can be fraught with peril. If you attempt it, be sure to save a copy of the document BEFORE you start futzing with it.
Dave LaRonde
Sr. Promotion Producer
KCRG-TV (ABC) Cedar Rapids, IA
Re: Separate Fields: Off by James Orlowski on Nov 19, 2008 at 5:11:04 pm
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.
www.rynoproduction.com
800-860-7966
Re: Separate Fields: Off by Dave LaRonde on Nov 19, 2008 at 5:59:27 pm
[James Orlowski]"(But I'd still like to have AE default to Separate Fields: Off.)"
If you work with interlaced footage in AE without separating the fields in the proper order, animate the footage's scale or position properties, you will have an ungodly mess on your hands. It doesn't matter if you render as complete frames or interlaced, it will still look like a certain highly-viscous, vile-smelling brown substance.
If you DO separate fields properly and then render with NO fields, you'll lose half the vertical resolution of your footage. It's not the end of the world, but you can certainly see the difference.
Face it: if you want progressive scan footage, you have three options in AE:
1) Invest in a pricey thrid-party deinterlacing plugin
2) Get a camera that shoots progressive scan
3) Endure lousy-looking video
Dave LaRonde
Sr. Promotion Producer
KCRG-TV (ABC) Cedar Rapids, IA
Re: Separate Fields: Off by James Orlowski on Nov 19, 2008 at 6:11:53 pm
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.
www.rynoproduction.com
800-860-7966
Re: Separate Fields: Off by Kevin Camp on Nov 19, 2008 at 6:23:16 pm
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.
