Windows 10, RME HDSP MADI, SL 11 … all latest drivers and versions.
I’ve just installed the upgrade to SL 11, so please bear with me if this is a known issue (… forum search didn’t show any related threads, though).
I have a perfectly working 5.1.4 (or actually Auro 10.1) output routing when I start playback, but as soon as I solo one of the channels, the audio is routed to all (!) channels offered by the ASIO driver, which is quite a lot on a RME MADI card. 8-/ … needless to say, the result is unusable.
There are no obvious errors in SL’s Preferences. I’ve also tried various options in the Prefs without success. Any suggestions?
It’s actually a new feature of SpectraLayers 11 to ease monitoring of individual channels, but in some cases that might be too much indeed. I’ll add an option to turn it off in the Device Preferences with the next patch.
Thanks for chiming in, @Robin_Lobel . I have to admit that I don’t understand the “feature”. Is it indeed intended behaviour ATM that the solo-function ignores the existing routing and uses all 64 channels (in my case) of the ASIO driver for output …? Or did you mean to say something else?
In any case: The expected effect of the solo function would be that the soloed channel is played in situ, using the routing assigned it the Prefs.
Listening with stereo headphones and working on stereo material I myself think this feature is pretty useful. If I need to concentrate on specific things in only one channel, I get information on both ears instead of only one, where I might not be able to discern some of the details.
But if I just want to check the spacial arrangement of a channel, this feature is not the best indeed. And having never worked with a multichannel listening setup (more than stereo that is), I can only image the disadvantages.
An option to toggle this on or off is a nice idea.
@Dietz Oh, I understand now, yes indeed that’s an issue. If it plays on all device channels regardless if they were assigned to a speaker or not, that was not the intended behavior… I’ll fix this.
@Laturec That will indeed be a feature in the upcoming patch 5.
