Just got a model:cycles and I am thoroughly enjoying it so far. I made a couple patterns and when I went to record them into my MBP via USB audio I discovered severe glitching (audio skipping, weird noises and pops/crackle), which renders any recording unusable. The system is 16" MacBook Pro running macOS 11.1. I am connecting via the stock USB cable that came with the unit, plus Apple’s USB-C adaptor. Just to note: I can record the Digitakt the same way and it’s flawless.
Any ideas? Is this a known issue with the current firmware 1.12?
No, this is not it. I tried going to the biggest buffer size in Logic Pro at 1024, and even set the processing buffer to large, but I still get a pop or a skip once in 1-2 seconds. I also tried monitoring both via model:cycles and via MBP’s own headphone out, same result. Interesting, but I tried recording via my iPad Air and it works fine, with recording in AUM and buffer size set to 256. Maybe I should open a support ticket for this.
Update: can record into my iPad Air with AUM and buffer size set to 128 or even 64 samples. No issues whatsoever. Perhaps model:cycles is overwhelmed by the USB 3 data rate that the MBP is trying to dictate? Anyone else experienced anything like this?
I am aware of this issue, however, it definitely should not be as severe - people were reporting a small dropout or pop maybe once in a few minutes. Definitely not what I have, which is almost continuous stutter, pops, pitch drift. And again, I also don’t have this with the Digitakt, it’s flawless.
There used to be a USB audio dropout bug in DT and DN that’s now in the M:C. It hasn’t been fixed yet, as far as I know. More info here. This might be the problem that you’re suffering from. EDIT: Ah sorry, that bug’s about USB audio going into the Cycles.
An unrelated issue: I got massive dropouts from trying to MIDI-control the Cycles via DAW while recording (a lot of MIDI data with multiple tracks etc). I got an answer from Elektron that this is simply not possible due to hardware limitations. It seems like that’s not what you’re trying to do, though, but I’ll mention it here just in case, if someone comes looking.
when I switch back and forth between interfaces Ableton will reset something internally and set itself to 96kh. I’ll get the same symptoms you’ve described here. (tr-8 has been notorious with regard to this… for me anyway).
when I set the audio settings back to 44.1kh the problem goes away.
I suggest you try connecting Cycles to another computer to see if it works there. If not, it’s probably time for you to contact Elektron’s tech support or to get the unit changed under warranty.
I have tested it with four other devices (including older MBP and MBA) and it works perfectly fine. It’s only my 16" MBP that it has problems with. Elektron said that it’s the widely known T2 chip issue, but I wonder why the same doesn’t happen with the Digitakt - it works great with my 16" MBP, never had a single dropout or anything, and I have recorded many hours. Anyway seems to me that model:cycles simply has a different USB-audio implementation, which is less robust with certain USB-C bus setups.
Yep… I have the same problems. Clearly Elektron has some issues working out USB audio. Not a shame, just annoying. It is obviously their first time dealing with USB (besides data transfer) and I guess they didn’t hire somebody who knows this stuff but rather tried to engineer it from scratch and going through all the “beginner” mistakes (wild guess but seems to be the case until proven wrong).
On the other side: Has anyone read a statement from Apple or the community saying the T2 issue is solved for good? I haven’t… but I can say: M:C is not usable with USB audio unlike Digitone which works at least in one way stable (still have to reboot the device from time to time when sending USB audio from Macbook to Digi / using it bidirectional).
There is an elephant in the room.
By the way: To all people working with a PC - is everything working 100% fine with Model-Series and the Digis with USB audio or is this problem only with the T2 Chip-Macbooks? Can we narrow it down maybe?
Yeah it’s a bit of a bummer. I asked them why there is such inconsistency - I am guessing the USB implementation is just different on the “lesser” models, whether it be software, hardware, or both.