Point LFO problem

Renoise have very nice LFO. Unlike many other DAWs, you can use points instead of lines, which is cool.
Problem is that points works the same as lines mode. If you trigger second LFO reset by first LFO points, it supposed to trigger that reset only at the moment when the point value is and do not trigger it between. Unfortunately - it triggers reset all the time, so second LFO is not moving then.

Make more math combined, add for example Formula.
LFO1 » Formula (set the function) » LFO2

I am not looking for workaround. I am trying to point the problem - if LFO uses points, then should not have any values between.

OK. But „Reset” state is logical: 0 or 1. So if LFO generates values between 0 and 1, then it will not work on Reset state.

No, reset is shown as a button, but is not logical 0 or 1. It has many values - from 0 to FF. Look at Renoise tutorial.
Or look at this example: https://www.media.xtdmusic.eu/down/reset_test.xrns
I used velocity tracker as a reset parameter and can control from what point LFO will reset depends on velocity.

Yes…. I understand the role of parameters for the Reset button (to do). But the fact of (any) button is Logical: It is pressed (1) or released (0). And you need to control values send to the command of the „resetting fact”, which is x8yy. „x” is your 2nd LFO in the chain, and „yy” is the value for the reset point of modulation.

I made a quick test and it works (resetting is just smooth, so the 2nd LFO may even change direction during modulation, it all depends on the shape of the 1st one). But I can not upload video shot here.
Try this link: https://fb.watch/xSVMXT77V7/

In the 1st LFO as Destination set the 2nd LFO, and as parameter: Reset.
Then on both LFOs use Custom shapes of modulation.

I did Bold a portion of text here, because here is probably the most important part of your modulation mistake.

I know what I am talking about, so please do not explain me (wrong) as an ultimate expert. I do not want to explain it to you since we apparently have different point of view. I hope someone from Renoise crew will understand my first post. Thank you.

Even first LFO connected to reset button resets is not as 0/1 but depends on first LFO value, so that proves it do not acts like button. There is no difference how do you pass values to that button - using commands, automation or LFO - it’s the same (value to button). There is no 0/1 reset. Period.

But this discussion is pointless.

I didn’t understand a little your 1st post, it’s the fact. English is not my primary language.

But it works, even with points in the modulation (not lines). It just switches the 2nd LFO to value states (not smooth movement, static switched states). The 1st LFO has to use points and the 2nd one has to use curved/lined shape. AND IT WORKS BEAUTIFULLY. It seems that you are overthinking something. It’s easy for anyone who just understands what LFO is and what it does. No experts help needed. Period. Good bye.

(edit)

So I repeat: The 1st LFO has to use points and the 2nd one has to use curved/lined shape

No, you don’t understand. Not a problem.

I’ll try to explain it.

Imagine that you use command for reset. You set 1880 command (for example). Then at line 16 you insert 1800 command. So when you press play, your LFO (one shot) will restart first at 50% and on line 16 it will restart completely. But between line 00 and 16 LFO will move.

So instead of using commands as modulators, I want to use points in another LFO. These points should reset second LFO, but DO NOT HOLD that LFO at fixed value. Meanwhile when I am using point LFO - it will reset second LFO, but keep it that way (second LFO do not move at all).

Both - points in automation, lfo and commands, should not work in linear, should not having values between points at all.

I hope it’s now more clear.

(I deleted my previous post accidentally btw)

The only way to stop LFO movement is to automate the Frequency slider (all way down, to the left). Eventually by automating the On/Off state of the whole LFO device. You can’t stop LFO movement other way.

1 Like

OMG, you really don’t understand what I wrote. Problem is that LFO STOPS when I don’t want it to stop.
Nevermind. Please let other people answer, ok?

https://www.media.xtdmusic.eu/down/reset_test2.xrns
This shows that second LFO contsantly gets values so it doesn’t move itself (only change position on reset).

OK. I did understand what is your setup of those LFOs finally.
But — again LOGICALLY (of course not solution and not resolving answer, but just PHYSICS) — the 2nd LFO constant movement cannot be achieved this way — it means — with points diagram modulation of the 1st LFO. Any CREW will not help to this. Just math, physics.
You understand this why, but it looks like a force installation of the doors into the woods, it seems.

And you’ll defend your point of view no matter what.
If there are three modes of lfo and automation (lines, points, curves) then points should only pass values at the moment they’re set, not constant.
You’re pretending to know everything, you know what crew answers etc. Unlike you - I prefer to wait until someone answers (@taktik maybe).
Points are not stairsteps, they’re just points - single values. They should behave more like inserting track commands than like lines between points.

I ask you again - please, wait until someone else answers. I know that some people are so happy to write answers, regardless if they know the answer or not, but I would be very happy if you can stop confusing personal opinion with facts. And facts can provide only Renoise programmer. If it works like it suppose to and the value is transferred continuously instead of point by point (even if LFO is in point mode) then ok. But then it supposed to be displayed as stairsteps, not points.

This would be a more intuitive display of lfo point mode function, as values are held until a new point is reached. Which, is generally consistent behavior throughout renoise. The last triggered value typically holds until a new value is encountered.

If I’m understanding your desired behaivor properly, you would want to craft your reset LFO something more like this:
reset_test2 var.xrns (5.3 KB)

Not using points, but ramps

It would be nice to have the option for points mode to act like a trigger instead of a staircase. Perhaps this could happen in a future release?

Please notice that in your case your first LFO actually pass value to second LFO as second LFO do not move other than by setting reset. I mean - if you set first LFO to the max - second LFO will not move. And about holding values - yes, but if you reset LFO by command, it can work like trigger point, not constant value. So it’s not really consistent behaviour throuhout Renoise. This shows that it could be possible.

Yup… Science is science. But… Overthinking FlatEarthers on steroids.

How static point (and space between points going strictly and immediately to zero) or stair-alike line can give changing in-real-time value for the Reset of another LFO?!? You need curved line (sinus, cosinus etc.) for that and not points or lined stair-alike diagrams, QRVA. PERIOD.

Good luck.

Yes, that is how the reset works. It accesses the LFO value at the reset position. Effect commands are different than modulation values. For instance, the Sxx command can not be automated except through clever use of phrases within an instrument
ie:
Sample Scrubber.xrni (7.2 KB)