solo\mute inconsistent behaviour

[Levitanus]

When track is muted - none of items is being proceed, which is from my point of view is correct behaviour.
Opposite to this, when any track in solo - at least midi items are still sending their messages to the FX chain, where they are been proceed.
This is bad from several points of view:
- within heavy VSTi, CPU and disks still work as hard as with full-arrangement processing. And with "true-mute" it would be majority reduced.
- within multi-tab (or multi-PC) setup with ReaStream or hardware routing:
I see several possibilities to mark with routing such complex setups for proper and stable work of solo for track with hardware\outboard send with return to other track (premixed return from net host), but can't see solution for excluding such track from processing if any other track has solo state. This problem affects at first place setups with hardware monitoring of outboard\reastreamPC
- I don't see any reasons for making difference between track which is muted by mute button or by soloing other track

Thanks for response

[Vadium]

+1

see: https://youtu.be/-F71LbrPhJ4

[Thonex]

I think you need to uncheck this preference:

[Vadium]

Originally Posted by Thonex

I think you need to uncheck this preference:

This option already switched on. This topic isn't about plug-ins activity but muting sends of MIDI messages from unsoloed tracks. Because in a case when we send midi over a network to other instance of reaper (or to hardware midi device), this option doesn't matter

[Obosya]

Actually, inconsistency is not only about midi.

Little experiment:
Simple project with 5 audio tracks, no midi, no any fx.
Trying to render an mp3:

1. All tracks "active" - 11.0x realtime.

2. 4 of 5 tracks muted - 20.3x realtime.

3. 1 of 5 tracks soloed - 10.6x realtime. WHAT? Shouldn't it be the same as in 2nd case?


v5.985/x64, Windows 10.