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

Limiting knob ranges/Knobs that behave like switches?

Discussion in 'Building With Reaktor' started by autogen, Aug 28, 2008.

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

    autogen NI Product Owner

    Messages:
    13
    Hi Reaktor Gurus,

    I've created my first instrument in Reaktor which is an emulation of a simple single oscillator synth. I'm now trying to create the controls while remaining faithful to the originals panel layout.

    I've managed to limit the knob I'm trying to emulate to switch between 3 values by limiting its range to a min value of 0 and a max value of 2 with 2 steps.

    However, instead of having
    0 at 7 o'clock 1 at 12 o'clock and 2 at 5 o'clock

    I really need to have
    0 at 11 o'clock 1 at 12 o'clock and 2 at 1 o'clock.

    Is this possible using Reaktor?

    I'd also like to know if it's possible to use a single knob to control multiple values of a macro. For example could I have a knob with 4 steps, with steps 1,2 and 3 sending different frequency values to an LFO and the 4th step turning the LFO off?

    I'm trying to re-read the manual now that I have a specific goal in mind, but so far the apparently relevant sections aren't shedding any light on the situation. Perhaps some of you know which of the more obsure macros might help me get nearer to this kind of functionality.

    Cheers.
     
  2. herw

    herw NI Product Owner

    Messages:
    6,421
    yes that's possible but not simple. You have to overlay a mouse area over the knob and change to several ranges by f.i. right clicking (using the mouse area as a cyclic switch) and changing values by left mouse drawing. It is possible but a hard job. Such complex event processing is not a good starting point to learn REAKTOR.
    And the mouse areas have no midi learn ability.

    ciao herw
     
  3. autogen

    autogen NI Product Owner

    Messages:
    13
    Thanks Herw.

    So even my first problem of changing the knob range would involve a mouse area? or would it just be this complicated for the knob which addresses 2 controls?

    Perhaps if I could create a skin for the 1st knob (the one that only needs the limited range, rather than dual functions) that only goes from 11 o'clock to 1 o'clock then change the mouse resolution value to match the perceived movement. Would this also effect the way MIDI would control this knob?

    I'll read up on mouse areas in the manual to see if I can get my head around it. Thanks again.
    ---
    OK got the 1st one sorted. I just created a skin for the knob with the 3 states I needed for the 11,12 & 1 o'clock positions then reduced the mouse resolution and it seems to work fine.

    Sounds like I'd best get reading if I'm going to sort out the other one :eek:
     
  4. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    don't know if this helps? as you say doing a skin for your first problem makes perfect sense. but i include a silly non-skin version.

    i also enclose a method of using 1 knob for different things.

    sowari
     

    Attached Files:

  5. autogen

    autogen NI Product Owner

    Messages:
    13
    Thankyou so much, this is perfect! I had to invert the min/max values to get it to behave in the same way the control i'm emulating does (for some reason LFO off is to the extreme right of the knob) but it works great.
    Am I right in assuming that I could have acheived the same result by re-wiring the constant values being fed to the selector?

    You've really just given me a huge boost in understanding with your example. I think I get how the path through the selector is working alongside the constant values. I just don't quite understand how the path from the LFO Rate control through the compare/equal macro to the multiplier macro is working? This is how your turning the LFO off right?
     
  6. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    glad to help :)

    you can have any constants (in any order) that you want for the Selector.

    make sure you have your Hints/Info ON so you can read how the Compare/Equal Module works. but to put it simply, depending on the values going into A and B, whether they are = or not, you get True (1) or False (0) at each of the outputs. the output that i have used (>) sends out a value of 1 if B is greater than A. when A and B both have an input of 0 then > sends out 0. if B is greater than A (even if it is 0.1) then > sends out a value of 1. 1 lets the LFO signal through (because of the multiplier). 0 turns the output of the LFO off, again because of the multiplier.

    does this make sense?

    sowari
     
  7. autogen

    autogen NI Product Owner

    Messages:
    13
    Yeah it makes perfect sense now. I checked the manual again after your other post and it was all a lot clearer with your modules there to reference. It just didn't seem to click with me that the compare/equal would be spitting out a 0 :eek:

    Thanks for clearing up my confusion. If you need any custom GUI elements designed anytime, feel free to give me a shout.
     
  8. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    glad i could help :) btw, the manual could be better ;) so please continue to ask questions here!

    i might take you up on the custom GUI elements :) but i know lots of us here would be interested. maybe you could think about uploading some stuff to the User Library?

    sowari
     
  9. autogen

    autogen NI Product Owner

    Messages:
    13
    Sure, why not. I've had Reaktor for ages, but never really got under the hood until recently. I'm sure I'll be using it a lot more now, so I'll try and build up a collection worth posting as I start trying to build more ensembles.
     
  10. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    great! looking forward :)

    sowari
     
  11. herw

    herw NI Product Owner

    Messages:
    6,421
    sorry i misunderstood your question.

    ciao herw
     
  12. autogen

    autogen NI Product Owner

    Messages:
    13
    No worries, you got me thinking about a module I might of overlooked otherwise.
     
Thread Status:
Not open for further replies.