BCC AE/Premiere Pro - 9.0.1 Release Notes

Tags: Continuum Complete

  • The FX Browser can now be applied to Precomps or Adjustment Layers in AE.
  • More than 100 new transition presets.
  • Built-in Vignette added to Pan and Zoom.
  • Motion Blur now supported for 3D Mode in Pan and Zoom.
  • Improved GPU support on ATI systems.
  • Help Docs refinements.
  • Colored Background option added to Swish Pan.

Bug Fixes In BCC AE 9.0.1:

  • Warp - Antialiasing not working.
  • Vector Blur Dissolve - Ignore Edge Pixels not working as expected.
  • Edge Grunge - Layer Border options not working as expected.
  • Film Damage - Error messages when applied to time remapped clips in Premiere.
  • Vector Blur Dissolve - Streaks visible on video that has alpha transparency.
  • Revise parameter defaults for several transitions.
  • Sporadic instability when loading animated presets in the FX Browser.
  • FX Browser - sporadic instability in Mac AE when closing the browser or switching from AE to other apps and then back again while the browser is open.
  • Extruded Text - Hitting Apply in the text edit window causes other apps to jump in front of AE.
  • Extruded Text - Refresh issue when launching the text window with fragments of the window bar being drawn in the wrong place and then not refreshing.
  • Cuda driver errors are displayed on some ATI systems which had previously installed NVIDIA cards.
  • FX Browser - Saving Workspace does not allow overwriting of an existing one.
  • FX Browser - Workspaces save number does not automatically advance beyond 2 on windows.
  • FX Browser - Open folders are not always saved and restored.
  • 3D Objects filters will incorrectly cache the first layer assigned as texture/bump map, even if that layer has been deleted and another assigned.
  • Sporadic instability with 3D Objects filters on windows, especially in Premiere on Windows 8.
  • Laser Beam - Motion Blur does not work in Premiere.
  • Damaged TV - Triangle and Saw edge shapes don’t animate.
  • Grunge - 4K displacement map doesn’t work when 4K media is selected as the layer.
  • Grunge - With 'use texture' turned off, displacement map uses source layer as map even when map is set to texture.
  • Grunge - Glow in 4K media gets bigger when dropping resolution.
  • Lens Flare 3D - Instability in AE when applying to alpha media and selecting images smaller than comp sized as background.
  • Grunge - Opacity parameter incorrectly adjusting scratches.
  • Vignette - When dropping resolution to third or quarter, the blur shifts unexpectedly.
  • Damaged TV Dissolve - Interference shows random gaps in interference on side edge of screen.
  • Preset library - Remove outdated presets in some filters which distract from browsing the more important entries.
  • Several Jitter presets contain incorrect default Y offsets.
  • Sphere Transition - Uses wrong folder for default preset location.

BCC AE 9.0.1 - Known Issues and Limitations:

  •  29745 - Grunge can render with missing textures on Radeon cards in 8 or 16 bit color depth on Windows when using driver versions prior to 14.x. The filter will work in 32 bit float color depth (in hosts that offer 32-bit color) even with older drivers.
  • 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:
  1. Justification (when Word Wrap is not enabled)
  2. Top Down Text
  3. Right to Left Reading
  4. Negative Line Leading
  5. Italics (for fonts that don't include an italic typeface)
  6. 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 work 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 an 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.
  • 29533 - The apply modes Boost Expo 1, 2, and 50/50 mix do not give the expected result in Grunge.
  • 29502 - In Grunge the Spot Light Cone Feather doesn’t follow the cone size
  • 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
  • 28552 - LED - For certain Size settings a thin black strip of missing LED elements can appear along the top and right edges of the image.
  • 30205 - Grunge and Lens Flare 3D - The Scale Random feature does not work in the Orbs groups.
  • 29395 - FX Browser - on Macintosh systems with Retina displays the tabs in the preset browser do not respond correctly to mouse click+drag events.
  • 29974 - FX Browser - The Animation timing is inaccurate when previewing presets with animated point pickers in the FX Browser.

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.
  • 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.


Join our email newsletter and keep up to date