Unless I’m mistaken, the length of automation lanes is tied to the pattern length.
It would be so much flexible if I could set up an independent length for each automation.
13 Likes
I fully support this request, for my genere automation is everything, the note sequence is rather short, and often repetetive.
1 Like
This. Or the opposite : long note sequence, short looped automation (think “custom LFO”).
2 Likes
When the pattern is changed, the automation should stop, it should not be independant.
Ofc this can be solved with rerouting track automations, if that would be available.
Or if independent, a switch to turn all on off. (math condition for automatin lane could also be intresting)
+1 for this request, I’d really love independent lanes.
use separate track routed to the same output and channel
3 Likes
Maths on automation would be killer
4 Likes
fine workaround but I think fundamentally the mod lanes should be unlinkable, just like independent drum lanes should be in drum tracks. it’s a waste of a track, i think. Even with the dual project architecture, these things start taking up unwanted space and can get in the way.
1 Like
youve got 32 tracks to work with. bounce to mpc! thats what i do anyway
yeah i understand, i’m saying it’s a waste of a track and I use all 32 tracks. you don’t need to respond to everyones suggestions.
I like this feature request. Having unsynced automation lanes would make it much easier to create evolving modulation patterns that don’t repeat at the same interval as the sequence. It would add more flexibility for generative music and long-form compositions without requiring workarounds or manual adjustments.
1 Like
It’s not a feature request unless you submit one!
1 Like
Sent!
1 Like