flowdesigner

Hi,
How can I change the rate of playback?


live-step-playback-rate

thanks, but it does not seem to be that easy when transport is synced to Live.

you can have multiple transports with multiple names and choose which to clock to.

if you want a logical timing relationship between them, either clock with one metro and some scaling maths, or modulo the master outputs.

ALL of this is clearly documented in the transport reference entry:

I wasn't sure what you were after. If you look at the [phasor~] helpfile it can lock to intervals of the transport BPM. Or you could use a master locked [phasor~] and then use [rate~] to get different divisions. Another option is to observe Lives Tempo and then feed it into [sync~] and get different rates using [rate~] again. It's in the helpfiles so not much need for a patch.

Does anybody know if there are plans to have [sync~] recognise timing intervals in the future. I like [sync~] it's handy.

Unfortunately the original question isn't quite clear.

Do you want to run the sequencer in sync with Live or independent at a different tempo?

In case you want to make a step sequencer synced to Live, take a look at the factory M4L step sequencer to see how it handles different "Timing" like 1/8, 1/16 etc.

@pid - Thanks man! I try to tweak my head around the patch when my brain is up for it, but are you sure the answer to my problem is in that patch?

@grizzle - If I use phasor, I dont get the live.step to "stay in position synced to Live" it gets more like free-running

another way is to use a phasor~ - it's in the helpfile.

ehhm, why do I need both @interval and @quantize?

ehhm, why do I need both @interval and @quantize?
Would not interval 16n quantize to 16n?


Your solution is actually not "position synced" to live, but free-running.

I think im forced to use the phasor instead of counter, could you please help with this?

I ripped the guts out of the Step Sequencer in M4L and just left the bits that do what you want.

live.step playback rate