@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.

@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.

@drfritzon Cool. I'm glad you've got it working.

That seems like a problem that could happen in shipping, so maybe it explains a few of the similar problems that have been reported. It could conceivably work okay for a while then work looser and become intermittent, or just stop working.

@drfritzon said in Anyma Phi frozen at start issue:

I think the issue might be with the power supply cable, it keeps loosing power and rebooting when just I barely wiggle the power cord. Not the most reliable when playing live.

It sounds like the DC jack socket has broken away from the pads on the PCB, making only an intermittent contact. Fixing that should be fairly simple, but it remains to be seen if it cures the other problem.

@blipson FWIW, I have a Kenton MIDI USB Host Mk II, which lets me control the Aerophone AE-10 from a MIDI keyboard - not something I've wanted to do, but I tried it a while ago and that worked. I used a Yamaha CBX-K1, which has DIN MIDI Out and no USB.

@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.

@Laurent_AODYO I'm glad @Lyricon was able to recover using that method, if so. Since these forum threads can be read by anyone, AFAIK, I think it's worth updating with the outcome, when someone reports a serious problem - for example if it's then resolved in a private conversation or by email.

@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.

@Clint Some electronic parts suppliers sell self adhesive copper tape, in a few different widths. It's also sold for shielding electric guitars, but more often in sheet form. A while ago, I saw it in pound shops (discount / clearance shops) being sold as slug tape / slug repellent tape, so garden centres might have some. You can find it sold on eBay too, of course, as some variation on "adhesive copper tape" or just "copper tape".

@wwoodard8 Nice. Yes, that looks like it's much better for ergonomics.

@Andy-B Cool. Glad to be of service :)

@hansgdaun You're welcome :) I'm glad you've got it working.

@wwoodard8 I don't own a sylphyo but octave buttons are always a problem. Having to move your left thumb around isn't really natural and means that fingerings in one octave are more comfortable than the same one in another. The EWI4000s, with its octave rollers, is the worst I've encountered, so far.

On my Yamaha WX5, I've stuck a small self adhesive felt disk on the larger central left thumb position, which helps a little. Raising it above the buttons seems to help, but also the roughness of the felt means I can get a better idea of where my thumb is. On my Roland Aerophone AE-10, I've cut a thin crescent shaped piece of self adhesive cork, to cover the first octave up button.

I don't know if that's practical on the syphyo, but maybe you could stick something to the left of one of the indentations, that you can feel as a reference.

@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:

https://github.com/ARMmbed/DAPLink/issues/982

Possibly the simplest solution would be to find someone with a Windows PC that you can use to do the update.

@hansgdaun said in Anyma Phi v1.1.0 update 🎉:

error 100093

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.

@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.

@join said in Anyma Phi v1.0 public beta:

I'll add a new global setting, Expr. detect, that allows you to set the condition used by the synth to switch between expression CC and velocity envelope for the synth expression signal, with these options:

Could there be an option to use the CC as an envelope amount, for the velocity envelope?

That would give an extra control while playing with a keyboard, and allow for wind patches like staccato brass, where a fairly short attack and decay at the beginning of the note can be useful. If the CC can control the overall amount of the envelope, then it can still play as a wind controller patch, but have the added response to velocity, which isn't necessarily as easy to get by just tonguing the note.

Most wind controllers have the ability to send velocity, by measuring the breath strength at a fixed interval, shortly after we start blowing. Adding the option of a velocity envelope amount would let us make more use of that - the initial tongued "tuh" would trigger the velocity envelope with a different velocity, depending on how strong it was, then breath strength would control the level of that envelope.

Ideally, Breath should still be able to make the sound as loud as we want, so the envelope shouldn't be a limit... maybe have an option to make Breath add on to the velocity envelope, instead of multiplying it?

I think that's probably two new options :) Having it add would be the most useful of the two, I think.

@bibenu You're welcome :)

@mickglossop said in Email notifications from this forum:

