@milododds I only do it as a hobby too. Thanks for your soundcloud link. That's an impressive collection of recordings. I've never recorded myself playing an instrument... maybe one day.
It will be interesting to see how the anyma phi evolves, and what else gets added to it. I like the idea of a brass simulation. The Korg Prophecy had one, apparently, but I don't know how useful it was. It seems to have been to hard to edit, for most people to do more than tweak the factory patches.
@peter-ostry My personal preference is to use all CCs, because a CC is only 3 bytes long, and can be shorted to two if there's a stream of the same one, by using "running status", where the first (status) byte is only sent when it changes.
It's also the easiest thing to program a hardware MIDI controller to send directly, i.e. for one where you can set which CC each control takes. Plus it's easier to use CCs than either NRPN or sysex in Ctrlr.
One problem with CCs is that there are only so many of them (128) and some of them are best not used for this purpose, because they have very specific meanings. Realistically, there are only maybe 100 that are useable, in most cases.
The other problem is that they only send 7 bits of data (representing 0-127).
The next choice would be NRPNs. They're longer than a CC but normally shorter than a sysex message. They can send 14 bits of data (representing 0-16383) and it's not essential to send both bytes at once, which has a big advantage;
Most MIDI controllers encode their knobs to 7 bits. On some, it's possible to set a control to physically send either the top 7 bits (course value) or the lower 7 bits (fine).
Failing that, it can be done in something like Ctrlr - the physical MIDI controller can sent CCs representing course and fine values, which Ctrlr can then translate to course and fine NRPN values.
I guess anyma phi needs to use NRPNs rather than CCs for those two reasons - two many parameters to fit in the useable range of CCs, and needing more resolution than 7 bits.
It could be done in sysex, but there are very few physical MIDI controllers that can do that at all, let alone well. Having made a few "panels", and changes to panels, in Ctlr, I much prefer using CCs, but I can see that might not be an option.
I'm very much in favour of one place to find user-contributed patches. Either
One thread (perhaps pinned ?) in the Anyma Phi section of the forum, or perhaps even a sub-forum of Anyma Phi General (similar to Early Adopter Lounge) ... either one of those.
Or get a new section set up on say https://www.presetpatch.com or https://patchstorage.com/
I’m pretty sure I’ve done exactly that to make an edit permanent. Might have been on the 8.80 firmware though.
Thanks. I have found a workaround, for now... actually two, but one way is a bid dicier.
The first way I found was to export the patch from the editor, then edit the file with a hex editor, before importing it again. That actually works, but I was having to guess where the name had to end, to avoid overwriting something else.
That step isn't needed though. I found I can rename it in the editor, then export the patch, then import it again. Importing it makes a permanent change on the synth.
If this isn't a bug, then the programmer is looking at the problem in a very different way from me. Sometimes when I point out bugs in software I'm told "No, it's meant to do that", even though I can't see any reason why it would be.
Either way, I'd like to suggest that the behaviour should be to rename it on the synth, permanently, when we use rename in the editor. Is this part of the forum an appropriate place to report such things?
@support_aodyo Oh that would be super cool. Oh don't worry I'm a patient guy, as you get to my age (50+) you tend to just take things in stride. I'm a Kickstarter Super Backer and I love helping projects like this, Aodyo is a huge success. I also just got your Sylphyo + Link and last night was playing some amazing things, totally beats a keyboard when it comes to just playing with your heart and soul. I know I'm getting close to figuring out the Anyma Phi setup. If/when I do I will reply back with what I did.
@bibenu Thanks... It seems to be Click, then turn, to see Diagnostics. I hadn't noticed it on power up. It seems to be shown below the logo, but barely long enough to register on my retinas.
On trying the new editor version, from the 0.8.90 zip download, I was told I needed to update it, so I'm now on the newest firmware version and didn't see what version it was on initially, before I did that.
However, the same thing still happens.
To be clearer, it's on the percussive patches. If I turn it on, then play those without sending CC2, it works fine, but as soon as I send CC2 I get the problem - no note can be played twice in a row on the percussive patches, even if I switch to a different patch and back again. That persists until I turn the anyma off and back on again.
That's going to cause problems if I try to play those patches with a wind controller, and there doesn't seem to be any reason why I couldn't, other than that bug.
On the subject of the captcha system, how would a blind person join this forum?
I've spoken to blind musicians before, and I'm aware that blind people use the internet with screen reader software. How would they solve a visual puzzle, like that one?
I agree that the power cable is far too short. I've extended mine using a guitar pedal daisy chain lead, for now, with short pieces of silicone tubing pushed onto the unused power jacks.
Why not use a USB socket for power instead of the 2.1mm jack socket? Those are typically used for 9V or 12V DC, and even 9V centre negative, for guitar pedals. Would the Anyma Phi survive someone plugging in one of those, by mistake?
If it had a USB socket instead, it would be less of a problem because we almost all have a variety of USB leads, of different lengths.
This is described in the "Settings" chapter (p.48). You just need to go to the Settings (press the display encoder), and to "CC mapping". There you can modify the CCs for Expression and controls A/B/C/D.
@paulbarnsley you’re right, this should be in the manual at least, for preference also on the website.
226 x 130 x 65 mm - depth 130 is approximate … doesn’t allow for the 1/4 inc jacks protruding of course.
@join Thank you for your response! That's a really good solution.
I missed something you had clearly stated in the manual:
"What this means is that you can actually have two
versions of the matrix in a patch, which could lead to two drastically
different sounds, and cross-fade between both using Morph."
The key there is that only the matrix settings are morphed. I have a Gotharman Tiny Little Deformer (sounds great routed through the Anyma Phi) which allows you to morph every single aspect of a patch, including sequencer settings and modulation routings and amounts. I'm not saying that the Anyma Phi should be like that - I'm just reminding all users that even if they are familiar with the idea of morphing from other hardware or software, they need to bear in mind that on the AP, what is morphed is specifically the matrix settings.
And I'll say it again, now that I understand it, the way you implemented that in the editor is very simple and clear. Thanks!
@support_aodyo I think he means adding the 3rd register flute fingerings. eg D3 has only 2 fingers left hand on, (index off, 2nd & 3rd fingers down.) The third register fingerings on the flute are the most difficult. 1st and 2nd are quite similar, but 3rd uses cross fingerings lifting some and pressing others not used in the first 2 octaves. I think you must give up this idea, and simply use the octave keys which simplifies this. See the Sylphyo as its own distinctive instrument, otherwise you will always struggle with this. Otherwise where do you stop wanting more similarities to the flute? For one, the D# key used mostly for venting on flute is not necessary... & there are no trill keys etc....
This is something we could decide to do at some point, but we haven't planned it yet, because there are third party tools that do this well. If there is enough demand, we might consider it.
With macOS, there is MidiKeys, and for other platforms you can use something like VMPK. Just tell the program to output on the Anyma Phi port (to send the MIDI to your Anyma Phi, not the editor) and you should be good.
Update: connecting both Anima Phi and Seaboard to the computer, Anima Phi didn’t freeze anymore. The question arises: does Anima Phi supply enough power to connect the Seaboard straight to the USB host post?
However, I couldn’t use the Seaboards onboard controls or aftertouch with the included presets. Maybe they are not programmed to be used with my Seaboard settings?
@friendly-noise As for the second question: so far in our testing the finish has been resistant but you should avoid scratching with things like sharp metallic objects on the lettering directly if you don't want to damage the finish! Other than that it's quite resistant. Let us know what you use to strike the piezo!
@ipi Agreed, very intuitive interface. The BSP worked 2 separate times for me but now doesn't work. I guess as support said, there will be a patch soon. I have a friend coming to jam this weekend with a keystep pro, an Impulse Command, a DFAM and a Bassline, so I can test it with those and report back.