Page 1 of 1
Posted: 26 Feb 2016, 22:15
by lytz1
Hey guys,
I need a LFO (or ramp) that has longer sync times than bar. (i.e. 4/8/16 bars like in the Sampler modules)
My workaround right now is to "fake" this via cycle mode and barlists,
*however* I need to be able to change the bar size on a per preset (or per grid section) basis.
Any ideas on how to do that?
Thanks,
tL.
Posted: 26 Feb 2016, 22:24
by sephult
You could take the Master Synchro and figure a way to convert the duration of a cycle to frequency, then you could control the LFO frequency rather than using the synchro options. Ill see later if I can help out.
-s
Posted: 26 Feb 2016, 22:56
by lytz1
Ah okay I see! I try to think about this as well. If you come up with a solution let me know.
For now I've solved this with a grainsampler (grainsampler -> pos out fader to mapper curve with LFO "Shapes" hand-drawn in)
Not very elegant but works for now. But I still would be happy to find a better solution.
Thanks,
tL.
Posted: 27 Feb 2016, 11:08
by oli_lab
calculate the time between say 16 bars (time) , in milliseconds then increment every millisecond a fader whith 1/time increment value
Posted: 27 Feb 2016, 12:16
by lytz1
Thanks Oli, will give that a try.
However also seems not to be very flexible. (Like I said I need to be able to change the "bar" lenght on the fly on a per-section/per-preset basis)
So basically I would need to calculate the time between 2/4/8/16 bars and setup a 1/time increment value for every one of them, but what would be the best way to switch the values?
Multiple 1/x to Selector module?
And I would still need to use handdrawn shapes it seems. (Which actually is not a big deal...

)
Thanks,
tL
Posted: 28 Feb 2016, 14:25
by Trogluddite
Hi Ltyz,
I've been working on a similar ramp generator as a sub-component of the clocking system of a bigger Usine add-on project. When I get some time, I could export it as an add-on in it's own right. It's specifically designed to allow the time signature to be independent of the global clock, as that is essential to me for the way I trigger loops. As it's a C++ add-on, the CPU load is very small as well, which is always nice. Don't know why I didn't think to export the clock as a module in it's own right before - it hadn't occurred to me that other people might find it useful!
Posted: 28 Feb 2016, 15:32
by oli_lab
I'm very interested in this bit of C++ code as I had trouble earlier to get proper timing for an audio ramp to animate various synthesis modules...
Posted: 28 Feb 2016, 19:32
by lytz1
Hey Trog,
sounds great. I am on OSX though..
Best,
tL.