[Rwp] OSARA reaper reacting to last touched track when in peak watcher

[James Teh]

Sounds like an instance of this issue 
<https://github.com/nvaccess/osara/issues/77>. In short, when you nudge 
the master volume, REAPER sets the master as the last touched (current) 
track. IMO, this is a REAPER bug... or at least an undesirable 
behaviour. I believe Scott is going to try to convince Cockos of this. :)

Btw, it'd be great if you can start a new message when you start a new 
topic, rather than replying to a previous one and changing the subject 
line. When you do the latter, it actually becomes part of the previous 
thread as far as email apps are concerned, which means that your 
messages get mixed in with the other (unrelated) thread. Also, it means 
people like me who delete entire threads that aren't of interest based 
on the subject line will miss your messages. :)

Jamie

On 24/02/2016 6:08 PM, Chris Belle wrote:
> Hey, love the new peak watcher implementation.
> But am noticing that when I do something like adjusting the master 
> volume, even if I have set the first or second peak watcher to monitor 
> the current or master track,
> it wants to jump to the master track.
> It's like it thinks I set it to monitor the master track even though I 
> didn't.
> If I focus the current track and then check, things are right again.
> If I need to I can put this on git hub,
> but I think something similar was already reported.
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie at nvaccess.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20160224/9a75940e/attachment.html>