Dolby Atmos and Pro Tools on a single Windows PC at last using Renderer V5 and Asiolink Pro!

[@Asrelis]

dude, thank you so so much for this video!!! this was exactly what i was scrounging around on the internet for, and i got DAR and Pro Tools up and running without having to do any nonsense with Dante Virtual Soundcard and a random switch i found LMAO you are an absolute godsend bro

[@SamHocking]

Cool Andy! I linked back to here from my video so people can watch this if they get stuck. Cheers for the credit! The ASIOLink re-initialization error is annoying. I haven't looked into if there's a solution yet, but it's because both Pro Tools & Dolby Atmos Renderer seem to disconnect and re-connect even when no actual audio settings with the interface changed. A shame ASIOLink's developer passed away as I think he could really get it running solidly for us : (

[@kyraipikuma]

Hi. I've been recently trying to follow these steps to make use of Dolby Atmos Renderer on my PC. I had to stop around 7:47 because I do not have Pro Tool Ultimate, just regular Pro Tools and the Dolby Atmos tab doesnt show in my peripherals. Are there any workarounds for this or is this only exclusive to the upgraded versions of Pro Tools? Ive already used up a free trial for Ultimate due to one of my college classes requiring it :(

[@MusikUndDesign]

Hi, you need either Ultimate or Pro Tools Studio..

[@llmh220]

Thanks ! I've spent an entire day trying to make this work with a Grace Design output interface because their Asio driver wasnt able to work with Asio link pro + renderer only to find out that in the renderer settings there is an output selection which let me route through Asio link + Asio4all into the right output to the Grace converter ! If you are having trouble with your own interface maybe this is the solution too ! Thanks again

[@raisingjakestudios1371]

I have my setup working following what you showed here but for some reason I have lost the ability to do any signal routing WITHIN Pro Tools. For example, I have a stereo reverb bus output routed to Atmos object channels 11 and 12. Track send meters show there is signal at the reverb SENDs - but there is no signal coming into, or out of, the reverb bus. Same thing happened when I tried to send tracks to a 7.1.2 summing bus (that was then routed to the BED channels). That "in between" 7.1.2 bus had no signal through it. The only routing ability I seem to have is DIRECTLY from a track to the renderer input buses. I can't do any usual sub-bus routing, grouping, sends, etc., WITHIN Pro Tools. Is this being caused by a limitation of this "bridge" or is something wrong in my setup?

[@MusikUndDesign]

Are you creating a stereo bus to use for the reverb send in the i/o setup and set that as input for the aux channel with the reverb on it ? Same with the 7.1.2 summing, have you created a new 7.1.2 bus in the i/o page then set that as the inout for the channel? should work, works fine here.

[@raisingjakestudios1371]

@@MusikUndDesign - yes, I have dedicated buses for the reverb and the 7.1.2 submix and set them as the track I/Os. Signal is being sent TO them (SEND meters show signal) but is not going THROUGH them (verb and 7.1.2 track meters show no signal and no sound). I switched back to a non-Atmos project and it works properly. I don't understand it. As you said, it should work. Wondering if anyone else here has had the same issue.

[@MusikUndDesign]

@@raisingjakestudios1371 what version Pro Tools? Mine was all fine on 2023.3

[@MusikUndDesign]

Just tried it on 2023.6, works fine as well. It must be something simple, my bet would be something in the i/o setup but as to what ..?

[@raisingjakestudios1371]

⁠@@MusikUndDesign- thank you for the follow-ups. I’m on 2023.6 Ultimate. I agree - it’s probably something simple but I’ve set up buses as I always have and don’t see anything wrong. Will give it another try tomorrow after shutting down and rebooting.

[@Powawized]

is there some way to make the windows DAR output the mix from a seperate Mac via HDMI to an AV-Receiver (in Dolby Atmos). Because I don't have an audio interface

[@MusikUndDesign]

Hi, I don't know but I doubt it. I don't think you can do more than 8 outputs from Windows system audio. Might be some way you could just use headphones and monitor the binaural but you'd sill need an asio driver

[@petargocic5520]

Can u please post link where did you installed driver and how did you set it up i tried million of them and nothing works

[@MusikUndDesign]

Hi, I used the asio driver for my SSL converters as the asio driver in Asiolink Pro, if that's what you mean... Are you using separate converters? If so they should have an asio driver for them in the software that came with them. If you are trying to set it up without using external converters and just using Windows sound card then I'm not sure if that works as I've never tried it. I've heard people use one called Asio4all to use windows sound with Pro Tools, but never tried it as I use converters with their own asio drivers.

[@DerekBenjaminMusic]

Your video helped me get my system up and running! Now i'm having a hard time bouncing atmos files. It either has the timecode noise in the render, or if i mute/disable it, the audio is blank, or seems to be. I'm probably doing some things wrong, but it's very confusing and trial and error with having to open and close pro tools constantly is time consuming!

[@MusikUndDesign]

HI Derek..do you have the timecode sync set to 'LTC over Audio' and the LTC input channel set to '64' in the Render settings, found in the file menu? The renderer is set up as default to ASIO sync by default, and that would cause the LTC to be audible

[@DerekBenjaminMusic]

@@MusikUndDesign I do! It's not audible until I pull the master file back into the renderer to check it out. So im not sure how to sync it but not have it play

[@MusikUndDesign]

@@DerekBenjaminMusic when you create a new mono track for the timecode wav and assign it to object 64 in the pro tools session, did you first disconnect the existing stereo channel called 'object 63-64' that is in the template? If not that could be the cause. The mono timecode track should be the only thing assigned to object 64. If you haven't either disconnected or deleted the 'Object 63-63' track that is in the template then you will have timecode audible in the master file. I deleted that track, and all the others after it, as well as the TC generator plugin track that were all in the the original Dolby Audio Bridge stereo template and resaved it as my own 646CH Atmos template. Hopefully that's the issue.. Let me know how you get on.

[@DerekBenjaminMusic]

@Andy Evans hmm! I'll have to do some more experimenting still. I didn't use the template I just adapted an existing mix and rebuilt my io. I don't have any other tracks with object 64 assigned. Do you mean the IO should be altered for that object? I'm assuming it would still need the output assignment, bus tab assignment and the connection to the renderer.

[@MusikUndDesign]

@@DerekBenjaminMusic not sure, it's really hard to say in regards to adapting a mix etc without being there.. I'd suggest you put that project on hold, and start one from scratch using the Dolby audio bridge stereo i/o and session templates and see if that works, that's what I've been using. If that works you can then have a look at it and see what is different to the way you currently have things..

[@BackscratchAudio]

Thanks for this Andy, almost got it working. Audio links pro seem to work fine and pro tools talks to the renderer when I assign objects and pan them, however I have no input on the meters nor can I get the sync working with the LTC? Am I missing something, any ideas anyone? I am on win11. Cheers

[@MusikUndDesign]

Have you set the LTC channel in the renderer setup to object 64 and assigned the channel im pro tools the TC wav is on to object 64, and set the TC frame rate in the renderer to match your LTC wav file? is the renderer set to external sync, and to monitor input?

[@BackscratchAudio]

@@MusikUndDesign Thanks Andy, done all that. Somehow missed the part with "Route to ASIO IN". All working nicely now. Cheers

[@MusikUndDesign]

Nice one!

[@Sitandcreatestudio]

How do I get a hold of a TC frame anyone have a link or file

[@SARATHPRASAD-b5u]

I can't open my dolby Renderer im using windows 11 , when i try to open dolby its automatically closing!

[@MusikUndDesign]

I'm on Win10 ,so can't really compare , but some users are experiencing this and Dolby are aware and working on a siluation. I don't know if this applies to your particular case, but have aread here.. professionalsupport.dolby.com/s/article/Dolby-Atmos-Renderer-v5-0-Crashing-on-PC?language=en_US

[@SARATHPRASAD-b5u]

@@MusikUndDesign and one thing is when i select ASIO4ALL as my driver in asiolink its closing automatically but its shows more i/o s than my other drivers(stereo).if i select asio4all its closing after some second so i jst opened dolby and asiolink at the same time so its working and dolby showed up its interface for the first . and suddenly both crashed again.😶 so is it anything with my driver. can i launch dolby renderer with stereo i/o in other systems (windows10)

[@MusikUndDesign]

@@SARATHPRASAD-b5u ASIO4ALL can sometimes be hit and miss, but I haven't tried it with Asiolink Pro. One thing you could try is setting the ASIO4ALL buffer size to 512, which is what the renderer needs. If that doesn't work, are your other stereo drivers ASIO? If so I'd try them and see, it shouldn't matter that they are stereo, you should still get 64 channels in Asiolink Pro, but I haven't tried stereo drivers..I have seen it working with only stereo drivers before