Zebra - Sync LFO to (n) Tuplet

[gwok]

Hey,

I'm trying to get Zebras' LFO's to sync to various tuplets (5,7). There is the setting 7/1, though this is so long it's not very useful to me. So far, by ear, I've found that having sync to 1/1, I can get pretty close with the rate knob.

Right now I've found this

@ lfo sync rate 1/1:

rate knob:

100 = 2 over 8 (quarter notes)
108 = 3 over 8
120 = 4 over 8
132 = 5 over 8
144 = 6 over 8
156 = 7 over 8

So I'd like to know if there is an accurate way to get the exact LFO rate to get 5,7,9 etc, tuplets. Is there maybe a list, or an equation to calculate it?

thanks!

g

[bmrzycki]

This page is really useful:

http://zebra.andreloker.de/

Be sure to read the manual on the page.

[ho66it]

Thanks for posting this link! I'm a newbie to Zebra programming and any resources like this are much appreciated!

[gwok]

This page is really useful:

http://zebra.andreloker.de/

Be sure to read the manual on the page.

cool thanks!

now to find a way to scale a midi cc to hit just the rates i want.

would be nice to see these subdivisions implemented natively in Zebra3

[bmrzycki]

now to find a way to scale a midi cc to hit just the rates i want.

Try using a modmapper with modwheel as the source and the destination as the LFO rate. You'll have to use the modmatrix and it'll probably also take some trial and error to find the right height for the MMap bars.

I've heard rumors Z3's LFOs are going to be super-mega-cool, so keep up that hope.

[pdxindy]

now to find a way to scale a midi cc to hit just the rates i want.

Try using a modmapper with modwheel as the source and the destination as the LFO rate. You'll have to use the modmatrix and it'll probably also take some trial and error to find the right height for the MMap bars.

I've heard rumors Z3's LFOs are going to be super-mega-cool, so keep up that hope.

The modmappers do not have a fine incremental control. The smallest step is in the large editor and that is 1.0 per step. So depending on how precise a task needs to be, the modmapper may not be sufficient.

Otherwise it is perfect for this sort of thing...

[gwok]

ya, i checked out the modmapper, seemed a little tricky, and not accurate enough. As well, having to use the mod wheel is kind of erratic. Keyswitches to the modmapper would be cool.....

[pdxindy]

ya, i checked out the modmapper, seemed a little tricky, and not accurate enough. As well, having to use the mod wheel is kind of erratic. Keyswitches to the modmapper would be cool.....

The modwheel works well... use map quantize and modwheel as modulator and if you have say 3 modmapper states, it is easy and sure to switch between the 3 states. and depending on what LFO rates you are switching between, the modmapper may be accurate enough.

If the modmapper is not accurate enough for an odd rate, you could also use the modmapper as an on/off switch between two different LFO's. Set both LFO's each to the precise rate you want. One LFO has Amp set to 0 and the other to 100. Then use the Momapper to control the Amp of both LFO's (+100 for one and -100 for the other). The Momapper has 2 steps. First step 0 and second step 100. Modmapper set to Map Quantize, modulator modwheel. So turning up the modwheel "turns off" one LFO while at the same time "turning on" the other.

[Sendy]

What I'd really love from a tempo-synched LFO would be for ALL of the speeds (or a selectable range, to narrow it down and save CPU) to be running at once, phase locked, and you can crossfade through them like a wavetable.

That way you can sweep around different speeds and the LFO will never miss a beat.

[gwok]

What I'd really love from a tempo-synched LFO would be for ALL of the speeds (or a selectable range, to narrow it down and save CPU) to be running at once, phase locked, and you can crossfade through them like a wavetable.

That way you can sweep around different speeds and the LFO will never miss a beat.

hell ya!

as well, to be able to sweep\morph thru various user tables as well would be insane

[gwok]

ya, i checked out the modmapper, seemed a little tricky, and not accurate enough. As well, having to use the mod wheel is kind of erratic. Keyswitches to the modmapper would be cool.....

The modwheel works well... use map quantize and modwheel as modulator and if you have say 3 modmapper states, it is easy and sure to switch between the 3 states. and depending on what LFO rates you are switching between, the modmapper may be accurate enough.

If the modmapper is not accurate enough for an odd rate, you could also use the modmapper as an on/off switch between two different LFO's. Set both LFO's each to the precise rate you want. One LFO has Amp set to 0 and the other to 100. Then use the Momapper to control the Amp of both LFO's (+100 for one and -100 for the other). The Momapper has 2 steps. First step 0 and second step 100. Modmapper set to Map Quantize, modulator modwheel. So turning up the modwheel "turns off" one LFO while at the same time "turning on" the other.

yes, there's a few ways to get some results, though I'm finding it hella easier to just use automation at this point.......