Announcement

Collapse
No announcement yet.

Ignoring incoming triggers if a sample is already playing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Ignoring incoming triggers if a sample is already playing

    I'm new to the BitBox micro (I'm on firmware 2.2.3) and I would love to have the option of ignoring an incoming trigger if a sample is already playing.
    Am I missing something? Is this possible?

    #2
    What is the exact problem? Are you getting multiple instances of the sample played back at the same time on different pitches (polyphony)
    or is it a loop thing where you don't want the loop to retrigger and start over again on each trigger?

    I think the only possibilities you have on the BBmicro are the launch modes and the polyphony settings on the conf page.

    For launch modes you have these three possibilities:
    Trigger (every trigger launches the sample again),
    Gate (Sample plays as long as Trigger, or rather Gate is high) or
    toggle (an incoming gate starts the playback and the next one stops it. and so on)

    And if you have multiple instances playing, make sure you set polyphony of that pad to mono.

    What patch do you need that function for, if I may ask?
    Is there nothing on the trigger generating side you could change?
    For example a VCA that controlls the "volume" of your triggers, and then you take an inverted copy of the Audio of that sample that is playing.
    With a little bit of finetuning, this could stop triggers at the VCA as long as Audio is playing.
    something like that…

    Comment


      #3
      It’s mostly for long pads or samples with a long release in the context of generative music, where a trigger might be fired before the sample finished it’s course.
      indeed, several workarounds, but I think it would be a nice to have

      Comment


        #4
        Although I'm not a 100% sure I understand, surely you're missing the point? If you have a sample set up to be triggered by either a Gate or Trigger, then it's normal that it will be triggered every time it receives a trigger/gate. If you want your sample to play from start to end then you need to either do it manually, or time your triggers.

        One way of doing it would be to work out how many bars long you sample is and then setting the sync settings in your samples set up - look up (I think it's in Pos): Quant size and Sync. If you work with these settings you'll understand that it's possible to make your sample play only at the beginning of a bar (or more) after receiving a trigger. This way, if you know how long your sample is, you could organise for it to trigger once every X beats, which might be what you're trying to do.

        Comment


          #5
          Im having the same issue, with the 6equencer. But, when I plug it into Pams the sample gets retriggered everytime.
          Im thinking about it now..
          I bet it has to do with the duty cycle of the gate. Its probably set to 100% and not receiving another trigger.

          Comment


            #6
            The pulse length was actually too short, i increased on the 6equencer and the gates are retriggering the sample. I changed it from 1ms pulse length to 2ms

            Comment


              #7
              Increasing to 3ms is better

              Comment


                #8
                You may consider more like 5ms for the Micro.

                Comment

                Working...
                X