Is there a device that writes automation

[interceptor]

Is there a device that can write all parameter settings of a plugin as automation in a clip?

[Johnisfaster]

I dont think there is but I WANT IT!

[madeofoak]

me too. just upgraded to 9, and the m4l midi generators were a selling point. can't believe you aren't able to record the data.

[dataf1ow]

Why can't you record the data from midi generators?
I was able to record midi from M4L devices to a midi clip in a different track by using the IAC bus (mac only). There are similar solutions on windows, but you'll need a third party application (midi ox, loopMidi etc.).

[clydesdale]

You can just route the MIDI Out directly to the Track In of a different MIDI track, or conversely route the MIDI In back to the other track's out. MIDI-OX loopback isn't necessary but it will work too. Arm and route the second track while the first is playing and any M4L or MIDI Effect notes get recorded. If the M4L device generates or modifies control channel data that should be recorded too.

I'll test it later, but I'd like to know if changes made by the live.object or live.remote~ in M4L will generate automation curves if automation recording is enabled. This would definitively answer the OP's question.

[dataf1ow]

You can just route the MIDI Out directly to the Track In of a different MIDI track, or conversely route the MIDI In back to the other track's out. MIDI-OX loopback isn't necessary but it will work too. Arm and route the second track while the first is playing and any M4L or MIDI Effect notes get recorded. If the M4L device generates or modifies control channel data that should be recorded too.

I'll test it later, but I'd like to know if changes made by the live.object or live.remote~ in M4L will generate automation curves if automation recording is enabled. This would definitively answer the OP's question.

I stand corrected! no need for an external midi loopback. I mocked up a device that just spits out CC data and it was recorded into a blank midi clip.

As far as the OP goes, I think you are asking to record parameter adjustments in a clip? or store the values of parameters as presets? If it's a non Live device, as long as you can observe settings via the api you could set this up. If you clear up exactly what you're after I'd have a better answer for you.

Changes made by live.object to a parameter will be recorded in automation AND the undo history. That's one of the reasons that live.remote is preferred for modulation. Parameters that are changed by live.remote DO NOT write automation or to the undo history therefore not clogging your undo history with tons of messages pre second.

[Johnisfaster]

Cant the new monolake lfo write data to automation?

[clydesdale]

Changes made by live.object to a parameter will be recorded in automation AND the undo history. That's one of the reasons that live.remote is preferred for modulation. Parameters that are changed by live.remote DO NOT write automation or to the undo history therefore not clogging your undo history with tons of messages pre second.

Is there a different behavior depending on whether you're recording or not? Since live.object's intent was to act as if a user was making changes, does it follow that the undo history reacts the same? If I record 10 channels at once, a single undo will revert back to just before the record button was pushed regardless of how many other actions took place during the actual recording. But if I just change the value of a single parameter while not in record mode it becomes an undo point all by itself. Does M4L do that too or just ignore the live_set state?

I had seen posts before that it was bad form to flood the undo history but up to this point I hadn't done enough m4l to understand the context.