[David Bogie]

THE Todd Gipstein?
From ye olde 35mm Multi Image days?
The master of the 20 second dissolve?

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Try a different format. While they should work fine, there’s no reason to sue PNG instead of pdf or psd or jpeg.
But there’s no mechanism that would cause FCP to be placing these white thingies into your pingy thingy.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

They will install by themselves, usually. Or they will come with installation instructions.
Try the FCP Plugins folder. But there are many of those folders. Look for them in the Library. Once they’re installed, they will appear in the effects menus the next time you start up the application.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Yep, that’s odd, but you’re still using a different playback system than the one on which you recorded.

I was generalizing, that’s usually the problem but now that you’ve provided more information, could be anything, including stretched tape, I suppose.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

There are no issues in working with the two applications but you must conform your AE renders to your project’s format. You could be seeing improperly set field order out of AE. Render a test of a shorter clip that contains some side-side motion and reverse the field dominance.

What codec are you using to render out of AE?

If the AE clip plays properly in QT at full rez, you’ve likely got a problem with your rendering settings inside FCP.

Keep trying, post back with results, and be sure to read the section of the manual that explains inter-application round trips.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

We see this with certain cameras like the lower end Canons, Eluras and such.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

First thing to try:
Disconnect all network. This means Firewire, USB and ethernet.
Compressor “looks for network engines” according to some wonks. All buses are considered network ports.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

It’s a complicated issue, far too many possible explanations and cures to list here.
Hit apple.com
and search for your terms. You are going to disappointed that there isn’t a magic bullet but you should eventually find an answer among the dozens of threads.

https://discussions.info.apple.com/webx?14@178.RxF3aPn5AlN.496586@compressor

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Sorry, first time I’ve ever heard of that particular error. Give us LOTS MORE detail.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

The Macintosh/Apple rumor sites have more or less agreed that any new hardware will be announced closer to MacWorld Expo in July. I’ve been informed that certain G5 models are no longer being restocked at CompUSA implying new machines are on the way. Meaningless speculation, however as Apple tends to announce new hardware when it’s available to ship and trade shows have little or know relationship to Apple’s shipping schedules. Last year IIRC the G5 speedbumps were announced a few weeks after NAB simply because they weren’t ready to ship in time to announce at NAB.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”