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

relay / router

Discussion in 'REAKTOR' started by kim (keem), Jan 14, 2004.

Thread Status:
Not open for further replies.
  1. kim (keem)

    kim (keem) Forum Member

    Messages:
    323
    question; is a [relay 1,2] constantly working at the sample rate, or is it some sort of “smart” version of a [router 1,2] which samples and reports the input value only when it or the pos input value changes? i.e. for event signals, is it worth using a router, merge, order, and value sandwich instead of one relay for better cpu efficiency?
     
  2. spoombung

    spoombung Forum Member

    Messages:
    747
    marriage in a value sandwich
    (cheese and cucumber)
    gone awry
     
  3. Tom Cohoe

    Tom Cohoe Forum Member

    Messages:
    55
    But not as bad
    as a bad bar lie
    in
    September
    sung
     
  4. John Nowak

    John Nowak Account Suspended

    Messages:
    3,493
    To be honest there's a lot of "samey" modules in Reaktor when it comes to signal routing, mostly to try and make up for the clunkiness that is graphical DSP. I say use Router for events and use Relay for signals and just don't worry about it really. ;-) For audio, you have to use relay. For events, router makes more sense, unless you want it to send a zero when the position isn't valid, instead of nothing, which -may- be how it works. Either way, I'm sure this is an area where not much CPU can be saved anyway, so if it works, just leave it alone. That's what I would do. ;-)
     
  5. self oscillate

    self oscillate NI Product Owner

    Messages:
    279
    the relay works constantly and is the right thing for audio.
    i mostly use relays for events too, but it depends on the
    application, which is the better choice for that.

    best wishes

    ingo
     
  6. sowari

    sowari Moderator Moderator

    Messages:
    27,759

    how many pints did you have last night?

    sowari
     
  7. triptonizer@yahoo.com

    triptonizer@yahoo.com Forum Member

    Messages:
    277
    As far as I remember this would not work with a router, so there is at least one big difference in behavior (a router's output won't change, if it's inputs don't change when the ctr-input changes state - haven't got Reaktor here at hand, but I think I remember right).
     
  8. lxl:::;xl::

    lxl:::;xl:: Forum Member

    Messages:
    222
    I think you are right, triptonizer. i also remember something about that.

    lx.
     
  9. ernest

    ernest Forum Member

    Messages:
    509
    Actually, I think for events the relay doesn't sample the input on control change either. Except if the input is unconnected in which case it is meant to generate a single zero event.
     
  10. kim (keem)

    kim (keem) Forum Member

    Messages:
    323
    no sonnets? wtf.?. :) thank you all for your replies, and poetics :) i guess if a relay is working constantly the “router value order merge” on rye is a better choice for what i am doing... i just need to “re-send” the event at either position (*100 or so) when the position changes.
    many thanks,
    and, of course, cheers.
    *edit*
    oh, ernest, did not see the last post somehow, oops... hhhmmm...
    some testing may be in order.
     
  11. skov2205

    skov2205 New Member

    Messages:
    1
    making routers behave like relays

    What I normally do if I need the router to give me a constant signal like a relay is that I connect up a value module before the router inputs. You connect the 'val' you want to the value input, and to the 'in' input, you connect a constant followed by an audio>events converter module. This pumps your value into the router at the event control rate and ensures that every time you change the control input the appropriate input will be triggered. You may need an event merge after the router though, depending on what you're doing.
     
Thread Status:
Not open for further replies.