Announcement

Collapse
No announcement yet.

Weird sample behaviour - after a while

Collapse
This topic has been answered.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weird sample behaviour - after a while

    Has anyone experienced samples distorting or changing character (as if it's FM) or whatever, after a certain period of time? I've found that I can load up a sample (example a flute note) and then have CV elsewhere control the pitch, and everything sounds great. Then over about 10 or 15 minutes the sample suddenly sounds as I've just said 'distorted' and changed. I've tried everything, checking the settings (nothing changed) and whatever I can think of but I cannot get it back to the original sound. However, if I switch off the Bitbox Micro and restart, it's back to the original sound .

    Has anyone got similar problems, and maybe has a solution. Or, maybe 1010 can explain the bug, I'd be most grateful.

    Thanks in advance.
  • Answer selected by Steve at 01-03-2023, 09:05 AM.

    We addressed this in firmware 2.2.4

    Comment


    • #2
      Please always share firmware by exact number. A video of what you're experiencing may also help us or other users diagnose the issue.

      Comment


      • #3
        Originally posted by Lucas1010 View Post
        Please always share firmware by exact number. A video of what you're experiencing may also help us or other users diagnose the issue.
        Firmware is 2.2.3.

        Comment


        • Lucas1010
          Lucas1010 commented
          Editing a comment
          Thanks. Please share a video of what you're experiencing, try to show the settings you're using as well.

      • #4
        Hi Lucas, I can't share a video, as I don't have that possibility, however I'll upload a soundfile of something so you can hear what is happening (after some time).

        Comment


        • #5
          Sounds like you have the sample getting bitcrushed issue, try newest beta firmware, seemed to help me!

          Comment


          • #6
            We addressed this in firmware 2.2.4

            Comment


            • #7
              Okay, I will do.

              BTW, as usual the issue hasn't come back - but if it does I'll post a sample. In the meanwhile I'll try the updated firmware.

              Comment


              • #8
                After about 30-45 min. using the Bitbox as drum machine triggered by Midi, the sounds start to get distorted again. (don‘t know if it has to do with midi). Reloading samples or sets doesn‘t help, also silencing effects. Only restarting helps (power off). Makes it unusable for me in live playing situation. Can you tell me, which firmware doesn‘t have that problem, so I can use it until this is fixed? Thank you

                Comment


                • #9
                  Sadly, I‘m still having this issue in FW 2.2.4, see my new topic posted…

                  Comment


                  • #10
                    And happend again today…

                    Comment


                    • #11
                      OK, I tried again today and let a sequence self running only triggering the gate inputs. It run for hours withpout problems but I left everything alone and didn't do anything else with the bitbox. After that, I reconnected MIDI and let it run for a while (1 hour), it also behaves quite normal. But after I started to use the screen and work with some parameters, it starts again to bitcrush afer about 20 minutes. This time I also let a record monitoring audio run through the device, the sound started also to bitcrush after a while. Interestingly the bitcrush desappears after triggering again one of the samples. But it came again after some minutes. Really strange. Maybe it helps you to find the problem. Seems the CPU has to much to do and can't update the audio buffer fast enough any more. Is there a way to show the current CPU load somewhere? Thank you...

                      Comment


                      • #12
                        Originally posted by Marfusio View Post
                        OK, I tried again today and let a sequence self running only triggering the gate inputs. It run for hours withpout problems but I left everything alone and didn't do anything else with the bitbox. After that, I reconnected MIDI and let it run for a while (1 hour), it also behaves quite normal. But after I started to use the screen and work with some parameters, it starts again to bitcrush afer about 20 minutes. This time I also let a record monitoring audio run through the device, the sound started also to bitcrush after a while. Interestingly the bitcrush desappears after triggering again one of the samples. But it came again after some minutes. Really strange. Maybe it helps you to find the problem. Seems the CPU has to much to do and can't update the audio buffer fast enough any more. Is there a way to show the current CPU load somewhere? Thank you...
                        I did a backup, reformatted the DS card and copied back may data as suggested by the support und let it run again. As far for now, I havent't any issues any more, cool! Beside that I also bought a faster SD card version as this was also suggested by the support: A SanDisk Extreme PRO A2 with 128 GB... hopefully it would work now flawless. Thanks to the support!

                        Comment


                        • #13
                          Oh no, it started to bitcrush agein... seems not to be the solution. Contacted the support again.

                          Comment


                          • #14
                            +1 Bug Report.

                            Firmware version 2.2.4. Factory standard SD card.

                            Issue: Samples become heavily bitcrushed after extended use.

                            * will try to identify "steps to reproduce" and post once found
                            Last edited by ocuvox; 01-23-2023, 04:10 PM.

                            Comment


                            • #15
                              Check your Master output levels and compressor settings. We did find this to be connected to those settings.

                              Comment

                              Working...
                              X