CakeAlexS
If a design flaw how come the mute buttons work? Are mute buttons designed differently to solo buttons when it comes to signal path or is there some sort of quantum black hole between each button? :)
Anyway gonna think of way of demoing this properly over the next few weeks...
There's no need to demo anything. The limitation is well understood, and I'm sure the Bakers will get around to
adding the capability to intelligently solo soft synth output tracks on the other side of a drum map eventually.
To hear a MIDI driven synth, it has always been necessary to solo both the MIDI track driving it and the audio track echoing the output. With hardware synths, it's still necessary to do that manually or by deliberately grouping the buttons or using Solo Override to keep audio outputs soloed. With soft synths, SONAR added the
convenience of linking the solo buttons for you.
But drum maps pre-date soft synths; in fact, they pre-date support for audio; they're just MIDI translators. So when you assign the output of the MIDI track to a drum map, SONAR currently has no way if determining what audio track(s) are on the other side of the synth(s) on the other side of the port(s) specified in the drum map or what you would or wouldn't want soloed when you solo the MIDI track. Adding that capability would require writing a significant amount of new code - i.e.
adding a feature.
And the solo buttons are working just l like they always have, limiting the output to tracks that are soloed. It just happens that it takes the output of
two tracks for a soft synth to be heard. Mute isn't affected the same way, because it only takes one of the two tracks to be muted (or not soloed) to silence the synth.
None of this is a bug in the conventional sense of a feature that is intended and advertised to work but does not. It's a non-existent feature.