Installation guide

Limitations and Known Issues
45
➤ Bug Number: UDEV00207851. You might not be able to render a FluidBlur,
FluidColorMap, or FluidMorph effect in an HD project if there is not enough memory
available.
Workaround: Try one of the following:
t In the Bins tab of the Project window, click the Clear button, and render the Fluid effect
(see “Managing Bins and Memory” in the Help).
t Close all unused bins, relaunch, and render the Fluid effect.
t In the Format tab of the Project window, switch the project format to an SD format,
render the Fluid effect, then switch back to HD.
➤ Bug Number: UDEV00221706. Very high speed Motion Effects with rates greater than
500% no longer play in real time; they now appear in the Timeline as a blue dot effect, and
must be rendered. Since any motion effect with a rate greater than 100% plays back
inefficiently, and the higher the rate the less efficiently it plays back, real time playback
efficiency will improve by rendering such motion effects.
➤ Bug Number: . (HDV) If a clip contains Timewarp effects, you should render the effects.
➤ Bug Number: . You might experience effects render issues with stacked effects.
Workaround: Render each individual track starting with the bottom track.
➤ Bug Number: UDEV00197962 . When you are working with AVX effects, performing an
Expert Render or a Render IN to OUT on a sequence that contains multiple third-party AVX
effects might lead to excessive memory consumption that could cause the application to
hang or to display errors.
Workaround: Render the effects in smaller groups.
➤ Bug Number: UDEV00214545. AVX 1.0 effects might have invalid color levels.
➤ Bug Number: UDEV00194693. You might see problems with superblacks in 16-bit mode.
➤ Bug Number: UDEV00189486. Performing an Add Edit on a promoted Advanced
Keyframe Picture-in-Picture effect might cause a “DataPointOneError.”
Workaround: Instead of first promoting to 3D, then Advanced Keyframe, promote in the
reverse order.