Weird one today, and I’ve owned and used DT for 6 years. There was a productive day of working prepping a live set, updating older patterns, and saving the project regularly along the way. After a power cycle, seems nothing that I have changed or added was saved. In particular, at first glance what I am seeing is Midi track channel assignments nor program changes have been saving.
Not sure this ever got solved and it got reported by a few people.
It only happened to me when I accidentally created 2 samples with the same name and loaded them into a project but I suspect this was a coincidence.
Never had an issue with 1.52
1.52 has the updates which allows you to turn off the backlights which for me was a game changer. Perhaps you got blinded by the 1.50 light show and forgot to save sorry. Joking.
Same thing happened to me… I made some changes on a pattern, copy&pasted it to the rest of the tracks in order to create variations during the next session, saved project (FUNC + SETTINGS) and turned it off. Next time i opened the project, all pasted tracks were blank. This had happened some months ago as well, but i didnt investigate it then. Today I verified that the reason was not that i turn off the power socket where the DIGI is plugged in. So I assumed that my unit was problematic… until I found this thread.
Anybody tried to contact Elektron about it?
Sorry, I don’t quite understand. Have you been able to replicate this problem, whenever you save a project and then turn off power at the wall power point?
I phrased it poorly.
I havent managed to replicate, no. After opening the project and finding out that the project save did not work, i tried to replicate by copy&pasting again the pattern, then saving, then turning off digi, then turning off the power socket.
Result: the pattern/project was saved as expected.
Maybe the time difference between turning off the DIGI and the power socket could matter ? (sounds dumb, I know).
I have faced similar problem once.
Projdect data corruption was caused by incorrect power cycling. This is what literally happened:
I have a saved project
I have unsaved vesion ‘on the fly’
I turn the unit off. Work is done for today.
I accidentally turn the unit on and instantly off so it doesn’t have a proper boot. A misclick.
I turn the unit the next day and try to work in the latest unsaved vesion ‘on the fly’. Unfortunately I save it in slot of ‘latest fully saved version’ instead of loading the ‘latest fully saved version’. As I would discover later, version ‘on the fly’ has some patterns missing.
Since that day I always load the latest saved version to begin my work.