Known limitations of our plugins with Final Cut Pro 5.x and 6.x.

Our FxPlug versions of our software support all bit-depths that FCP supports, hoewver, all of our AE-compatible plugins only support 8 bits per channel processing within FCP.

Projects authored on PPC with our AE-compatible plugins, when opened from FCP on an Intel Mac, may cause FCP to not find the plugin, even when the plugin is properly installed. When opening an FCP project with one of our plugins authored on PPC Macs, opening the same project on an Intel Mac will cause FCP to ask "Can't find plugin, would you like to load it from somewhere else?". If you point FCP to the new plugin on Intel (after authoring on PPC) it will act as if you had not done pointed it the plugin and ask again. Your only choice is to say "no" (that is, don't search for the plugin somewhere on dis).

The workaround? Apply a fresh newly applied plugin instance. Copy the parameters from the plugin's settings as authored on PPC to the new instance of the plugin. Then you can safely delete the instance of the plugin that was applied on PPC.

This is a known bug within FCP and we have reported it to Apple.