Hi - is it possible to set up email notifications as/when anyone replies to a message one has uploaded?

Click on your profile, at top right, then choose Settings, on the menu that appears.

On the right of the Settings page, you should see some settings for Watch (e.g. tick both boxes and set Default category watch state to "Watching"), then a whole list of options for Notifications. You'll want to set some of them to either Email Only, or Notification & Email,as you prefer - the second one means it will also tell you with a pop up box, or some such, if you're currently looking at the site when it happens.

@mickglossop said in AnimaPhi Editor Import Patches / Bank doesn't work:

• When importing a patch, it seems necessary to manually select a new empty patch slot,. Otherwise the current slot will be overwritten. Please make the import command automatically load into a new empty slot.

Good point. Import Patch has now been added to the context menu for each patch slot, so you can say where to put it. That works for me, but maybe it should now also be taken off the File menu, so you have to specify where you want it to go.

@mickglossop Agreed. Being able to categorise patches by type of sound, and select them on that basis, would be a very useful feature.

Maybe add a favourites tag too, and make that one of the categories that can be chosen. Maybe have a category choice as a global menu option, with ALL, as a way of disabling it, then turning the encoder should select patches within the chosen category when it would normally work to select them from the entire list.

@join I think so, yes. The critical part is linear FM modulation, rather than exponential frequency modulation - which is what happens with VCOs on a volts per octave scale. If they can do that, then we should be able to make 2 or 3 operator FM patches.

@jls said in Feature request - some tips:

• piano/epiano physicall model
• brass physical model

A brass model would be great to have. An electric piano model would be good too.

The DX7 has effectively been done for the Korg Minilogue digital engine, and Korg NTS-1, but it requires a lot of parameters to specify an FM sound, so the real difficulty is in providing a user interface to make use of it properly... plus there might not be room in an anyma phi patch to store them all.

The Yamaha PSS-480/580/680/780 2-op FM is still a lot of fun to play, and can make some interesting sounds. That takes a much smaller number of parameters to define a sound - there's, I think, 10 via the front panel, and maybe 30 to completely describe the patch, in an editor. That's probably closer to what can be done with the anyma phi patch structure, if you separate out the envelopes from the rest of the two operators, and then have two or three linear FM oscillators (not operators, because they wouldn't have their own envelopes), which are able to be modulated by another.

@deepsea said in Anyma Phi v1.0 public beta:

@join said in Anyma Phi v1.0 public beta:
Indeed, my DAW was running in the background. Closing the DAW and hence freeing the MIDI ports let me connect to the Anyma and finally enter the editor. Cool, what an easy solution.

FWIW, in Windows 7 when a MIDI device can't be opened, it's usually because the application that had it before hasn't shut down properly - i.e. even once you know to shut down other things. that doesn't always solve the problem. With USB-MIDI devices, it often helps to unplug the device, wait a moment, then plug it back in. That tends to let the problem program finish shutting down.

If it still doesn't work, you'll probably see the guilty application is still there, showing as a process in Task Manager, or something more user friendly like ProcExp64. Sometimes it's not possible to terminate the process from one of those two, in which case it might be necessary to reboot. If nothing else works, rebooting always gives the MIDI device back so you can use it again.

@mimj44 said in Anyma Phi v1.0 public beta:

Pourrais t-on obtenir des démos et/ou tutos suite à la 1.00, car je suis un peu dépassé, malheureusement. Merci, Jérôme.

Good idea. Demos and tutorials, especially of the new features, would be great.

@join Yes, save on the File menu of the editor, immediately after import, works too.

FWIW, I had one patch that seemed to have imported okay, without needing to save it to get it to play properly, but after clicking a different one then coming back to it, it sounded like the default patch again, so I imported it again.

The Save Patch function would be good to have on the context menu for the patch slot too. It doesn't seem to logically belong on the File menu, because it applies to saving from memory in the editor, to memory on the synth, without involving the computer's filing system... plus, while it needs to be used to make sure an imported patch is saved, it's more convenient to right click on the patch slot, than to reach for the File menu, though hopefully that won't be needed so much, after this version.

Having Import Patch on that context menu for a patch slot would be good, either way.

@join said in Anyma Phi v1.0 public beta:

@AndyHornBlower Could you confirm that a "save" after import works for you too?

Yes! That works.

So far, it's worked every time... I think. One of the Broken Gadget patches still sounded a lot like the default patch, so I wasn't sure about that one, but maybe it just does, without tweaking things on it... I went through quite a few of those, so I'd have to go over them again to find that one again. I think it's reasonable to assume that does always work :)

