Also worth noting. I found in the Release notes for 1.30 to 1.30B that this may have been an issue that was fixed in that update. I really hope it’s not a bad capacitor.
This happened to me again this morning.
Digitakt running 1.30B.
Made a lot of new patterns last night. Moved between them fine. Saved all in Temp (i.e. didn’t hit FUNC+Gear before powering down).
This morning, turn on the Digitakt and all the new patterns are gone.
I think I might’ve turned the power off while it was in Play mode, which isn’t ideal. Maybe that caused the bug? But this has happened to me before after the new firmware update–patterns disappearing after power down.
Hi, just a silly question really - I updated my DT today from 1.40B to 1.50, with new Transfer 1.6,
all smooth and nice but at the very final stage (rebooting) at one point the graphics stopped showing any progress so I waited a few minutes, nothing happened and then, well, I just turned DT off and then on again after a minute or so.
Would you say it’s anything to worry about or all’s good since now it politely says 1.50 on the power up, machines are there and so on? I am pretty sure when I did it previously (1.4A to B) the reboot / restart indeed was automatic, hence the question. Confusion will be my epitaph Thanks for help!
I wouldn’t worry, my DT sometimes gets stuck during boot up, I just turn it off again and back on after a couple of seconds and it’s fine.
Yeah, I think mine wasn’t a perfectly smooth update, hanging on reboot so I had to switch it off.
No problems since.
Maybe it was a bit overwhelmed and needed a bit of a rest to psyche itself up for was it was about to engage in, what with all the new machines etc
Thank you! 1.50 stresses me out for some reason
So, it has happened to me more than once that patterns or sounds that I programmed the day before disappeared the next time I boot (i’m on 1.50). Far too often than it could be my own stupidity every time. I startet saving like a maniac. Yesterday a complete pattern disappeared from me, which I have been rehearsing with my band for about two months and on which I no longer work directly. I usually just turn on the song mode in the rehearsal room and off we go… but yesterday everything was suddenly gone. ok, the sounds were still there. but all trigs from all tracks are gone. That just can’t happen. I haven’t made a ticket yet but it’s probably the best idea…that just can’t happen. it’s killing me
It’s definitely an issue although strangely, it hasn’t happened to me for a while but I now save a backup copy of every project I’m working on to make sure.
Yeah, but now I have the feeling that before I make a backup, I have to check every pattern from the project beforehand. it could be that something is missing all of a sudden.
I’m assuming that if it’s saving a duplicate then it’s saving everything in the project and on those occasions when you’re losing work the DT isn’t saving anything at all, but I could be wrong.
Please do, it will probably help to prioritize this.
is that so? that would be great of course. Can anybody confirm this?
in this particular case, i worked the whole evening on something new and we wanted to play through the set afterwards. so now i can decide what i lose if i put the last backup back on…but i made a ticket now, let’s see what comes out of it
It happened to me again and again. But not always. Could it be a broken capacitor? If so, wouldn’t it be reproducible? It isn’t.
Keep reporting these issues! Elektron is watching.
This week I had an instance where the previous evenings work had disappeared when I returned to my Digitakt.
I had saved the project though so when I reloaded it all came back.
Please report this to Elektron, if you haven’t done already. Cheers mate!
I’m pretty sure jump step record is (half) broken. It works maybe…30 percent of the time. Usually in a fresh project and it will work, but most of the time it doesn’t. There’s a slight chance of user error on my (and others) part but I’m pretty sure it’s just bugged out. Hope for a fix soon!
Any news about the disappearing data? I refuse to believe that we all have broken capacitors after updating to 1.50
How many capacitors does a Digitakt contain? 50? 500? So it is simply stupid to assume that the same capacitor in every DT blew up when 1.50 came out.
same happened to me
Sequencing and CC’ing microgranny with DT.
Somehow whenever the DT is running midi cc is not being transmitted properly, the encoders that are assigned to parameters of the Microgranny don’t do anything.
Only after I press stop on the DT the corresponding encoders on the DT transmit to the Microgranny.
I had similar weird issues going on when sequencing and CC’ing the 0Coast.
Anyone else with a Microgranny has similar issues?
Someone with a MG kind enough to replicate the issue, sequence and automate it from a midi channel on the DT?
Don’t know if this is a OS 1.50 bug but I just found that if I disable a trig when the sequencer is at the step just before this trig, the trig is still played.
Say for instance Trig 8 is enabled and I disable it when the sequencer it at step 7, Trig 8 will still be played when the sequencer arrives at Trig 8. This happens just once and then the next time the sequencer arrives at Trig 8 it will not be played.
This is more visible when the sequencer stays a long time on each step, at very low bpm or when choosing a low track scale, like 1/8x
Anyone can reproduce?