Monitor in for sampling USB(L+R) audio still doesn’t work. Previews of samples over USB audio fixed though.
Thank you for the update.
One thing I noticed which hasn’t been resolved is sometimes certain audio tracks drastically drop volume. For me, it’s only been an issue on tracks 5, 6 and 7 on a particuliar project. Sometimes the audio track volume level is fine, sometimes it’s not. Seems to be very random.
Anyone else experience something similiar?
With the original DT sometimes a lfo on pan changed to volume, maybe the same thing is happening here?
Have you checked the compressor settings?
I got ce get more then once…
When pressing FUNC+Samples, if you go into +Drive or Project Ram and then press “no”, it will make you go back directly to the main page (like if you press “no” two times in a row). I had an issue that didn’t let me delete a folder, so i went for a factory reset + format drive, but now i noticed this bug, and it’s pretty annoying.
1 Like
Has the input volume been fixed yet? Or is that a hardware issue?
fixed 
input vol was my main issue.
5 Likes
It’s known about, pretty annoying indeed, hoping next update fixes it.
I had the exact same bug today. Could not delete an empty folder on both the machine itself and transfer.
After formatting the +Drive it becomes ok. But I’m afraid it is something related to “when +Drive reaching a certain capacity” like the previous bugs are, and may come back at some point when I copy my sample library back to the machine. Plus the fact it takes years to copy my 10GB sample library to the machine, I feel quite reluctant to do it now.
By the way, when I was trying to update the machine, it stucked at the first time. I restarted the machine and transfer and tried the second time then it worked.
Agreed. Trying to sample via USB but unable to monitor. Just shows N/A for Mon option
1 Like
I never had any issues with this. I’ve backed up and loaded projects a bunch on the last version of the firmware. Maybe this was a selective concern?
Any P. locks do not affect retrig notes
When a MIDI track CC are set up with values (for example 70-77 with 127 value) a trig without any p-lock sends 0 values for 70-77 CC’s. Same bug was in Digitakt 1 but it happened sometimes and only when Func+No was pressed. On Digitakt 2 it happens all the time trigger plays.
Here is the link to the similar Digitakt 1 bug: Digitakt 1.51 : Bug reports - #176 by zhelnerovichda
And this happens on Digitakt 2:
2 Likes
Recorder length is not accurate enough. For example if you choose 16 step R.LEN at 120 bpm default tempo the recorded file is shorter than it should be. If you try to record 16 step loop (trying to make seamless loop without clicking) you’ll fail. The recorded file will play with click if you loop it with play mode FWD.L.
You can see how shorter the recodred file is (It should be exactly 2 second length):
Digitakt 1 does it properly:
26 Likes
Hi All
-Step Recording (standart and jump) mode in midi track doesnt work with 1.02
-Also in Grid mode trig + keyboard doesnt allow to input notes for both midi and sample tracks
The Transfer app experience is pretty bad, so bad I’d go as far to say it’s currently unusable for me
- Generally very unresponsive and slow
- The spinner on the right spins constantly
- Reports “active requests”, no matter how long I wait it never clears until I switch off the DT2 and switch it back on
- Changes such as new folders and samples are not shown
I’ve never been a heavy Transfer user, but I never had any issues using it with my Model:Samples from what I recall.
1 Like
I posted this in the other thread, but figured I should post it here as well.
My transfer app crashes as soon as I press the ’explore’ tab. I’m running a MacBook Pro M1, Sonoma 14.5, Transfer 1.8.10 and of course 1.02 on the Digitakt II
Do you mean 1.8.10 ? That’s the newest one. Available on the digitakt 2 support page.
Yes, sorry. I meant 1.8.10
Try to switch to MIDI only in Digitakt’s USB config. It helps for me. Nevertheless it’s a crucial bug certainly.