Format my +DRVE is done, now I have to reimport my files library, I’ll try to not exceed the 7-8 gig of audio files, that was when it started to became tricky and my DIGITAKT was a barely usable brick.
1 Like
I’ve been complaining about this for years, and even reached out to support, who claim they’ve been “working” on it. I don’t think it’ll ever be fixed. It is, by far, the most infuriating bug for me with Elektron devices.
I have the same issue. Trying to transfer my samples to the digitakt 2.
(Transfer 18 GB of samples with the transfer app over midi is pain in the ass, but other story)
At some point the transfer failed and the digitakt hangs, sometimes with the same exception screen as in your screenshot. After that, every sample I try to import is corrupted and not usable. I can’t delete samples/folders via tracker or in the digitakt itself. All I can do is to format the +drive. I have spent the last 4 days trying to import my samples 
4 Likes
yukio
67
Transfer also failing here on Mac M1 latest OS X / Transfer version. Tried transferring 1.5 gb waves from a samples library (2 levels of folders). Crashed 3/4 into the process. Also the speed was only 0.33 mb/s. Seems archaic to me by today’s standard.
Firmware 1.01
3 Likes
After sample is recorded zoom behaves differently on start and end point. Start point seems to follow zoom setting while end zooms in 10x the track.
Did anyone upgrading from an OG Digitakt notice that the input is much more quieter on the Digitakt II?
I was using the Digitakt to monitor a Nord Piano but it’s basically impossible with the Digitakt II because it’s just too quiet.
2 Likes
After assigning sample to a track, sampling screen window gets messed up. All works though.
1 Like
similar examples of these rendering / absent artefacts were reported and addressed during testing … it’s much more likely to get a fix if next time you try to recall and note exactly what steps had preceded it, or to ideally be in a position to document the steps which repeat the outcome
even when the functionality is not impacted or it takes just going in/out of a page to tidy it, it still needs to be trapped as a specific bug to get fixed, easier said than done
Changing filter type while an LFO is routed to a selectable filter type parameter will visually display the new filter, but the one routed to by the LFO will still be in effect
For anyone coming to write about crackling audio the beta firmware resolving this is released now - it changes nothing else whatsoever, so it is safe to download whether you are affected or not, just don’t look for other changes if you are not affected.
See here
4 Likes
Did anyone notice that adjusting the micro timing feels laggy? I.E. the micro timing slider doesn’t react immediately after pressing the left/right buttons.
- Transfer had crashed many times, this started at +Drive filled > 10GB
- now I have corrupted samples in some folders
- I cannot delete folders in Transfer
- I cannot delete folders on DT2 (“Folder not empty”)
- If I select all samples and delete on DT2 it says for example “deleting 81 samples”, then freezes
@elektron is there a limit in path length on the device?
1 Like
I have opened a ticket about this issue two days ago, when your +DRIVE is corrupted it becomes impossible to sample or resample, because every new file will be corrupted too.
The only solution is to format your +DRIVE if you want to use your DT II or wait for a firmware update.
1 Like
Yes, will format, factory reset and try again.
The first chunk of my library transferred without problems, even with nested folders and long path names.
Problems occurred at > 10GB transferred data. And lost connection and freezing happened with increasing frequency until problems like corrupted data and permission problems occurred.
1 Like
If you select all samples in the folder and delete them first, then you can delete a folder. Not sure it is a bug, more like a safety feature.
1 Like
Unfortunately with the corrupted +DRIVE bug it is impossible to delete neither the files alone or the folders.
1 Like
You should be able to delete them from the machine itself, at the very least.
So the most exciting feature for me is buggy as hell! Elektron need to thoroughly retest midi track functionality and bugs in that area, I ran into multiple bugs listed below. It usually starts off working fine and then it goes sour.
- Tried saving midi track preset that I made on track 9 and Digitakt froze, had to reset
- Midi buggy in general, can work one minute, then switch pattern stops working when returning, no midi data been picked up in Ableton. When loading a midi preset that was previously saved it doesn’t work.
- On reboot midi tracks work again, but if I go to a new pattern and load my midi preset, midi tracks stop working on all patterns until reboot.
- Track 16, Val 13, 14, 15 on midi track dont send midi date at all, even after reboot.
- Digitakt crashed again when trying to load preset (conflict with midi track behaviour?). With midi track preset loaded on pattern 16 bank 2, this happens every time after rebooting.
- I loaded midi preset on tracks 9-16, after rebooting only track 9 would work.
- Note: I am sending midi via channel 10, cc numbers 16-32
7 Likes
