View Single Post
Old 12-20-2016, 12:33 PM   #1
Paul Eye
Human being with feelings
 
Join Date: Feb 2006
Location: Helsinki, Finland
Posts: 305
Default Bug with exclusive solo and hidden tracks

As the title says, there's a bug when exclusive soloing tracks that are hidden, either from TCP or MCP. It seems a bit complicated but I'll do my best in trying to explain the situation.
I have a simple .rpp attached, consisting of 3 tracks:

1: Not hidden
2: TCP hidden
3: MCP hidden

Basically the bug is that if I exclusive solo track 3 (from the TCP obviously) and then track 2 (from the MCP), the solo for track 3 isn't cleared.
Then again, if I first exclusive solo track 1 from the TCP and then track 2 from the MCP the solo for track 1 is cleared. If I then exclusive solo track 1 from the TCP, the solo for track 2 isn't cleared, but if I do the same for track 1 from the MCP instead, the solo for track 2 is cleared.
So it seems that this bug happens only after a hidden track is exclusive soloed, and another track is exclusive soloed from the other CP.
Of course the first solo doesn't need to be explicitly "exclusive" if no solos are active.

This also affects unsolo all, hidden tracks don't get unsoloed if unsolo all is done from a different CP than where the (exclusive) solo was done from.
For example: solo tracks 1 and 3 from the TCP, then unsolo all from track 1 in the MCP and track 3 is still soloed. This works on more tracks too: all soloed hidden tracks are unsolo all-able (yes, that's a silly sounding term) only from the CP they were soloed from.

I think that's about it, if I come up with more scenarios I'll add some info.

REAPER 5.30 (haven't done anything in REAPER for quite some time so I have no idea how long the bug has been there).
Attached Files
File Type: rpp hidden_tracks_exclusive_solo_bug.rpp (3.0 KB, 277 views)
Paul Eye is offline   Reply With Quote