Change LFO designer step length?

Hi all

I’m working in a project in 3/4 for the first time and I wanted to automate an LFO to hit various parameters on the 1 of every bar. Obviously that doesn’t work with a 16 step LFO designer though… can anyone think of a clever way to automate a ONE two three style emphasis? At the moment I’m having to do it manually by doing things like increasing the cutoff, decreasing attack time and so on… a bit time consuming!

Any help much appreciated

J

2 Likes

it certainly is unfortunate the custom LFO cannot have custom step length

I sometimes use a neighbor track set to only a handful of steps to have a custom step length for a simple modulation pattern, but obviously that will only allow certain possibilities

edit: maybe if you set the LFO speed to 12, 24, 48, or 96 and you are only doing a simple modulation you could ‘fake’ a bit of this behavior? would take some fiddling depending, but would be interesting…

1 Like

You could set the LFO to restart at start of the track/pattern with SYNC TRIG or SYNC ONE.

3 Likes

the sync options will be helpful, in my mind SYNC TRIG would be more useful than SYNC ONE, but depends on context. However, that still doesn’t really solve the problem except for very simple use-cases, and the LFO speed will still need to be one of those multiples of 12 - the problem that gets created is the LFO can potentially change values mid step as you can’t combine SYNC and HOLD behavior (perhaps with an LFO modulating another LFO though…) - this ‘mid-step’ issue makes things tricky in the OPs use-case and would require careful design of the interaction between the custom LFO and the pattern trigs - and at that point they may decide it’s easier just to p-lock what they want to happen - which is what they wanted to avoid in the first place. Hypothetically it should be pretty easy to make a basic ‘ONE two three FOUR five six’ accent pattern using the LFOs, though I haven’t tried. Not sure how fancy OP is trying to get

1 Like

Just a thought, not sure but maybe some other possibilities with midi loopback…like send values with same scale.
A concrete example would help.

1 Like

haha! an OT :mage: appears! :slight_smile: MIDI loopback actually seems like the perfect solution for this problem to me!

1 Like

to my mind setting odd values on speed lfo parameter is simpler and more elegant solution. think of custom lfo not as steps but rather a wave, or cycle

Several solutions here for several contexts and setups. OT is a box full tricks :-). Curious which solution best fits topic starters problem.

1 Like