BCC AE/Premiere Pro - 9.0.0 Release Notes

Boris Continuum Complete AE 9.0.0 was released on 4/7/2014.

Registration:
Make sure to register your product in order to receive the latest technical and upgrade information.

BCC AE 9 supports the following host applications:

Mac OSX 10.7, 10.8, and 10.9:

• Adobe After Effects and Premiere Pro CS5, CS5.5, CS6, and CC

Windows 7 64, Windows 8 64:

• Adobe After Effects and Premiere Pro CS5, CS5.5, CS6, and CC

What's New in BCC AE 9 (Summary of major changes since BCC 8):

•  FX Browser™ - our best-in-class new graphical preset browser. Preview your preset library over moving host video, not just static frames, with two different workflows. The Integrated FX Browser™ is available inside every effect and allows intuitive preview of all presets for that effect. The Standalone FX Browser™ is applied as a separate standalone effect and allows browsing presets from EVERY effect in the full BCC library.
• 10 new effects and 25 new transitions for a total of 35 new filters:

Effects:

Transitions:

• Support for 3D moves and built in cropping in Pan and Zoom
• Native Premiere Transitions - true NLE-style versions of all BCC transitions are now available in Premiere CC
• Animation Tuning heads up display overlays in all transitions for intuitive tweaking of transition timing directly in your Composition/Preview pane.
• New HTML-based help system offering richer and more dynamic learning guides.
• Improved 4K rendering support in OpenGL accelerated filters.
• GPU acceleration of important filters such as Film Glow and Film Process.
• Simpler and cleaner UI for enabling/disabling the on-screen Heads Up Display widgets via the new H.U.D. button in the redesigned preset banner.
• Major performance improvements in some OpenGL filters such as Damanged TV, Scanlines, and Glint.
• New Gradient feature in many BCC Wipe transitions.
• Film Damage Flicker Bias allows controlling the direction of the brightness flickering - always brighter, always darker, or centered.
• Numerous bug fixes.

BCC AE 9.x Compatibility Notes :

While in general your previously saved projects should render identically in the newer version, bug fixes and quality improvements can sometimes change the look of older projects. While every effort is made to ensure project compatibility, the following notable areas may see some change to the look of previously saved projects.

• In all wipe-style transitions which contain Border options, the opacity of the border elements fades automatically at the start/end of transitions (except in manual mode) to fix potential jumps in the renders at the start and end of the transitions even when border offsets were non-zero.
• The largely unnecessary Hold In / Hold Out parameters were removed from the Animation Tuning group in all transitions which could cause changes in the transition timing in the unlikely event these parameters had been changed from their defaults.
• As part of the major performance optimizations implemented in Damaged TV for BCC9, some details can such as the randomization patterns can render differently although the overall feel of the effect should remain the same.
• BCC9 fixes a bug introduced in BCC8.2 that affected the perceived rate of progress of the underlying dissolve in BCC Lens Transition. Projects saved in BCC8.2 or 8.3 maybe appear to render somewhat differently now that the dissolve rate has been fixed.
• BCC9 fixes a gamma shift in some externally loaded images on Mac systems (such as those loaded by Pan and Zoom, or the particle files in Particle Emitter 3D, Organics Strands, or Particle Array) which caused the images to appear slightly too dark as compared to the same image when imported on Windows. These images now render identically on Mac and Windows but Mac projects saved with these filters prior to BCC9 may display slight brightness boosts in such images.

BCC AE 9.0.0 - Known Issues and Limitations :

• 27855 - Rendering errors can occasionally occur when using Adobe Media Encoder to render filters that rely on OpenGL acceleration such as 3D Objects filters, or the new particle filters. Rendering directly from within the original host should alleviate these errors.
• 28732 - BCC Extruded Text and BCC Type On Text use a custom text entry window and some of the changes that can be made through in this window are not reflected in the preview within the text window on Mac OS (although they will be apparent in the effect when previewed/rendered back in the host). The following text attributes do not preview within the text window:
• Justification (when Word Wrap is not enabled)

