1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Restarting the Sine LFO

Discussion in 'Building With Reaktor' started by PedalPoint, Nov 20, 2010.

Thread Status:
Not open for further replies.
  1. PedalPoint

    PedalPoint NI Product Owner

    Messages:
    6
    Greetings,

    I'm trying to use the “Sine LFO” (under standard macros in Core) and I want to restart the LFO at a certain phase in response to a “note on”, but I can't figure out how to use the “Rst” input. Whenever I plug something into it the LFO seems to get stuck and doesn't oscillate. So my question is: What goes into the “Rst” input?

    I feel a bit stupid for not being able to figure this out, so any help would be much appreciated.
     
  2. James Nicholl

    James Nicholl Forum Member

    Messages:
    354
    Here's an example.

    This structure is inside an audio core cell.

    The frequency is an audio input (black) and the reset/note in is an event input (red). This can be set in the properties of the Note In and Frequency terminals.
     

    Attached Files:

    • LFO.PNG
      LFO.PNG
      File size:
      3.4 KB
      Views:
      278
  3. Makrophag

    Makrophag NI Product Owner

    Messages:
    208
    Usually you can drive "Rst" inputs by Gate Events. Maybe you need a seperator to fish out the "note off" events, but this is easy. Perhaps your osc. gets stucked, because you send events with a high frequency to the rst, like from another LFO, so the oscillator is reseted all the time?
    If the core-macro does not have it yet, implementing the phase to wich the oscillator should reset (like primary sync oscillators) can be tricky if you are not familiar with building in core. But it is worth to find out and do this.
     
  4. PedalPoint

    PedalPoint NI Product Owner

    Messages:
    6
    You hit the nail on the head there, James.
    My error was that the input to which the LFO was connected was set to audio, not event. I won't make that mistake again.
    Thank you!
    ---
    Yeah, that's what was happening. The oscillator was constantly restarting, but it didn't even have to be connected to anything more fancy than an input, as long as that input was set to audio, for this to happen. Even if nothing else was connected to the input.

    This turned out to be a fun story actually. I had this great idea for an instrument I wanted to build. I built it and it sounded not bad. Than I noticed that my LFOs were stuck, but when I disconnected them my instrument didn't sound so good anymore. Turns out the stuck LFO's unintentionally created a nice inharmonicity in the sound. When I now finally managed to fix the LFO's, so the structure actually does what I originally intended it to do, it sounds quite horrible. I guess this would be the time for me to rethink this great idea of mine a bit (but I suppose it's okay as long as I'm still able to learn something from it)
     
Thread Status:
Not open for further replies.