view of automation tracks
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
if you have a midi track with a lot of automation events (e.g. pitch, volume, cutOff, whatever, ...) and these events are part of the track,
is it then possible to automtically allocate/spread out these events to several (sub) tracks (one track per event type, but with same behaviour as mixed together in one track) ?
Reason is to have a better (simultaneous) view to all these automation tracks.
is it then possible to automtically allocate/spread out these events to several (sub) tracks (one track per event type, but with same behaviour as mixed together in one track) ?
Reason is to have a better (simultaneous) view to all these automation tracks.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 2938 posts since 18 Jul, 2005
I'd love multi-lane display of automation --- editing automation of multiple parameters in a single part feels slow whilst editing automation of single parameters in multiple parts feels cluttered.
Jo's just getting towards M3 release and we're still not giving him a second's break from the FRs
Jo's just getting towards M3 release and we're still not giving him a second's break from the FRs
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Personally i also put 1 parameter per part, on subtracks.
I see that as multi-lane, don't you? If not, what's the difference?
I see that as multi-lane, don't you? If not, what's the difference?
-
- KVRAF
- 2938 posts since 18 Jul, 2005
Well, it's a matter of speed when working with automation imo. With the new subtracks the multi part approach takes up much less space in the composer than it did. But it still means you have to do multiple trips between the composer and part views. This also means if you have a lot of modulations that you want to synchronise at certain points you have the extra challenge of remembering the timeline positions.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Just to jump in -- I think what's being asked for is a single part with multiple automation lanes in the sequence editor, rather than the ability to keep separate parts together. Rather than having to switch between parameters in the editor, any with a value would be shown.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I think the main thing that is FRed is to be able to edit the automations (each on a part on a subtrack) from within the composer itself, right? (and preferrably also using breakpoint envelopes) All this is on the m4 whishlist.
Having multiple automation envelopes on top of eachother is not very user friendly imho, i would still keep 'em separate i.e. a parameter per part, on a collapsable subtrack.
Having multiple automation envelopes on top of eachother is not very user friendly imho, i would still keep 'em separate i.e. a parameter per part, on a collapsable subtrack.
-
- KVRAF
- 2938 posts since 18 Jul, 2005
+1 for an in-line track feature from me.mutools wrote:I think the main thing that is FRed is to be able to edit the automations (each on a part on a subtrack) from within the composer itself, right? (and preferrably also using breakpoint envelopes) All this is on the m4 whishlist.
Hmm... maybe it's just my workflow. It's not uncommon for me to be automating 4 parameters of a given plugin. Often, these parameters are related at particular points in time. So first of all, clicking in and out of different views 8 times or so to edit each track of automation is cumbersome in itself. Then remembering what's happening in the others at these key points is an additional bit of work. Where being able to view multiple lanes like:mutools wrote:Having multiple automation envelopes on top of eachother is not very user friendly imho, i would still keep 'em separate i.e. a parameter per part, on a collapsable subtrack.
==========
Cutoff
==========
Res
==========
Drive
==========
in the part editor would be extremely useful for seeing how the tracks relate, as well as doing a bit more to justify using an entire separate screen for the data (although you can already drag the single automation lane to fill up the screen now).
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Oh, seems that this topic is of common interest.
The reason I raised this topic was:
To start creativity process
I like to analyze ready midi songs.
When importing a midi file and assigning an appropriate instrument (vst),
then sometimes the sound is changing due to automation events.
For this case it would be convenient to see all this automation tracks at a glance, to check what is going on.
The reason I raised this topic was:
To start creativity process
When importing a midi file and assigning an appropriate instrument (vst),
then sometimes the sound is changing due to automation events.
For this case it would be convenient to see all this automation tracks at a glance, to check what is going on.
Everything should be made as simple as possible, but not simpler!
