[FIXED] Still no proper backup?

Ok, managed to. Simple procedure, but could had been explained in the manual.

For others likes me couldn’t figured it out.

1 create a new project, be within like you could create some patterns
2 don’t go in sysex dump menu, useless
3 Send the sysex via c6

That’s it, pattens and settings are writting one by one real fast.

4 u can save your project now

Note just after the transfer, my DT was chaining 2 patterns automatically , just hit stop or select only one pattern.

AND important here, samples are well assigned in slots like in the original project, not any problem on this side.

7 Likes

The calculated hash for a sample has nothing to do with its position within the +drive.

The hash is a unique id for the sample content which is independent from its name and location. As long as the sample content doesn’t change you can move it around, rename it, delete it and upload it again.

But beware of auto-sample conversion when uploading with different programs. This may change the sample content (changes the hash, too).

"unique" id: well, not completely unique (that’s simply not possible with hash codes), but the chances to get the same hash for different samples is really, really low.

2 Likes

It works by by just sending the sysex dump of the project with Transfer App (or c6) while the Digitiakt shows a regular pattern page. Previously I used the sysex-receive function from settings menu.

:relaxed:

2 Likes

All this aggravation because of this particular OS, which is different than the OT. The differences in the OS which I find somewhat weird. Why not the same OS, like the OT but on all the other boxes? I think it’s because that guy who developed the OT passed away and they don’t have the ability to port the OS to the different hardware platforms.

you are right, my wording was not very clever or clear.
and i was anyway wrong in the whole it seems.
my post also reflecting a growing antypathie within me…i have ashamedly to admit.
in that sense: Great that it was cleared now.

while: how is right now, is nevertheless not doing it for me in any way.
we have 2018 and i personally do not count the innards how they look on paper, respectivly how nice they can be made to look with proper wording
(in this case: ie. = its allready here ! )
but anyway, sorry ! need to be more cautious to what i suck me in myself.
negativity really beeing a trap for me these days.

That was the key instruction. Now, my samples are mapped correctly to their slots. Thank you! Who would think that “sysex receive” should not be used for sysex receive. :slight_smile:

1 Like

No matter what I do, it won’t import the sounds, only the patterns…

I backed up all the samples from my previous DT, and did Sysex dumps of the projects. Then on the new DT I copied the folders with samples from the backup to the new one with the Transfer app. Then I created a new project, and from the pattern page I sent the Sysex dumps back. All patterns get loaded, project settings too, but all sounds are empty… Doesn’t matter if I use C6 or Transfer app. And yes, I stayed away from the Sysex Receive menu…

Does anyone have an idea of what I’m doing wrong? I was using the 1.11beta6 firmware on the old DT, and have it on the new one as well.

Did you put the appropriate samples on the new DT?

Yes, I’ll edit my previous post, I meant “samples”, instead of “sounds” when I wrote that I backed up and restored everything with the Transfer app.

Also, after receiving the Sysex file the DT thinks that Track 1 points to Sample nr. -1, and it crashes as soon as I hit the play button. It doesn’t crash if I change it to Off or another number. It also does some other strange things when I try to reconnect the samples, like playing back samples in reverse even though they are set to FWD.

I asked Elektron support about this and apparently its a known bug in the latest version - OS 1.11_BETA6. As things currently stand using the latest beta it is not possible to restore a saved DT project. While it appears that the C6 app saves the sysex files - there’s no way to test whether theses .syx files are properly formed using the latest DT beta.

1 Like

Elektron - please sort this out. Breaking backup is possibly the worst thing to break in a beta!

1 Like

Thanks for the info! That’s unfortunate. I hope the error is in the restoring side of things and not in the sysex-files themselves, but we’ll have to wait and see. Usually I don’t do actual work on beta-software, but I wanted Overbridge a bit too badly…

1 Like

Yep … I’m sure things will be sorted when out of beta. Let’s hope it won’t take too long.