Shift-R: Automation Mode Inactive

[Todd R]

If replace a region with automation off and you had automation written on top of said region, automation will be stripped...

from the User Manual:
"Replacing MT Entries! Placing the MT Cursor on an entry and pressing [Shift-R] will replace the entry with the currently
selected Region Listbox region. If Automation Mode is active when you engage the operation,
automation entries are preserved."

I didn't realize this until today...it's amazing how there is so much to learn...and I can see this as an excellent way to strip automation
altho, there are many, many ways to strip automation in SS

In my work, 95% of my automation in SAW MT is purposefully placed within region boundaries to keep the automation sync'd
to the audio...so, if the region gets moved...automation goes with the audio

[MMP]

I have a macro on my x-keys that seeks the start of the region my cursor is on (including the leading softedge if there is one) and marks B, then seeks the end of the region ( again with trailing softedge if there is one) and marks end, and then sets the cursor to the very front of the region. One key, and the region is ready for any automation move I want to make and ready to play that region. It has been a very fast workflow with other similar macros.

In my work, 95% of my automation in SAW MT is purposefully placed within region boundaries to keep the automation sync'd
to the audio...so, if the region gets moved...automation goes with the audio

[Dave Labrecque]

If replace a region with automation off and you had automation written on top of said region, automation will be stripped...

from the User Manual:
"Replacing MT Entries! Placing the MT Cursor on an entry and pressing [Shift-R] will replace the entry with the currently
selected Region Listbox region. If Automation Mode is active when you engage the operation,
automation entries are preserved."

I didn't realize this until today...it's amazing how there is so much to learn...and I can see this as an excellent way to strip automation
altho, there are many, many ways to strip automation in SS

In my work, 95% of my automation in SAW MT is purposefully placed within region boundaries to keep the automation sync'd
to the audio...so, if the region gets moved...automation goes with the audio

I was not aware of the swap region/keep automation feature. Cool. I have other ways of doing that, but not as quick and simple as this. What else don't I know?

It's long been a SAW best practice to never (there may be exceptions) create automation outside of region entry boundaries. I.e. always create automation within region entry boundaries.

[Todd R]

I was not aware of the swap region/keep automation feature. Cool. I have other ways of doing that, but not as quick and simple as this. What else don't I know?

It's long been a SAW best practice to never (there may be exceptions) create automation outside of region entry boundaries. I.e. always create automation within region entry boundaries.

Wow, I'm glad I could shed light on sumpfin =-D
Indeed, so much to not know, eh? There is so much we'll never know

Well, the keeping automation within region boundaries falls on it's face when said automation is in a RETURN or OUTPUT (Bus) track

[Dave Labrecque]

Well, the keeping automation within region boundaries falls on it's face when said automation is in a RETURN or OUTPUT (Bus) track

True 'nuff. If you're gonna move stuff around, you need to stay vigilant of such things. I guess that's why Bob invented the Slip-Track functionality.

[Dave Labrecque]

I have a macro on my x-keys that seeks the start of the region my cursor is on (including the leading softedge if there is one) and marks B, then seeks the end of the region ( again with trailing softedge if there is one) and marks end, and then sets the cursor to the very front of the region. One key, and the region is ready for any automation move I want to make and ready to play that region. It has been a very fast workflow with other similar macros.

Show-off.

[UpTilDawn]

True 'nuff. If you're gonna move stuff around, you need to stay vigilant of such things. I guess that's why Bob invented the Slip-Track functionality.

Yup...
It took awhile to sink in, but I eventually learned to use marked areas for the bulk of my track moving chores (over Select Mode). The slip-track option is killer. Just have to remember to make return and output tracks part of your group move, if including automation on those! (I used to rely on Select Mode way too much.)

You can write automation outside of region boundaries too, especially helpful if you need to include 'X' fade slopes at either end in the automation. Helpful, also, is using alt + left/right arrow to go exactly to the edge of the boundary 'X' fade slope, when marking the start and end points of a marked area (with or w/out automation).