Start a new topic

Known Issues for Music Panner 1.0

 This release has some known issues, for which we provide workarounds, comments, and solutions.

We are working to resolve these issues in upcoming releases.

•If a Dolby Atmos Music Panner drop-down menu is open and the plug-in window is moved, the

drop-down menu remains in its original onscreen location. To avoid this, do not move the plug-in

window until you have closed the menu. [EUROPA-651]

• The curve elevation shape displays in automation as Ceiling. Throughout this guide, the elevation

shape is described as curve. [EUROPA-753]

• The bypass button for the Dolby Atmos Music Panner does not stop plug-in metadata from being

sent to the Renderer. The metadata continues to be sent to the Renderer. [EUROPA-240]

• Duplicating a track that has a panner with an object assignment breaks the metadata connection

in the original panner. To fix this, give the duplicated panner a new object assignment. Then,

navigate to the original panner, set the object assignment to None, and set it back to the desired

object assignment. [EUROPA-669]

• When you assign a panner to an available input channel that was assigned an object in the

Renderer, the object in the panner can display as inactive (gray) instead of active (blue).


• In Ableton Live, when importing 16- or 32-bit files, the panner UI can become unresponsive while

the application calculates the waveform overviews and analyzes the incoming audio files. As a

workaround, save the project after all of the 32-bit tracks have been analyzed, and then relaunch

the project. [EUROPA-736]

• When using the AU version of the Dolby Atmos Music Panner plug-in with Ableton Live, panner

controls with discrete parameters (such as the Sequencer Enable and Elevation controls) do not

record automation when using the panner UI. As a workaround, use the VST3 version of the panner

plug-in. Alternatively, you can use the AU version of the panner plug-in and manually draw

automation for these controls. [EUROPA-729]

• When using the AU version of the Dolby Atmos Music Panner plug-in with Ableton Live,

automatable control parameters do not sort in the correct order in the automation drop-down list.

As a workaround, use the VST3 version of the panner plug-in. [EUROPA-730]

• In Ableton Live or Logic Pro, when using a large number of Dolby Atmos Music panners, you may

see one of these issues:

• The audio input indicators in the Renderer blink.

• The Renderer displays an audio device disconnect dialog.

Both of these issues indicate that the Renderer cannot process the amount of incoming audio. As a

workaround, reduce the number of panners to alleviate the problem. [EUROPA 725], [EUROPA-743]

• With Logic Pro, you may experience a short audio dropout during playback when turning a Dolby

Atmos Music Panner plug-in bypass on and off. [EUROPA-689]

• In Logic, the object cannot be repositioned with UI controls until audio plays through the track. As

a workaround, always play audio in the track before adjusting the object position in the panner. If

the track does not have audio, add audio to the track, start playback, and then adjust the object

position. [EUROPA-607]

 • In Logic Pro, when running a project with a large number of objects and automation data, a system

overload alert might appear. If this occurs, reduce the number of panners in the project.


• With Logic Pro, automatable control parameters displayed on a EUCON-enabled control surface do

not sort in the correct order. [EUROPA-730]

• In Nuendo, recording initial Z automation with a scroll wheel will record the automation, but the

automation will be not be read when played back. As a workaround, first record automation with

the Z rotary knob. Automation will now be read after being recorded using the scroll wheel.


• In Nuendo, after you insert a Dolby Atmos Music Panner on a soloed track and assign an input

channel number, output will be muted. As a workaround, toggle solo off and then on to unmute

the audio. [EUROPA-716]

• When the sequencer is toggled on, the object in the room view may jump to the default object

position (the middle of the room). For example, this occurs when you enable the sequencer for the

first time in the plug-in, or when you reset the sequencer. [EUROPA-610]

• Using a fractional sequence step duration for objects can result in object movements that are too

quick to be rendered correctly. Use caution when using a fractional step duration. [EUROPA-684]

• When using the sequencer, an object being positioned by the sequencer may appear blue in the

Renderer. The object should appear blue only when it is being controlled manually (for example,

when writing automation). [EUROPA-465]

Login to post a comment