I missed reading part of that, so I've only tried Save on the anyma phi, so far. I'd forgotten there's a Save Patch on the editor. On the old version, that just locked up the editor. I'll try that shortly.

@bibenu I'm inclined to think that since I could install the new firmware, without any problems, there can't really be a problem with the USB connection.

@join You're welcome. It's directly connected to a USB2 port, on the front of the PC. It was cabled up exactly the same when I upgraded the firmware, and that worked perfectly.

No, I didn't have any problems importing them under the older editor / firmware (on my original faulty anyma phi).

The display of the older editor tended to get out of sync, and show the wrong patch name for the slot, and to rename one and have the new name "stick", on the synth, I was having to export the patch, then import it again, so I probably did that to all of the ones I made or edited, before renaming on the synth was an option.

I also tried importing several of the unmodified Broken Gadget ones, without any issues on the old setup, but with mostly issues on this latest one - same pattern, mostly requiring retries and often still not working after several attempts.

@join
Here are some of the patches I previously tried, categorised by whether importing them was successful, and if so how easily, i.e. whether or not they needed two or three attempts - they mostly did, apart from the ones I gave up on, after three attempts.

testing patch import in editor 2022-01-13.zip

There was no bias in selecting them - I've gone through two of the folders of patches I'd made or tweaked, attempting to import every file in those folders.

AFAIK, I using v0.8.90 when I created, or edited these. I've categorised them by;

"loaded on 1st try" - which was only a couple, out of the ones I've tried today,

"retries needed", meaning I tried again, up to three times, using the patch reset in between (on the context menu), but was then able to load it, and

"gave up", meaning after three retries, it still hadn't loaded.

FWIW, the ones with an & on the end are patches I'd tweaked, using the older editor and firmware, and the ones here that didn't load after three retries were ones I'd tweaked from the collection of patches by Broken Gadget. They're not alone in failing to load, but they were out of the ones I've tried today. The others were ones I created from scratch, using a mixture of the editor and the front panel controls.

Since a lot did load after a couple of retries (some after three), I suspect there's some randomness to it, but with a high chance of failure, rather than simply a case of some that can load and some that can't.

I had no trouble upgrading the firmware, with the same cable (supplied with the replacement anyma phi) so it doesn't seem like a cable problem. It could be specific to Windows 7, I suppose.

Incidentally, it would be nice if Import Patch was also on the context menu for a patch slot in the editor - it would reduce the RSI inducing effect of importing a lot of patches, one by one.

@markusschloesser said in Anyma Phi v1.0 public beta:

btw I managed to import all the TW patches, is there any way I can send those to you?

Thanks for offering, but I have the zipped patches from brokengadget's website (http://www.brokengadget.org/anymated-synthesis/)... I see the thread that used to link from the Patch Exchange part of the forum to that page has been deleted, but the patches are still there.

Has the patch format changed, making importing older patches a problem? Maybe it's just a Windows 7 / USB driver thing.

@join said in Anyma Phi v1.0 public beta:

Apart from the handful of currently identified bugs, it looks like the beta is working fine. I'll post a new version in the upcoming days, and if nothing new comes at the end of the week (or the beginning of next week), we'll be able to roll out the official v1.0 release pretty soon.

