If transfer can access/utilize digitakt memory as part of the creation process (hooked up to USB during the conversions) that would be good, who knows maybe it will happen one day? I’m not going to sell my digitakt any time soon, I can wait for now 
Yeap, correct. It generates a # based on the waveform. This is why you can freely move samples around on the plus drive without messing projects up or back them up to a computer and re-transfer them into DT without breaking projects.
The above idea for wav files to be converted into sounds is neat but it’s not really what a “sound” represents in the Elektron world.
Really what the definition of a “sound” is in Elektron world is the collection of parameter settings across the sound parameter pages (so sans the TRIG page) and on some elektron boxes (synths), anything related to a sound like midi mod matrixes, drift on/off etc etc.
On Elektron samplers it is the same, it contains all parameter page parameter settings. With one exception being the sample slot. In stead of saving the original sample a lot number, it references a sample on the +drive that will be imported into a free sample slot when loading a sound.
2 Likes
This is what I was remembering. Thus, it is machine specific correct? (meaning: my machine, my “sounds”)
Ah eh no
It’s really based on the waveform of a sample. You can save a project via transfer and send that to anyone and they’ll be able to load it. Though of course project files nowadays also contain the used samples hehe. And this is referencing samples, not sounds 
“Samples” and “sounds” are different things entirely basically.
2 Likes
Right, sample is an audio file, sound is a parameter cluster.
1 Like
I thought, that maybe converting could simply mean adding default values with all the parameter infos to the .wav (and changing the file-format ofc.)
But I guess the #-system means the transfer app would need to counter check with the machine before it can assign that number to avoid using already taken #s?
Ah yeah, anything is possible I guess.
Could just be that when you drag a wave on a sound slot it uploads the sample to a default folder. If it recognizes the waveform it will just make that sound reference the already existing #.
It does already check when importing samples the normal way. Can’t upload duplicate samples because of that.
1 Like
As is, the transfer app doesn’t even show the .wav files on the left side (desktop) when choosing “sound” on the destination side (right). So, no drag and drop, unless I misunderstand you and this is only hypothetical.
Well, I posted in the transfer feature request thread. Maybe there is hope they will expand the app funcionality in the future. Much potential there. Best case scenario an expanded native elk-herd like thing
Indeed
2 Likes
Thanks Dave.
1 Like