[Rwp] Automation

[Justin Macleod]

I was just wondering about that. I have a track I want to put automation on.
After learning to deal with the fact that I needed to let the track play to
the end for the automation to take the way I want, not having known about
that action thanks Jamy, it worked well. Only thing is now I wanted to apply
an automated effect to the same track. Using Daniel's method, I set the
parameter to be automatable but it whipped out my volume automation. What do
you do if you need to automate more than one parameter per track without
whipping out what you've previously done?

Justin 

-----Original Message-----
From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of Jim Snowbarger
via RWP
Sent: 08 June 2015 18:24
To: 'Reapers Without Peepers'
Cc: Jim Snowbarger
Subject: Re: [Rwp] Automation

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