Bug with editor import ?

bibenu

I think there may be a bug with importing using the editor.

I've just loaded the new factory patches twice over, and what I see happening is this.

In the editor I right-click and choose 'import..' and choose my file
I notice the diamond appears on the anyma screen, but then the messages 'saving patch' and 'patch saved' appear on screen, and the diamond disappears
I find I can play the new sound and the editor shows the right patch name, and a new color.
because the diamond has disappeared (and because of the messages), I think the patch has saved, and I go to another patch. No message 'unsaved changes' comes up, so I'm sure the patch has been written permanently to the anymas memory.
I come back to the patch later, and it has not been saved. Though it has the right name, it appears to be an initialised patch (grey colour)

I've just updated to 1.0.0 (was on the beta previously) and I'm using the mac version of the editor.

The only way to save the patches permanently is to explicitly save them with the editor.

I would have expected one of two things

given the diamond disappearing and the messages suggesting it had been saved, I would expect to to need to then explicitly save afterwards
if I am expected to explicitly save myself (which is consistent with the rest of the UI, I think) then I would expect to see the diamond warning me a save is needed, and the 'unsaved changes' warning when I navigate away to another patch. (I have 'warn if unsaved' ticked in the options)

join

The editor should be triggering a save right after importing.

Which exact macOS version are you using, and on which Mac?

bibenu

@join said in Bug with editor import ?:

The editor should be triggering a save right after importing.

Well, the messages on the anyma screen certainly suggest that's happening, so the editor is definitely making something happen on the Anyma. (EDIT: maybe it's the way the firmware is responding to the editor that's the problem, and not the editor? I can only guess of course.)

I'm on a macbook pro, late 2013. MacOS High Sierra, 10.13.6 .

bibenu

@bibenu said in Bug with editor import ?:

Well, the messages on the screen certainly suggest that's happening,

Sorry, I left it a bit unclear. Though the messages suggest the patch is being saved, it is not being saved. if you go to another patch, and come back, all you get is an initialised patch (sine wave). The only thing that has been saved is the name of the imported patch, everything else is gone.