Workflow AE & FCP HD 1920×1280

[Jasper Russell]

SOLVED!

You need to change the item properties in the browser from “upper” to “none”, as well as have your timeline settings set to “none”.
Sounds obvious…. you bet… I’ve tried it a hundred times and it didn’t work – BUT GET THIS – it won’t update your clip already in the timeline, so it appears not to work. You have to delete that clip and drag it down again once changed from the browser.

hope this helps someone out there it’s been killing me.

[Lissette Santos]

This fix definitely works. I had the same issue, but I’m not sure if it is a FCP bug. All the progressive quicktime files I rendered in AE (tried all codecs: Animation, ProRes, etc) show up in VIDEOSPEC as UNDEFINED in the INTERLACING field and look bad jagged in a FCP progressive timeline.
Then I inspected other progressive footage made in other apps and they clearly show up as PROGRESSIVE in the INTERLACING field. These files show up fine in FCP in a progressive timeline.

I don’t want to point fingers but there might be something weird going on with AFTEREFFECTS rendering program. Even footage de-interlaced in Adobe media encoder shows up clearly as PROGRESSIVE in VIDEOSPEC, then why is AE rendered footage showing up as UNDEFINED in the Interlacing field?

[Chip Swetnam]

I know it’s been a while since your post but THANK YOU! This was driving me crazy because there was no logical reason for it to be happening. I rendered with no fields in AE but FCP always showed the clip as “lower”. I just wish I had read the post before spending hours re-rendering and smashing my head on my desk.

[José miguel Biscaya]

hello there,
to confirm,
just ran into the same problem:
exported from AE in 1920x1080p 25 using animation qt codec with fields off.
fcp handels it as upper fields.
maybe some metadata issue?

i came up with the same solution but i thought i’d check the internet to see if somebody was having the same issue.
glad to find this thread. it was driving me mad.

thanks

[Kelly Richardson]

Exact same issue. Certainly a fault of some description but Jasper’s solution worked a treat. Unfortunately I’ve noticed this too late and exported a previous project in interlaced format despite being progressive and deleted the original as the Master included audio added by FCP. I’m a little (very) angry I didn’t notice the issue before and instead, trusted FCP to match the format on import into the sequence.