I’m having a problem with audio artifacts, pops and clicks, when using one of my custom drum kits. It was working earlier, but I think something happened to the SD while it was overwriting, and now, even after formatting the SD, my kit is creating these artifacts during playback. This happens only on the pedal and not on BBMO. If it helps to know, I am on the latest firmware and the kit is only 70mb. Other custom and factory kits are working fine. Is there a way to fix this? Thanks!
Is this the only option you see possible? Like you didn’t change the tempo or anything
For me this is arguing that it’s not the SD
This too
My first idea is that it’s a bug in BBMO, since I believe there have been similar issues where user defined stuff doesn’t work while default works
I’d guess you haven’t modified other kits than those that has the issue, is this correct? If yes, then I’d like to ask when did you modify it last time before it started malfunctioning? This could help to identify if it’s a new bug in BBMO 1.5.2 or already in an earlier version
Those are good observations. Didn’t change the tempo, no new samples. Can definitely rule out the SD, since I tested another one and got the same glitch. Was there an update to BBMO recently? The last time I modified my project was probably no more than like 3 days ago.
A new development: I can hear artifacts during playback in BBMO with this drumkit now wearing headphones. So it’s not anything to do with the pedal, which is good. Also hearing the pops in legacy version of BBM, so we might be able to rule out BBMO as the issue.
When I click to preview a sample, the pops consistently come in at a delay. For instance, I’ll click on a tom sample three times, and after 1 second, will hear 3 corresponding pops. All the artifacts appear after the sample playback ends, repeatably. And that is a strange thing that just started happening today when I tried syncing to SD.
So, to update the situation: ruling out the SD, BBMO (likely not), and pedal itself, the issue seems to be with how BBM/O is computing the sample info, and whatever change made it act that way starting today. The samples are otherwise clean when playing from the source .wav file.
Yes, I don’t remember the exact date but it could’ve been within couple days
I was just about to ask this
My guess is that the wav file ends with some noise/value other than zero. Apparently the BB/BBM/BBMO doesn’t do smooth transition from that value to zero and that causes the pop sound
These kind of issues are typical with loopers/loops that end/start with different values
You should be able to fix this by cutting the wav at a point where value is zero Or by doing the smoothing yourself