1.    Top Down Text
2.    Right to Left Reading
3.    Negative Line Leading
4.    Italics (for fonts that don't include an italic typeface)
5.    Superscript and Subscript

• 27362 - Filters in the 3D Objects category can show clipping or shifting when applied to layers larger than HD, and if such clipping is observed it may be necessary to apply the effects to HD or smaller sized clips.
• 23630 - In BCC Particle Emitter 3D the interaction layer does not working accurately with 3D Text layers in AE unless they are precomposed at comp dimensions.
• 26068 - In BCC Particle Emitter 3D, changing the Blend Mode in the Spawn group can unexpectedly affect the main particle compositing.
• 27591 - 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 extra step is not necessary if the tracker point picker location has changed.)
• 25867 - In BCC 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.
• 28724 - Importing Premiere Pro projects containing BCC effects directly into After Effects can lead to effects with some incorrectly transferred parameters which can lead to incorrect renders or other unexpected behavior. This project import workflow is currently not recommended for BCC filters. Please contact Boris technical support if represents and important desired workflow.
• 27313 - The Beat Reactor propagation options generate unexpected results in Organic Strands. Use non-propagation modes which work as expected as a temporary workaround.
• 28590 - Optical Stabilizer does not currently analyze correctly when applied to precomps in AE. As a temporary workaround it should be applied directly to individual clip elements instead of to precomps.
• 26750 - The Beat Reactor audio graph becomes less accurate as the Frequency Resolution is increased to high values. Use lower values near the default setting of 32 as a workaround.
• 28774 - When using a video track to define a texture in the 3D Objects filters, the scaling of that texture can vary incorrectly when changing resolutions so effects that use layers as textures should be set up in full resolution.
• 29832 - Antialiasing options are not working as expected in Warp.
• 29504 - Lens Flare 3D can fail to render when selecting a layer smaller than the source layer to be the background layer.
• 30043 - Triangle and Saw edge shapes don’t animate properly in Damaged TV
• 28741 - The FX Browser does not currently work when applied to Precomps or Adjustment layers in AE although this will be fixed in the very near future.
• 30130 - Hitting Apply in the text edit window in Extruded Text and Type On Text can cause other apps to jump in front of AE in the UI.
• 30144 - Some ATI systems will render incorrect error message concerning Cuda drivers when using Fast Film Glow, Fast Film Glow Dissolve, or Fast Film Process.
• 29745 - With the Radeon HD 5450 Card on Windows 8, Grunge textures render as black in 8 & 16bit (but not 32bit).
• 29533 - The apply modes Boost Expo 1, 2, and 50/50 mix do not give the expected result in Grunge.
• 30151 - In 4K projects with Grunge the displacement map doesn’t work when 4K host media is selected as the displacement map.
• 30148 - In Grunge with "Use Texture" turned off, displacement map and erosion map uses source layer as map even when map is set to texture.
• 29502 - In Grunge the Spot Light Cone Feather doesn’t follow the cone size
• 29994 - In Grunge the Opacity parameter in the scratches group does not function correctly.
• 29841 - In Grunge when using the Chromatic Aberration feature, white pixels render over blur region when the Vignette feature is also enabled.
• 29777 - In Grunge the Edge Offset control in the Chromatic Aberration group is not working as designed.
• 29758 - (Mac Only) In Grunge the noise does not animate smoothly and can yield unexpected repeating patterns at some settings on mac

Known issues that are specific to Premiere Pro:

• 29030 - When rending in Premiere to a final resolution that is lower than the projects main resolution, the Premiere host will render effects are lower resolution internally which can cause some effects to generate significantly different results than if rendered and full resolution and resized afterwards. Some filters that are highly resolution dependent such as BCC Match Grain will even render error messages when used at less than full resolution. To ensure renders internally at full resolution and then resizes as a secondary step you can enabled Premiere's "maximum render quality" option.
• 23498 - Versions of Premiere Pro prior to CS6 have problems getting the correct frame with filters that access layers at alternate times when applied to trimmed clips. Adobe resolved this issue in Premiere Pro CS6 but in prior versions of Premiere Pro you may need to export trimmed sections and reimport them as untrimmed in order for time based features such as Optical Stabilizer, Motion Key, or the Motion Tracker to work properly.
• 26212 - In Premiere Pro CS5.5. and earlier, enabling the Use Individual Layers control in BCC Pin Art will generate a rendered error message.
• 26994 - Currently the only way to select from the list of installed image shapes in the new particle filters on Windows Premiere Pro is to use the prev/next arrow keys to step through the list which is inconvenient due to the length of the list. Using a host layer to define a particle shape can serve as a workaround.
• 29111 - Preset banner popup menus do not work in Premiere Pro on Windows. Presets must be loaded with the Load (L) button instead.
• 28423 - Stacking multiple 3D Objects filters on a single clip can lead to performance degradation or psuedo-hanging. It is recommended that for the time being 3D Objects filters be applied to separate tracks or separate clips in Premiere Pro.
• 28714 - The Beat Reactor does not properly recognize audio levels in AIF files exported from Premiere that use 32bit non-float formatting. As a temporary workaround use 8 bit, 16 bit, or 32bit float formatting for exporting AIF files from Premiere for use in the Beat Reactor.
• 27000 - BCC frequently enables/disables individual parameters within the effect control pane to help make clear which parameters are relevant in a particular configuration. Premiere CS6 and earlier have a host problem where they sometimes fail to fully enable or fully disable parameters in response to other parameter changes. This can at times make parameters appear unavailable when they should in fact be editable. Newer versions of Adobe Premiere do not show this problem, but for older versions you can usually force the UI to refresh correctly by twirling an effect group closed and then back open again.
• 30087 - Motion Blur is not working as expected in Laser Beam when running under Premiere.
• 30051 - Film Damage and Trails can generate BFX memory errors when applied to time remapped clips in Premiere.
• 30143 - Even when parked on a single frame in Premiere, the Video Scope log file can generate entries for multiple frame when a render refreshes e.g. due to changing a parameter. This is caused by Premiere's predictive background rendering scheme where it automatically renders many frames ahead in the timeline. The Video Scope log file entry for the current frame should be the first entry in the list if you clear the log file prior to forcing a render refresh.