Anyma Phi v1.1.0 update 🎉
We are releasing the v1.1.0 update of our physical modeling synth, the Anyma Phi.
We added 10 new modules to the Anyma phi including new WaveTable oscillators, new VA oscillators, 1 new Noise oscillator and a new LUT16 modulator.
Get it there:
After updating, it's important to turn your Anyma off and on twice.
Here's a quick video showing one of the new Wavetable oscillator first on its own, then blended after 15" into a simple 1 voice modal resonator:
bibenu last edited by
@Laurent_AODYO Thanks. I'll try that soon.
Did you intend to block comments on the YouTube video? That's what posting a video as suitable for kids does, effectively.
Thanks for the update.
But… I have trouble installing it on my Anyma Phi.
I get an error 100093 when I try to copy any file to the ANYMAPHI drive.
I have tried with different USB cables to no avail.
I am on a MacBook Air 2020 (M1) running MacOS Ventura 13.0
Is anyone else experiencing the same problem ?
Does anyone have a suggestion for how to solve this problem ?
A quick google of error 100093 shows it's a problem more commonly associated with file transfers to iOS devices, but it's evidently a well known Apple problem, so some googling and searching on reddit, maybe, should find you an answer.
Possibly, the anyma phi is acting as a removable drive, which is a common way to load firmware. The solution is probably not specific to this synth, just a configuration problem on your Mac, to make similar behaving devices compatible.
@hansgdaun This doesn't appear to offer a solution, but it's a related problem, illustrating the fact that it's not limited to updating this particular device:
Possibly the simplest solution would be to find someone with a Windows PC that you can use to do the update.
bibenu last edited by
@AndyHornBlower Thank you ! That was a helpful link. I did manage to update my anyma phi by using the RSYNC command from the Terminal App like this
// select download folder, e.g. cd downloads/anymaphi-macos // copy to ANYMAPHI drive rsync anymaphi-v1.1.0.ayo /Volumes/ANYMAPHI
The Terminal App hangs while the anyma phi updates, but that is as per release notes.
Thank you everybody for helping to solve this problem !
@hansgdaun You're welcome :) I'm glad you've got it working.
@Andy-B Cool. Glad to be of service :)
synth618 last edited by
update went smoothly. Sounds great!
I'm still learning how to program the phi in general, but was able to assign lfo to scanning wave position on several of the models : ) next is to figure out how to do so with the mod envelope.
can the WT sounds be played paraphonically? [havent tried diving into making paraphonic patches from scratch, thats a whole other thing].
I really like the chord setting, set up a sound where im scanning that, and it sounds like moving chords , very neat .
I noticed though, when i had it at default mode, the notes came on a bit slower [if i tried to play fast succession of notes] but that might be a setting if i changed it, the 'tracking' aka responsiveness would be fine.
Also, is it only one osc at a time [I tried doing different WT osc on the 3 oscillators, but only got one to sound] that will work?
Again Ive only just started with this, I plan to look closer at these and play through them . So far pretty happy. Haven't even tried the sequencer yet... very curious.
Hi Laurent and the Aodyo team, I can't make the new lookup table work. No matter what I'm taking in input, I get a flat line in output. Is that a bug or I misunderstood that modulator?
@simonbou I just checked the lookup table and there seem to be a bug somewhere compared to our internal beta ... I will try to find the problem and fix it
I performed the update on MacOS Ventura (using Terminal because of the already mentioned 10093 error). During the update process it gives an error message stating:
MB: ERASESECTOR 4 ERR: 0 2
After that it finishes the update and interface asks to eject the Anyma Phi and after that's done to turn it off and on. That results in an unresponsive and therefore useless Anyma Phi with a black screen.
I tried to reinstall v1.0.0 but with same error message and same result. Another attempt with v1.1.0, also the same.
(The entire sequence can be viewed at https://youtu.be/CAtcoLzLEYI in a for the public hidden video.)
How can this be solved?
@Laurent_AODYO Hi Laurent, you are all busy with the awesome campaign for the Omega but did you had a chance to look at the bug into the V1.1.0 firmware regarding the LUT16 module?
Yes Simon, I found the bug and fixed it.
I still have to make a few more test before updating the files but as you guessed we are quite busy with the Omega today.
@Laurent_AODYO Have you been able to solve the problems people have had in trying to install the update, such as Frank (@Lyricon ) had? Failing to update is one thing, but being left with a non-working synth unless it succeeds, is a much bigger problem.
@AndyHornBlower We cannot "solve" this known problem on our own as it looks like a Ventura bug also reported to have impact on many other devices.
Hopefully, Apple will fix this.
Meanwhile, I do not think anyone has been left with a none working device. As far as I know @Lyricon succeeded to recover using the trick you provided.
bibenu last edited by bibenu
I think it's worth updating with the outcome, when someone reports a serious problem
I absolutely agree on this. The reported problems above have put me off doing the upgrade till now. I'd be interested to know what the workaround was for MacOS ventura for instance.
Anything you can tell us would be much appreciated @Laurent_AODYO
@bibenu Yes, I was thinking people would be put off by reading this thread too.
AFAIK, the solution was the one posted by @hansgdaun, above, who deserves more credit for it than I do - I found the page that led to that answer, but he was the one that tested it and wrote it down in a clear way. Basically, it relies on using rsync, in a terminal window.
FWIW, I've put it off too, but mostly because I thought there might be minor updates afterwards, and I wasn't in a rush.
bleedingobvs last edited by
Can confirm @hansgdaun's rsync solution works for me too - hooray!
Thanks so much :)
I just got a new Anyma Phi and tried updating today. I followed the instructions for updating via pc (not mac), but the Anyma Phi did not provide the "UPDATE DONE" message as the instructions indicated it would. Instead, I get the message to connect a USB cable and drop the update in the disk--which I've already done. I didn't get an error message.
Now the Anyma Phi won't even boot up -- I just get a blank screen with a white Patch LED light. I've tried several more times, but with the same result.
Anything you can do to help me get the device working again would be greatly appreciated.
AndyHornBlower last edited by AndyHornBlower
@Laurent_AODYO Was there a solution to KDJ3992's problem, other than maybe having to return it?
I would like to try this update, on Windows, but frankly, I'm too scared to do it without more information from Aodyo. If there's a way for us to recover our anyma phi when this happens then good, but please explain it to us.
I've already had to return an anyma phi, due to a hardware problem, and that took a couple of months. I'm not complaining, but that's not something I'd want to go through again, and mine is presumably out of warranty by now anyway.
I appreciate you're all busy with your new product development, but as has been said elsewhere, the mystery around this would put me off buying another Aodyo product in case something similar happened with that, and you were all too busy to talk to us about it.
For me, this is a problem, and it's a big one.
@AndyHornBlower Apologies for the late reply. I never heard back from anyone at Aodyo regarding this post or my multiple e-mails to the support e-mail address. I live in the US and couldn't find a seller here, so bought my Anyma Phi from Thomann. I had to return it to Thomann in Germany for repairs--which was an additional expense and took a few months. It was finally returned and is working well so far. I was also able to update it to v.1.2.0. So fingers crossed.
AndyHornBlower last edited by AndyHornBlower
@KDJ3992 Thanks for letting me know. Yes, it's a shame you had to pay to return it for repairs. It would be an even bigger problem if it had been out of warranty, which I think mine is now, especially without adequate discussion with Aodyo.
I'm under the impression it's done with STM32 MCUs, in which case it is update-able by a user with the right simple tools (usually just an ST-Link programmer or an STM32 Discovery board), without relying on the standard method, but also not without adequate discussion with Aodyo.
I finally gave in and updated mine to v1.2.0 a few days ago, successfully, on a PC with Windows 7. I haven't tried the new editor yet, but I mostly prefer to just use menu diving. I haven't explored setting up a MIDI controller for the new CC/NRPN mapping capabilities either, but that seems like it could be very useful.
I see this forum is now "protected" by reCaptcha. I know it had a spam problem, but I was under the impression most of those were from sweat shop workers, who spend all day solving Captchas, so aren't deterred by them at all. I am though. They annoy me so much, i can't focus for long enough to solve them. FWIW, pressing the headphones icon, for the audio version, is a lot simpler.