Automation Interpolating Between Patterns

Ideas & suggestions
1

So, requesting this same stuff again and always hoping that this time we’ll get this feature.

Automation curves don’t interpolate between patterns and it would be nice to finally have this feature.

If not possible how about just adding extra point to end of last row?
It’s already possible to do this by adding extra rows and using pattern break. (For example 64 row pattern has 65 rows and pattern break in 64th row.) It’s possible with simple workaround like this, so shouldn’t be a problem adding the extra “hidden row” which is skipped and only seen by automation data.

(Tho I bet you want to avoid hack fixes like that :)

2

In ideal case it interpolates differently when pattern 5 for example is followed by pattern 6 or pattern 18 when those have different beginnings for their automation. Your one extra hack wouldn’t work in that case.

3

Ye, It wasn’t actually solution to pattern to pattern interpolation, but to related problem of automation curves ending to beginning of last tick instead of end of last tick.

4

I hope the automation envelopes get overhauled to accommodate this. And if they’re getting an overhaul, it’d be awesome to have mixed-mode envelopes made up of points, curves and lines (all in the same envelope! \o/) and a possible two points per increment a la Ableton Live so that sudden straight-down changes can be made (I know that’s been requested a septabazillion times before too).

5

I make it a septabazillion times + 1

6

Yeah I agree we need this

  • 1 for cross pattern interpolation
  • 1 for straight up/down automation (just let two points be on the same line)
7

martyfmelb has suggested a nick trick here

a] use pattern join built-in function to join the patterns you want to automate

b] use Pattern split scripting tool to split the joined pattern back

8

I vote for general Automation overhaul. The current implementation is just too limited. But I’m guessing this is out of the scope of 2.6. Can we have it on the next version though, pretty please?

EDIT: Now with the scripting, can an automation script be written that has the features we want?.. Maybe I’ll research this.

9

Been plus one’ing this since the dawn of times :) , though with an update, I think the current limited resolution system should be kept intact for backward compatibility and musical reasons. Use an lfo now for more fluid parameter changes, maybe a smart scripter can use lfo’s to bypass the current resolution limit and cook something nice?

10

I’m with you all in terms of “seriously needed, great to have”, but this really is nothing for 2.6. Sorry…

11

Thanks. “hardly” indeed was not what I meant.