I received my replacement anyma phi earlier, and updated it to the latest beta firmware. I've had problems importing patches I'd saved from the old one, via the new editor - some worked, some worked after resetting the patch in the editor, some still didn't work after a few attempts, so I moved on. On a couple of occasions, I seemed to get the name of one patch, with the contents of an other.

Among them, I tried to load the patches from the AnymaPhiPatchesTW collection, in the patches section of the forum, and managed to load maybe two out of three, some with a few attempts.

When I try to load a patch, with File->Import, the name of the patch shows on the anyma phi, but quite often, it just plays the default, sine wave, patch.

I'm using Windows 7. I haven't had the loss of USB connection issues I used to have, with the last version I was using. With that version, I had to close the editor and re-open it a lot, but in this one, there doesn't seem to be a need to, and doing that doesn't appear to help with the patch loading problem.

Will we be able to backup patches with a sysex librarian, like Bome's SendSX, and send them back again? I could cope without an editor, so long as I could reliably dump and restore patches, either over USB or MIDI.

It would be nice be able to get it to work with KnobKraft Orm, which is an open source sysex librarian, meant for choosing patches off a grid, while playing.

That needs a specific "adaptation" written for each type of synth it works with, in Python. I managed to make one for the Korg Minilogue XD, recently. All it really takes is device discovery, loading a patch to the edit buffer, dumping either from a specified location or from the edit buffer (after selecting the patch, e.g. with a Program Change), and being able to extract the name from the patch, so it can be shown in Orm. Ideally, the patch number too. There's no real need to know any more about the sysex format than that, to get it to work.

I received a replacement anyma phi, earlier, from or via Juno. This one seems to be working fine. Thanks.

I have tried to email you to follow up my warranty return, but my emails are rejected by the server.

Since it seems I can only contact you through this forum, here is the body of the email I tried to send, with my full name redacted, for privacy reasons.

@@@

Hi Matthias,

After trying to discuss the problem through your support forum, and then in
private with your former employee, Maxence, I returned my anyma phi via
Juno, to get the intrusive background noise repaired - or to get the synth
replaced, under warranty. I sent it to them two months ago, on the 5th of
November.

On the 2nd of December, I received the email forwarded below, from Juno
support, and replied to it at length. I have not heard back from them,
despite further attempts to elicit a response.

I had already answered these questions in your community support forum, in
detail, and provided a recording of the problem, and a screenshot of a PC
based oscilloscope trace.

In short - turn it on, connect just a set of headphones (any - it didn't
make any difference which sort I used), let it warm up for a couple of
minutes, and you will hear the sound. It always starts within a few minutes
of turning on from cold, or sooner if the synth is turned off and back on
again afterwards.

It will then not stop until you turn off the anyma phi, even with the volume
turned all the way down - and that's after calibrating the volume knob.

It made my anyma phi useless for both recording and performance purposes.

It doesn't matter what the power source is, or what headphones are used, or
whether an amp is used first, as I explained, and it doesn't matter what
else is connected, if anything - either by MIDI or USB. It still makes the
same sound.

My conclusion is that it's probably picking up a harmonic of the PWM signal
that drives the LEDs, as I was able to affect it by turning up the level of
Audio In, then varying the brightness of the LEDs, in the global menu. The
sound is picked up and amplified further, via Audio In, and the tone and
volume of the sound are then affected by the LED brightness level.

I put all of this in the support forum thread, as I discovered it. I used
the username AndyHornBlower, and the thread is called "High pitched
background noise, around 2340Hz (anyma phi)", started on 13th of September.
Although the thread was written over a couple of weeks, it will only take a
few minutes to read it, and to listen to the recording. I also enclosed a
letter, addressed to yourselves, with the anyma phi, when I returned it.

I ordered my anyma phi the day they first came into stock, at Juno (aka Juno
Records, UK), on 12th of July (Order number C10458002), and although I spent
some time familiarising myself with it, and even contributed some patches to
the forum, I never had much use from it, due to this fault. I've now been
without it all together, for two months, without being told what's happening
about it.

