Announcement

Collapse
No announcement yet.

Let me get this Bitbox forum going....

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

  • Let me get this Bitbox forum going....

    I am absolutely thrilled with my Bitbox! It is now the cornerstone of my performance rack. This being the case I am limited to 6U 104 hp and I want to trigger every sample. So, having sequencer modules providing 16 triggers along with CV available can take up alot of HP. Prior to Bitbox I was running (4) of another companies 4hp sample players which used a files selection mode by CV modulation and trigger. What I liked about this was I only needed (4) triggers/gates using the CV to change samples through the sequence.

    This brings me to my question. Would 1010 be able to add this type of feature with the next firmware update?

    I am currently running the beta 1.3 and have been running four individual mono outputs. Essentially, I would like to use a column or row of 4 samples each as one track/channel.... totaling 4 separate mono tracks of four samples each. Using one trigger to activate each column/row and a paired CV signal to modulate through these 4 samples according to the CV being sent to the modulation input and with each trigger. This way I could use say a 4 track cv/gate sequencer (i.e. Stillson Hammer MKII) to play all 16 samples with 4 different tracks/sequences running at the same time to each of the mono outputs. Sparing me the need for 16 different trigger sources.

    Maybe there is someway of doing this with the module already , but, I am unaware of it in my exploration of the current beta firmware at this point. I have used the cv modulation to modulate whole grid and row/column etc. but this still seems to call for 16 triggers to play all of the samples concurrently.

    Apologies for the long winded explanation and thanks in advance for your time and consideration of this request.

  • #2
    Hi Dexter!

    Bitbox can do this, although it's a slightly different workflow to your previous method! You'll need to create four wave files with the four individual samples in them, slice them up and turn on Atomic mode, then assign the mod cells to "Slice Sel" for each clip and off you go! You'll have to transpose your sequencer down to C-2 to trigger the first slice though!

    Comment


    • #3
      You would have to use 2 of the mod cells assigned to "Scene Trig" to trigger all 4 cells in a row at once, though. This means you could only have 2 tracks running with the functionality you wanted, but you can have up to 127 slices (samples) on each cell.

      Comment


      • #4
        Thanks so much for the reply and insight. Atomic Mode it is!
        A couple of follow up questions.
        I maybe mis-understanding the need for 2 CV mod inputs per, why would this be needed?

        Could I assign each of the four cv modulation inputs to one cell each and output to each of the four mono outputs? With each cell containing a .wav file sliced full of samples?

        In the example you have outlined, will Atomic mode be able to sequence back and forth within a group of slices in the .wav file based on the cv being sent through the mod input? I am guessing this is why you have noted the need to transpose the sequencer down to C-2 (to give a full range of CV to be allocated to the various slices)?

        Thanks again for the help.

        Comment


        • #5
          Originally posted by Dexter View Post
          Could I assign each of the four cv modulation inputs to one cell each and output to each of the four mono outputs? With each cell containing a .wav file sliced full of samples?
          Ok, I understand now. I thought you wanted to use 1 trigger input to fire off 4 cells at once..

          Yes, that will work just as you describe!

          Comment


          • #6
            Originally posted by neuron divider View Post
            Hi Dexter!

            Bitbox can do this, although it's a slightly different workflow to your previous method! You'll need to create four wave files with the four individual samples in them, slice them up and turn on Atomic mode, then assign the mod cells to "Slice Sel" for each clip and off you go! You'll have to transpose your sequencer down to C-2 to trigger the first slice though!
            After tinkering around with Atomic mode a bit, it does not seem to perform in the manner I was hoping. It appears that in atomic mode the file continuously plays while the cv modulates the playback around throughout the file.

            What I am looking for the module to do is, for a sample to only play when triggered and for the corresponding cv to modulate from sample to sample based on the voltage being sent. Again, I may be missing something ( hopefully I am and someone can enlighten me on how to accomplish this), but, it does not appear that this is a function the bitbox is able to perform with the current beta 1.3 firmware.

            My hope is that this functionality can be added. I feel like this mode would be best suited and the most fun to explore in the sample grid environment.

            I am super excited about the bitbox and happy to have it as the core voice in my performance rack. I am also thrilled about the dedication of 1010 to fine tune this module and continue to make it better based on user feedback. Thanks 1010 for a fantastic module.

            Comment


            • #7
              https://drive.google.com/file/d/0B5d...ew?usp=sharing

              Comment


              • #8
                Neuron,

                Thanks for the excellent video.

                Dexter,

                It is important that the CV that sets the current slice remain at the same pitch in semitones for the duration of the note. If it changes notes, bitbox will jump to a new slice. If you look at this stuff on a scope, often the gate will fire about 5ms before the pitch settles, making sample selection tricky.

                Also, the "Slice Sel" modulation type will update selection immediately. The "Slice Next" type will wait until the next trigger. This may help you or get in your way depending on how the pitch and gate work on your rig.

                Comment


                • #9
                  Neuron!
                  Thanks SO much for taking the time to put together the demo video, I really appreciate it!
                  Proof positive that the module is fully capable and user error was the culprit of my inability to accomplish task at hand.
                  I appreciate your help in walking me through this process.

                  Comment


                  • #10
                    No worries at all Dexter, glad to help!

                    Comment


                    • #11
                      Originally posted by Aaron View Post

                      It is important that the CV that sets the current slice remain at the same pitch in semitones for the duration of the note. If it changes notes, bitbox will jump to a new slice. If you look at this stuff on a scope, often the gate will fire about 5ms before the pitch settles, making sample selection tricky.

                      Also, the "Slice Sel" modulation type will update selection immediately. The "Slice Next" type will wait until the next trigger. This may help you or get in your way depending on how the pitch and gate work on your rig.
                      Aaron!
                      Thanks SO much for your informative notes!
                      It seems that I need calibrate my sequencer to make sure that the CV that sets the current slice remain at the same pitch in semitones for the duration of the note.

                      I really appreciate your help and guidance. Loving the module!

                      Comment


                      • #12
                        Originally posted by Aaron View Post
                        It is important that the CV that sets the current slice remain at the same pitch in semitones for the duration of the note. If it changes notes, bitbox will jump to a new slice. If you look at this stuff on a scope, often the gate will fire about 5ms before the pitch settles, making sample selection tricky.
                        As an update, it turns out the output cv from my sequencer was not slaved to the corresponding gate. So the cv was running and changing while no gates were triggering/advancing. Thanks for the heads up on this Aaron.

                        Also, thanks again Neuron for your help.

                        Comment

                        Working...
                        X