Weird sample behaviour - after a while

[tries.tracts-0r]

I also noticed the bit crushing on 2.2.4. Took me a while to wonder what had changed as I was mangled the sound to death anyway. A power cycle cleared it though.

[Marfusio]

Interesting. I was not aware that "excessive" CC data results in bitcrushing - I was under the impression it was a time oriented thing.

Do you find lots of CC msgs triggers the bitcrushing, and then it continues even if you solo that channel and/or send basic Note On/Off info only?
It seems only time oriented in my case

I guess it was a kind of buffer/memory overflow. It needs time to fill the buffer and or the memory gets fragmented which reduces the performance gradually. I don‘t know … but it seems to be corrected meanwhile.

[Satans Squidnipple]

Sending too many MIDI messages (e.g. LFO generated ccs) still results in bitcrushing after 15-30 minutes.

Interesting. I was not aware that "excessive" CC data results in bitcrushing - I was under the impression it was a time oriented thing.

Do you find lots of CC msgs triggers the bitcrushing, and then it continues even if you solo that channel and/or send basic Note On/Off info only?
It seems only time oriented in my case

[Marfusio]

Sending too many MIDI messages (e.g. LFO generated ccs) still results in bitcrushing after 15-30 minutes.

[Marfusio]

Did you use MIDI and a lot of cc messages?

[Steve]

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

[ocuvox]

+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

[Marfusio]

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

[Marfusio]

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!

[Marfusio]

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...

[Marfusio]

And happend again today…

[Marfusio]

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

[Marfusio]

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

[joeshi]

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.

[Steve]

We addressed this in firmware 2.2.4