I notice Juno have had more stock of these, since the beginning of December,
but don't seem to have sold any of them. As you apparently haven't been
able to repair mine, or find the time to look at it properly, perhaps you
could ask them to send me one, to replace mine, then sort out the details
between yourselves.

Regards,

Andy (aka AndyHornBlower, in your community support forum)

----- Original Message -----
From: Davide | Juno (Juno Records Support Desk)
To: Andy
Sent: Thursday, December 02, 2021 2:23 PM
Subject: 448556

Please type your reply above this line

Davide | Juno (Juno Support Desk)
Dec 2, 2021, 14:23 GMT
Hi Andy,

I hope this email finds you well.

Could you please let me know which headphones and cables you used with Aodyo
Anyma Phi synth?

I'm in contact with Matthias@Aodyo who is trying to replicate the fault.

Best regards,

Davide
Juno Customer Support Team

Kind Regards
Davide
This email is a service from Juno Support Desk.
[Q5O6ZD-OEYQ]

@bengersfood Yes. I've tried various power sources, including an Apple ipad USB charger, direct power from a smallish USB power brick, and 5V produced from an adjustable step up / down (aka buck boost) converter, powered by a 9V DC wall wart, then the same converter powered by a NiMH battery pack.

The advantages of the buck boost converter are that it is a very quiet power supply, which I normally use with guitar pedals, and also that it meant I could eliminate the USB A -> DC jack cable because it has its own (short) DC jack cable.

In all cases, the 2.3kHz (or so) whine noise starts within a minute of turning it on from cold, or immediately, if it's already warmed up, i.e. it's been on for a while, then turned off and back on again.

About the LED noise being picked up - if I use a patch with the external audio in, I can hear the difference when I turn the LED brightness level up and down in the settings - brighter is louder.

My guess is that it's the LEDs I'm hearing at all times, even with the volume turned all the way down, which is why I asked about the PWM frequency that drives them.

@support_aodyo Could you pass this question to your hardware designer(s), please?

@jan That's definitely not normal behaviour.

I updated mine to the current version via a hub, using Windows 7. It probably depends on the hub though. I think the problem with some of them is that there's a voltage drop, due to the cables, and the hub doesn't necessarily correct it. It would certainly be possible to design one that did, using a DC-DC converter, but I don't know how many do.

Using good quality cables helps with the voltage drop - the better the wires in the cable conduct, the lower the drop in voltage.

It may be better to try an adapter, rather than a hub, if you don't have USB A sockets - assuming you have some other sort of USB socket. On eBay, you can find simple adapters, which are two different connectors back to back, or short cables, to adapt just about any sort of USB connection. The ones to avoid are OTG cables and adapters. Other than that, they tend to work well.

Are you sure the update completed? The fact that it asks for it again suggests that it didn't.

@support_aodyo Yes, the sound is always the same, though the amplitude of it sometimes changes suddenly.

I've now tried it with an adjustable power supply, powered by a battery pack, and a different cable. That's the quietest power supply I own. There is no difference. I've also checked that the same noise/sound appears on all three audio output sockets, even with Volume all the way down.

I notice the sound is also picked up at Audio In, even if I plug in a cable to short it to ground - e.g. if I take an "(EMPTY)" patch and set the Main Audio In as In-R, with a short mono patch lead plugged into the Audio In socket, shorting the right input channel to ground. If I then turn up the Main Audio In level, I can make the sound louder using the Volume knob.

Is there a DC-DC converter inside the anyma phi, with a conversion frequency of 2340Hz, or similar? If so, my guess is that it's being picked up by whatever circuitry drives the outputs, and also being picked up at Audio In, so it can be amplified further.

Perhaps this will help me get a reply. Here's a scope and frequency analysis of the high pitched noise. You can see the fundamental is around 2.3kHz, as detected by ClearTune.

