Logic Pro 8 how do you copy automation data between tracks?

Sort by date Sort by votes
Here's a quick and dirty way that will get the job done:

* Turn your track based automation into region based automation.

* Copy your region onto your new track.

* Covert the automation back to track automation on the new track.

* Delete the region. Save the track automation when prompted.


It should to the trick....
 
Upvote 0
Eli said:
Here's a quick and dirty way that will get the job done:

* Turn your track based automation into region based automation.

* Copy your region onto your new track.

* Covert the automation back to track automation on the new track.

* Delete the region. Save the track automation when prompted.


It should to the trick....
Click to expand...

Why that complicated? It works pretty much like copy regions. Use the Automation Select tool to rubberband-select any portion of automation data you like (or click with held Option key in front of first automation node to select entire automation on that automation sub-track) and use the standard copy/paste key commands. Just make sure no region is selected when you copy the automation. To copy an existing automation to another automation parameter/sub-track on that track hold the Command key while selecting the target automation parameter.

It's that simple that I had the impression the question wasn't meant serious😉

Best...

Manfred
 
Upvote 0
Hi Manfred,

I hadn't realized you could copy and paste track based automation from track to track. You learn something new every day with Logic!
 
Upvote 0
Use the Automation Event List (key command only.)
1. Open and select ALL.
2. Command-C to copy.
3. Go to the second track and click in a staring node.
4. Open the list and hit Command-V for paste.
 
Upvote 0
Petrosil said:
Why that complicated? It works pretty much like copy regions. Use the Automation Select tool to rubberband-select any portion of automation data you like (or click with held Option key in front of first automation node to select entire automation on that automation sub-track) and use the standard copy/paste key commands. Just make sure no region is selected when....
Click to expand...

Why that complicated? 🙂

Just rubber-band the automation you want to copy (with Shift) - this will ensure that the underlying region is deselected - then use Copy/Paste.
 
Upvote 0
Jay Asher said:
Use the Automation Event List (key command only.)
1. Open and select ALL.
2. Command-C to copy.
3. Go to the second track and click in a staring node.
4. Open the list and hit Command-V for paste.
Click to expand...

I always find that it pastes two beats later than it's supposed to, so watch for that if you use this method. I didn't know about the Automation Selection tool, though - have to read up on that!
 
Upvote 0
sonnykeyes said:
Jay Asher said:
Use the Automation Event List (key command only.)
1. Open and select ALL.
2. Command-C to copy.
3. Go to the second track and click in a staring node.
4. Open the list and hit Command-V for paste.
Click to expand...

I always find that it pastes two beats later than it's supposed to, so watch for that if you use this method. I didn't know about the Automation Selection tool, though - have to read up on that!
Click to expand...

Not here. A entry box for the first event opens up allowing you to type in the position.
 
Upvote 0
Jay Asher said:
sonnykeyes said:
I always find that it pastes two beats later than it's supposed to, so watch for that if you use this method. I didn't know about the Automation Selection tool, though - have to read up on that!
Click to expand...

Not here. A entry box for the first event opens up allowing you to type in the position.
Click to expand...

True, but it defaults to a position two beats later than the position that the original data was copied from. It forces an extra step where none should be necessary.
 
Upvote 0
Understood and agreed. That said, in my experience, the word "should" when applied to how any DAW works, especially Logic, is irrelevant. It is all about learning how the app works best and adapting your workflow to it.
 
Upvote 0
Jay Asher said:
Understood and agreed. That said, in my experience, the word "should" when applied to how any DAW works, especially Logic, is irrelevant. It is all about learning how the app works best and adapting your workflow to it.
Click to expand...

Amen to that brother!! A lot people would be a whole lot happier if they dealt with the world as it is rather than as it should be. But, I digress.


.....[that was not intended to dis anyone on this forum - just a general life observation that I've found to be true in a more general context]
 
Upvote 0
Back
Top