Hi all! After getting the DN2 a while ago I purchased some DN1 sound packs not long after that, which I couldn’t import yet, since they’re .syx files. Until today, I thought, when I updated to OS 1.10, which says “Added support for importing legacy SysEx data.” But I’m still not able to transfer data. Is there anyone who might shed me a light on this?
Hi! You have to change the setting within the Digitone II. Go to Settings > System > USB Config > and check OVERBRIDGE instead of USB AUDIO/MIDI.
2 Likes
I had so much fun with chord memory that I would love to have the possibility to save banks of chords that would work like kits. I could switch from my Debussy to my Italo or my NIN style bank of chords in the middle of a set.
1 Like
Are you referring to this :
1 Like
no idea, but you may need to use transfer as opposed to a third-party sysex handler as it may not make the system exclusive to one suddenly fine for another - this is what Transfer would likely be doing
Yes that was what I had in mind but I incorrectly attributed it to Elektron. I was hoping that they might have done zero-crossing cleverness for mono samples but @JoyrexJ9 's experiments suggest that’s not the case.
3 Likes
If you want to reproduce my experiment, I was using Legowelt’s Korg Monopoly samples LEGOWELT OFFICIAL WEBSITE the samples in the PAD folder. I picked these at random because I remember they have droney/loopable sections
1 Like
that is actually really disappointing
didn’t elektron mention this as being addressed among the bugs that were fixed?
Only for the GRID machine, people seem to have read this as “popping & zero-crossing is now fixed”
It’s far from fixed
2 Likes
After this update my Digitakt 2 not saving kits. No problems with the previous kits though.
1 Like
Unfortuntately I´m not able to understand what you are saying. Maybe my English is too bad. I’m using the Transfer app, I can load the .syx file, I have prepared the DN2 USB Config settings, I have activated Sysex Receive, it’s waiting, but nothing happens on “Send”.
if using Transfer you wouldn’t need to activate sysex receive, just drag and drop - if it works as i’d expect it to - but i am guessing, so best wait for a more authoritative response … it can’t be that complex
i do realise Transfer has a separate ‘sysex’ bit - no idea if you are expected to go that route or drag/drop
When I drag & dop the .syx file into the “Drop” section of Transfer and press “Send” nothing happens. When I drag and drop it into the “Explore” > “Sounds” section it tells me “File(s) not supported on this drop area”.
1 Like
i’m not sure what’s going on under the hood, but if they were able to eliminate pops and clicks in the “slices” of the grid machine, one would have to assume that it was done with either a zero-crossing detection or cross-fade
if they’re not applying these same methods to the loop function, then maybe seamless loops are not an intended feature or a priority for the team
that is disappointing, but hopefully the grid machine is click-free now?
1 Like
You can drag and drop, it will open a page in Transfer to send. On the Digitone II you go to SETTINGS > SYSEX DUMP > SYSEX RECEIVE and select the location. I just tested with several Digitone .syx files and had no issues.
3 Likes
Instructions above - maybe you need to update Transfer !!
1 Like
But the improved sysex support is in the 1.10 firmware isn’t it, not in transfer ?
1 Like
In my imagination it’s as easy as you say. I followed all instructions as documented (and as you describe above), I´m on all latest apps/OS, but to no avail. While the OS upgrade .syx get accepted without any issue, all sound packs are rejected. Maybe there’s a flag in those sound pack files telling Transfer they’re DN1-only…
8 Likes
That’s how it reads, however, there is no way the firmware is doing the conversion for the project upload … it’s inefficient - so i am assuming it may be the same - although the corrections to cater for translation between a DN1 sound and a DN2 one are relatively minor - so you could be correct in your interpretation of the handling
the acid test is to fire a sysex from sysex-librarian or midi-ox etc and see how that goes … then we’ll know
my hunch is that it could get messy for elektron if the firmware becomes less sysex specific - but i am sure they are all over that
the sysex ID parsing would throw out inappropriate files straight away - if they open that up - who knows, but i imagine they do and have it all covered off …
1 Like