🚀 go-pugleaf

Hey Ed.

Are you using source footage (video) in your project?
If so, have you interpreted it to separate fields (using the correct dominance setting)?

If you imported interlaced footage, and moved, scaled, or applied effects to it in your timeline without separating fields first, then you'll likely be seeing some reversed fields issues. For PAL, the frame size of your comp should be 720x576 @ 25fps. The PAR will vary depending on whether or not your making an anamorphic comp, or a standard comp.

Your PAL DV footage should most likely be Lower-field dominant (lower field first). You can re-introduce fields in the render queue as desired.

Go To Avid.com and type "Avid Codecs" in the search field >> Choose LE 1.10 Codecs >> read about field ordering beneath >> install

Ae >> interpret footage in Project Panel, fields set to none >> add to render queue >> choose avid codec in output module >> choose render settings and set appropiate field rendering on output.

FYI: <http://community.avid.com/forums/t/55996.aspx>

Thomas, Ed may need to interpret his footage & separate fields if he is transforming or effecting his footage in the timeline (if he's using any imported footage).

Thanks for all the suggestions. None have worked so far.

The AEX project is a mixture of progressive and interlaced footage, with one title which is bevelled and which moves. It needs to be exported into Avid as an interlaced DV movie.

I render the AEX movie in the usual way using "Comosition>Add to Render Queue".

When I add it to the render queue using normal DV AVI settings, it plays back fine in Adobe Premiere. However, the file appears low resolution (this is particularly obvious on the bevelled caption) when it plays back on the Avid timeline, and also there is clearly a problem with the field order.

I've tried exporting it to Avid in a Quicktime Movie using the Avid DV codec, both Lower and Upper field first and indeed "No Fields". No fields removes the field rendering problem but not the low resolution, and it's no good to me anyway as it's not progressive material. I also tried using the (memory hungry) Avid 1.1x codec - same result.

I have tried Thomas' suggestion of turning the fields off within the AEX project menu and it doesn't help.

Any other suggestions?

Hey Ed. Have you done the below?

For each piece of footage, you must interpret it correctly.
In the Project Window, select the footage item, and under the "File" menu, choose "Interpret footage". Interpret each item accordingly. If the source is 24fps footage, apply the pulldown removal cadence that is required. If it's interlaced, separate fields as appropriate.
When your done, add the comp to Render Queue. Render to the DV codec (your frame size should be 720x480 NTSC, and 720x576 PAL. The PAR will vary depending on your project, and version of AE (CS3/CS4).
Render to LFF.

Can you post OS type/version, AE version, source footage types, etc...?

I would seriously consider using porgressive Quicktime animation or
maybe even a PNG sequence. It never fails.

On Apr 2, 1:08 pm, Ed_Stradl...@adobeforums.com wrote:
> Thanks for all the suggestions. None have worked so far.
>
> The AEX project is a mixture of progressive and interlaced footage, with one title which is bevelled and which moves. It needs to be exported into Avid as an interlaced DV movie.
>
> I render the AEX movie in the usual way using "Comosition>Add to Render Queue".
>
> When I add it to the render queue using normal DV AVI settings, it plays back fine in Adobe Premiere. However, the file appears low resolution (this is particularly obvious on the bevelled caption) when it plays back on the Avid timeline, and also there is clearly a problem with the field order.
>
> I've tried exporting it to Avid in a Quicktime Movie using the Avid DV codec, both Lower and Upper field first and indeed "No Fields". No fields removes the field rendering problem but not the low resolution, and it's no good to me anyway as it's not progressive material. I also tried using the (memory hungry) Avid 1.1x codec - same result.
>
> I have tried Thomas' suggestion of turning the fields off within the AEX project menu and it doesn't help.
>
> Any other suggestions?