User16841753119578310691 (Robert Lakatosh) asked a question.
LTC bus not available with Pro Tools Studio
To replicate error, I am using Pro Tools Studio (latest updated, 2022) on a M2 Mac mini running Ventura. I have connected Dolby Atmos in peripherals, and I have the renderer open. My playback engine is set to Dolby Audio Bridge, and in the I/O settings window, I have deleted all busses and selected default for stereo routing to the renderer. However, this gives me 128 object busses (which I only thought 64 were possible in Pro Tools), and I don't have a LTC bus 129. In the production suite renderer, I have made sure my clocking is coming from bus 129.
If I try to create bus 129 myself in Pro Tools I/O settings, I am given an error saying that it cannot route to the renderer. Otherwise, I have gotten signal to run through the renderer successfully, but I unfortunately can't get the benefits of Atmos because I can't establish clocking. Does anybody know what could be causing this problem?
If I try to create bus 129 myself in Pro Tools I/O settings, I am given an error saying that it cannot route to the renderer. Otherwise, I have gotten signal to run through the renderer successfully, but I unfortunately can't get the benefits of Atmos because I can't establish clocking. Does anybody know what could be causing this problem?
The LTC output bus does not need to be mapped to the Renderer, as this column is used for metadata mapping. The LTC bus only needs to be mapped to output, which creates the audio path.
The Renderer only supports object metadata up to input 128, which is why you are unable to map metadata beyond 128 and seeing this pop up alert.
See the screenshot below for a properly configured I/O setup bus tab.
-B