Just unboxed my brand new DT2. Updated it to firmware 1.15A when all of a sudden all samples are erased from the factory patterns. When I try to load a new sample or open the +Drive the whole unit freezes requiring a reboot.
I have tried reinstalling the firmware several times, as well as a factory reset and +Drive format. When formatting the +Drive the device freezes again.
This appears to be a question for support, it sounds serious
It would probably help if you explain to them if it worked before the update and how the update went, but whilst i’ve never heard of a similar report it sounds like an unhealthy device
it may be recoverable, but the best advice will come from support if you can describe your whole experience with it to them
I already made a ticket, but I figured i’d try here aswel.
I did notice when booting up the unit for the first time, before upgrading the firmware, the boot up screen displayed 1.15b.
I didn’t think much of it an asumed 1.15a was the most recent so I upgraded immediately. From here on the problems started.
i genuinely don’t know, but my hunch is this may be significant … but i have a further hunch that the update was likely not even needed, but i guess you’ll find this out and if it contributed (although it obviously shouldn’t have resulted in this)
some letters, depending where on the screen they are, mean more to Elektron than the end user - so be very clear where the B was
Most likely defective unit I’m afraid.
Trying test mode now, and when doing a key test trig 1 doesn’t light up and give a white screen, trig 2 doesn’t light up either and gives a black screen.
Other trigs are responding as they should.
if you got into test mode (to try the trigs/encoders) without any listed errors it’s a decent start i guess
maybe there’s something about the installed firmware which is unique to your board which is why they sometimes use these additional letters (normally remote from the os version) … pure guesswork
maybe it will make sense to support, you might be asked to send an update via DIN as sysex whilst in the startup menu or so on … it might be something they understand or maybe it is borked ?! it is bad timing to discover it on a Friday afternoon though !
I’m on 1.15A which according to the support page is the latest.
My boot up screen has 2 'A’s on it, looks like
A 1.15A
Where did the B show up on your screen, left or right ?
Not that this will help with your problem any … but it would be interesting to know if another firmware was floating about, or if it’s the left letter that was a B … suggesting a hardware revision maybe (following @avantronica 's message above).
The B was displayed in the right bottom corner as “1.15B”, on the left bottom corner was displayed a single “A”.
Now my boot up screen looks the same as yours.
got the exact same problem here!
try 2 new devices in store cause I thought the first one was defect.
But to saw your post and that the same thing happen to me today, makes me think that there’s a software problem in the new batch of DT2…
I tried the in store demo unit with the most recent firmware 1.15A and everything works perfectly…
Also created a ticket for that, we’ll see what happen.
Same thing just happened to me too. After buying a Tonverk as soon as it came out… and then this with a brand new Digitakt 2, I’m starting to feel a little bit beat up.
Did anyone have any further luck re support for this issue?
Same issue here. Brand new device, running 1.15B when switched on the first time.
I was thinking the right thing to do is to update 1.15A, so did that before anything else.
Got no sound. Re-installing latest OS, factory resets and test mode gave nothing so I was thinking I have faulty main out and headphone out in my hands.
But reading this now I realize that most likely the samples got erased. Maybe bit impulsive I returned the unit to the retailer and waiting for a replacement as we speak. When getting the new device I’m going to hold on any OS installs (assuming it has the same 1.15B) and see how it works. Will post here.
Would appreciate any updates if anyone gets further information.
Sounds like a new revision required a minor firmware update that was not yet released to general public. 1.15B is newer than 1.15A.
There is a chance that when you get your hands on the 1.15B from support, you can upgrade back to it and issues should be solved. But since the device was (possibly) never meant to work with anything less than 1.15B it also might not. better wait for support to reply.
From the top of my head I was assuming that the B stands for Beta, and based on that I installed the 1.15A. But could it be that new batch of units are shipped with later build than publicly available, and installing 1.15A is actually a downgrade, causing issues?
I just got a brand new unit too a week ago or so, it was equipped with something prior to 1.15A (can’t remember the exact digits, no letters tho), instantly updated to 1.15A as that’s the only one available at the moment - everything seems fine, also transferring about 4GB of samples and basic tests produced no errors or supernatural phenomena so far.
Let’s see what lies ahead. Maybe we gonna get the x-fades from TV in “B” once B’s official lol.