hello, i figure out some weirdness about the lfo device and fileter
lfo device control th filter cutoff freq
set these parametert to the lfo device
.sine
ampl: 50%
offset: 0% - 25%
freq: 64plc
and you can see the cutoff is moving backward like an accelerated potmeter, dunno why but only the sinus lfo - or tri - the lower numbers are accelereted
the top section is moving smooth and fine.
the cutoff moves exponential in the low section of the sinewave, or curve
set the offset to 25 and see the cutoff slider movements.
when it goes back to ~0.18khz it is speed up and stay in 0 for long time but when it reach teh top 2.0khz it is move smoothly back… did not stop at 2.00khz.
create cutsom triangle and you can see the problem again! but the custom triangle is linear!!! and the slider move not
(I was originally going to reply with this, because I thought you meant something else entirely. I thought you had misunderstood how the Amplitude and Offset parameters worked, but then I saw your 2nd post. Anyway… I’ll post it here anyway, just in case anyone else has been confused by the LFO usage in general.)
When the LFO cycle reaches the lower or upper limit of the parameter itself, it cannot go any further, so it has to stop there until it can move again. You simply need to set the correct Amplitude and Offset values to make sure it cycles within the range you are looking for. Here’s a little diagram that will hopefully show things a bit more clearly:
Sine and triangle will of course behave slightly differently, so there’s no surprise there.
I see what you’re saying though, about it behaving more exponentially as it moves towards 0kHz, but in this case I think it’s simply a display / numerical accuracy issue. Two decimal places simply isn’t enough to accurately show the correct frequency in kilohertz when it gets down to that point, so I think the display value is just being rounded off a bit. The parameter itself is still being set to the correct/accurate value behind the scenes, so I don’t think there’s anything serious to worry about here.
The LFO is doing its job just fine. You cannot trust what you see in the GUI to be an absolutely 100% perfect representation of what is going on internally, because the parameter sliders, graphical meters, numerical displays, etc. all have a much lower resolution than the parameter itself. Everything has to be rounded off to the nearest sensible value for display purposes, but the real output from the LFO itself is always accurate and precise.
To prove this, I logged the values generated by the LFO itself. I did this by making a very simple VST plug-in that logged the value of every parameter change it received, and then I connected Renoise’s LFO to it. I’m sure the same thing could be done by monitoring the LFO output via LUA scripting, but I haven’t had much time to familiarise myself with that side of Renoise yet.
Anyway… here are some snippets from the logs that show the behaviour when the LFO is moving around it’s minimum and maximum values. Please notice that in each case the minimum and maximum values of the LFO cycle are only reached once. The LFO does not stop at zero or behave in any other strange way.
LFO / Sine / Amplitude 100% / Offset 50% / 64 LPC
Rising up to 100% and then falling back down again…
