Animated text from AE looking bad in FCP 7

take2visualmedia

take2visualmedia

Well-known member
For the life of me I can't figure out why text looks good in AE but when rendered out looks bad in FCP. I have a Apple Pros Res LT sequence. AE file gets rendered out in Animation Codec then FCP renders to Pro Res LT. Looks bad.

File looks perfect played in quicktime. If I open a new sequence with nothing in it and allow FCP to set the sequence to the same settings as the rendered file...it looks good in FCP. But I can't get it to look good in the working sequence. I tried rendering to different codecs out of AE but same result.
 
take2visualmedia said:
For the life of me I can't figure out why text looks good in AE but when rendered out looks bad in FCP. I have a Apple Pros Res LT sequence. AE file gets rendered out in Animation Codec then FCP renders to Pro Res LT. Looks bad.

File looks perfect played in quicktime. If I open a new sequence with nothing in it and allow FCP to set the sequence to the same settings as the rendered file...it looks good in FCP. But I can't get it to look good in the working sequence. I tried rendering to different codecs out of AE but same result.
Click to expand...

So it looks ok in FCP, but only "looks bad" when you render out Prores LT ? What happens when you render out animation codec out of FCP ?

Can you be more specific? Text "looks good" and "looks bad" can mean 100's of different things

What is wrong? aliased edges? gamma ? macroblocking ?

Chroma subsampling of LT is 422, so color edges will look blocky compared to unsubsampled RGB in animation export from AE
 
The frame rate is 29.97 on both AE and FCP.

By looking "bad" I meant that the text had aliased edges.

It looks like I found a fix although I'd still like to know what happened. When rendering out of AE at Animation codec, the field order is correctly set to OFF. When I imported the file into FCP the field order was changed to UPPER in the project panel (even though the sequence is NONE for field order). I switched it to NONE and the text looked as it should. Question would be why did FCP read it as Upper Field if it was rendered with none in AE? At least I have a fix if it happens again. Thanks for all responses.
 
You must log in or register to reply here.
Back
Top