[Paul Jay]

If you want real help. Give more info.

Mac, FCP version, type of footage, type of sequence.

[Paul Jay]

Trash your preferences
https://www.digitalrebellion.com/prefman/
If that doesn’t work, Reinstall
https://www.digitalrebellion.com/fcsremover/

[Paul Jay]

This is indeed a bug in the latest Final Cut Pro update.
The issue is not with progressive footage.
If you deinterlace the footage the problem is gone.

Not that it’s a solution to the problem but It’s definately a 7.03 bug.
Maybee if we scream loud enough Åpple will hear us.

[Paul Jay]

Get out of the H264 codec. Even in Premiere.
Convert to something more editable.
H264 will get back at you sooner or later.

[Paul Jay]

Frame rate conversions in combination with H264 on the Best settings may be your problem.
Have you chosen BEST settings for all?

Try to go from ProRes to ProRes with just the frame rate conversion.
Also test these kind of custom templates first with small 20 sec clips.

And ofcourse the previous tips.
Send to Compressor is terrible and clustering on multicore machines is great.

[Paul Jay]

Great! Please mark as solution for future viewers!

[Paul Jay]

The most important thing is:

How is your 7D footage shot?

24 or 25?

Did you match your timeline the first shot you put in the timeline?

First check your source footage.
Select clip in browser.
Command+9

[Paul Jay]

Change your compressor in Sequence settings to Animation codec.
Looks supersharp here compared to ProRes.

But then you will have to stay in Animation codec on output.

What is your delivery format?

[Paul Jay]

a 64 bit FCP will be able to use both MacBook Pro cores. You will be fine.

[Paul Jay]

Why do you have to render?
Using Filters/FX on the XDCAM HD footage?

XDCAM is long gop codec.

If you use a lots of effects and filters with this footage.
Go ProRes from start. It wil save you a LOT of time.

Next to the fact that current FCP is NOT 64 bit ofcourse.
But i heard the next version is gonna be awesome:P