Hey all,
what is the best "Set Value Grid" setting to nail the LFO CyclesPer Beat as close as possible
to the full numbers?
I am trying to figure this out, but I just can't calculate the formula.
cpb has .99 steps, cpb starts at .01, so it is very difficult to get the divisor right for the setvaluegrid setting.
The cleanest is a setting of 5, but then the steps are very coarse.
(t 1.01 to 4.01 and so on.)
With a setting of 10 I still get the 1.01 and 4.01, but inbetween I have 0.26, 2.26 and so on.
.26 is already a bit too loose for what I need to automate here. When I get smaller, so that I get the 3.xx, 6.xx and so on, everything is all over the place, so that I need another solution.
Now what I want is: I want to get .01 or .99 at every full number (1-8 are obviously the most important),
So that the cycles are clean and not late/early.
So how do I do that?
Perhaps this is a little bit advanced, so maybe Jo can share some light on the setvaluegrid thing in general.
I know that I can paste numbers from the GUI (in this case MuSynth) to the eventlist directly with the "copy as parameter event" command. That is indeed a workaround, but this is very cumbersome, because I need to automate quite a bit on that one.
Thanks,
tL.
Question: Set Value Grid -> Correct formula to nail CyclesPerBeat modulation.
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
Ooooohhhh, in the Multi Mode Envelope and Automation tracks you mean?! Ahhh...I'll have a closer look!
I still don't get how this relates to time, though?
All "Set Value Grid" matters, including the suggestion by its name, seem to point to values and not to timing?! Quite possibly I'm missing something, but I'm honestly curious!
What troubles me is that you can't seem to turn the snap off for the value grid, only for timing.
...I'd really like to see the value grid just as orientation.
For pitch, if you have a whole octave of pitching (1200), you can use a value grid of 12 and the notes seem to be sitting just fine on the grid, by the way. (Am I hijacking your -umpf- this thread?)
OOooohhhh, or you mean driving the LFO frequency via values and using a value grid to nail the rhythm!? Ahhhh...
I still don't get how this relates to time, though?
All "Set Value Grid" matters, including the suggestion by its name, seem to point to values and not to timing?! Quite possibly I'm missing something, but I'm honestly curious!
What troubles me is that you can't seem to turn the snap off for the value grid, only for timing.
...I'd really like to see the value grid just as orientation.For pitch, if you have a whole octave of pitching (1200), you can use a value grid of 12 and the notes seem to be sitting just fine on the grid, by the way. (Am I hijacking your -umpf- this thread?)
OOooohhhh, or you mean driving the LFO frequency via values and using a value grid to nail the rhythm!? Ahhhh...
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
Yes, as the LFOs CyclesPerBeat relate to time.Taron wrote: OOooohhhh, or you mean driving the LFO frequency via values and using a value grid to nail the rhythm!? Ahhhh...
Professional.
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
From my quick tests, if you set the lfo frequency to 1.00 cbt it is perfectly looping at each beat. I'm not entire sure about the math behind it, but I noticed that 7% on the frequency input doubles the speed(1/8th), but 20% quadruples it(1/16th), 36% time eight (1/32th). So...I'm not sure entirely what to make of it, yet, but my test environment is kind of sloppy, too.
I'm sure there's a simple formula, but ...eh...
If you set the LFO speed to 2.00 cbt, 28% gets you 1/32th, 11% gets you (1/16th)...so strange, but then...again...I'm just trying to get closest to proper timing.
Don't forget your LFO curve, though! If you start at 0, you'll feel a significant offset to 1.0 or -1.0. I put a kind of saw into it, starting at 1.0 at 0 and 0.0 at 360 (full circle).
Not sure, if that helps at all, but those are interesting observations that could be useful to find clarification!
I'm sure there's a simple formula, but ...eh...
If you set the LFO speed to 2.00 cbt, 28% gets you 1/32th, 11% gets you (1/16th)...so strange, but then...again...I'm just trying to get closest to proper timing.
Don't forget your LFO curve, though! If you start at 0, you'll feel a significant offset to 1.0 or -1.0. I put a kind of saw into it, starting at 1.0 at 0 and 0.0 at 360 (full circle).
Not sure, if that helps at all, but those are interesting observations that could be useful to find clarification!
-
- KVRist
- Topic Starter
- 179 posts since 26 Feb, 2007
Yes it is a little bit quirky, thats why I was asking.Taron wrote:From my quick tests, if you set the lfo frequency to 1.00 cbt it is perfectly looping at each beat. I'm not entire sure about the math behind it, but I noticed that 7% on the frequency input doubles the speed(1/8th), but 20% quadruples it(1/16th), 36% time eight (1/32th). So...I'm not sure entirely what to make of it, yet, but my test environment is kind of sloppy, too.
I'm sure there's a simple formula, but ...eh...
If you set the LFO speed to 2.00 cbt, 28% gets you 1/32th, 11% gets you (1/16th)...so strange, but then...again...I'm just trying to get closest to proper timing.
Don't forget your LFO curve, though! If you start at 0, you'll feel a significant offset to 1.0 or -1.0. I put a kind of saw into it, starting at 1.0 at 0 and 0.0 at 360 (full circle).
Not sure, if that helps at all, but those are interesting observations that could be useful to find clarification!
You know, the problem comes, when you want to do what I want to do.
Image the following scenario: You have a Bassline with LFO on the Filter and you want to automate the CpB on the LFO for the whole track *all the time* very frequent. (Which is a quite typical scenario)
Now obviously you want it beatsynced with full CpB numbers, so that its all tight and pretty.
Now how would you do that, without spending 10 hours?
Try to automate just 3-4 changes somewhere, you'll see what I mean.
You have to have a grid setting that when you automate per "penciling-in" , it only allows you to draw onto full numbers. Now we *can* set the value-per-grid setting, so that we have steps, however in my case theese are off, because you need to tell the grid the right subdivision. In the sequence editor.
(Think Logic pro, where when you draw automation for an LFO of a stock plugin, it only allows you to draw useful numbers, as long as you have beatsync on)
Second solution would be quantizing the automation itself to round numbers after automating, but right now we can't do that (yet).
Best,
tL.
Professional.
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
Yeah, alone my tests were showing that a rigid grid wouldn't give you perfect subdivisions, or so it seems. But it might be possible just like I did with the pitches, to find a grid fine enough to hit all the right levels and then it's just up to you to skip all the wrong ones, haha. The other thing I'd be worried about would be fast enough speed changes, because the lfo will run continuously, gradually offsetting, if you had transitions between speeds. It's probably advisable to have inaudible retriggers, you know, where you just hit the note again.
Ah well...I'm curious what you'll end up doing and what it will sound like!
Ah well...I'm curious what you'll end up doing and what it will sound like!
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
The LFO Frequency parameter is exponential so it won't work well with the vertical value grid which is linear. Solution: Set the values for the LFO parameter automatio points by double-clicking a point, double-clicking the value and entering the Cycles Per Beat you want. Alternatively select a point and double-click the point value in the point property panel at the bottom left of the editor.