There’s no thread for Transfer 1.9.5 bug reporting
Would the best place be here?
There’s no thread for Transfer 1.9.5 bug reporting
Would the best place be here?
Yes.
Transfer SYX to DN2 is not working.
If you try to “write” a bank or preset, nothing will happen.
No way to upload SYX files to DN2 if you dont have a DN1 to convert!
I’ve given up using the Transfer app with the DT2. It’s just ridiculously bad
It takes 4 or 5 restarts of the app (sometime more) for it to successfully load and scan the DT2. I’ve switched to the elk-herd tool which is way more reliable.
Kinda embarrassing, that a fan made, web based tool is better than the official software.
I found a strange bug in the transfer app. Took me some time to really isolate the problem. But now I can describe and reproduce it:
when I transfer an empty folder from the Digitakt II to my Mac and the destination folder ends on the same letter as the empty folder begins, the destination folder is exited and a new folder is created on the upper level.
In the video below I have reproduced this with dummy names, but before that it actually happened to me in the field when I wanted to transfer all content from my Digitakt.
Implications: Transfer should never operate outside the selected folder. It feels like paths are not being validated properly here and it may be possible to break out with files and not just empty folders. And then it is a potential security issue.
Hidden video on youtube:
II have also reported the bug to support. So this is just in case anyone else is having the same problem.
There’s a bug I’ve found on Transfer 1.9.5 and DT2 1.10. Transfer does not always correctly detect duplicates currently on plusdrive when restoring, and creates a new copy of the sample in /projects/. When I pick one of these files, I can always find the original on the plusdrive, with both the original and and the new copy in /projects/ pointing to the same sample slot.
If the two files are pointing at the same sample slot, then presumably they are identical files, with identical hashes, in which case, why did transfer create a new copy ?
I will attempt to boil this down to a simple repeatable example and then raise it with support.
EDIT: Now emailed to support
EDIT2: Bug confirmed and they’re working towards a fix.
Been getting major headaches from Transfer all night. Totally new issues, already reached out to support.
Basically it is transferring extremely slowly and, more strangely, some of the transferred samples end up with no sound, though Transfer shows them as being the right size.
So when transferring a batch of samples, it not only takes forever, I then need to audition every sample to make sure it works, then delete and re-transfer the broken samples, then repeat until they all work… huge pain in the ass.
Tried different USB cables, USB ports, USB modes, no change.
Edit: It seems to have somehow been related to the active project.
Weird.
Check that you have the very last version of Transfer and firmware.
Maybe take another USB cable.
If it’s happening only with one project, save it through Transfer and send it to Elektron Support.
This sounds like a transfer (on windows) bug to me.
Goodday,
I am having trouble with tranfer. I have the syntakt 1.40, wit the latest transfer 1.10.3 and overbridge 2.25.3.
Always had trouble with transfering. but couldnt find the fix for it. So i bought the overhub, problem solved I thought. But still hanging after 3 tranfers. Tried them one by one, or all in one bulk. Nothing helps.
Tried diff usb ports, with another ush hub. tried fact reset, re-installed overbridge and tranfer. But keeps experiencing trouble, cant fix it.
Anyone can help me please?
Elektron Transfer 1.10.3 crash on Windows 11 while trying to connect my og DT:
I’ve just got 5 crashes and reboots of my Win 11 PC immediately after pressing the connect button.
Some minutes before I had no issue connecting and transferring some samples to my Rytm MKII.
I’ve been having an issue where Transfer pinwheels (on a Mac; latest OS) when selecting the instrument I’d like to update my Tonverk or Digitone II (doesn’t matter which one).
The issue is persistent after a re-install, and happens when connected through my monitor or hub.
Recommendations welcome.
Does it happen when you connect to the Mac directly?
I could try that but it means re-orienting my desktop/set up for the cable to reach.
Other hardware like the Oxi One performed a firmware update via the monitor and USB-C.
First time this has ever been an issue. Was actually surprised by it.
I just meant to try once and identify if the problem is Transfer or the external gear.
That Oxi works doesn’t mean the gear doesn’t have any problem.
it may be due to how its connected to the mac.
old monitors just used a usb lead … basically an extension usb socket…
modern monitors might be via hdmi / lightning / whetever the latest thing is on a mac…
older gear might have issues on usb depending if the monitor was on before the mac was turned on … (for me anyway… obviously depends on mac , monitor etc)
typically , i always use direct connection to mac … ive not tried my recent monitor sockets . …
plus tonverk is just a sdcard mounted on the mac like any shared drive (i assume) ,… digitone is transfer specific . i havent tried tonverk with transfer , i assumed it was irrelevant …
I remembered: Tonverk is not supported by Transfer app yet. Thanks for the recommendation. It did lead me to the manual eventually ha.