FR: Handle Automation Events the same way as a MIDI Sequences: Shared Copies, Loops

[masterjoe]

This FR is related to the Composer module.

When editing MIDI events you can re-use these sequences in other parts of the overall sequence ("shared copies", "pooling"). And you can define loop points in a sequence so that changing the length of a MIDI sequence will make the notes loop as defined. Cool!

For automation events on the other side currently such features do not exists. An automation curve cannot be re-used elsewhere (no shared copies). Also loop points cannot be defined so that changing the length of the event makes the defined part loop.

My FR is to unify handling of automation events and MIDI sequences in a way so that automation events get the same flexibility than MIDI sequences:

- allow pooling / shared copies (re-use)
- add loop start and loop end definitions


Would be wonderful
Do you have that on your list already?

Thanks!

[humanboeing]

Loop point can be defined by right clicking on a point, afaik an improvement on that is currently on the list to allow loop creation by dragging on the timeline.

[masterjoe]

Ah, okay, I missed that! Thanks!!

But pooling / shared copies for automation data is currently not possible?
I would still FR that

[Michael L]

Perhaps you can get partway there by rendering the audio as a sample, add markers to the sample & 'pool' it for use in all Devices. You can then copy and paste automation.

[masterjoe]

No that's not really what I meant I mean to re-use automation curves in the same way as MIDI controller automation in a MIDI sequence can be re-used as the MIDI sequence itself can be re-used.

So what I want are the same features as there exist for MIDI sequences where you can define a new MIDI sequence and even change the used MIDI sequence for any instance of a MIDI sequence.

This would allow to define a complex automation curve only once and use that same curve again elsewhere and even for multiple effects. And also trying out some of the existing curves in place by changing which automation curve shall be used from the pool would become possible.

Rendering to audio is no good option as it makes things much less flexible...

[Michael L]

So if you draw some automation and Copy it to your clipboard, rather than just Paste it, you want to also Save it as an 'automation clip' in the browser ?

[masterjoe]

It's not really saving.
If the automation curve of said shared automation clip is modified then ALL shared copy instances shall change elsewhere in the project.
So it is "shared copies" for automation data really. You re-use a clip multiple times in one project and can edit its contents at any time to reflect the changes in all instances of the clip.

For automation data I think that is currently not possible?

[Michael L]

Oh I see, and yes you did clarify that in your second post!
Would you 'share automation' of different parameters in different parts?

[masterjoe]

Yes it should be as flexible as possible. Because the automation curve can be mapped to any param.
It's the actual curve data, loop points and so on that I want to use as shared copies across at least one composer instance.

Also a "time stretching" param per shared copy instance or a value offset would be nice to have some instance parameters...