Hi!
With the latest version of Wavelab (Win 10), I only get silence when switching the renderer to “Binaural”. All other “Output formats” work just fine. Any one else?
/Bauer
Thanks, I know! Doesn’t make a difference. Also, if I set the first playback bus to “Stereo” and then add a second bus and set that to “Atmos”, the first bus also changes to “Atmos”. If I then set the stereo bus to “Stereo”, the Atmos bus changes to “Surround”. Something very wierd is going on under the hood.
In Atmos, only the main bus is used. Don’t try to assign binaural to another bus.
Well, that’s not correct. In the instruction video for Atmos in Wavelab 13 https://youtu.be/hgVVqoHaxbc?si=o4BuzA2Ia3WrbQv2
(@ 5min ca), they do exactly what I do. Namely, the 7.1.4 output on the first
“Speaker arrangement” assigned to 12 discrete outputs, and then the binaural assigned to another dedicated stereo output (AES, just as in my case), to the second “Speaker arrangement”. But, when I switch the renderer to “Binaural”, silence. As I said before,
all other downmix formats produce sound on the second “Spekaer arrangement” except “Binaural”. Go figure 
The video is wrong. Do as I tell you: in the main bus, define both eg. your 7.1.4 speaks and the binaural outputs.
Ok, so how do you suggest I set up a dedicated binaural headphone output?
see the picture I have uploaded previously, this is the way.
Hi!
After some further testing I can confirm that choosing “binaural” in the Wavelab Atmos renderer on my Win machine results in silence. “Stereo”, and “Stereo direct” works just fine without any other changes than changing the output format in the Atmos renderer.
When choosing “Binaural” the meters indicate signal output, but no sound reaches the physical outputs, which are the same outputs used for “Stereo”, and “Stereo direct”.
Also, the exact same setup on my Macbook Pro works fine, and I can there switch between “Binaural”, “Stereo” and “Stereo direct” without any problem whatsoever.
Just to make sure, I uninstalled and reinstalled Wavelab 13.0.10 on my W10 machine, but without any improvement. So the problem seems to be with the Dolby Atmos Renderer in the Windows version of Wavelab 13.0.10. Am I the only one experiencing this?
That’s the problem: these should be different outputs.
See the picture I uploaded a few days ago.
These two output devices must be used exclusively for your headphones.
I found this thread after a few hours of searching for any possible WLPro13-specific detail I might’ve missed and finding nothing.
My busses were already setup, but I removed them and did it again, just to be sure.
Speaker Config 1 (top of list): Dolby Atmos 7.1.4 > ch.1-12
Speaker Config 2: Dolby Atmos > Binaural > ch.13-14
Speaker Config 3: Dolby Atmos > Stereo > ch.1-2
I remapped Dante Controller, from its usual Nuendo to Dolby RMU routing, to route directly from the host PC’s Dante PCIe card to the MTRX (DAC/mon-con) for the first 12 channels and 13 & 14 to the RedNet AM2 headphone amp.
With the native renderer set to 7.1.4 and speaker config 1, audio playback on the 7.2.4 system in the Atmos mastering room. When I switch it to Binaural, no audio is audible. I then switch to speaker config 2 and, despite the meters all indicating audio should be audible, there is still no audio coming from anything in the room. I just printed this client’s Atmos master today and exported this ADM from the RMU. So, I know everything works. The only thing that’s not working is WaveLab.
The only thing I haven’t tried is deleting all speaker configs except binaural and seeing if it works, but even if that were to work, its still not a viable solution to have to create and delete speaker configurations every time I want to jump between the 7.2.4 system and quickly checking in headphones.
Sorry to hear that you’re having problems, but thanks for confirming that it’s not only me.
Your problem seems to be identical to me, and you seem to be on PC to, right? Like I’ve said, I do not have this problem on my MacBook, so it’s obviously a Win-version bugg.
The solution is in this thread: