Integrated Dolby Atmos

[philwrightsound]

Hi Everyone,
I've been using Reaper with Dolby Atmos now for 2 1/2 years. I use the Dolby Renderer with the Dolby Audio Bridge and it's seemless and I've done some really big studio and live projects using Atmos.
My question is - by using the renderer and bridge, I'm having to render in realtime. Given that ADM is an open model and Dolby want as many people creating content as possible when will Reaper be catching up with the other DAW manufacturers and offering native ADM renders offline within Reaper?
I've loved the fact that from day 1 I could use 128 objects with LTC on 129 using the bridge, which was a larger channel count than many DAWs (including PT to begin with), but the realtime render occasionally causes me issues with time, and I'm just wondering when Reaper will address this?
Ignoring Avid PT,...... Cubase, Nuendo, Logic, Resolve, Pyramix, even PreSonus Studio One (6.5) have the integration, so the last two DAWs I'd consider professional tools are Ableton and Reaper. Who's coming in last?

[Gass n Klang]

yes, much needed.

[Gass n Klang]

pro tools got an integrated atmos renderer with the new 2023.12 update

[plush2]

Originally Posted by Gass n Klang

pro tools got an integrated atmos renderer with the new 2023.12 update

Yes, and for studio and ultimate...I guess I have to eat my hat on that one.

[Berg]

Originally Posted by philwrightsound

Hi Everyone,
I've been using Reaper with Dolby Atmos now for 2 1/2 years. I use the Dolby Renderer with the Dolby Audio Bridge and it's seemless and I've done some really big studio and live projects using Atmos.
My question is - by using the renderer and bridge, I'm having to render in realtime. Given that ADM is an open model and Dolby want as many people creating content as possible when will Reaper be catching up with the other DAW manufacturers and offering native ADM renders offline within Reaper?
I've loved the fact that from day 1 I could use 128 objects with LTC on 129 using the bridge, which was a larger channel count than many DAWs (including PT to begin with), but the realtime render occasionally causes me issues with time, and I'm just wondering when Reaper will address this?
Ignoring Avid PT,...... Cubase, Nuendo, Logic, Resolve, Pyramix, even PreSonus Studio One (6.5) have the integration, so the last two DAWs I'd consider professional tools are Ableton and Reaper. Who's coming in last?

Yes we are waiting...so long before the light is coming

[jm duchenne]

An interesting video from AudioBrewers to compare Dolby Atmos production in six DAWs.
The good part is that Fiedler Audio's Dolby Atmos Composer plugin is always better than integrated Atmos renderer, so Reaper is already in the top rank ;-)
https://www.youtube.com/watch?v=-0r_52cpgqY

[Berg]

Hi JM ! Best wishes !
Dealing now with Fiedler integration, it’s very valuable, working on some bugs, and
metadata adjustments !

[ScuzzyEye]

Originally Posted by jm duchenne

The good part is that Fiedler Audio's Dolby Atmos Composer plugin is always better than integrated Atmos renderer, so Reaper is already in the top rank ;-)

I had been watching lots of videos of people using Logic, and other DAWs. I only had Fiedler's Atmos Composer. Other than the no post-fader inserts, I felt like everything doing in Reaper was more flexible. I just got the 6.5 update to Studio One, and tried working with it for a bit. I still felt more limited there, than with Reaper + Fiedler.

[drichard]

I agree completely about post-fader inserts. Because of licensing, Reaper will probably never have its own native Atmos integration, and Fiedler might be the only solution. But post-fader inserts would make it everything I want.

Originally Posted by ScuzzyEye

I had been watching lots of videos of people using Logic, and other DAWs. I only had Fiedler's Atmos Composer. Other than the no post-fader inserts, I felt like everything doing in Reaper was more flexible. I just got the 6.5 update to Studio One, and tried working with it for a bit. I still felt more limited there, than with Reaper + Fiedler.

[jm duchenne]

This news has already spread in other posts, but the Essential version of Fiedler Dolby Atmos Composer is now free!
So it could mean that Atmos can be everywhere, thus why not in Reaper, OR that it doesn't have anymore to be integrated since it is already free to use...
https://fiedler-audio.com/dolby-atmo...ser-essential/

[MixMonkey]

Post fader insert point to fully enable the Fielder Atmos plugin please

[GoHard]

Originally Posted by MixMonkey

Post fader insert point to fully enable the Fielder Atmos plugin please

I have already used it extensively in my project. It is a very good product. Can you tell me in what scenarios it must be used after the fader?

[ScuzzyEye]

Originally Posted by GoHard

I have already used it extensively in my project. It is a very good product. Can you tell me in what scenarios it must be used after the fader?

It doesn't technically have to be after the fader, because it has its own internal volume control. But when it is inserted before the fader, the fader does nothing at all. The audio is "beamed" to Composer before it hits the fader.

So if you're mixing levels with the faders, and then insert Beams as an attempt to add Atmos to an already mixed project, you end up disregarding the faders and resetting the mix.

The work around everyone is doing in this case is to send the (post-fader) mixed track to another track with the Beam inserted there. This works perfectly, except it doubles the number of tracks in your project.

[GoHard]

Originally Posted by ScuzzyEye

It doesn't technically have to be after the fader, because it has its own internal volume control. But when it is inserted before the fader, the fader does nothing at all. The audio is "beamed" to Composer before it hits the fader.

So if you're mixing levels with the faders, and then insert Beams as an attempt to add Atmos to an already mixed project, you end up disregarding the faders and resetting the mix.

The work around everyone is doing in this case is to send the (post-fader) mixed track to another track with the Beam inserted there. This works perfectly, except it doubles the number of tracks in your project.

I understand, you are mainly describing the situation of using the track as an object. (I mainly use reasurroundpan when using beds.) However, there are also some benefits to using the parent track when each object is sent to the beam:

For example, if I want to send an object to other tracks as a sidechain or as an additional input trigger, the send from the child track will not affect the parent track (Beam), and the routing will be clearer.
Multiple groups of audio can be sent to the same object.
The envelope of the spatial coordinates will be clearly displayed on the parent track, while the child tracks focus on audio processing.