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

Value module and Mux 16

Discussion in 'Building With Reaktor' started by omx, Sep 24, 2008.

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

    omx Forum Member

    Messages:
    308
    Hi again.
    Just tell me if I get it right: Value module samples and holds the value at its input and sends that value to the output same time, right?

    Now comes the Mux (multiplex) 16: someone described it as a row of Value modules: now could the Pos be driven by an audio rate clock ? My idea is that the Mux would sample an incoming number of SelNote gates, doing a kind of a keyboard scan, to be then "demultiplexed" , you know, still trying to get a kind of LRU assigner but in a simpler way that what has done Ernest Meyer with Marx :could it be done in theory?
    Thx for replying
     
  2. omx

    omx Forum Member

    Messages:
    308
    Any hint about this?
     
  3. omx

    omx Forum Member

    Messages:
    308
    Hi, still anybody can give me an explaination?
    Thx
     
  4. Chet Singer

    Chet Singer NI Product Owner

    Messages:
    822
    A value module is like a sample-and-hold module. A 16-input multiplexer doesn't sample; it's just a signal router.
     
  5. omx

    omx Forum Member

    Messages:
    308
    Yes, Chet but, for what I could understand from the manual it routes inputs to output according to the "Pos" input: I was asking then what kind of signal can I drive into the Pos input? An audio range pulse ? A sequence?
    Moreover, how can I link several Mux modules in order to get larger avaliability of inputs?
    Thx for any reply
    M
     
  6. Chet Singer

    Chet Singer NI Product Owner

    Messages:
    822
    The pos input can accept audio sources. Many primary-level inputs can, although it's not obvious which ones. Just attempt to connect an audio output to the input in question; if Reaktor won't let you, then it's an event-only input.
     
  7. herw

    herw NI Product Owner

    Messages:
    6,421
    ? very simple to see:
    • black input: audio input (accepts events too)
    • red input: event input (accepts only events)
    • green input (red input name) : macro can be used as audio or event macro (hybrid macro). Color of inputs and outputs changes to black when connected with audio or red when connected to event.

    ciao herw
     

    Attached Files:

  8. CList

    CList Moderator

    Messages:
    3,299
    Sorry Chet, you are incorrect.
    1. Yes, the Multiplex-16 is like a series of Value modules
    2. It cannot be driven from an audio source, the Pos input only receives events, and a received event is what triggers the output to fire an event.

    There's no need to run it at audio rate that would be highly inefficient. A better solution is to run it using an Iterator, firing events valued 0...15 which will scan all of the inputs in a single tick of the sample clock (events do thing thing *between* sample clock ticks).

    Cheers,
    CList
     
  9. CList

    CList Moderator

    Messages:
    3,299
    Note that the Multiplex-16 (which is in the sequencer section) differs from the Distributor in Herw's post by the fact that events arriving at the 0...15 inputs are NOT passed to the output (since they are audio inputs the events "die" at those ports, but the port remembers the event's value). Events only fire at the output port when an event arrives at the Pos input. This may or may not be te functionality you need. sometimes you want the event to pass through, and in that case you'd use the Distributor and not the Mux-16.

    The Mux-16 differs from other sequencer modules in that it is driven by events and not audio, and is, therefore, far more CPU efficient.

    Cheers,
    CList
     
  10. Chet Singer

    Chet Singer NI Product Owner

    Messages:
    822
    Yeah, I was wrong. I was thinking of the signal selector module. My bad.
     
  11. omx

    omx Forum Member

    Messages:
    308
    Time-division mux-demux

    Hi
    Has anybody tried it?
    I'm trying to translate this into Reaktorish:

    Given a clock turn time that we can divide in ticks (8 in my needs) a pitch+gate event is encoded (sampled) at tick "1", the next at tick "2" (delay both events one tick), the further at tick "3" (delay both events of two ticks) and so on.

    Can Reaktor do this (is THIS tdm? )or do the inverse job? That is, if I have already encoded pitch+gate (internally done) events and I want to route them one by one sequentially so that a poly event is reset by sampled new event (like, say an Event Combiner but with Poly output) ?

    Can Multiplex help me in this work? CList told me to use an Iterator: let's say I want to scan the inputs at SR/8 and encode the pitch+gate events at tick 1, next at tick 2 etc.......any suggestion?
    ---
    The picture below would show what I want to achieve, don't take it as a building example! it's just for making clear my idea: if an event at "Pos" opens the output gate of the Mux the notes should be encoded with a shift of +1 and stored in a memory which could output a polyphonic pitch+gate "last event", the goal should be to make something like the Event Combiner but with also the ability of keeping the "last event" of a chord
     

    Attached Files:

Thread Status:
Not open for further replies.