I could have sworn when I first installed X3 that soloing an individual drum track using a drum map (midi tracks and superiour drummer remained linked in soloing) that it worked.
 
Now it does not.  Soloing the folder works but thats not an option in console view nor what one always wants if say you want to hear just the kick.
 
Does it work for you? Could it be a change in X3b?  Or is my sanity in question?

Maybe my quesion wasn't clear....
 
If you have a midi track assigned to superiour drummer through a drum map, then solo the midi track, can you still hear the drum audio track?
 
X3b

This has always been a long standing bug with drum maps.
 
I thought I read somewhere that this functionality was working in X3, but it appears it's still broken.
 
Send a feature request in:
 
http://www.cakewalk.com/s...ct/featurerequest.aspx

Yes and I was certain when I first installed X3a it was working, now on b it's not,  unless I was mistaken?

I'll check on my system when I get home in about 3 hours.
I'm currently on X3 (no updates)

How about enabling Solo Override (Shift+Solo) on the audio track(s) for the drums? Then the solo state of the MIDI track(s) determines whether you hear the synth. I could be missing something, but it seems to me that would solve the problem (until the Bakers get to it - kind of  sticky wicket, because they'd have to read the drum map, and manage audio track solo states based on output port assignments, and keep up with changes).
 
For cases where there's only one MIDI and audio track (mixing done in the synth's GUI), just grouping the solo buttons should do the trick. I do this with hardware synths all the time since they don't "know" they're connected.
 
 
 
 
 
 

Yep, it's definitely still broken.
 
I think something weird is happening with one of the default maps for Session Drummer - it seems to be triggering a different vsti.
 
Got some troubleshooting to do 

Someone stated when X3 came out that the solo function with drum maps was fixed....but then stated they had made a mistake.
 
It still works the same as it always has...or I should say it "doesn't work" the same as it always has... :) .
 
Being able to solo a specific drum would be really handy.

Well that was weird - the Drum Map I inserted - "Session Drummer Default" had the output parameter for each drum artic set  to Dimension Pro, and triggering the Bass patch that was loaded.

brundlefly
How about enabling Solo Override (Shift+Solo) on the audio track(s) for the drums? Then the solo state of the MIDI track(s) determines whether you hear the synth. I could be missing something, but it seems to me that would solve the problem (until the Bakers get to it - kind of  sticky wicket, because they'd have to read the drum map, and manage audio track solo states based on output port assignments, and keep up with changes).
 
For cases where there's only one MIDI and audio track (mixing done in the synth's GUI), just grouping the solo buttons should do the trick. I do this with hardware synths all the time since they don't "know" they're connected.
 
 
 
 
 
 

Yes, your workaround is perfectly feasible. At least that way, the Mute & Solo buttons in the Drum Map work as expected and like you say, the whole vsti solo status is controlled by the Midi track Solo button.