I've also attached a short recording of the noise, made through a cheap generic USB sound "card" (key fob style audio interface), simply setting the level for that input via Sounds, in Windows - no other hardware. No MIDI or USB device is connected to the anyma phi, just power and a connection from stereo audio out to the audio interface.

high pitched noise on ap EMPTY patch (no USB or MIDI).zip.

This is exactly the sound I hear when I connect headphones directly, or via my FiiO E06 headphones amp. I can make the level less, compared to the synth sound, as described, but I can't get rid of it all together.

It doesn't always start making that sound from cold. It kicks in, usually after selecting a patch with the encoder, then it stays on until I power it off again - changing patches again, makes no difference.

Since it's always the exact same tone (frequency and overtone series), it seems to me there must be a physical reason for it, or maybe even a firmware bug, and the exact frequency ought to be a clue as to why.

On this occasion, altering the LED brightness in settings didn't affect it.

Turning the Volume knob to zero didn't affect it either.

Only the original power supply and cable (no extension added) was used for this analysis and recording. I've also verified that it sounds the same with an Apple USB power supply, used for charging my iPad 3.

@jimhanks Great tune and great playing. The digital desert was fun too.

Oddly, the Raspish Tenor sounded more like a large flute, watching you play it on the WARBL. Power of suggestion, I suppose.

Would it be possible to extend the Windsyo oscillators down to a low Bb? I.e. two semitones / half steps lower than the lowest C they currently play?

They're my favourite part of the anyma phi but I'm playing them on a Yamaha WX5 (sax-like) wind controller, which has keys to play down to a low Bb, like most types of saxophone. I keep trying to play a low B, without thinking about it, and getting silence.

I've noticed the Windsyo sounds can't be bent much below the low C without going silent too, so it might be better if they could play as low as the A, or even the Ab, to allow for bending - I can play the WX5 comfortably with two semitones of pitch bend down available, but on the low C, those sounds cut out almost as soon as I try to bend down from it.

Is there a fundamental reason why they have to stop on a C as the lowest note in their range, or is it just part of the fact that they were made for the Sylphyo?

I've been meaning to mention that my anyma phi has a high pitched background noise, most of the time, wavering slightly, around 2340kHz (maybe 2343Hz) - that frequency is according to ClearTune on my iPad 3, connected with an iRig, and it identifies it as roughly D7. It sounds above the top C that I can play with an "empty" patch, but within the range that I can bend that note up to.

It's present on the headphones socket and the left audio out - I assume that's what I should use for mono. I expect it's the same on the right audio out, but I haven't checked. It's largely independent of the volume knob - I hear it as clearly with the anyma phi's volume knob turned all the way down.

It does it whether I'm using DIN MIDI or USB MIDI via the USB Host socket. It does it with headphones plugged in directly, or when taking the output of either the headphones socket or left line out to something else.

I've been working around it by using a FiiO E06 headphones amp from the output (either from the headphones socket or left line out), by turning the gain on that low enough so I can't clearly hear the noise, and turning the volume full up on the anyma phi, to get a better signal to noise ratio.

If I switch to the original factory patch 7 (a piezo patch that has audio in turned full up), I hear the same sort of sound, but louder.

At one point, I was able to get the sound to get louder and softer by turning the LED brightness up and down - I did it a few times in a row and it seemed consistent. I can't get it to do that reliably though. Once when I did that, it suddenly stopped, or got much quieter so I couldn't really hear it any more (still via the headphones amp, with less than unity gain, so it might just have got quiter). I've heard it suddenly get louder when changing patches too - to ones without audio In turned up, and no envelope follower.

Is there a way to turn the LEDs off all together, so I can hear the difference? Since they can be faded, and the colour mix can be adjusted, I'm guessing they're driven by PWM. Is the frequency I hear the PWM frequency, by any chance, or maybe an octave either side of it?

It would be good to be able to turn the display off too, to check if that's being picked up.

