FxPlug SDK 1.0 was introduced together with Motion 2.0 in April, 2005. A few months later, version 1.0.2 was released with support for Universal Binary plug-ins but no API changes.
Version 1.1 of the FxPlug SDK was the first version that worked with Final Cut Pro 5.1.2 . Version 1.1 added a number of new features, including:
Transitions.
New FxBaseEffect parent protocol for filters, generators, and transitions.
String parameters.
A new -properties method that returns a dictionary describing plug-in attributes.
8-bit and floating-point YUV ('r408' and 'r4fl') bitmaps.
Rowbytes support in bitmaps.
SMPTE wipe equivalents for transitions.
A new FxHostCapabilities class for determining the capabilities of the host application.
Version 1.2 of the FxPlug SDK was released with Final Cut Pro 6.0 and Motion 3.0. The features in this version of the SDK are detailed below in the section “Features of FxPlug SDK 1.2.”
Version 1.2.1 of the FxPlug SDK was released with Final Cut Pro 6.0.1 and Motion 3.0.1. The features of this version of the SDK are described below in the section “Features of FxPlug SDK 1.2.1”
Version 1.2.2 of the FxPlug SDK was released with Final Cut Pro 6.0.2 and Motion 3.0.3. The features of this version of the SDK are described below in the section “Features of FxPlug SDK 1.2.2”
Version 1.2.3 of the FxPlug SDK provides minor bug fixes and documentation corrections.
In general, to make your plug-in work with any version of a host application, have the plug-in first check for availability of a host API for an SDK feature, and then only use that feature if the API is available. If a particular host API is not available, your plug-in needs to fall back to an alternative behavior.
Last updated: 2008-07-04