Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
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
Old 04-25-2017, 04:38 AM   #2
bFooz
Human being with feelings
 
Join Date: Jul 2010
Location: Slovakia
Posts: 2,588
Default

Still present in 5.40. (Win7 x64, Reaper x86)

bFooz is offline   Reply With Quote
Old 04-28-2017, 11:35 AM   #3
Dstruct
Human being with feelings
 
Join Date: Jul 2006
Posts: 12,480
Default

Confirmed (5.40 x64).
Dstruct is offline   Reply With Quote
Old 04-28-2017, 01:10 PM   #4
EpicSounds
Human being with feelings
 
EpicSounds's Avatar
 
Join Date: Jul 2009
Posts: 7,568
Default

I find this behavior pretty useful to be honest.
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
EpicSounds is offline   Reply With Quote
Old 04-28-2017, 06:25 PM   #5
Paul Eye
Human being with feelings
 
Join Date: Feb 2006
Location: Helsinki, Finland
Posts: 305
Default

Quote:
Originally Posted by EpicSounds View Post
I find this behavior pretty useful to be honest.
Exactly how do you find this useful? I guess the majority of us finds this rather irritating
Paul Eye is offline   Reply With Quote
Old 05-15-2018, 06:42 PM   #6
Paul Eye
Human being with feelings
 
Join Date: Feb 2006
Location: Helsinki, Finland
Posts: 305
Default

Still there in 5.80
Of course, if this is by design, could someone tell me what the practical use of this even is? I find it rather counterintuitive having to remember where I've soloed my tracks from.
Paul Eye is offline   Reply With Quote
Old 05-16-2018, 06:12 AM   #7
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by EpicSounds View Post
I find this behavior pretty useful to be honest.
I could see it being useful for mutes, but for solos it seems like it would be annoying more than anything, since a hidden soloed track prevents all nonsoloed tracks from playing.
Justin is offline   Reply With Quote
Old 05-16-2018, 08:24 AM   #8
EpicSounds
Human being with feelings
 
EpicSounds's Avatar
 
Join Date: Jul 2009
Posts: 7,568
Default

Quote:
Originally Posted by Justin View Post
I could see it being useful for mutes, but for solos it seems like it would be annoying more than anything, since a hidden soloed track prevents all nonsoloed tracks from playing.
very unlikely a user would solo and hide a track accidentally.

I do it when editing multitracks. I might solo kick and snare, plus the track I'm editing and only show the drum bus folder and the track I'm editing.

I frequently use shortcuts to show only selected tracks, hide selected track, and show all tracks. Hidden in both TCP and MCP. I don't use the track manager.

Don't remember exactly what I was working on a year ago when I made the comment.

I wouldn't want an action like 'unmute all' or "unsolo all" to apply to non-visible tracks.
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
EpicSounds is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 06:33 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.