So I recently bought a digitakt, love the machine and work flow but found it difficult to record uninterrupted audio jams without experiencing glitches.
I have been trying to record into ableton with each drum on a separate audio track via overbridge. For the most part this works ok in terms of the audio being allocated to each channel, sometimes overbridge can’t seem to find the device but closing and re setting up the session usually fixes this. The real problems occur once I actually start to record.
At first the recording sounds great, but at some point the recording and digitakt will start to glitch/ dropout/distort, this usually lasts around 2-3seconds and sometimes sounds as though the digitakt is speeding or pitching up, then it will continue as normal. It can happen at any point but seems particularly prone to happening when I use either the Fill button or use the mute mode to bring drum channels in and out of the mix. I have tried various changes to the settings to get round this but with little success.
My specifications are as follows:
Digitakt: - latest firmware
- overbridge selected - clock receive -audio routing is standard
Overbridge: - beta 2.0
- coreaudio - buffet size 512, I have tried lower as recommended but did not fix. - output was none but just switched to core audio but same results
Mac desktop: macOS Mojave 10.14.6
2Ghz intel core i5 8GB 2133 MHz ddra 811.43 GB of 1TB available
Ableton: - Trial version, I found overbridge integration with logic poor so I downloaded ableton trial. I had wondered I this could have been part of the issue but having read about various problems with over bridge and not being a computer genius thought it might be something else. I also tried recording just via overbridge without ableton and encountered the same problems.
- audio input: digitakt core audio, or bit accurate have tried both - in/out sample rate: 48000, ableton won’t allow to go lower with digitakt selected - buffersize: I have read both that matching the buffer to overbridge’s and using a higher number such as 1024 should improve things but neither has fixed the problem. CPU: 3%
Sorry for the long post just thought i would be thorough,