The way I'm planning, automation won't be restricted to MIDI tracks. It will apply to almost everything scalar that is already subject to undo/redo commands. That is, for example, track volume/gain, panning, mute/solo states and most wanted of all, to any plug-in parameter.
Each automated scalar subject may be (optionally) assigned to an external MIDI controller and that indeed should complete this recent MIDI controller map implementation.
OTOH, automation deals with editing, storing and rendering pre-recorded values in the time line, probably as a step-wise curve. The curves should be displayed super-imposed to the current track view and control points visually editable as usual.
One of my biggest concerns about automation is how should the automation control points get stored. Should it be serialized inline with the XML session/project file? Should it be stored in separate files, one or several per track? Should it be plain standard MIDI files, for instance?
The way I'm planning, automation won't be restricted to MIDI tracks. It will apply to almost everything scalar that is already subject to undo/redo commands. That is, for example, track volume/gain, panning, mute/solo states and most wanted of all, to any plug-in parameter.
Each automated scalar subject may be (optionally) assigned to an external MIDI controller and that indeed should complete this recent MIDI controller map implementation.
OTOH, automation deals with editing, storing and rendering pre-recorded values in the time line, probably as a step-wise curve. The curves should be displayed super-imposed to the current track view and control points visually editable as usual.
One of my biggest concerns about automation is how should the automation control points get stored. Should it be serialized inline with the XML session/project file? Should it be stored in separate files, one or several per track? Should it be plain standard MIDI files, for instance?
Well, still wandering :) Any suggestions?
Cheers