It would have to be an option, because it would also disable the ability to solo a midi channel, then switch instruments (that are routed to different audio tracks) by changing the send channel on your controller.
 
That would be very bad me thinks :-)
 
I think the answer to this might be "Don't Solo the MIDI Channel".
Sound crazy ?. Try it.
 
Soloing the audio track also solos all the MIDI tracks, because it too, has no real way to tell which MIDI track you might decide to send data from.
 
I think it's a case of choosing which you solo (audio or midi), and then that's the group you have to take notice of. Maybe hide the others ?.
 
To me, the current behaviour makes total sense, and I think would essentially "break things" to change it.
 
Cheers - Cliff

Jlien X
I just checked S1, and yes, the behavior is exactly the same.

That's what I would expect. I think there's an inherent limitation of VSTi technology that the host has no way of knowing what routing of MIDI-to-Instruments-to-Outputs is going on inside the synth so it has to include all outputs when soloing a MIDI track that points at that synth to ensure that whatever instrument that track is driving is audible. Possibly VST3 addresses this somehow, but I don't know.

brundlefly

Jlien X
I just checked S1, and yes, the behavior is exactly the same.

That's what I would expect. I think there's an inherent limitation of VSTi technology that the host has no way of knowing what routing of MIDI-to-Instruments-to-Outputs is going on inside the synth so it has to include all outputs when soloing a MIDI track that points at that synth to ensure that whatever instrument that track is driving is audible. Possibly VST3 addresses this somehow, but I don't know.

I also think that is the case. Solo/mute is not really bugging me, though ... Try freezing one track that's routed to a sysnth in a Kontakt rack and it'll freeze all that is in the rack, which even on a fast DAW takes a while if you have e.g. Abbey Road drums routed via 16 Outs in the same rack as the synth you want to freeze.
 
That's why it's more conventient to have several instances of Kontakt, BUT recently I had troubles where one instance of Kontakt would start behaving badly (not wanting to freeze at all / causing crashes at project open) but I'm not sure if that's due to multiple K5 instances, Sonar project migration from X2 to X3, project corruption or just a K5 issue ... life's just too complicated to know anything for sure ;-)
 

I find that if you group the solo buttons by right-clicking the control and selecting a color/Letter from the midi track to the audio track you get the behavior you intend. The mutes would have to also be grouped individually if you want both to work. I tried this with session drummer using separate midi tracks going to separate audio outs like this:
 
Snare Midi Solo - Red Group
Snare Audio Return Solo - Red Group
Kick Midi Solo - Green Group
Kick Audio Return Solo - Green group
etc...

Lance Riley [Cakewalk]
I find that if you group the solo buttons by right-clicking the control and selecting a color/Letter from the midi track to the audio track you get the behavior you intend. The mutes would have to also be grouped individually if you want both to work. I tried this with session drummer using separate midi tracks going to separate audio outs like this:
 
Snare Midi Solo - Red Group
Snare Audio Return Solo - Red Group
Kick Midi Solo - Green Group
Kick Audio Return Solo - Green group
etc...

Interesting, I will try this. I did toy with the idea of playing with grouping but I thought it would just confuse me even more...

brundlefly

Jlien X
I just checked S1, and yes, the behavior is exactly the same.

That's what I would expect. I think there's an inherent limitation of VSTi technology that the host has no way of knowing what routing of MIDI-to-Instruments-to-Outputs is going on inside the synth so it has to include all outputs when soloing a MIDI track that points at that synth to ensure that whatever instrument that track is driving is audible. Possibly VST3 addresses this somehow, but I don't know.

Yes, the behaviour is exactly as it should be, it would break what is and should be "Normal" to change it.
As I said above, if all the audio tracks did not get soloed too, that would disable 9or "Break") the ability to solo a midi channel and switch instruments (that are routed to different audio tracks) by changing the send channel on your controller.
 
If you solo and audio track, you'll see that automatically solos all the MIDI tracks - which also makes sense since it has no way of knowing which MIDI track you might send on.
 
It's not a limitation of the technology, a VSTi doesn't and shouldn't care about where you're routing or sending data from. It's only job is to respond to the data when it's received.
 
Cheers - Cliff
 

sharke

Lance Riley [Cakewalk]
I find that if you group the solo buttons by right-clicking the control and selecting a color/Letter from the midi track to the audio track you get the behavior you intend. The mutes would have to also be grouped individually if you want both to work. I tried this with session drummer using separate midi tracks going to separate audio outs like this:
 
Snare Midi Solo - Red Group
Snare Audio Return Solo - Red Group
Kick Midi Solo - Green Group
Kick Audio Return Solo - Green group
etc...

Interesting, I will try this. I did toy with the idea of playing with grouping but I thought it would just confuse me even more...

 
Lance, that's what I meant in my earlier post. I used to do it but I stopped it. Because, as I said, soloing doesn't work properly in PRV's Track pane. Try it. You'll see what I mean.

Is this SOLVED, then?