• FCP 7 projects created with BCC7 will open correctly when running FCP 7 with BCC8.

• Due to complications arising from the new FxPlug2 API for 64bit Apple hosts, projects created in Motion 4 with BCC7 will display the BCC effects as missing/unknown when opened in Motion 5 with BCC8 and those effects will need to be re-created. Saving BCC presets in Motion 4 may provide a partial workaround for recreating the effects in Motion 5.

• Due to limitations in the FCP X host, it is not possible to bring forward FCP 7 projects with 3rd party filters intact in FCP X.

BCC FxPlug 8.0.0 - Known Issues and Limitations
:

• Currently in the public beta for Motion 5 and FCP X, contextual controls are completely disabled so parameters are not hidden/exposed depending on whether or not they are needed in a particular context. FCP X does not support contextually hiding/exposing parameters and they are left exposed in Motion 5 for the time being to facilitate easier creation of effect templates for FCP X.

• BCC8 includes a improvements to the Motion Tracker but when opening projects created with BCC7 in FCP 7 you will notice that the older Tracker UI is displayed instead of the newer Tracker UI. The tracker should still function normally for you although you may see tracker messages referring to parameters that are only available in the newer tracker UI. The newer tracker UI is available when applying new instances of effects (as opposed to effect instances that were present in previously saved BCC7 projects).

• When using the 3D Objects category of effects on Mac OS, enabling the "Transparent Object" checkbox will result in the object becoming fully transparent.

• Previewing/Rendering BCC Damaged TV in FCP 7, particularly on older graphics cards, can lead to low memory warnings. Increasing the memory available to the application may help work around this problem.

• In the new particle filters, particularly Particle Array 3D, particles with the same Z depth can sometimes exhibit clipping errors when Depth of Field is enabled.

• In BCC Particle Emitter 3D, changing the Blend Mode in the Spawn group can unexpectedly affect the main particle compositing.

• As part of the new Motion Tracker workflow, if you change the tracker search width, target width, color space, or accuracy after an initial tracking pass, you must now reset the tracker data with the reset button in the tracker banner before starting a second tracker pass. (This is not necessary if only change was to the tracker point picker location.)

• In Type on Text the Line Leading in the text entry preview window does not accurately match up with the leading in the rendered result and the leading may need to be adjusted to generate the desired final render.

• Due to fixes in random number generators, you may see differences between random patterns in saved BCC7 projects when opened in BCC8. The overall “look” will remain the same but the details of the patterns may be differently randomized.

• In Particle Emitter 3D, Organic Strands, Particle Array 3D, and Pin Art 3D when using the pre-installed Image Collection files to define the particle shape, particles with soft alpha boundaries will render with unexpectedly hard edges if you select 10-bit high precision rendering and Apple Pro Res codecs. As a temporarily workaround you can use a well layer to define the particle shape which renders the alpha channels with proper softness.

• You may notice a slight discontinuity in the Stage Light gradient when applied in SD resolutions. This issue is minimized in HD projects.

• Lens Flare 3D generates unexpected darkening in the alpha channel when applied to images with transparent regions. As a temporary workaround apply Lens Flare 3D directly to opaque clips which produces a correct final composite.

• The Beat Reactor audio graph becomes less accurate as the Frequency Resolution is increased to high values. As a temporary workaround use low values near the default setting of 32.

• The Beat Reactor propagation options generate unexpected results in Organic Strands. Use non-propagation modes which work as expected as a temporary workaround.

• Glyph fonts such as IMG Extreme or HolidayPi BT will sometimes render incorrectly or cause unexpected behavior in Extruded Text or Type On Text.

• Gaps in text characters in Extruded Text and Type on Text will sometimes jump between filled and unfilled states while animating with changing geometry such as text on a path or jittering text. Increasing the Polygon Count or adjusting the font or font size my provide a temporary workaround.