SuperG
Hmm, to be honest...
 
I'm not fond of having multiple midi tracks for drums. I prefer to see all the percussion on one (PRV) page. A relational view seems to work better.
 
A lot of the files I run across (usually internet sourced) with drums like these seem to done on workstation keyboards - I'm not sure why though...

I'm not sure which post that's directed at...? Maybe I missed something, but I don't really see anyone advocating multiple MIDI tracks here - mainly multiple synth outputs. But even if they were, it wouldn't make any difference; you can see and edit multiple tracks in the PRV at the same time.
 
And the Solo Override strategy I mentioned works in either case, also.

I'm not sure which post that's directed at...? Maybe I missed something, but I don't really see anyone advocating multiple MIDI tracks here - mainly multiple synth outputs. But even if they were, it wouldn't make any difference; you can see and edit multiple tracks in the PRV at the same time.

 
I'm not directing at anyone in particular... just relating...
 
I had thought about just that - you can do multiple tracks in PRV - after I posted, unfortunately. Maybe I am mistaken, for me, multiple synth outs are a given, and sticking things in a folder doesn't even register to me as issue.
 
I've had a few grunts about multi-synth-out mapped drum soloing - but I usually work around it. That's just me - if it's not bad enough, I won't invest more time than the work around.

As for the Track Folder method (which I also use), you can't solo a track folder in the CV, PRV or by a keyboard shortcut. As for Solo Override, as I mentioned in my first post, it gets disabled if you turn off the Control Bar's (global) Solo button. I sent in a FR to change this behavior only last week.

Jlien X
As for Solo Override, as I mentioned in my first post, it gets disabled if you turn off the Control Bar's (global) Solo button. I sent in a FR to change this behavior only last week.

True, but that's pretty easy to avoid if you're aware of it. Personally I've almost never had occasion to touch that global button.

brundlefly

Jlien X
As for Solo Override, as I mentioned in my first post, it gets disabled if you turn off the Control Bar's (global) Solo button. I sent in a FR to change this behavior only last week.

True, but that's pretty easy to avoid if you're aware of it. Personally I've almost never had occasion to touch that global button.

So, when you're monitoring only the drums, bass and guitars, if you want to unsolo these tracks you unsolo the track folders for these instruments one by one? Isn't it faster to use the global solo button?

I tried all the workarounds, none of them worked for me. I can solo in the piano roll view for the drum map however. It's a pain and the main workflow happens in console view....  I see plenty of interesting workarounds that can work for some however I don't see how this makes it any less a bug (these workarounds wouldn't work otherwise for instance). This really should get addressed for X3E IMHO (so there's still time as it's coming out in late March I've just heard).

brundlefly
 
 
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.

This was a great explanation.  I still hate the flaw in the design (if that is what we are calling it),  but now at least I understand it.  I've been using the workarounds posted in this thread for a long time now (usually with a bus instead of a folder).  Its a pain, but I can't live without drum maps.

brundlefly
And the Solo Override strategy I mentioned works in either case, also.

Are you saying that with a drum map deployed and Solo Override on I can (in TV or CV) simply click solo my kick audio track of a multi-out folder without having to first click solo the folder (in TV) or the MIDI (in CV)?
 

Its a pain, but I can't live without drum maps.

 
Same here!

Because of the bug (errrm design) I've purposely stayed away from drum maps.
 
I need to understand brundlfly's method mo bettah.
 
I will give it a try when I return to my DAW.