Very Nice Wagner, thank you. Another useful way to use the SOURCES might be routing the headphone output from DOLBY ATMOS RENDERER to one of the sources in order to have the option to monitor Dolby's binaural as well.
I have found another problem with the Bass Management. When switching to another OUTPUT, there appears to be a residual amount of DC removing in the LFE channel (it doesn't show on Sphere's meters) but I see it in RME Totalmix and Digicheck. Switching back nd forth between the Bass managed and normal outputs, results in this DC signal building up. (I've reported it to support and waiting to hear back)
@@michaelgwagner I'd be curious to know if you could observe similar. It is obviously inaudible, but certainly visible. (on the output device, not Sphere)
Thanks for the video Michael. Have you tried to set your first output as a 7.1.4 layout and then insert for instance Halo Downmix set to stereo out? Would it output just the stereo downmix? Or even Virtuoso there to have a binaural out from a 7.1.4 input. I don´t have either of those plugins so I can´t try it.
@@michaelgwagner Ok. What instead of a 7.1.4 hardware interface, you assign a 12 channel virtual device, for instance Sphere 32 in a 7.1.4 layout to the first output for instance. Then place the Halo Downmix there. Then go to Loopback, create a new device whose inputs are the same Sphere 32 first 12 channels and the first two outputs (in Loopback are routed to LR on your physical interface using the Monitors tab. As the Halo downmix (or Virtuoso) will only output in those first two channels downmixed (LR) the signal should arrive to your interface or even the MAC headphone outs. Humm, just guessing here.
Hey Michael, you're way off here. Head tracking? Totally unnecessary. Some "self-proclaimed music engineers" are even calling it a gimmick. 😆 But for those of us who love spatial audio, let’s just keep rolling with the awesome tech like Sphere V2 from Ground Control. Seriously, you can have an entire 360-degree "Spatial Christmas party" around your tree! 🎄 Enjoy the ride, and may your holidays be as immersive as your sound experience! 💥
I disagree re head tracking. What many people have not yet realized is that the vast majority of consumers listening to Atmos do so on a head tracked system. These are not only the AirPods but an increasing number of other headphones/IEM as well. At the very minimum you should test how your audio sounds on these systems. 😉
@@michaelgwagner Okay, maybe give my sarcastic comment another read? 🤔 I design head-trackers with Arduino, so I'm a little too sensitive when TH-camrs like Colt from Tennessee spread total B.S. just because they don’t know what they’re talking about. Also, I'm pretty sure you two have some unresolved beef over Dolby Atmos... just saying. 😂
Very Nice Wagner, thank you.
Another useful way to use the SOURCES might be routing the headphone output from DOLBY ATMOS RENDERER to one of the sources in order to have the option to monitor Dolby's binaural as well.
Thanks! Interesting idea. 👍
Nice review Michael :) I think this is a great update to Sphere and there are loads of new possibilities for it :)
Thanks! I agree.
I have found another problem with the Bass Management. When switching to another OUTPUT, there appears to be a residual amount of DC removing in the LFE channel (it doesn't show on Sphere's meters) but I see it in RME Totalmix and Digicheck. Switching back nd forth between the Bass managed and normal outputs, results in this DC signal building up. (I've reported it to support and waiting to hear back)
Very interesting! Thanks for the info!
@@michaelgwagner I'd be curious to know if you could observe similar. It is obviously inaudible, but certainly visible. (on the output device, not Sphere)
Thanks for the video Michael. Have you tried to set your first output as a 7.1.4 layout and then insert for instance Halo Downmix set to stereo out? Would it output just the stereo downmix? Or even Virtuoso there to have a binaural out from a 7.1.4 input. I don´t have either of those plugins so I can´t try it.
You would need a 7.1.4 interface to do that, but that would work, yes. Otherwise you can just use the same trick I used for Virtuoso in the video.
@@michaelgwagner Ok. What instead of a 7.1.4 hardware interface, you assign a 12 channel virtual device, for instance Sphere 32 in a 7.1.4 layout to the first output for instance. Then place the Halo Downmix there. Then go to Loopback, create a new device whose inputs are the same Sphere 32 first 12 channels and the first two outputs (in Loopback are routed to LR on your physical interface using the Monitors tab. As the Halo downmix (or Virtuoso) will only output in those first two channels downmixed (LR) the signal should arrive to your interface or even the MAC headphone outs. Humm, just guessing here.
You would have to route that somewhere. Then yes.
@@michaelgwagner Ok, thanks!
Hey Michael, you're way off here. Head tracking? Totally unnecessary. Some "self-proclaimed music engineers" are even calling it a gimmick. 😆 But for those of us who love spatial audio, let’s just keep rolling with the awesome tech like Sphere V2 from Ground Control. Seriously, you can have an entire 360-degree "Spatial Christmas party" around your tree! 🎄 Enjoy the ride, and may your holidays be as immersive as your sound experience! 💥
I disagree re head tracking. What many people have not yet realized is that the vast majority of consumers listening to Atmos do so on a head tracked system. These are not only the AirPods but an increasing number of other headphones/IEM as well. At the very minimum you should test how your audio sounds on these systems. 😉
@@michaelgwagner Okay, maybe give my sarcastic comment another read? 🤔 I design head-trackers with Arduino, so I'm a little too sensitive when TH-camrs like Colt from Tennessee spread total B.S. just because they don’t know what they’re talking about. Also, I'm pretty sure you two have some unresolved beef over Dolby Atmos... just saying. 😂
Haha, sorry for that. 🤣
@@michaelgwagner No problem 😀