No “Sounds” in my unit either unless I’m confusing them with Samples which I doubt based on this description in manual:
When performing a factory reset on the Digitakt, it will overwrite and re-initialize the active RAM project (in- cluding all pattern, sound pool and global data). The +Drive project slot 1 will be overwritten and re-initialized with factory preset patterns, sounds and settings. Sound bank A will be overwritten with the factory sounds.
Do you have LFO enabled to modulate the sounds PLUS manual modulation? That might cause an issue. OR if the LFO type / configuration is not set to modulate through the entire key press. Just throwing stuff out there, sorry if it’s already been checked.
The DT is buggy responding to midi right now. OS 1.02 did not fix it.
Three crashes in one hour. All of them midi related.
I can’t use this thing for now. I’m putting it away until the next update.
@olle or anyone else at Elektron - I live next door to you. I can come over with my unit, hook it up to your debug gear and replicate these issues, if it’s of value. If so, PM me. I’m only happy to help.
Sorry for the silence. We’re all pretty swamped.
We have a good understanding of the MIDI related crashes and are working on fixing them ASAP. The sample loading related crashes looks to have been fixed already.
Yes it’s nice to hear from them! Now all we need to do is to figure out how to enable verbose output on Simon 
I think the first item is quite intentional: those global menus retain your “location” when you exit them by going to some other screen (other menu, or a sound parameter page). Hitting the menu button again simply brings it back to where you where rather than “restart from the top” each time.
This is useful if you need/want to jump out to the playing sequence and do something, while you are menu diving - you can jump back and keep diving. Setting up MIDI channels is an example of where this is quite useful.
Thanks for the heads up. Crunch time sucks for devs. Make sure they get some rest every now and again.
I’m on 1.02 as well and sequencing to Waldorf mQ. No crashes like everyone else reports. I troubleshoot for a living (network transport) and I understand how frustrating it is, especially if you can’t replicate.
have to say i’m really happy with my digitakt, i come from MPC world… yeah theres a few kinks but this is gonna be super dope when the few bugs are sorted…
Only bug i’m noticing is when I have a pattern & swap the samples they don’t trigger from the sequence they just go silent, this typically with track one.
Anyone else having this one? If so all good, i’m sure these dudes are working on it!
peace …
Matt
Thanks for the update! 
I may be wrong, but don’t the DT pages work the opposite of the other boxes? On my OT, AK, And AR you set pattern length track by track (if wanted). On the DT, today I hit a snag when:
I started with 16/16, selected per track length
recorded trigs on T1 16/16
recorded trigs on T8 64/64 using Live record. Started Live recording and noticed it looping at 16.
Quadruple checked it all- same result.
I had to make pattern length 64/64 before switching it to individual lengths and then I could access longer patterns.
Is this a bug or merely a new way of doing things?
I guess I’ve kinda just gotten used to the little quirks between silver/OT/analog boxes.
I only recently remembered that you can adjust the knob sensitivity on the MnM due to the wonkyness of the DT encoders.
Is anyone else having screen freakouts when trying to adjust sample start/end points graphically? Mine only shows a flat waveform when zoomed in. And even then it’s confusing.
I had this yesterday. More Worryingly as when I turned the power off and on again the power did not come back on. I had to do 2 more power cycles before it flickered into life. This happens again and it’s going back to elektron.
As Simon said we have quite a good understanding about the crashes, but I’ll send you a PM and invite you over anyway neighbour 
Hey Matt - you’re probably swapping the samples “up” the RAM list - the first slot (0) is always off. If you swap them “down” the list it should work.
If nothing else, we can swap stories and share coffee
Sorry to hear you got the same trouble. When it happened the first time and i could not turn it back on i thought that it is fried. 5 min ago i tried to make a kit and got the error three times in a row.
For now the machine is just not usable. Let´s hope for a quick and reliable update. This sounds pretty good:
Sorry if it has been reported before, but it seems that you can’t P-lock the track’s volume (the master volume, accessible from the Level/Data knob). Everytime I try to do it, the DT would say “Lock Mem Full!”, even on a new pattern with nothing recorded on it.
Happens on every tracks.