Digitakt 1.03 : Bug reports

Can’t you switch the tt78 to an empty pattern- so the sequencer is running but doesn’t trigger anything?

1 Like

That’s a good idea - thanks.

I’m curious if folks who are experiencing crashing on 1.03 are experiencing these crashes while in Projects that were created in 1.01-1.02.

And I wonder if anyone is experiencing crashes in 1.03 while in a Project created in 1.03 , and if so, what are the conditions of those crashes?

3 Likes

Dont forget to also get your sounds out of bank A!

1 Like

Interesting. I will try this and report back.

Deluge looks interesting! thanks for sharing

I keep getting crashes in midi mode this happens mostly when I stop the sequencer it freezes.

I worked on a project today on 1.03 and it froze repeatedly when saving. I wonder if it has to do with me using different pattern lengths for different tracks. Anyway it would save and then lock up on the screen that says “Done”. You have to do a hard shutdown (turn it off) to get it to work again.

no crashes here on 1.03 projects thus far. extensive sampling, sample importing, loads of locks, different track lengths, trig conditions etc. DT din midi master controlling a beatstep pro, volca & ms20 mini. ain’t tried midi in yet or usb midi.
nb - saving projects using pattern menu, not func+cog shortcut.

It’s weird that the quick save shortcut crashes but the other way doesn’t. Since they’re likely calling the same code, it’s probably a threading issue - wait, do these embedded OSes even have threading??

1 Like

Mine freezes when I stop the pattern with midi or without never did this in 1.02

had my first exception crash ever 5 mins ago with 1.03… loading a small sample from my Recorded folder to active project.

already created a ticket - hope they´ll be able to fix it rather sooner then later :-/

1 Like

Ditto.

Freezing quite frequently upon saving projects with 1.03. Stopping playback before saving helps, but even then not 100% reliable.

Additionally, after power cycling the frozen unit, one time it also got hung on the initial load screen, showing the logo and OS, but never progressing to the logo dissolve or further without power cycling again. :confused:

Crashes when loading samples: much less frequent but still happening - I got one crash so far.

Update: crashes seem to have been replaced by freezes. It is also very random - e.g. loading the same sample that caused the initial freeze will not recreate the issue

Discovered bug-
set Master length to infinite and the chain length to what you want, say 64. Now chain the pattern If you only play the pattern once in the chain it’s fine but play it more than once and it never changes.

I’m getting the same extreme slowness when saving samples that was reported earlier. Previously with 1.02 the saves were nearly instantaneous. Now they take several seconds each. Does it make sense that saving a 0.25 second sample takes 7-10 seconds?

Update: I tried downgrading to 1.02 and the saves are much faster but the “Saving” message is no longer displayed while the sample is written to the +Drive and saving still takes twice as long as it did on 1.02 previously. Ugh.I also deleted most of the files I had already transferred to the +Drive in case the issue was due to a lack of space (unlikely but worth a shot). That made no difference. I am so frustrated. Whoever decided to release this device for sale before so many major bugs were fixed should be ashamed.

I deeply regret ever upgrading to 1.03. I highly advise everyone to stay away from this release.

On the SRC screen the sample select seems to be opening on its own now and then, I have noticed it most when adjusting tune and play direction but it could be a coincidence. Sometimes the screen bugs out as it flicks back and forth between the two, I wonder if its an encoder problem as there was a similar issue with others registering .01 movements on there own in both previous updates, anyone else getting fantom encoder drift?.

1 Like

When in assign and scrolling thru samples, the sounds play in the proper list order but everything is offset by one or two slots. So sound 1: kick. Might not play until I scroll to sound 3. And so on and so forth.

I seem to be getting a sample playback bug where if I load in and replace a sample too many times in a row that pad will stop playing until I reboot. I have had a crash while turning midi cc knobs while running a sequence for an extended period also.

1 Like

Yeah, while midi seems much more stable 1.03 seems like over all a much less stable build… maybe try moving your sample to another folder, who knows it might load in… or renaming it, file systems can be fickle