Mono Sequencer Pattern Knob
Hi,
I'm really into the Max for Live Mono Sequencer these days and I'm having lots of fun with it. One problem I have though is the fact that the pattern starts from the beginning when i switch patterns using the pattern knob.
For instance, when I switch from pattern 1 to pattern 2, pattern 2 starts over from step 1 no matter what. I would rather like it to start from whatever step pattern 1 is playing when I switch. I would like it to be continuous, seamless.
I'm sure it's possible to change this by tweaking the Max patch, but I'm too much of a noob to figure it out on my own. The patch is too mysterious for me. It would be really helpful to get some input as to what section of the patch is making the pattern start over every time and how to make a smooth transition from one pattern to another.
Looking forward to your help!
Thanks
what about uploading that patch ?
Sure, there it is!
really large spread patch...
message s ---sync_now is sent to all 6 subpatchers
named counterx of which there 5 are in bpatcher datalanes (scripting name)
and 1 in bpatcher stepdatalane.
datalanes is upper, bigger live.step bpatcher
and stepdatalane the lower ione.
Both are embeded in the main patcher, so to edit them
you can either go directly into them by doubleclicking on that
message s ---sync_now which will show you all receiving objects.
The key are counter objects inside which get reset on different occassions,
one being pattern change.

Here a screenshot of one unlocked counterx subpatcher,
you must also have a look inside reset bpatcher.
------
I think that is enough infos to put you on the trace.
message s ---sync_now gets sent from 2 sources
first on the root of main patcher, when device gets loaded and initialised,
the other is suBpatcher change_pattern_housekeeping which
i guess is the place to look.

Hope that this infos help you.
I've also looked into the device (which is part of the 'M4L Essentials' pack). For example, deleting the message 's ---sync_now' marked red in the previous picture leads to continuous play at pattern change, but with unreliable timing. I wonder if this can be solved properly at all.
Oh nice, thanks guys! Yeah the transition is still a little unpredictable but it's already a huge step towards what I'm looking for
counter is easily controllable.
I think you need to follow all events that get triggered when a pattern changes,
and tame that.
Like if metros get reset, etc etc
Or make your own, trash all that unneeded stuff.
I wonder why some programmers place stuff on GUI sooo far spread that one gets sore
muscles for mousing and scrolling arround...