Announcement

Collapse
No announcement yet.

Latency issues with micro bitbox

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Latency issues with micro bitbox

    Hi guys I hope you’re all well. I wanted to ask if I’m the only one getting quite a bit of latency with the module. Has anyone ever done test comparing analog voices getting triggered vs bitbox sampler ? I did the comparison with a chimera from wmd which btw is also digital and does have 1 or 2 ms delay from analog stuff but these are the results I got: (see picture) I’m getting 9ms delay which for one shots is a lot. I’ve always heard it sound a bit off but now I know why.

    im using a fast sd card. My samples are 24 bit 48.

    if anyone has been recording etc and knows how I can improve this it would be much appreciated

  • #2
    I was hoping someone would chime in on this thread. I've been trying to use the BBM as my main drums (simply triggering one-shots on 3-4 channels, so clearly not overloading the engine) together with some other percussion modules, but the latency is audible and transients get smeared all over the place. My measurement stands at 10ms, which is frankly just not acceptable. It's not just elitist knit-picking - people notice that the kick sounds off when the transient of it flams with other sounds, and the groove is ruined.

    Is there ANY way, with settings, audio quality or whatever, that this can be reduced to an acceptable level (say, 5ms or less)? If it's not possible to address this, I'll have to find another sampler, which is really sad because I love the features on this thing otherwise.

    Comment


    • #3
      Same problem here, measured it and got about 8ms delay from triggers into the bitbox. The exact same trigger triggering an analog drum module is bang on time so it must be latency introduced in bitbox.

      ​​​​​​This happens when only triggering one voice too, makes everything sound out of time especially when using bitbox for one hits (which is the main reason I bought one)

      Any chance this can be fixed in a firmware update?

      Comment


      • #4
        How are you triggering? What are your pad settings, and which version firmware (as number) are you using?

        Comment


        • #5
          I am triggering it from the Nerdseq. I tested the timing of the nerdeseq triggers by recording them in case it was causing the issue, but the triggers are bang on time. When I trigger a sample in bitbox, the latency seems to be introduced on the output of bitbox.

          I am using one shots in "sample" mode. I am on firmware version 2.1.1, but the issue was present before I updated to this firmware. I have also tried multiple different projects but same result each time

          ​​​​

          Comment


          • #6
            Just tested it some more by sending the bitbox midi triggers, and the delay is around 1ms. So the issue seems to only happen when using analog trigger/gate inputs

            Comment


            • #7
              Any update on the analog trigger latency problem? Not sure if it's a known issue or just a few units effected, but my unit seems to suffer pretty bad from it.
              The latency renders bitbox pretty useless as a one shot drum machine unless you use midi, as the delay is very noticeable with the analog triggers

              Would absolutely love if this was fixed as I mainly want to use it for my drums and want to avoid midi as much as possible

              Cheers!

              Comment


              • Steve
                Steve commented
                Editing a comment
                Please.... contact us directly. use the contact info on our website.

            • #8
              Originally posted by nktrnl
              Just tested it some more by sending the bitbox midi triggers, and the delay is around 1ms. So the issue seems to only happen when using analog trigger/gate inputs
              Yes the difference between triggering with analog gates and midi seems like night and day. The BBM seems unusable using it with analog gates due to the latency issues at the moment.

              Comment


              • #9
                Yeah the latency is bad on mine. You guys definitely need to fix this. I can even notice it slightly on clips and it is very frustrating considering what I paid for this thing.

                Comment


                • #10
                  Yes, when triggered via midi, mine is late too. Especially frustrating, when you use a combination of analog triggers for some pads and midi for others...

                  Comment


                  • #11
                    Originally posted by nemoyy
                    Yes, when triggered via midi, mine is late too. Especially frustrating, when you use a combination of analog triggers for some pads and midi for others...
                    Mines the opposite, midi triggers are bang on time, but analog triggers are about 8-10ms delayed
                    Have done copious amounts of testing with different chains and can't get the analog triggers to have less than 8ms latency

                    Comment


                    • #12
                      Hi all,

                      Please always share the exact firmware number you're running when providing feedback about features and performance.

                      Comment


                      • #13
                        Originally posted by Lucas1010
                        Hi all,

                        Please always share the exact firmware number you're running when providing feedback about features and performance.
                        I've tested it with firmwares 1.0.12, 2.1.1 and 2.1.3. Each gave the exact same results with analog triggers, 8-10ms latency. Midi is bang on triggering all of them for me though.

                        Have tested with multiple chains and setups using different modules to trigger the inputs.

                        Tried with every input using a single one shot at a time (so as to not overload the engine) and got worse latency on channels 1-4 (around 10-12ms)

                        Comment


                        • nktrnl
                          nktrnl commented
                          Editing a comment
                          I've tried using my Mackie Onyx 1620i interface as well as a Focusrite Scarlett 18i8. Same results with both. Using a sample rate of 48k on both and a buffer size of 128 samples, but have also tried using 44.1 sample rate and changing buffer size. Changing the sample rate/buffer size just effects the total latency of all incoming audio, but I am measuring the latency from the start of the clock pulse and trigger recording(as there will always be some latency when recording), which always are bang on time with each other. Mainly testing it on a 2019 iMac with 64gm ram buy have also tested on a powerful enough windows device (not sure of exact specs though as it was my mates!)

                          Let me know if you need any more info!

                        • Steve
                          Steve commented
                          Editing a comment
                          That seems ok to me. Which input jacks are you measuring on the Micro?

                        • nktrnl
                          nktrnl commented
                          Editing a comment
                          I've measured them all. Inputs 1-4 seem to have slightly more latency of around 12-10ms. Inputs 5-8 are reading as about 8-10ms latency

                      • #14
                        Originally posted by nktrnl

                        Mines the opposite, midi triggers are bang on time, but analog triggers are about 8-10ms delayed
                        Have done copious amounts of testing with different chains and can't get the analog triggers to have less than 8ms latency
                        aah, I meant the other way round. sorry.... english is not my 1st language.

                        Comment


                        • #15
                          Any updates on this issue? I could hear one shots triggered by my noise engineering numeric repetitor were a bit off so recorded them and could visually see that they were off. Then I found this thread.

                          What's the status, is it fixable?

                          Comment

                          Working...
                          X
                          😀
                          🥰
                          🤢
                          😎
                          😡
                          👍
                          👎