More Midi / Drum Map Weirdness

Someone else may get to it before I do but I will try it tonight.
 
Can you create two projects (with MIDI only) and PM me a link to them? Sometimes it's easier to see what others did without incorrectly trying to reproduce it.

This is what I was mentioning in the other thread. Applying a drum map now effectively applies a hidden Solo Override to the MIDI track(s) that has the side-effect of causing the Mute button in the parent track not to work, but lane and clip muting will still work.
 
Soloing a Drum-mapped MIDI track has never worked, and still doesn't. The new functionality supporting soloing audio outputs(s) and not having to also solo the MIDI track does not address the reverse case.
 
Other threads have discussed the many helpful-but-imperfect workarounds involving the use of folders and Solo Override.

snaut2000
But soloing a Drum-mapped midi track workes fine in X3, when the parent track is soloed as well.

I'll have to check this but, yes, because of the way this works now, you cannot solo a MIDI track to exclude another that is using a drum map (the same one or otherwise). The intent is that you'll do all isolation by having separate audio outs for the different kit pieces, and soloing those as needed while all drum-mapped MIDI tracks continue to be active. If you really need to isolate different drum-mapped MIDI parts by soloing, I think you'll have to put them in lanes of the same MIDI track, and solo lanes as needed.
 
I have to say I don't think this change was well advised - too much fallout for users who are used to the historical functionality. I think the only full and transparent solution would be to have drum maps be fully mute/solo-aware in both directions with potentially multiple MIDI tracks, synths and audio outputs per synth - not a trivial task, but necessary.
 
 

For my workflow, the new way is the BEST.
 
I would not (normally) build multiple MIDI tracks for a drum kit. Therefore solo/nuts of a MIDI track is pointless to me. I (almost always) build a drums folder with individual outs and think of the audio (VSTi output) as the thing I want to solo/mute. 
 
If I want to solo the whole kit I just solo the drum bus. Simples.
 
Yes, brundlefly there seems to be fallout with other workflows but that seems to be for those that veer from the default behavior of a drum folder as it is created by SONAR

Please continue here:

http://forum.cakewalk.com/CWBRN31230-Mute-not-working-on-Midi-drum-track-in-Sonar-Platinum-m3165865.aspx
 
For clarity and to avoid dupes I'm freezing this thread... thanks...