That's good to hear as partly the reason I make them. It's easy to work out and show something working when you've spent $20K setting it up, not so easy to just dip your to into it all to see if it's for you or not.
Hey, im having some issues with what im guessing is the renderer, its saying that the driver is not supported and that i should also look for another valid device, and another message saying "Failed to create shared information" im guessing it could be my processor since its really weak. Im also wondering what asio am i supposed to choose for both the asio link pro?
Hey, do you know what to do in nuendo? I don't really understand where to do the routing. Should I use the external renderer dialogue or the control room or am I am doing something completely wrong?
@@SamHocking This could have been an option but I actually managed to connect it via localhost! This has the advantage that I can use the panner inside Nuendo
@@SamHocking Hey, sorry for commenting again but does this approach still work for you? I have switched from the trial version to a full license and the renderer doesn't seem to recognize Asio Link Pro anymore
@@ferdmusic8 I haven't tried recently, but new/better solution can be found using VB-Audio Coconut got released recently. It has a 128/256 channel virtual ASIO so more than enough and much more usable/stable. Search VB-Audio Coconut or Matrix
Have you noticed any flakiness in Resolve's implementation of Dolby Atmos? I'm getting problems with saving configurations in the Preferences window and also when patching to Dolby Send. Things are simply forgotten.
Apologies for another query: although I'm seeing the Resolve bed tracks light up in the Renderer the Object tracks are visible only as bed items: there's no movement in the "theatre" display,- the metadata isn't getting through. If I export from Resolve and open the Master file in the Renderer all is well. BTW I'm working in 5.1.2. I notice that you have eight ASIO DRIVER IN patches whereas I only have two: is this significant? Thank you for any pointers you are able to give.
The way the Dolby Atmos Renderer works is it receives Metadata from the Dolby Atmos Panner. This metadata is needed, it's not simply an audio channel connecting DAW channel to DAR object/bed channel. You also need the LTC timecode to be working for transport to work. Basically the DAW must transmit the metadata via the DAW Atmos panner or you must use the Dolby Atmos Panner plugin on the track (macos vst/aax/au only)
Thank you very much for taking the time to reply. I'm using the panner in Resolve 18.6 and am wondering how to enable the LTC timecode at the Resolve end,- or is it simply that I'm not using timecode in my own clips?
I haven't watched it, but I saw you have a video about davinci resolve and Dolby Atmos Renderer, but doesn't Davinci Resolve(studio) have a built in Dolby Atmos Renderer, Is it a cut down version and lacks the features of the stand alone V5 Dolby Renderer?
It does, although there's several features not in the internal renderers such as mp4 dd+joc export as an obvious limitation. I would demo this using ProTools, but that licence isn't on my tablet where i'm testing the new Renderer demo. I generally work on things on the tablet and then update the main workstation if it's proving to be useful.
Hi Sam, this is a very informative tutorial. But can you explain each step? from connection to hearing something? Because when I use Resolve with Dolby Renderer, when I switch on the remote controlling, the ASIO Link pro Driver interchange with resolve. What I mean is, first I switch on Atmos Renderer, I use ASIO4ALL so I pick that driver, then I switch on Resolve. On Resolve's ASIO Link Pro's Driver it's written, ASIO Link Multiclient. But as soon I switch on the remote control from resolve to control Atmos Renderer, both driver in ASIO Link Pro interchanges. In resolve now it's written ASIO4ALL and on Dolby Renderer it's now showing ASIO Link Multiclient. What should I do?
I must admit, I'm not sure how it would behave using asio4all. You're then using ASIOLink (a virtual driver) to connect with ASIO4ALL (another virtual driver) and then I assumed ASIO4ALL is connecting to you actual audio device, be it ASIO, WDM or whatever? Order of connections is: 1. Renderer = ASIOLink Pro and then open it. This should list your audio driver (ASIO4ALL if that's all you have). Davinci = ASIOLinkPro and is opened second. The problem you might have have is Davinci Resolve is a little greey and starts trying to connect to things it shouldn't and this can flick it from being a client to being a server. It's tricky to diagnose i'm afraid.
Hi Sam, thank you for the vids! Quick question, does the davinci relsove panner works as good as the dolby panner? And with this general setup could I use the binaural option in dolby renderer option and use headphones to make a mix?
In terms of the Atmos panning capability, yes, the Resolve panners allow 100% control of the object in the Renderer. Resolve is a bit convoluted in that the binaural render modes are not set on the channel strip itself or even in their panner, but in the Index tab (alongside media pool). Re. headphones, sure, you'll set the Renderer to be a binaural output and experience it on headphones.
Forgot to say, you can set binaural modes for each bed and object in the Renderer itself though. When you get to the point of having the Atmos ADM master you then have options to re-render it and change the binaural settings then rather than going back to the DAW session and exporting/recording a whole new ADM.
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
Not as a Dolby Atmos HDMI stream I don't think. iirc HDMI to an AVR is typically 5.1 or 7.1 maximum. You could monitor in 7.1 and see if that will route through to an AVR maybe?
@@Powawized Windows does have something called Dolby Access which acts as the interface between a Dolby Atmos file/stream playing in Windows audio system being passed through to your AVR/Soundbar/TV but it can't take the raw/standard audio out of your DAW or Dolby Atmos Renderer and move it over HDMI, it only passes through Dolby encoded Atmos. ie DD+JOC & TrueHD. I would love for there to be a way to get audio from DAW to a consumer AVR in 7.1.4 but I'm yet to find it. The nearest you can get are AVRs like Tonewinner Atmos AVRs that have standard audio inputs you can map to 7.1.4, but you'll still need a pro audio interface having enough channels to connect to it.
Dolby only make their VST Panner for MacOS for some strange reason. You either have to use a DAW that supports Dolby Atmos (Cubase, Nuendo, ProTools etc) and use the native panner or only use the 7.1.2 Bed channels. ie push your instruments to the speakers you want to hear them.
A very helpful video: thanks to you I've managed to get this working with Resolve on Windows 10. I'm trying to produce 5.1.2 and can see both bed and objects in Renderer but when I export audio with an MP4 video the resulting file is 5.1 only. Do you happen to know why this is?
Thank you for all that you've done to help us with this. I am running into an issue though. My renderer is not giving me an option to select ASIO link in "Audio Input Device" and "Audio Output Device". Ive installed The renderer and the ASIO Pro Tool software. I hope that I installed it all correctly. I tried to follow your tutorial on installing the software and patches. Do you have an idea as to why the render is only showing "None" for the device settings?
It will be difficult to help over UA-cam. Did you follow the video showing how to install the ASIO Link software at ua-cam.com/video/TxxVmvcaSTs/v-deo.html
@@SamHocking I understand. yeah. I followed the instructions. Installing it and adding in both patches before running the software. I’m wondering if it’s a compatibly issue because I’m running windows 11.
Just to add, the ASIO Link application itself, does require you to have at least one working ASIO device. So if you've e.g. got a laptop and it's only got Realtek windows drivers you will will need to install an ASIO driver either for actual hardware or a virtual one that will bridge to a windows one. Easiest way to do it imo is to install VB-Audio Voicemeter which comes with one. That is the ASIO device I did the video with.
@@DavidMartinez-se5vl Could be an 11 issue. You definitely patched both the 32bit and 64bit .exe? What happens when you open only C:\Program Files (x86)\ASIOLinkPro\x64\asiolinktool.exe This should open the small control windows. You then click Start ASIO and that will fire a server instance of ASIO Link Pro and also allow you to pick a driver. Does that work?
Dolby Atmos when exported to .mp4 from the DAR is a 5.1 audio file (5.1 DD+) but it also contains JOC information which handles rebuilding the full Atmos mix. If you go to View>Text in mediainfo you should see it says it's Dolby Atmos with a Complexity index of 16 which is kind of meaning it can rebuild upto 9.1.6,
![If you can't hear this then you're not an audiophile [See description for link to followup video]](http://i.ytimg.com/vi/48PxwspDvrE/mqdefault.jpg)
![If you can't hear this then you're not an audiophile [See description for link to followup video]](/img/tr.png)
Thank you again Sam for sharing. These videos of yours are opening up possibilities for small mixing studios this side of the world.
That's good to hear as partly the reason I make them. It's easy to work out and show something working when you've spent $20K setting it up, not so easy to just dip your to into it all to see if it's for you or not.
Hey, im having some issues with what im guessing is the renderer, its saying that the driver is not supported and that i should also look for another valid device, and another message saying "Failed to create shared information" im guessing it could be my processor since its really weak. Im also wondering what asio am i supposed to choose for both the asio link pro?
Hey, do you know what to do in nuendo? I don't really understand where to do the routing. Should I use the external renderer dialogue or the control room or am I am doing something completely wrong?
Should just be a case of setting up your audio output in Nuendo to ASIOLink outputs/inputs?
@@SamHocking This could have been an option but I actually managed to connect it via localhost! This has the advantage that I can use the panner inside Nuendo
@@SamHocking Hey, sorry for commenting again but does this approach still work for you? I have switched from the trial version to a full license and the renderer doesn't seem to recognize Asio Link Pro anymore
@@ferdmusic8 I haven't tried recently, but new/better solution can be found using VB-Audio Coconut got released recently. It has a 128/256 channel virtual ASIO so more than enough and much more usable/stable. Search VB-Audio Coconut or Matrix
Have you noticed any flakiness in Resolve's implementation of Dolby Atmos? I'm getting problems with saving configurations in the Preferences window and also when patching to Dolby Send. Things are simply forgotten.
Usually pretty solid with the config. So much with DAR external is channel and routing config with reliable LTC sync though.
Would I have any CPU resource/heat issues running the Renderer and Ableton on one machine that is a 13900K,64GB ram + rtx4090?
Should be fine with that processor. The Renderer consumes about 15% CPU depending on binaural settings and spatial coding on or off.
Apologies for another query: although I'm seeing the Resolve bed tracks light up in the Renderer the Object tracks are visible only as bed items: there's no movement in the "theatre" display,- the metadata isn't getting through. If I export from Resolve and open the Master file in the Renderer all is well. BTW I'm working in 5.1.2. I notice that you have eight ASIO DRIVER IN patches whereas I only have two: is this significant? Thank you for any pointers you are able to give.
The way the Dolby Atmos Renderer works is it receives Metadata from the Dolby Atmos Panner. This metadata is needed, it's not simply an audio channel connecting DAW channel to DAR object/bed channel. You also need the LTC timecode to be working for transport to work.
Basically the DAW must transmit the metadata via the DAW Atmos panner or you must use the Dolby Atmos Panner plugin on the track (macos vst/aax/au only)
Thank you very much for taking the time to reply. I'm using the panner in Resolve 18.6 and am wondering how to enable the LTC timecode at the Resolve end,- or is it simply that I'm not using timecode in my own clips?
@@northillvideo I will try and do a video later. You are using the internal renderer or have installed the full Dolby Atmos Renderer btw?
Thank you, that would be great. I have the full Renderer 5.1 as I need MP4 export.
It would be very useful to know how you configured Resolve to "talk" to the Renderer in terms of the object metadata.
hi, there is no simple atmos visualizer free? just to test games etc...
Theres Cavern but I dont know if good for Atmos games it's really for movie and music Atmos
@@SamHocking Oh thank you ! I need to check that !
@@RGsunlight091 Search google for 'download cavern' and first result should be it.
I found it thank you @@SamHocking
I haven't watched it, but I saw you have a video about davinci resolve and Dolby Atmos Renderer, but doesn't Davinci Resolve(studio) have a built in Dolby Atmos Renderer, Is it a cut down version and lacks the features of the stand alone V5 Dolby Renderer?
It does, although there's several features not in the internal renderers such as mp4 dd+joc export as an obvious limitation. I would demo this using ProTools, but that licence isn't on my tablet where i'm testing the new Renderer demo. I generally work on things on the tablet and then update the main workstation if it's proving to be useful.
Hi Sam, this is a very informative tutorial. But can you explain each step? from connection to hearing something? Because when I use Resolve with Dolby Renderer, when I switch on the remote controlling, the ASIO Link pro Driver interchange with resolve. What I mean is, first I switch on Atmos Renderer, I use ASIO4ALL so I pick that driver, then I switch on Resolve. On Resolve's ASIO Link Pro's Driver it's written, ASIO Link Multiclient. But as soon I switch on the remote control from resolve to control Atmos Renderer, both driver in ASIO Link Pro interchanges. In resolve now it's written ASIO4ALL and on Dolby Renderer it's now showing ASIO Link Multiclient. What should I do?
I must admit, I'm not sure how it would behave using asio4all. You're then using ASIOLink (a virtual driver) to connect with ASIO4ALL (another virtual driver) and then I assumed ASIO4ALL is connecting to you actual audio device, be it ASIO, WDM or whatever? Order of connections is: 1. Renderer = ASIOLink Pro and then open it. This should list your audio driver (ASIO4ALL if that's all you have). Davinci = ASIOLinkPro and is opened second.
The problem you might have have is Davinci Resolve is a little greey and starts trying to connect to things it shouldn't and this can flick it from being a client to being a server. It's tricky to diagnose i'm afraid.
Hi Sam, thank you for the vids! Quick question, does the davinci relsove panner works as good as the dolby panner? And with this general setup could I use the binaural option in dolby renderer option and use headphones to make a mix?
In terms of the Atmos panning capability, yes, the Resolve panners allow 100% control of the object in the Renderer. Resolve is a bit convoluted in that the binaural render modes are not set on the channel strip itself or even in their panner, but in the Index tab (alongside media pool).
Re. headphones, sure, you'll set the Renderer to be a binaural output and experience it on headphones.
Forgot to say, you can set binaural modes for each bed and object in the Renderer itself though. When you get to the point of having the Atmos ADM master you then have options to re-render it and change the binaural settings then rather than going back to the DAW session and exporting/recording a whole new ADM.
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
Not as a Dolby Atmos HDMI stream I don't think. iirc HDMI to an AVR is typically 5.1 or 7.1 maximum. You could monitor in 7.1 and see if that will route through to an AVR maybe?
@@SamHocking in macOS 7.1 is maximum via hdmi but on windows atmos is supportet via hdmi. But the questions is if I can use that on the windows DAR
@@Powawized Windows does have something called Dolby Access which acts as the interface between a Dolby Atmos file/stream playing in Windows audio system being passed through to your AVR/Soundbar/TV but it can't take the raw/standard audio out of your DAW or Dolby Atmos Renderer and move it over HDMI, it only passes through Dolby encoded Atmos. ie DD+JOC & TrueHD.
I would love for there to be a way to get audio from DAW to a consumer AVR in 7.1.4 but I'm yet to find it. The nearest you can get are AVRs like Tonewinner Atmos AVRs that have standard audio inputs you can map to 7.1.4, but you'll still need a pro audio interface having enough channels to connect to it.
hey where do i get the dolby atmos music panner for windows version?
Dolby only make their VST Panner for MacOS for some strange reason. You either have to use a DAW that supports Dolby Atmos (Cubase, Nuendo, ProTools etc) and use the native panner or only use the 7.1.2 Bed channels. ie push your instruments to the speakers you want to hear them.
A very helpful video: thanks to you I've managed to get this working with Resolve on Windows 10. I'm trying to produce 5.1.2 and can see both bed and objects in Renderer but when I export audio with an MP4 video the resulting file is 5.1 only. Do you happen to know why this is?
Is that the external Dolby Atmos Renderer or the internal one that comes with Davinci Resolve Studio?
Can u give link where did you installed driver for asio link pro
Andy Evans has expanded on my initial video with more detail showing the install procedure and use in detail.
ua-cam.com/video/eARw4dZ2PxU/v-deo.html
Thank you for all that you've done to help us with this. I am running into an issue though. My renderer is not giving me an option to select ASIO link in "Audio Input Device" and "Audio Output Device". Ive installed The renderer and the ASIO Pro Tool software. I hope that I installed it all correctly. I tried to follow your tutorial on installing the software and patches. Do you have an idea as to why the render is only showing "None" for the device settings?
It will be difficult to help over UA-cam. Did you follow the video showing how to install the ASIO Link software at ua-cam.com/video/TxxVmvcaSTs/v-deo.html
@@SamHocking I understand. yeah. I followed the instructions. Installing it and adding in both patches before running the software. I’m wondering if it’s a compatibly issue because I’m running windows 11.
Just to add, the ASIO Link application itself, does require you to have at least one working ASIO device. So if you've e.g. got a laptop and it's only got Realtek windows drivers you will will need to install an ASIO driver either for actual hardware or a virtual one that will bridge to a windows one. Easiest way to do it imo is to install VB-Audio Voicemeter which comes with one. That is the ASIO device I did the video with.
@@SamHocking thank you. I will be going up my focusrite Scarlett interface soon so hopefully I can use that.
@@DavidMartinez-se5vl Could be an 11 issue. You definitely patched both the 32bit and 64bit .exe? What happens when you open only C:\Program Files (x86)\ASIOLinkPro\x64\asiolinktool.exe
This should open the small control windows. You then click Start ASIO and that will fire a server instance of ASIO Link Pro and also allow you to pick a driver. Does that work?
how the dow-n dolby atmos renderer
and what is the ILOCK
You can download a 90 day demo from Dolby. Dolby will add licence to your ilok account.
@@SamHocking you can make a tutorial video how make ILOK accout because I can't.
@@KreatívŐzike ua-cam.com/video/WCfzZ3uoGQQ/v-deo.html
Can it support 128 channels?
No, Steinberg limit ASIO protocol to 64 I/O I believe. If Dolby would allow JACK2 then 128 would be very easy though.
..that is, MediaInfo shows only six channels.
Dolby Atmos when exported to .mp4 from the DAR is a 5.1 audio file (5.1 DD+) but it also contains JOC information which handles rebuilding the full Atmos mix. If you go to View>Text in mediainfo you should see it says it's Dolby Atmos with a Complexity index of 16 which is kind of meaning it can rebuild upto 9.1.6,
Thank you very much.@@SamHocking