Display corrupted/strange for patches self-created/saved on editor? Solutions?
-
Hi - got Anyma Phi today - the patches that i have made and saved on the editor display in a weird way
The supplied patches, plus the 57 patches downloade from http://www.brokengadget.org/anymated-synthesis/ all work fine (thanks for the latter!)On my self-created/saved ones the four boxes at the bottom of the display will only display one bit of coherent text depending on what knob in the matrix is selected, so, if "timbre" is selected, the word displays OK, but the other 3 boxes have random pixels, if you then select "color", the word "color" appears, but the other 3 boxes have the gibberish.
I've attached a couple of pictures here
https://www.dropbox.com/s/3kn6hx5hfyl2a2m/IMG-4112.JPG?dl=0
https://www.dropbox.com/s/ghpxcjozfw45fn1/IMG-4113.JPG?dl=0Is it because I am using an old computer (Windows 8.1)?
I've updated to the latest firmware -
@neilcmanson
Just to add, in case it helps diagnose problem - the same thing applies to the "empty" slots - display name/label is random pixels, except for the currently selected item -
@neilcmanson said in Display corrupted/strange for patches self-created/saved on editor? Solutions?:
Hi - got Anyma Phi today
Do you have the latest firmware?
You can see the version number very, very briefly, when you turn it on, but the better way is to click the encoder under the display (press it in then release it) then turn it to get to the Diagnostics menu. Use the encoder and the left and right arrow keys to navigate the menu.
-
@neilcmanson See this thread for links to download the latest (0.8.90) firmware:
https://community.aodyo.com/topic/753/anyma-phi-v0-8-90-pre-release-update?_=1629498033447
That also includes the latest version of the editor.
Then, read this thread for a workaround for the bug that stops us renaming a patch easily, in this current version:
https://community.aodyo.com/topic/763/renaming-a-patch-doesn-t-stick-v0-8-90-updated-today
I also do that when saving an edit - first export it to a file, then import it again. I'm not sure that's needed, but I do it anyway, and it means I always have a backup of my patches saved.
-
Hi - yes, is the latest 0.8.90, and the latest version of editor too.
I am running the diagnostics now (it has been running for ages, but no "err" messages yet -
Thanks for that - I don't think it is a problem with re-naming per se - i.e., all the empty patches have it, and they haven't been named.
I've tried to doing some changes, then "save", but they still have the "gibberish" pixels.
I've tried exporting the whole lot as a bank, then re-loading - makes no difference.Weird thing - it only seems to be the case where there are 4 boxes at the bottom (that display the level of the parameter) - where there are only 3, they display OK.
-
@neilcmanson I'm guessing you've just encountered a bug. A couple of us have had one where it kept restarting, or the sound would keep playing but the user interface would stop responding. It seemed to be tied to particular patches. I'm sure they'll get it more stable, at some point.
IIRC (mine's not currently connected), Shift + Left arrow should get rid of the boxes, then Shift + Right arrow saves, and hopefully the patch now won't show the corrupted boxes when you select it again.
Agreed, it won't be a problem with renaming. That's just something you'll need to know, about using the current version.
-
Thanks again -
I feel I am getting to know this "bug" and its very distintive profile:
The top three rows only allow one "proper/legible" text box at a time
The "morph" row, starts with one (morph), but will allow 2, but no more than 2 to be legible at any time, and MORPH has to be one of the two.
The ENV row only has three boxes, but all 3 are OK! -
Update - definitely seems to be something to do with the latest firmware v0.8.90 (or how it interacts with Windows 8.1) -
I've just tried the v0.8.80 version and the editor to go with it - the text is all OK, can edit, save without the gibberish; uploaded the bank saved from the "new" version and all is OK.
I will stick with the "old" version for now!
Thanks for all the suggestions and support!
-
And, as a double check, re-updated to the new version and the "gibberish" display returns -!
-
@neilcmanson That's interesting. At least that confirms it's a firmware bug.
There's a Patch Exchange section, if you feel like sharing some of your patches:
https://community.aodyo.com/category/17/patch-exchange
There's currently just one thread, so feel free to add to that, or start a new one in that section, if you prefer.
I'm actually using it with Windows 7, which seems okay, but maybe it will do the same with those patches. I'm not sure if the editor will keep working with older versions of Windows, with future updates. I'm just hoping it will, if only because it's the only way to save or load patches or rename them, at the moment.
Failing that, maybe they'll add a sysex implementation, and renaming directly on the synth front panel, so I can save and load patches with MIDI librarian software. That's the only way to make sure it can always be done, once support for it ends.
-
@neilcmanson What you've encountered isn't a bug, it's an unfortunate UX decision of mine that backfired :).
We "dim" the labels of the parameters that aren't used/mapped in the patch (except the selected one, so that you get a chance to know what you're manipulating), but the way we dim them make them look garbled. We'll try to find some other way to visually discriminate unused parameters that doesn't involve scaring our users ;).But don't worry, nothing is broken or corrupted, that's just a visual effect.
-
- I'd like to support SysEx-based loading/saving/renaming of patches some day, for the reasons you describe.
- We don't plan to end support of old operating systems for now. In fact, I'm fiercely opposed to that due to the waste it generates, and I hope we'll be able to continue supporting old systems (Windows 7+, OS X 10.9+) as long as we realistically can.
- Any detailed info about your crashes/restarts are very welcome (descriptions, videos, specific circumstances, any reproducible steps if possible; send to support@aodyo.com and say they're for join). Our personal Anymas don't crash, and they can run for days without freezing in any way. If yours do, this is something we need to fix. As opposed to some other "reliable" bugs, these ones tend to be nasty because they don't appear reliably, every time you do a particular thing, so it's very difficult to observe them and find where they come from. Some aren't even software bugs, but hardware defects, which makes the problem even less trivial. Hence, the more data we get, the better the chance to catch them.
