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

Sampler

Discussion in 'Building With Reaktor' started by Lowkus, Jan 13, 2004.

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

    Lowkus NI Product Owner

    Messages:
    802
    I'm using a simple three-input sampler control, and have run into a problem. I want to loop a sound until a key is no longer pressed. The problem is that the sound keeps looping forever, even after the key is released. For the sound being played, I set the "Loop!" to be on, and the "Rel" to be off. According to the manual, this should be keeping the sound from looping unless the [Trig] input is receiving a "1" value. A meter shows the value at the input to read "0", so I'm at a loss as to why the thing keeps looping. What am I doing wrong with my setup?
     
  2. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    you need to attach an Envelope module to the A input of the sampler. try an ADSR envelope. use the same MIDI Gate module
    for the G input of the Env and the Trig input of the sampler.

    you can choose between "Rel" on or off depending on your sound.

    sowari
     
  3. Lowkus

    Lowkus NI Product Owner

    Messages:
    802
    Using an envelope on the [A] input will silence the sound, but it won't shut off the looping action being applied to the sound file. If I loop the middle portion of the sound file, it won't ever play the ending part of the sound file that comes after the looped portion.
     
  4. ernest

    ernest Forum Member

    Messages:
    509
    This could very well be a bug. But first, are you sure you haven't sent a 1 value and then followed up with a zero value so you can't see the 1 value when hovering over the wire? If you look with clist's event watcher macro, you can check events specifically.
     
  5. Lowkus

    Lowkus NI Product Owner

    Messages:
    802
    Probably a bug in the software...

    I think it is a bug with the three-input 'sampler' component. I replaced the three-input 'sampler' with the more complex 'loop sampler' component, and now everything works exactly as expected. I hooked up the same three inputs and left all the other inputs unconnected.
     
Thread Status:
Not open for further replies.