Fiedler Audio Dolby Atmos Composer in Reaper

[@SamHocking]

The Composer Binaural & Speaker Output is running concurrently. If e.g. you had Composer set to 9.1.6 speaker outs across channels 1-16 in the DAW, the binaural will be outputting on 17 & 18. Will depend on the DAW how easy that is to access through, because if you put it on 16 channel master bus you won't hear the binaural unless you switch off the speakers so it comes out on channels 1 & 2.

[@Tony_Kosinec]

Many thanks for working out these problems. This is exactly what I was looking for.

[@ImmersiveAudioMixer]

Glad to help :-)

[@user-hj9lc6dh6i]

Hi there, many thanks for this tutorial. For the volume problem, may I ask why you recommend bussing instead of using parent tracks with child tracks inside?

[@Not-Only-Reaper-Tutorials]

did they work on these glitches, so far?

[@prosart1]

Thanks!!!

[@kelvinfunkner]

I'm new to the whole concept of atmos so forgive me if this is a silly question, but does this replace the Dolby Atmos Renderer? Or does that still need to be purchased alongside this software? Thanks so much!

[@ImmersiveAudioMixer]

Yes, it is meant to replace the need for Dolby's application (and therefore for an iLok).

[@armchairaudio]

@@ImmersiveAudioMixer Do we not still need the renderer to listen to an already bounced atmos file? Like if we brought a 118 channel atmos file into reaper.

[@dannykirsch]

Hey Patrice. I’ve been demoing this plug-in in Logic Pro. I find that if you have lots of channels with the beam plug-in on everything is fine however if you also have one on a bus then the timing of that bus will be out of synch with the other tracks. Have you found the same thing and if so do you know of a fix?

[@ImmersiveAudioMixer]

Hi Danny. I tried to add many tracks and a bus with a metronome plugin. Then rendered every track to test with audio and finally bounced the stereo output from the Dolby Audio Composer and imported it into my session to be sure, but timing was perfect all along. Did you find the plugin more useful than the built-in Atmos in Logic Pro ?

[@dannykirsch]

@@ImmersiveAudioMixer Hey Patrice. I was having too many timing issues in Dolby Atmos Composer and therefore deleted it yesterday when my demo ran out but either way I prefer the built in Atmos in Logic by a million miles. It's so much more straight forward and sounds the same. The only issue I'm having with the Logic one is that if I turn an instrument track into a 3d object it goes out of synch. Audio track as 3d objects are fine and both instrument tracks and audio tracks as beds are fine....it's just instrument tracks as 3d objects. Sometimes it's okay but then it will suddenly go complete out of synch until I turn it back into a bed track. Do you have any fix for this at all please Patrice or anyone else reading this as it's driving me nut?

[@sebguyader]

@@dannykirsch I have both Reaper and Logic Pro, but I just started learning Logic Pro. I also found that under some circumstances Logic gets out of synch on some tracks, even with audio IIRC. I think it's a Logic issues. In my case stopping playback and hitting play again would make things in synch again, but I haven't tried with instruments. If this problem occurs too frequently with your instruments, you should probably bounce these instrument tracks in place (without the Atmos rendering) to transform them into audio tracks, and strat producing in Atmos from only audio tracks.

[@dannykirsch]

@@sebguyader yes bouncing in place to audio does the trick however clients often want revisions to the production so I prefer to stay with the instruments rather than bounce in place. I wish apple would sort out this bug.