Digitone 1.21: trying to back up my project via sysex dump (Project > Active Project). It claims to be sending, but only one packet ever arrives and then I need to restart the unit in order to ever transmit sysex again. Otherwise, it claims to be sending, but it doesnāt. I can send patterns one at a time (after a restart), but it eventually stops transmitting, as well (after 2 when I just tried it). USB MIDI.
EDIT: looks like I need to kill overbridge on my host machine, disable OB mode on the DT and try again with the ānormalā USB MIDI mode. Now Iām receiving (slowly) a syx dump. Would be nice if OB didnāt kill sysex, though.
I cannot reproduce this.
I tried something similar but with 16 steps for the main, and different multipliers on each track, I canāt seem to get weird results.
Can you make a 16 steps track and reproduce this ?
Itās possible if it appears slow that you have USB+DIN MIDI enabled (the DIN midi rate becomes the determining speed in that case) - OB certainly needs to be off (set it to USB only (for MIDI) for larger data transfers) - but I think sysex will work fine via DIN - itās not that it kills sysex - itās just that itās no longer visible as itās sent along with the other OB stuff via the USB connection
I doubt killing the host OB engine is necessary, but I donāt own that device - if you use C6 it shouldnāt be a factor
I already got response from the support. They suggest me to start a new project to reproduce.
A new project works as it should work. I tried to copy the whole pattern from the bugged project to this new project, but that doesnāt work, same bug occurs. What does work is copying the tracks & arps separately and copy the sounds and load them in a the new project. Itās not ideal, but it works. Now I have to copy all my projects to a new project? Or should I wait on a patch update?
Ps, an example of a song :
Trk 1. Length : 64/64 scale 1/4 (16 step arp speed : 1/8 mode : up range 1 )
OK, well pretty good that itās not a bug per se, but more a backward compatibility problem (even if itās still annoying).
Have you sent them your sysex project ? Maybe a good thing for them to investigate thisā¦
And yeah, ratio offset is the bomb ! I had really been waiting for this, Iām psyched
Hi, thanks. Iāve disabled USB+MIDI on the ports (now just USB), and have disabled OB on the device. Turbo Speed wonāt enable, though, whether I connect the DT to my laptop directly (via USB-C adapter), or via a Thunderbolt hub. I can confirm that itās a lot faster (even without Turbo, although Iād like to understand whatās up there). And the resulting sysex file is 3MB instead of 291.6KB which I got with the ports set to USB+MIDI.
Iād suggest that sysex transmit be disabled in OB mode, though, with a note on the display to that effect. As for these other oddities re Turbo Mode, Iām curious about other usersā experiences. Thanks!
Turbo mode is primarily a way to get 10x MIDI baud rate between DIN connected Turbo devices - they need to be bi-directionally connected Out to In and In to Out - itās an Elektron protocol but a couple of other manufacturers have adopted it in some devices
It would appear to be present in C6 for the purpose of using their own TM-1 USB midi interface which was developed to speed up SDSdumps wrt the Machinedrum.
Now wrt USB midi connections, I am less clear on the applicability of the Turbo setting and whether the rate is either slow 31250 bit/s , turbo 300k bit/s or faster
However, due to the funkiness of the program and wrt the my experience part of your question- my C6 workflow is as follows
If the device attached is the last one connected to C6 you should see that the Turbo indicator is on when you start C6 up - if you toggle it it will go off and stay off (but may still be a speedy transfer?!) ā¦ so I have got into the habit of checking that the device I want to Tx/Rx from is selected in the menu and then close/re-open C6 and stay away from that menu&toggle - itās always been fine for me - itās clear that Transfer is the future MIDI program for Elektron, but I read too many anecdotal reports of hanging uploads on that and I tend to view it as safer for sample transfer only and recommend C6 (or even trusty Sysex Librarian by snoize)
Wrt the dumps captured, this is where C6 is handy, it will show you the contents summary in terms of sounds/kits/patterns/etc
The Control All Revert feature still only reverts the current page and not every control-all tweaks done on several pages. If you keep holding the MIDI button and go back to the different pages you were tweaking and press NO they will revert to their default state.
This is a bug since it doesnāt work as described.
I am also experiencing issues like @erikie with ARPs drifting slightly after changing to scale per track. Also after the first loop.
In the first half you can hear the ARP being tightly synced to the metronom of the DN but after changing to scale per track, the ARP gets out of sync in the second roundā¦ Am I missing something?
Update: I can confirm that after increasing M.LEN the drift appears later - right after hitting M.LENā¦
Update: Feedback from Support:
We have confirmed this as a bug. The issue is due to scale per pattern not being defaulted to 1x when changing to scale per track. Setting per pattern scale to 1x manually is a workaround until we have a fix out. Thanks for reporting!
Encountered some weird shit I never had before but with this new update:
-I was in function mute mode, when quickly track muting and selecting a non muted track volume control affects all the tracks! (bug or function I donāt know of?)
-when jamming with MD midi out to DN midi in, DN with long reverb I pressed double stop to cut the verb and lost midisync, DN refused to start on MDās midiclock, had to powercycle!
