Ah gotcha. Could the second comment here help you? Digitakt Organising samples, sounds frustration
Can you say what you’re doing specifically and at what point it’s not working?
A - selecting the Digitakt midi usb
B - selecting dump sysx
C- dropping the sysx file into the transfer app
Files show as if it was transferred ( green color at transfer app), when I go to the Digitakt it won’t show on any bank nor a samples folder
PS: when I drop manually wave files into the transfer app I can find the files ( wave samples) into the sample folder. Is it correct that the sysx files will be organized in my Digitakt banks once I get it to work?
Are the sysex files sounds?
I’ve only done it how the Electronisounds video shows, which again was using C6. But one tricky thing was choosing which Sound bank the sounds should be put in. Is it possible you put them in a Bank different from bank A where the factory Sounds are?
Choose a Sound bank by turning the Level knob to browse Sounds, then tapping one of the 9-16 trig buttons to select a bank.
First: No, the Digitakt does not store or organize SysEx dumps the way it does samples. You cannot store patterns or projects in the +Drive along side the samples.
In fact, you can’t store patterns at all in the +Drive, only projects, and projects aren’t stored in a nice directory tree (like samples), but instead in a list of 128 project slots. This list is in a totally separate area of the +Drive from the samples.
Now, turns out that transferring dumps is even more awkward: You cannot transfer to or from that list of Projects in the +Drive. Instead, you can only transfer to/from the currently loaded in memory Project. When you use Transfer or SysEx librarian or whatever to send a dump file back to the Digitakt, it is simply overwriting what is currently loaded. If you don’t save it to the +Drive (Settings 
︎ > Projects > Save Project As), then it will be lost as soon as you load another project.
_(And a warning: If you load project X from your +Drive, and then hours later decide to transfer a dump of project Y from your computer… The DT will think you have just changed the data for project X, and if you use the Save Proj command (Func + ︎) you’ll overwrite project X… probably not what you want.)
All that being said, may I humbly suggest you try using my free, on-line, no-installation software, elk-herd? It will let you peer into your downloaded Project dumps, as well as organize your sample directory tree in ways that Transfer cannot. See thread here: Elk-herd 3.0 beta: Project Import at last! - and I highly suggest watching the two short videos at the top to see what it can do and how.
10 Likes
elk-herd for the win!
1 Like
thanks for the links and congrats on a great tool. I was able to manage my samples (wav) with control! The only thing is, sysx files, don’t see how to make it work. Thanks again
Click on Projects on upper left area. SysEx files are project files. They are managed separately on the DT from the samples in the +Drive.
1 Like
MZero, your work is legendary. I so appreciate your work. I have some basic questions about the interface - like how to minimize directories to make scrolling more efficient. Can you point me to a manual or video? Thank you again!
thanks for answering and sorry for the delay, I was out of town. I did click on the project and then tried to import and open file (SysEx) although I get this error:
Error reading project:
Does not parse as SysEx messages (unknown sysex type 2)
thanks
Can you tell me how or where you got this SysEx file originally? The message “unknown sysex type 2” means that the file contains an Elektron sysex message, but it is neither the +Drive API (used for samples), nor the dump messages (used for Projects). As far as I know, this type of sysex isn’t generated or used by Digitakt.
1 Like
those are files from elektron’s page, the free packages they have there. I think they are not Digitakt, but they are SysEx
thanks,
SysEx isn’t a universal format: It is just a standard way of packaging up synthesizer specific information in a MIDI message. So, SysEx containing a patch for one synthesizer is, in general, completely useless on another model.
So, if you found a package on the Elektron page that is designed for, say, Analog Rytm, you cannot use those sounds and other things contained in the SysEx files with Digitakt.
The samples, however, are of course usable: They are just audio files, and you can use any audio file with Digitakt.
1 Like
Machinedrum samples are SysEx files (I think in SDS format, Sample Dump Standard). I was just looking at this yesterday after seeing some free sample packs for MD UW in Elektron’s website and wondering how to convert them to use with the OT and DT. The DT transfer app doesn’t seem to know how to handle those samples. But I think it will be easy to write a converter to WAV, maybe you could add it to Elk-herd, or I’ll give it a shot when I find some free time.
Ah yes, SDS is a SysEx type that is supported by multiple synths… but not Digitakt. Yes, I could make elk-herd convert those… but not high on the queue of features to implement.
I found the same MD UW packs you did, and they do actually work in the Transfer app, but only on the “Drop” page, not the “Explore” page of Transfer. They got filenames like 01, 02, 03, and they didn’t go to the folder I thought they would, but other than that it works.
Oh, cool, I didn’t try the drop page and I thought they were not supported 
I spent some time today writing a python script to convert them to wav https://www.elektronauts.com/t/tool-to-convert-md-uw-samples-to-wav/
thanks I was not aware for that
Thanks,
I’m having issues transferring sysex soundbanks to my digitakt. using sysex librarian since c6 isn’t available anymore. m1 mac monterey - DT os 1.40.
transferring, the Digi only receives around 50% of the sounds in the bank. I’ve tried reducing transfer speed but it doesn’t help. seems to be skipping lots of them.
any ideas? 
Update: I turned off Recieve cc/nrpn in DT’s port config n it works perfectly now.