[Rwp] creating custom action chains

James Teh jamie at nvaccess.org
Thu Sep 10 02:01:05 EDT 2015


It's latch, not flash.

Touch means that automation starts getting recorded when you first 
adjust (touch) the parameter and stops when you stop touching it. So, 
once you stop touching it, if there was previously recorded automation, 
it won't be overwritten.
Latch means that automation starts getting recorded when you first touch 
the parameter and then keeps getting recorded until you stop the 
transport. So, if there was previously recorded automation after you 
stopped touching the parameter, it will be overwritten.
Write means that automation gets written as soon as you start the 
transport and stops being written as soon as you stop it. In other 
words, previously recorded automation will be overwritten, regardless of 
when/whether you touch a parameter.

I seem to recall that from some testing I did a while ago, touch seemed 
to behave the same as latch for me. If I'm right (and I'd need to 
re-test to be sure), I think the reason is that REAPER doesn't seem to 
realise that we've stopped touching a parameter when we adjust it with 
an extension like OSARA. In contrast, REAPER probably has logic to guess 
when a mouse user has stopped moving the parameter; e.g. the mouse stops 
moving.

Jamie

On 10/09/2015 3:25 PM, Justin Macleod via RWP wrote:
> What is flash? I assume that touch is last touched parameter. I posted on
> here a while ago about what flash meant and no-one seemed to know,
>
> Justin
>
> -----Original Message-----
> From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of Chris Belle
> via RWP
> Sent: 10 September 2015 06:23
> To: Reapers Without Peepers <rwp at bluegrasspals.com>
> Cc: Chris Belle <cb1963 at sbcglobal.net>
> Subject: Re: [Rwp] creating custom action chains
>
> One db isn't bad,
> that's 20 stacks of the 0.05 db.
>
> With stacking one can make what ever intervals they need.
>
> Automation is sure different in reaper than sonar, but I'm learning how to
> work with it, and it's actually better in some ways, we can actually edit it
> or over-write it in useful ways, just have to figure out when to use touch,
> and when to use latch, and so on and so forth.
>
>
> On 9/9/2015 11:24 PM, Justin Macleod via RWP wrote:
>> I thought about using 1 db gaps. My concern was that the increments
>> would be too large to go unnoticed and that you might have zipper
>> noise or a jurky fade, bearing in mind that you would have to mash the
>> key with individual presses to keep count of how many decibels of gain you
> were applying.
>> Is that actually the case?
>>
>> Justin
>>
>> -----Original Message-----
>> From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of Chris
>> Belle via RWP
>> Sent: 10 September 2015 04:57
>> To: Reapers Without Peepers <rwp at bluegrasspals.com>
>> Cc: Chris Belle <cb1963 at sbcglobal.net>
>> Subject: Re: [Rwp] creating custom action chains
>>
>> Gosh you know, I'm chuckle headed sometimes 'grin'.
>>
>> That was mentioned, but I thought it might be the un-do instead if you
>> mess up stacking your actions or something.
>>
>> I'll go edit or remake them and see if it works.
>>
>> On 9/9/2015 9:48 PM, Snowman via RWP wrote:
>>> Chris,  there is a checkbox for consolidating undo points,  which
>>> suggests that will take care of that.
>>>
>>> ----- Original Message ----- From: "Chris Belle via RWP"
>>> <rwp at bluegrasspals.com>
>>> To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
>>> Cc: "Chris Belle" <cb1963 at sbcglobal.net>
>>> Sent: Wednesday, September 09, 2015 9:33 PM
>>> Subject: Re: [Rwp] creating custom action chains
>>>
>>>
>>>> Yep, touch mode seems to be the most friendly about following you
>>>> around, obviously.
>>>>
>>>> But that stacked actions thing has one down side, if you want to
>>>> undo, you have to undo a million things because each one is counted
>>>> separately.
>>>> It's not counted like one action.
>>>>
>>>> But we're getting a tiny bit closer to the wonderful automation I am
>>>> used to in sonar.
>>>>
>>>> But we must cowboy up and learn this new DAW if it kills us, Ha.
>>>>
>>>>
>>>> On 9/9/2015 9:15 PM, Chris Belle via RWP wrote:
>>>>> Hey, I got it to work with NVDA by staying and clicking that
>>>>> default action numpad insert plus numpad enter till it went in
>>>>> there a bunch of times.
>>>>>
>>>>> Hurray.
>>>>> I can have my one db volume down that should work with automation now.
>>>>> riding a fader.
>>>>>
>>>>> I'm sure there are better ways to do this, but this is my work
>>>>> around for now.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 9/9/2015 9:06 PM, Chris Belle via RWP wrote:
>>>>>> Well by golly I have jaws too, I'll just try that, can you keep
>>>>>> clicking to add it several times?
>>>>>>
>>>>>> Like makin that volume thing alt down arrow and alt up arrow stack up?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 8/16/2015 2:07 AM, serge monahov via RWP wrote:
>>>>>>> Hi, Patrick!
>>>>>>> With JAWS I  just double click on action in first list and it
>>>>>>> appears in second one.
>>>>>>>
>>>>>>> hth
>>>>>>> Best regards
>>>>>>> Serge
>>>>>>> ----- Original Message ----- From: "Patrick Perdue via RWP"
>>>>>>> <rwp at bluegrasspals.com>
>>>>>>> To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
>>>>>>> Cc: "Patrick Perdue" <patrick at pdaudio.net>
>>>>>>> Sent: Friday, August 14, 2015 11:36 AM
>>>>>>> Subject: [Rwp] creating custom action chains
>>>>>>>
>>>>>>>
>>>>>>>> Well, after using Reaper for about six years, I finally have a
>>>>>>>> need to create a custom action based on a chain of existing
>>>>>>>> actions. It seems the default way of doing this is to create a
>>>>>>>> new action in the actions list, then drag and drop actions into
>>>>>>>> a list in your preferred order of operations. I'm having no luck
>>>>>>>> getting this done with NVDA. Honestly, I'm feeling pretty stupid
>>>>>>>> at the moment, as I'm sure there is another, or at least a
>>>>>>>> better way to do this.
>>>>>>>> Any tips are greatly appreciated.
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>> _______________________________________________
>> 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
> _______________________________________________
> 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



More information about the RWP mailing list