The upcoming 1.10A version has been tested for a little while and we’re now adjusting some last things. Will be released to public as soon as it is ready.
Can also confirm some of the user reported bugs above:
10 Likes
DT 2 with 1.10 : occasional short term freezes where pressing STOP without me holding FUNCTION clears or undos clearing trigs, instead of stopping the running sequencer as was intended. The sequencer does not react to STOP at all, just keeps running … Then suddenly it responds to my franticly pressing STOP button, and stops.
Is it something that usually happens to individual units or is it a bug actually?
1 Like
One might think it’s probably natural due to DT2 being heavily burdened by massive amount of P-locks and trigs , and all 16 tracks running at different resolutions , with LFO modulations etc. etc. But no, only three or four tracks, and not many P-locks or modulations… I doubt there is such computational burden that should cause such behaviour…
1 Like
Never heard about it before, so please contact support, preferably with your project and a video when it is happening and they will take it from there. If you want to check your buttons, you can enter test mode.
Well, Test mode was used twice, nothing suspicious there, but yeah, I was going to submit a ticket, but thought first that forum people could know something… Thanks anyway)
1 Like
Hope that’s here for the weekend 
3 Likes
Going to post this here since a reddit post was the only hit and it had no solution. I’ve already reported it to Elektron but the first fix (noted below) doesn’t work.
This update caused an error to pop up: ALERT FAULTY SAMPLES FOUND. PLEASE UPDATE TRANSFER, BACKUP PROJECTS AND THEN FORMAT +DRIVE SAMPLES. CONTACT SUPPORT FOR MORE INFO.
Support said I’ll need to format my +drive and provided steps on that. The issue is that one of the steps notes: to close the “ALERT” error message and use the unit, you can press [YES] or [NO]. In some cases, you may need to press [FUNC] + [YES].
The issue is that it won’t close with those or any button combos I can think of so I’m currently sort of bricked. I’m sure support will have a solution, and I’ll post it here when I get it, but thought it might help others w the algo.
Update: It’s midnight or so in sweden so I’m not expecting a response from elektron, but some nice people over on Substan’s discord helped me out (shoutout to Myk and dzyndzel).
Going into test mode and downgrading via DIN cable (30 mins) still brought up the issue. The key is that unlike in 1.10 I COULD use Y/N and back out of that ALERT screen and format the +Drive. I’ll wait for the next iteration of the OS.
4 Likes
I tried to p-lock post/pre on the base width filter and got immediate audio drop on the sample. Could anyone verify?
Just in case I am posting a video of the issue I described earlier; maybe somebody had similar occurrences. Looks like this:
Test mode didn’t reveal anything bad - according to it the unit is OK .
I’ve submitted a ticket, so possibly it will become clear what’s the deal with this.
1 Like
Hi,
i have the same now with my DT2. But looks like only with one pattern. It freezes after a while with the same screen.
I opened a ticket at elektron.
Could be some MIDI problems. Midi goes from Launchkey to DT2. When i start playing the Launchkey (Arp) it crashes…
Interestingly, this ‘stuck’ state actually returns to normal after about 20 seconds. And I don’t have much going on on the three tracks to account for that…
Not sure if this has already been mentioned or if its even a bug or intentional? So… the new UI update for Mod destinations is great, I love the fact we can hold down function and jump to a category quickly. This works for LFO’s but not for Mod Wheel, Breath Controller and the others. Intentional or overlooked?
1 Like
thanks because right now this is reaaalllyy annoying
Hello everybody !
First, I’m am a french speaking guy and I don ’t really speak English. So I will do the best I can.
Since I installed the last update on my Digitakt 2 (1.10) I have an issue about the “sample replacement” on the SRC menu with FUNC+YES…
I think the easiest way to be understood is to give you an example !
Before the update : I wan’t to replace the sample of the track 1 (let say “BD Palak”), i press FUNC+YES on the sample and i’m directed to the folder “BD Hard” (so basically the folder of the sample). I choose an another sample in an another folder and i replace it. Then, i want to replace the snare sample on the track 2 (let say “SD Stank”). I press FUNC+YES on the sample and I am directed to the folder "SD Snappy. Everything is fine !
After the update : I wan’t to replace the sample of the track 1 (“BD Palak”), i press FUNC+YES on the sample and i’m directed to the folder “BD Hard”. I choose an another sample in an another folder (let say « TECHNOKICK24) and i replace it. Then, i want to replace the snare sample on the track 2 (“SD Stank”). I press FUNC+YES on the sample and now I’m directed to the « TECHNOKICK2024 » folder ! Do you know what I mean ?
Maybe it doesn’t feel like a real problem for you but i’m annoyed about this …
Do you notice the same thing on you Digitakt ? Anyone know if there is a way to fix this ?
Thank you so much for your help and have a nice night !
I think your problem is the same one described here.
2 Likes
Thank you !
with firmware 1.10, trying to save a kit from a pattern and applying it to another one. Mysteriously, the sample slot of track 4 has the wrong value.
On a brand new project it looks like no sample slot is saved in the kit:
- create a new project
- modify the sample slots on various tracks
- save a kit
- load the saved kit on another pattern
- the sample slots are back to default values
Problem noted above
2 Likes
any news on the bugfix for the kit save regression so far ?
5 Likes