On a maybe not directly related problem, I've also been hearing a metallic ping or pling, not unlike the sound that the built in piezo might make if something small and hard fell on it. It's intermittent - it can go quite a while without making the sound, then do it a few times within a couple of minutes. I was hoping that was a bug, maybe from CPU overload, but it does it even on an "empty" patch.

Are these known problems? I thought I'd read about noise on the outputs, but I can't remember who said it.

My Yamaha Reface CS works too - plugged in with a USB cable to the USB host socket. That's a better choice than the PSS-A50 because it has a pitch bend lever, and 13 sliders/faders that send a continuous CC value, from 0-127... actually 14, if you don't mind using one with detentes (the Poly / Portamento selector isn't just a multi position switch - it can send values in between the positions).

Those can be assigned to control A, B, C & D (in the anyma phi settings menu), which is more convenient than turning the encoders.

The Reface CS can't take power from the anyma phi though - it needs an external DC supply, or a set of batteries.

I have the others in the Reface series, so if anyone wants me to check a particular one, let me know, but I assume they all work the same for USB-MIDI. The other logical choice would be the Reface CP, because it has 8 knobs that send continuous CCs, but no pitch bend, unfortunately.

FWIW, my Yamaha PSS-A50 works fine, plugged into the USB host socket of the anyma phi.

I found it's best to plug it in before turning on the anyma phi, then turn on the PSS-A50 with its power button. It draws power from the USB host socket. I habitually leave a short audio extension lead plugged into the PSS-A50 audio out socket, to keep it quiet.

It's not likely to be a popular choice because it doesn't have a MOD or pitch bend wheel, but it does have pretty good mini sized keys, with velocity. The program select buttons change patches on the anyma phi too, though the number shown on the LED display of the PSS-A50 doesn't correspond to the PC it sends. It sends about 40 different ones, so it's still useful if you don't mind making a chart or trying to remember which is which.

Some of the PSS-A50 sounds might be worth feeding to Audio In on the anyma phi.

@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 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.

@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.

@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.

@markusschloesser said in Anyma Phi editor software:

2. I want to upload @Broken-Gadget 's patches, how do I bulk import them into the editor? Drag and Drop would be great as well!

I made a start on them, then got distracted. I'll get back to it... However, I figure if it's not a problem to have the PC/Mac editor connected at the same time as the instrument or keyboard you want to try them with, it doesn't matter much because you can import one, try it briefly, then import another, and so on.

3. Again, could you please show the current version with a version number?

I've been thinking it should show the version number on the update download page. Otherwise, the only way to tell for certain if it's a new one is to download it and open the zip.

I've been wondering how we'll know when there's a new release, unless we haunt this forum regularly. I don't see any way to ask for a notification, or to get notified of new threads, for example in the "anyma phi general" sub forum.

4 I seem to have lost my great patch, although it was definitely shown as saved. What happened here? (Windows)

After finding the problem with renaming, and finding the workaround for that, I've been doing the same with each patch edit, to make sure I don't lose it. I don't know if that's needed, but it seems like the best bet:

1. Use File->Export, so you have a backup in a single patch file
2. Use File->Import, to import the same patch back again - because that's currently the only way I can be sure it's saved permanently on the synth.

The philosophy seems to be that changes are only saved from the front panel of the synth (with Shift+Right arrow), which personally, I don't think fits well with using a PC/Mac based editor. I'm not sure if there are other exceptions to that, but File->Import always works.

@milododds My Yamaha CBX-K1 is fully compatible, because it has a standard 5 pin DIN MIDI Out.

It has the advantage that the mod wheel can be assigned to send other CCs instead, just using a button on the keyboard and its own keys for data entry, to say which. So, it can be used to send controls for A (MOD), B, C or D, or to send Breath.

They haven't been available new for some years, but they keep appearing on eBay, from time to time, so I guess quite a lot of them were made. They've lasted well.