can I store clips with just recorded automation

[flowdesigner]

Hi,

can I store clips with just recorded automation and use them with midi note data later on?

thanks.

[invol]

No and Yes.

No, Automation is track based, so you cannot save it with a Clip.

Yes, you can import Tracks from other Sets via the Browser, so you can store them that way.

Yes, copy it into a Clip, then drag the Clip into a folder in the Browser. Or, import Clip from .als in Browser.

Cheers,
Brian

[hoffman2k]

No, Automation is track based, so you cannot save it with a Clip.

This is a bit wrong. You can save the automation with the clip if you also save the instrument with the clip so that you have a Live Clip (.alc).
MIDI CC data can also be stored inside a clip.

[invol]

No, Automation is track based, so you cannot save it with a Clip.

This is a bit wrong. You can save the automation with the clip if you also save the instrument with the clip so that you have a Live Clip (.alc).
MIDI CC data can also be stored inside a clip.

Are we just using different terminology? Perhaps the OP is not making a distinction between Automation and Modulation?

If I am wrong, please explain in more detail, as I don't find that to be the case about Live Clips. Automation is Track-based, Modulation is Clip-based. Both are Envelopes. Automation, i.e., Track Envelopes, is only available as a Live Clip if they are accessed in the Browser by unfolding the .als. As you know, CC Data is only found via Clip Envelopes too, and therefore is also not considered Automation in Live - i.e., it is only found in Clip View, not on Tracks in Arrangement View.

If there is a cool work around for this, please explain your steps, because the standard way of creating Live Clip, by dragging from a track to the Browser, does not bring the Automation with it when you drag it back out onto another track.

Cheers,
Brian

[hoffman2k]

Yeah, I meant modulation. Which can saved and reloaded as a Live Clip.

[flowdesigner]

If there is a cool work around for this, please explain your steps, because the standard way of creating Live Clip, by dragging from a track to the Browser, does not bring the Automation with it when you drag it back out onto another track.

well, it does, its automation recorded with a moog voyager rack. I record a nice curve into a clip in session with cc19, drag it into the browser and save it and name it, and drag it back into another session and use the automation curve on another melody

[invol]

well, it does, its automation recorded with a moog voyager rack. I record a nice curve into a clip in session with cc19, drag it into the browser and save it and name it, and drag it back into another session and use the automation curve on another melody

Again, there is some confusion about Ableton's terminology here. Automation is only on a Track, and since MIDI CCs are recorded into Clips, it is not technically automation in Live. Functionally, yes, technically no.

Generally speaking, for most DAW's, MIDI CC data is not considered "Automation", it is MIDI CC data : ) Automation controls mixer and plug-in parameters for the most part. Some DAW's mixers are MIDI controlled, which blurs the lines a bit, but Live is not one of those - e.g., CC 7, CC 10 for volume, pan, etc.

Cheers,
Brian

[flowdesigner]

thank you, you really know this stuff !

I bookmark this post

[3dot...]

you can 'drag' the track-header to the browser..
it saves the track (with automation)...the clip/s(with the clip envelopes)..and any devices (including vst)

and yes..
arrangement envelopes = linear automation..
clip envelopes = modulation
(right click any parameter in a device to quickly get to it's envelope..whether it's clip/arrangement)
the 'Master' track contains additional global envelopes to automate(like bpm..x-fade etc)

[maciejsawicki]

I figured out a workaround.
Use Max For Live "Expression Control" device and map it to the modulation parameter that you want to store with your clip. Record this automation as modulation. Drag the clip into the library.