Buma

I'm working on a step sequencer with the help of [live.step]. I want each beat of the sequence to have a different resolution/division. Between 1/4 and 1/32. That means that I'm using a different live.step object for each beat. They're supposed to play one after the other in a seamless way.

But that's not that easy. For each beat, the steps of the corresponding [live.step] object are played at a different rate ( e.g : 8 steps at 1/32, or 7 steps at 1/28, 2 steps at 1/8, 1 step at 1/4, etc.)

I've been experimenting with [tempo], with [metro], with [transport] (with the raw ticks output) and finally, with a [phasor] and [rate]. This last option was pretty accurate. If a step is considered as "active", a 1 would trigger a phasor (synced to transport). This phasor will ramp for 1, 3, 5, 7... times ( each live.step, at a different frequency). The results with [edge] and [Counter] are not always accurate, not always in time, and there's a risk that the live.step starts to loop, so I'm wondering if there's a better solution.

Hello,
I'm working on a step sequencer with the help of [live.step]. I want each beat of the sequence to have a different resolution/division. Between 1/4 and 1/32. That means that I'm using a different live.step object for each beat. They're supposed to play one after the other in a seamless way.
But that's not that easy. For each beat, the steps of the corresponding [live.step] object are played at a different rate ( e.g : 8 steps at 1/32, or 7 steps at 1/28, 2 steps at 1/8, 1 step at 1/4, etc.) 

I've been experimenting with [tempo], with [metro], with [transport] (with the raw ticks output) and finally, with a [phasor] and [rate]. This last option was pretty accurate. If a step is considered as "active", a 1 would trigger a phasor (synced to transport). This phasor will ramp for 1, 3, 5, 7... times ( each live.step, at a different frequency). The results with [edge] and [Counter] are not always accurate, not always in time, and there's a risk that the live.step starts to loop,  so I'm wondering if there's a better solution.

trigger-n-phasor-ramps

I read on another thread that phasors are not meant to be stopped. That makes sense. At the moment, I keep them running and I just open some gates when they are needed. That works quite fine too

Maybe I'm missing something, but with this solution, the phasor is not being "stopped" after n ramps, is it ?

Thanks Roman,
Maybe I'm missing something, but with this solution, the phasor is not being "stopped" after n ramps, is it ?


Maybe pong~ could help? Here's what I use to generate a specific number of ramps within a given time.

I was experimenting with a non-signal solution ( a simple [line]), which works fine too, but this solution with [pong~] seems to be perfect ! Thank you !

a sequencer based on a non signal line will either freeze the system or be extremly inaccurate.

Thanks for the tip ! Starting one [metro] after one other was also not extremely accurate. I will test the [pong ] solution with my 32 live.step :)

Thanks for the tip ! Starting one [metro] after one other was also not extremely accurate. I will test the [pong ] solution with my 32 live.step  :)


Trigger n phasor ramps