Yeah. I got early Tempest vibes for awhile there.
Well, given that it kept working on the trim, itās possible it became overheated due to that. No idea how taxing that is for the hardware, but if it is, and it kept at it, and I let it go for minutes, then that might explain it.
For now, I wouldnāt bring the DT on stage, either way. Itās far too unreliable for that. Iām not particularly worried, though, if itās in software Iām sure Elektron has it covered soon, and if itās in hardware, Iām sure theyāll recall and replace.
Though it does raise another thought, unrelated to this thread so Iāll be brief - is Elektron just doing too much at the same time, given their teams and resources? Are they properly prepared to maintain and keep developing this amount of hardware and software, or is the DT launch a sign that theyāre just not geared up for the amount of quality stuff they want to put out?
I have no idea, and since itās off topic, Iāll stop now.
hm yea the perceived cool down time until it boots again makes it appear like it could be a hardware problemā¦ still think itās more likely some software glitch very early in the bootloader, who knows tho.
I dunno, likely a ton of the bugs & things people are having rn are gonna be squashed very soon with a planned update, to the point where I feel itās almost redundant to hunt for bugs & report for 1.01ā¦ feedback from Elektron staff indicates that a lot of things are still being moved around - should be more relevant reporting bugs for a more āfinishedā iterationā¦
2 Likes
Fortunately (until now) I have not experienced any rebooting issues. Hopefully for everyone facing these issues it can be solved within the next OS update, would be a real bummer to send back a DT for repair, but thatās the risk of stepping in early with these kind of machines.
Especially when these are so fresh and not been tested over a longer period.
1 Like
True. Letās look at this like pioneers. We are boldly going where no one (from the QA and test-staff) has gone before 
1 Like
They have already had 6 months since announcement to squash the bugsā¦ if itās easy to fix the bugs, I wonder why they released the device in this state just to fix it soon after.
Elektron must have encountered at least half of these bugs before units shipped. A release note informing early adopters of the state of things would have been the obvious/respectful thing to do? It wasnāt said to be in beta as far as I remember so some of the more obvious bugs should have been made public imoā¦
3 Likes
Donāt count on it. Even if they have a decent amount of QA people around, itās almost impossible in a test situation to match the climate of a live release, where hundreds or thousands of users just get their hands on the stuff and go about it with ways the developers never intended.
Even a super pro test environment, is still just a simulation of the wild. And the more complex the code base, the more you just canāt predict all the weird stuff weāll try with these instruments as soon as we get our hands on them.
You hit the nail on the head and I quote āletās look at this like pioneersā. It should be fun taking part of this. Of course I hope there wonāt be any real technical problems, but again, it can happen. Regarding the bugs, itās just a matter of time, being patient and enjoy playing with the DT.
2 Likes
I dunno man, Cenk looks like he rinses Elektron gear to the limits, Iād be surprised if even just Cenk as a lone OS warrior hadnāt hit most of the bugs people are ādiscoveringā 
Thatād mean that Elektron knew about all these bugs and launched anyway, without any notice to make us aware. I just donāt want to believe that.
Iām sticking to my pioneering blue skies, where being first at the front just means youāll encounter stuff no oneās seen before.
2 Likes
2 Likes
I have only a coupe hour with mineā¦ but I was experiencing some issues with the encoders not responding properly ā¦ they would not change the value then jump past where I was trying to get to. I donāt remember if it was a specific knob but Iāll try to pay more attention this tonight. Hopefully fixable via software update.
Ran into this exact issue last night. I only have an OT and canāt really get my head around where my samples live after I transfer them. Still havenāt read the manual in full yet 
the answers could be right in front of me
nope iāve already reported this one.
2 Likes
im getting crashes randomly after about 10 to 15 minutes of use. The only constant in the crash is that the pattern is playing while im adjusting sample parameters. The DT screen locks and the audio output goes to a high pitched buzz the same every time. Im only using the DT stock sounds and patters, just learning the machine, so its in its original state other than the upgrade to OS 1.01.
I can reboot instantly and oddly enough it goes to a random pattern on reboot. Not the same one I was playing before the crash.
Also Iām not using OB during the crash, just have the USB plug, the Midi in and Thru and audio cable and power. But only using in standalone mode.
If mine does anything like that, itās getting returned.
Even if itās software and patched in 1.02?
1 Like
I do recall now that my issues appeared after Iād made a clean reset. Before that, I had no issues.
Nope, I get this, too.