[Rwp] Automation

[Chris Belle]

I don't know why they did it that way, just doesn't make sense to me.



On 6/8/2015 12:23 PM, Jim Snowbarger via RWP wrote:
> And try not to want to muck with automation at an earlier point in the
> project than some previouslly constructed automation on that same track.
> Otherwise, you will wipe out, or generally screw up, that later event.
>
>
> -----Original Message-----
> From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of James Teh via
> RWP
> Sent: Monday, June 08, 2015 11:27 AM
> To: Reapers Without Peepers
> Cc: James Teh
> Subject: Re: [Rwp] Automation
>
> On 8/06/2015 2:33 AM, Chris Belle via RWP wrote:
>> That reaper default behavior of not staying put when you write
>> automation but snapping back to the original drives me nuts.
> Try the action Automation: Write current values from cursor to end of
> project.
>
> Jamie
>
> --
> 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
>