Thanks! Much appreciated!

Excellent tips!

Thanks! It depends a bit on the DAW you are using but generally yes, you can use Audio Brewers with the DAC as long as your DAW is multichannel capable.

I’ll probably do more than one because there are different ways to approach this.

Yes, makes sense. There are different interpretations on how the Atmos bed should be used. Some route everything into the bed that has no automated position. Some avoid the bed completely. My approach is to route ambient sounds into the bed. And in all examples I use that essentially means the spatial reverb only. But there are no strict rules. Whatever works for you workflow is fine.

@@michaelgwagner Thx Michael. I am the very definition of a noob. I’m so new to Dolby Atmos mixing I don’t yet have my own workflow. Someday I will figure out what works for me but for now I’m in exploration mode. Your videos and responses have been very helpful in this exploration.

I was just monitoring in stereo in this video if I’m not mistaken.

Yes, the bed would always be 7.1.2.

Yes, you can have multiple instances.

Not something I have a lot of knowledge about. But Atmos is being used in theater settings so a 300-800 audience should not be an issue.

You’re very welcome!

I figured it out! The Spacelab Beam plugin must be loaded on to the Loop track inserts before you go into Spacelab Ignition Source Setup. It's first mentioned later in the video at 9:00, but should be mentioned from the beginning. :)

I should pay more attention the Pro Tools. :) That function does not exist in Nuendo. But there is a workaround. I’ll most likely post a video about that next week.

I need to correct myself. You can actually do the same thing In Cubase/Nuendo. It is a bit hidden but it is possible. Thanks for the tip!

I have a DearVR version of this video scheduled to go live in three weeks. In DearVR the reverb is position agnostic, only the reflections require automating the object position in DearVR Pro. Automating both simultaneously should be possible but likely depends on what DAW you are using. I have not yet found a good way to do it, but it is on my to-investigate list.

@@michaelgwagner thanks for the reply and i look forward to your future videos 🙂

Not quite sure if I understand the question. You mean putting the reverb on the object itself?

Working with two systems and the mastering suite is a bit more complex. Dolby has some very good documentation for that. With respect to your second question. Atmos deals with beds just like with objects. In other words, it should upmix it correctly to 9.1.6.

Soll schon vorgekommen sein… 😂

Ideally you would have an Atmos capable reverb and those are still rare. For most applications you should get away with surround reverbs though. Did not look at the Audio Ease reverbs yet.

@@michaelgwagner Thanks for the reply! I'm trying out ignition now and I really like the workflow. One thing I'm wondering though is how to get various reverbs for a case where I have a project that has two different rooms. Would I use two different busses? I don't think an effect send can be a part of a bed, can it?

You would have to create two bed busses and then just sum them together before passing it on to the renderer.

@@michaelgwagner Ah okay. Wonderful! Thanks.

Cubase

Thanks! I vaguely remember that I ran into the same issue once but it ended up being something trivial. Double check all the steps.

@@michaelgwagner Tried millions of times. The "LOOP" does not appear in Input in Input Source no matter what I do. Only Spacelab. This drives me crazy.. 😀

@@michaelgwagner I used all evening yesterday trying figuring it with no luck at all. I have tried everything in various combinations. Not matter what. The Loop object track is being recognized as an Input Source in Ignition. I've looked through anything possible. Please help. :)

Do you have a project file you can send me? DM me on Discord.

@@michaelgwagner OK, will try. Thank you very much! :D I will send it when I get home from work. I really appreciate it!

Simply because you can’t do that in an Atmos configuration. There is no equivalent to a “main mix” in Atmos. Everything is rendered at the endpoint device, so you need to separate that out during production. And some of the routing is a bit complicated by the way the Atmos panner works. You cannot tap into the signal between the panner and the renderer. That’s why you need to pan it twice.

@@michaelgwagner but in my case it worked. I used a MUSIC 7.1.2 Bed (patched to Atmos Rendered) then I've a Reverb 7.1.2 Submix bus (send it's signal to MUSIC 7.1.2 Bed). I've panned an object (object is patched to Atmos Renderer), send it's signal to Reverb Submix bus then applied reverb plugin on Submix bus. And done. What's the matter to complicate things like shown in this tutorial, when you can just make a submix bus to do the same?

Are you working in DaVinci Resolve Fairlight?

@@michaelgwagner I've worked in both Fairlight and Nuendo but this method works same in both spftwares

I am not sure about Fairlight because it has a custom implementation of the renderer, so the routing could be different. But if you are working with the official Dolby Renderer, internal or external, the panning of objects is done within the renderer. If you do it the way you described, your reverb would not take the position of the object into account. Now, depending on the reverb you are using and the purpose of using it this might or might not make a difference. However, if you are aiming to recreate a realistic reverb in a 3d space, you need to also pan what is going into the reverb. In other words, your approach works as long as you are ok with the reverb being object position agnostic.

starts 0:00 😂