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

[James Teh]

Nope, doesn't work. The thread info is contained in the message headers, not the body or subject.

Sent from a mobile device

> On 26 Feb 2016, at 10:56 AM, "theoreomonster at reaperaccess.com" <theoreomonster at reaperaccess.com> wrote:
> 
> The trick to getting changing the subject to work  as a new  thread is deleting the message chain so it will get sent to the list as  a brand new message without a history 
>> On Feb 24, 2016, at 5:31 PM, Chris Belle <cb1963 at sbcglobal.net> wrote:
>> 
>> All right pard,
>> my bad, I get lazy sometimes and don't want to look through the
>> junk and find the address.
>> I always do my filters on the subject lines,
>> which works well enough for me in separating messages most of the time.
>> 'grin'.
>> yeh, I thought it was like you said,
>> that related issue,
>> so that's why i didn't post it on github,
>> but thought I'd mention it anyway here just because.
>> 
>> 
>>> On 2/24/2016 4:42 AM, James Teh wrote:
>>> 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
>>> 
>>> 
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>> 
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
> 
> 
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp