Can´t delete an empty directory, and once I`m on it I can´t step out of it and I need to recycle everytime I get into that specific folder… just upgraded to 1.72
I read some info here in the forum and seems the solution is to reset the +drive? not clear for me how to do this without touch projects?
Trying to delete whitin the AR I got thsi error once, had to restart the unit, everything works well but the directory still there and also I created couple more just to see the behaviour, now I have 3 empty folders that I can´t delete, and once I enter one of this folders I can´t get out out, the rest of the folders behave normally… I`m doing a back up right now, do I really need to erase the drive?
I had this sort of behaviour earlier with my Rytm MKI. If I tried to send samples over to the unit it would lock up, couldnt delete the folder etc… Then I tried using transfer with an older mac (intel i5 macbook), and transfers worked again.
I am not sure what happened exactly but the problem seems to have gone for now. However, I am still unable to delete those folders I created back when transfer was acting up… most likely those files/folders corrupted somehow, and the Rytm OS doesn’t understand how to deal with corrupted data
I got everything back in working order, but I can’t figure out what cause the issue.
I’m running Windows 11, Transfer 1.9.5, ARMKII 1.72.
Here’s what I do :
I tried to transfer a project file .arpjr including some samples. Transfer app managed to load samples but it failed transferring the project file.
I retry with no luck. I reboot everything, nothing more.
At this point, I tried to deleted the sample folder. Samples were well deleted but not the directory itself, within the AR or with Transfer.
Within the AR, when you enter in the corrupted folder, there’s no way to get out of it.
So I backup all my samples with transfer. No problem.
I then format samples in the AR system menu. No more corrupted folder.
I transfer back all my samples. And finally, I retry to transfer the initial project that cause the problem. And it works as it should.
It seems the bug was related to Transfer but I never encountered such a issue.
With my correspondense with Elektron CS, they are aware of some transfer issues and told me they are working towards addressing them. No ETA for now though…
Its reassuring to know that backup/reset/restore is a viable workaround in the meantime, so thanks for the info