Posts made by AndyHornBlower

@join said in Renaming a patch doesn't stick (v0.8.90, updated today):

This is fixed in the upcoming update, with the Export filename pre-fill too.

Great. Thanks.

@jimhanks said in Patch Exchange Thread:

@andyhornblower simple but fun! particularly like the "clari" one

Thanks. Good video, and both good patches. The Raspish Tenor is great.

I'm having to blow quite hard on my Yamaha WX5 to get the buzzy flute to sound, which makes me wonder if your WARBL has a different response. The WX5 is adjustable, but it's fiddly to do, so I leave it alone now I've got it mostly comfortable.

My monitor is only 1360x768, so I watch YouTube videos in 720p. I gather yours is much higher resolution. I was still able to follow it though, and I guess most people have more pixels than me. FWIW, the editor works fine at that lowish resolution, though it starts with the window a bit too big. I have to make it full screen, by double clicking the title bar, to make it fit. There's more scrolling of boxes to do, but I can still get to all of the controls, which are all a fairly reasonable size.

Here's a couple more patches. One is another variation on Clari1, using the EQ filter with the peak, making something between an alto and a tenor... maybe, so I've called it CMel1, for C melody sax.

The other started as an experiment to see if I could get playable bugle series overtones with the EQ filter, which I can, but don't have any way to take away the original sound to leave just those, so I scaled my ambitions back a bit. In the lower octave, it sounds a bit like a bowed cello or double bass, crossed with throat singing, with overtones chosen by blowing harder or softer.

CMel1.anymaphi-patch

FeynmanBass.anymaphi-patch

I just noticed a third demo by Mark Steiner, on Vimeo. This is one is done without any additional effects. It's all coming directly from the anyma phi:

Anyma Phi - Dry Exploration Sounds

@jimhanks said in Patch Exchange Thread:

Here's my very first attempt. Not saying it's great. :-)
JH_First_Flute.anymaphi-patch

I like it. I haven't had much luck with making flute sounds with the "Blow" sounds on my MI Elements, so maybe that one's based on Braids? I have a cut down Braids clone (12 bit DAC and no display or menus). I'll have to look into that.

I tweaked it a bit trying to get it a bit louder, and largely failed, but I did add some MOD wheel response:

JH_First_Flute&.anymaphi-patch

I've played both versions with my Yamaha WX5, with the expression wheel mapped to MOD for up, and pitch bend down, for down. It starts to get into pipe organ territory, on the lower range, with a bit more MOD...

If you press the hand icon twice (the one that selects the lowest row of the matrix - next to the right arrow button), you get to use the knobs as A, B, C & D. A works as the MOD wheel, so you can use that with your WARBL.

@bibenu said in Patch Exchange Thread:

Nice work collecting all the patches so far @andyhornblower

Thanks. I missed the other Vimeo demo link that Mark Steiner posted, which is also well worth watching:

Anyma Phi Analog Engine Demo

Yes, we'll just have to keep pestering them to make this thread a sticky :) For now, we can all bump it once in a while, by adding a new patch.

Here's some I made earlier, exploring the Windsyo oscillator options a bit, in fairly basic patches. Each one responds to Breath, or velocity, and MOD:

CrudeFlute1.anymaphi-patch

CSax1.anymaphi-patch

CClari1.anymaphi-patch

CDuduk1.anymaphi-patch

CDuduk2.anymaphi-patch

The sax and clarinet ones are made with different voice options, but initially sounded very similar, so I tweaked the response of the parameters a bit to tell them apart.

I've found a workaround for this, but you have to apply it to each patch you want to have a volume control.

You need one free Mapping, plus one free external control out of B, C and D, which aren't currently used in a mapping - that doesn't necessarily need to be the same one for each patch, but it's probably easier if it's always the same one.

First, set one of the external controls (e.g. D) to be controlled by CC7 for Volume (or CC4 for Foot Controller). Each one has two CCs that can control it, and you set them by pressing the encoder under the display, then turning until you see CC Mapping. Press the right arrow to choose it. The details are in the manual, but perhaps a little sketchy, so let me know if you get stuck. Basically you change it with just turning the encoder, pressing the encoder down, and some use of the arrow buttons. Use Shift + Left arrow to get out of the menu when you've done it.

Next change one of the Mappings so that the source is your external control (e.g. D), and the destination is Patch Volume, then set the amount to +100%. E.g. turn the display encoder while holding down the shift button, on the synth, to get to Mapping 32, or any other unused one - or use the editor software. Shift+Left exits the menu, if you're doing it on the synth,

That lets the control influence the sound level, but it won't yet turn it all the way down, and if it's already full up, you won't hear a change. If you press the lowest matrix button twice (the hand icon), you can use the knobs as A, B, C and D, to try it.

The final step is to set the patch volume to zero, or the minimum level you want it to go to. On the synth, that's done with Shift + turning the display encoder, then picking Patch, at the top of that menu, then pressing the second matrix line button (waves icon), to show the Volume parameter.

When you've finished, press Shift + Right arrow to save it, on the synth. Or in the editor, File->Export followed by File->Import, seems to be the best way at the moment - you've then saved it to your PC or Mac, and made sure the changes are saved on the synth.

This might sound a bit tedious, but it took far longer to explain it than it did to do it to a patch :) You could do all the factory ones in a couple of minutes, probably.

@bibenu Yes, I guess the fact that the synth doesn't consider a Rename as a change to the patch could be considered a bug. I wonder if that problem extends to any other changes from the editor. The only thing that currently makes a permanent change from the editor is Import, as far as I can see.

Even so, I think having Rename make an immediate permanent change would make for a better workflow. The point of it is to rename the patch on the synth, and it's done from a PC or Mac, which isn't necessarily directly next to the synth, so it's easier if it can all be done smoothly, from the editor software.

Another thing that bothers me a little is the Export on the editor doesn't prefill the filename box with the patch name. That's sort of on topic, because it's currently part of the process of working around not being able to do a Rename in an obvious way, and have it be permanent.

@jimhanks I think you've just officially started one :)

A couple of us recently asked for a sub section, or similar, for patches to be shared, but so far that hasn't happened. One thread to rule them all seems like a good start, so I vote for yours.

broken-gadget shared a link to a large collection of patches he's made, in a thread about the editor, here:

To keep it all in one place, here's the link he gave:

@broken-gadget said in Anyma Phi editor software:

I've written a review of the Anyma Phi and published 57patches here: [http://www.brokengadget.org/anymated-synthesis/]

Mark Steiner linked to a demo of his own patches, on Vimeo. I'm not sure if he's planning to upload them here, but that's well worth watching, either way:

Anyma Phi - Exploration Patches (many engine types)

Thanks for the flute patch. I'll try that tomorrow. I liked your demo of factory patch 15, in your YouTube video. You might try making a variation on that by changing the oscillator type to the Windsyo Duduk, which is quite sax like. You may need to tweak it a bit afterwards to get something useful though - it responds differently.

From the front panel of the synth, you can press the encoder under the display to get to Copy Patch, then change to an empty patch slot and press the encoder again to get Paste Patch - you get a patch with the same name, with a + added on the end.

I uploaded a couple of tweaks of factory patches, in another thread, which are different to the originals, if not actually any better :) I've done the same with some of broken-gadgets patches, partly as a learning exercise, but uploading those seems like cheating, so I won't.

These are the two altered factory patches I posted before:

Atmos Pluck&.anymaphi-patch

Piezo or Play&.anymaphi-patch

I have a couple more I like the results of, but I may tweak them a bit more first.

I've read your replies to other threads. I'll let you have the last word on those, for now. It might get people's attention better to see someone else replied, after I did.

@markusschloesser said in Maxforlive device?:

Please leave my C4 out of this! I can bank thru pages, so 128 params is no problem for me 😉😂

Yes, the BCR2000 can do that too. I could add bank switching to the Akai MIDImix fairly easily, by making an Arduino based box to sit in between that and the synth, capturing the Bank Up/Down buttons (which only send two fixed notes).

More would be better, certainly. I was thinking of the way Dave Smith / Sequential do it, which is to have a full set of NRPN parameters, plus a much more limited set of CCs that duplicate some of those, making them useable with just a CC based MIDI controller... there are quite a few of those.

If I was doing the programming, I'd want to start small, with a limited number of CCs. Adding more would then be straightforward, but just a little more work. Doing the full set of NRPNs would take longer.

Alternatively, it might be practical to do a general numbered parameter via sysex or NRPN that's just an index into the patch data, like indexing an array. In which case, it wouldn't take so long to program, but it would still be a fairly large task to document it all, for the user manual.

@join Thinking about it some more, I think it might be better to have CCs for the 32 modulation depths/amounts of each mapping. Though it would be nice to have CCs for each matrix parameter too, ideally, even though there would be some overlap when those are assigned in mappings.

32 controls is a good number for a MIDI controller like the Akai MIDImix or the Mackie C4, or Behringer BCR2000.

@marksteiner Great videos, and some very interesting patches.

Very much off topic, I like your Blip! module demo too. If I could get that PCB and panel set in the UK, or import the module ready made, I'd be very tempted.

@jimhanks Interesting videos. Thanks. I like your WARBL controller.

You might get a better view of the screen, in your videos, if you turn the display brightness down... I think there's a setting for that.

Failing that, you could put a piece of coloured plastic over the display. I do that with my DynaSample Xpresso, so I can stand the glare from the backlight, in a dimly lit room. I bought some different coloured plastic document folders and cut them up to find the best one to use. There are proper acetates for theatre lighting you can buy too, but the plastic folder probably works well enough.

@broken-gadget said in Anyma Phi editor software:

I've written a review of the Anyma Phi and published 57patches here: [http://www.brokengadget.org/anymated-synthesis/]

That's great. Thanks very much. When I get a new synth with patch memory, I'm in the habit of going through some of the factory patches and tweaking them, as a first stage in learning about the synth - rather than just diving in and trying to make new ones from scratch. Needless to say, the provided ones didn't give much scope for doing that, so it's really good to have a decent sized set of good quality patches like yours to start from.

Your review was interesting too. Personally, I'm finding I prefer to edit patches from the actual synth - or I will do, once the firmware is more stable so it doesn't keep frustrating me by crashing while I'm editing. I'm confident that will improve though.

What I would like is sysex support for bank and patch dumps, and a way of putting a saved patch into the edit buffer, with a sysex librarian - if there is an edit buffer on this synth. If it was able to do that, I wouldn't really miss the PC based editor.

@bibenu said in Anyma Phi - shift to the alternative version of the matrix:

There is, but it's not terribly interesting. Two threads.

That's good to know. Thanks :)

@bibenu said in Anyma Phi - shift to the alternative version of the matrix:

EDIT: here on the forum somewhere ... not necessarily in this thread :)

Agreed. I think the github support model is a good one, and this forum would do well to follow suit. I'd suggest a sub forum for anyma phi bug reports, and another for feature requests.

Once the support staff feel they've dealt with a bug adequately, I'd be okay with them archiving or deleting that thread, if they feel they must. On github those threads are normally closed, which means they're not immediately shown, but are still available to be read. That's better than deleting, in my view, because sometimes the same bug resurfaces later, so it's useful to be able to refer to the original discussion.

As for feature requests, there have already been a few, but they're lost in the general anyma phi section. It would be good to give them their own place, so it's easier for people to join in the discussion. That way, Aodyo would gain a better understanding of which new features are worth spending the time on.

Incidentally, @join, is there still an "early adopters" section that us mere retail customers are barred from? It seems to me that we're all early adopters, because it's still some way from being finished or stable - just an observation, not meant as a criticism.

@bibenu said in Anyma Phi - shift to the alternative version of the matrix:

The only thing I can add to the above is that the synth carried on processing midi notes from my keyboard and making sounds, even though the screen was frozen, and the knobs and buttons did nothing.

Yes, I've had that happen quite a lot too. The user interface locks up but I can often keep playing.

As you say, it's usually hard to pin it down to any particular circumstance. The only case where I can see a definite correlation is in setting the mapping destination - e.g. I've set the destination object as SFX3, which is for example a cross fader with gain, then I turn the other encoder to try to set the part of it to be controlled. That often causes a crash, in the manner I described, but not always, so it's hard to make a set of instructions for a reproducible bug. I've often found I can't set that destination at all too - I turn the encoder but it won't let me choose one.

@join I don't personally feel that reporting bugs in the form of a one to one conversation with support would be very fruitful, at this point, because we're probably all going to suffer from them for a while, until the firmware is made more stable. It seems to me it's better to adopt the github model of being able to report bugs, and also ask for enhancements, semi publicly - just within this currently very small forum. That lets us collaborate on an explanation, as we're doing here.

I accept that it's not really ready yet, and I thought that might be the case when I bought it. I don't mind putting some effort into reporting the problems, but not if it means exchanges in secret between me and your support staff, which can get very time consuming, and won't necessarily yield results any quicker.

@bibenu I've been having problems with mine locking up, or sometimes restarting, when editing patches from its own controls.

I was worried that it had gone wrong for a while, but now I'm thinking it's just some instability in the firmware. It may just be that the particular patch you're trying to use when it crashes is corrupt in some way.

I made a patch with the external audio-in plus a simple synth sound, which seemed fine when I first did it, but after turning the synth off for a few days I couldn't get it to behave at all, and finally just gave up on that patch.

I fairly commonly get crashes when trying to set the destination of a Mapping (e.g. setting which element of an effect it controls, after choosing the effect as the first part of the destination), so I'm thinking that's probably a null pointer or an off by one sort of bug. When that happens, it typically either goes completely silent or emits a constant tone, which starts as I turn the encoder. The user interface then appears to still work, but if I try to switch to another patch, it locks up.

Also, turning off and back on again doesn't always clear the problem properly. I find I have to leave a few seconds in between - e.g. count to ten.... Which is odd, but I can sort of see how that might work if it's in separate modules and one of them draws very little power - possibly there's a power smoothing capacitor that can keep part of it running a short while after it's turned off.

I think, quite likely, the firmware is still just in an early release stage, with some fairly critical bugs.

@join Could we have some CCs to control the matrix parameters?

I gather that's meant to be one of the main features of the anyma phi, and there aren't all that many of them, so it seems like something that could usefully be done. Allowing for the shift function, that appears to only need around 40 CCs, so it also seems practical.

That would allow us to connect an external MIDI controller to give more immediate access to those parameters, or for DAW users to have better control over the synth.

I realise that allowing every single parameter to be controlled externally would be a big job, but just limiting it to externalising just the matrix controls seems like a good start.

@bibenu You're welcome :)

I've since bought a 2.1mm/5.5mm extension lead, on ebay, to extend the round plug end of the power lead. They're popular for CCTV installations, so they're not hard to find. I won't give a link because ebay listings are short lived, and it would probably only be of use to other people in the UK.

The one I bought was from a seller called switch_elec, and has a right angled plug, to go into the anyma phi. They also had straight ones, and different lengths. It was listed as
"1M Right Angle Male to Female 2.1mm x 5.5mm DC Extension Lead Connector".

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

@support_aodyo Soft MIDI Thru would be useful.

Since it would be done in software, you could also consider having the option of simple polyphonic chaining - by not passing on notes that are played, and having the option (as a Note Priority setting) of not accepting a new note while one is held down but passing it on to the next synth in the chain, instead.

That would encourage people to own more than one anyma phi, to add more polyphonic voices.

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

@markusschloesser said in Maxforlive device?:

Mackie C4

Nice. Can Maxforlive host the VST version of Ctrlr?

I've made a generic panel with the same layout as the Akai MidiMix knobs... so far, I haven't bothered to add the buttons. The idea was to use it as a translation table, to use that controller with different synths, by making a variation of the panel for each one.

So far, it just sends CCs, which can be edited easily enough in "panel mode", to make CC controls for synths. I have some code I could add to send NRPNs, but that gets a bit more complicated.

As yet, I've only used that method to add more knobs to my MODOR NF1-m - the mini desktop version of that synth, not much bigger than the anyma phi. I could adapt it to the a.p. though, once I have a better idea of what parameters would be useful to control.

@milododds You might want to look into using Cockos Reaper (from reaper.fm), as your DAW. For one thing, they have a very active forum, with members helping each other, and there's lots of tutorials, on YouTube.

Also, it's very cheap to buy a license that gives you updates for the next few years, but you can just start using it for free, and put up with the nag screen for a while, when you start it up.

I don't have a lot of experience of it, but I have tried it, and it seems suitable. It can do the thing where you have tracks of MIDI data that you can see the details of on the screen, to send whole songs or just loops to a synth.

The DAW I actually use, a little, is Cantabile, with the Solo license (cheapest paid license), but that's not what I do with it, and I'm not sure it can do that at all. It's meant mostly for hosting VSTi and effects plugins, for playing live.

I mostly use it to host Ctrlr, which lets me make control panels for synths, or use ones made by other people, then I can assign physical knobs, from a MIDI controller. That's something you can still do in Reaper though, so you could add a control panel to tweak things with CCs, at some point in the future.

FWIW, Nick Batt, from sonicstate, who reviews a lot of synths on YouTube, uses Reaper.

Your M-Audio M-Track Duo interface seems ideal for taking sound from the synth, to feed back to the DAW. Probably the main uses of that would be to record it, in the DAW, and/or feed it through effects plugins.

@milododds Cool. The volume thing could just be that some of the patches take quite a bit of velocity, to get loud - I'm pounding on my little Yamaha keyboard more than I'm used to. They can be tweaked though.

Yes, plugging it in with USB shows the anyma phi as an output for notes and CCs, and also shows its MIDI In and Out, which you could use to connect other gear to the PC, I guess - I haven't tried that yet.

I don't use DAWs much, but you could use one as a sequencer to send notes to the anyma phi. If you have an audio interface, you can route sound from the ap to effects plug ins in the DAW.

@milododds That sounds promising. I'll resist the urge to make any more suggestions, and let Matthias get on with it :) I hope you manage to get it sorted out. I hate having to send things back too.

@milododds I'm sorry to hear that.

The point of trying to get the white LED on the synth to get brighter or dimmer as you drag a key in VMK with the mouse, was to check that the synth is actually receiving MIDI and responding to it. I haven't seen a MIDI indicator anywhere, but that would be it responding to MOD, as though you were turning the mod wheel.

One final thing you could try is patch 7, "piezo_pling", which doesn't rely on MIDI at all - just turn up the volume and tap on the case. If it's working, you'll hear a sort of clanging sound, provided the internal piezo is working too.

@milododds A common problem with having a new MIDI interface is getting the sockets mixed up, incidentally. On most, you'd have a cable from a socket marked OUT, on the interface, going to MIDI IN on the synth. I have an M-Audio one where the Out socket is labelled "To In" instead, which still throws me.

Here's a test you can do - set one or both of the X and Y Controller options in Virtual MIDI Keyboard to send CC1 - which shows as "1 Modulation Wheel".

Now, try dragging one of the virtual keys in whichever direction you've set it on, with your mouse - or drag diagonally, which covers it either way. If it's all working, you'll see a white LED get brighter or dimmer, as you move the mouse. It's the one to the left of the row of four encoder knobs, next to the Shift button (an Up arrow).

@milododds Those settings don't really matter, at the moment, but you can set CCs for the two USER knobs you see towards the right of the virtual keyboard. I normally set either the X or Y one to CC1, which is the same as moving the MOD wheel, on a real keyboard. All the patches on the anyma phi will respond to that. Some will respond to others, and there's a list in the manual, somewhere. CC2 is worth a try too, which is Breath, though the results could be a bit confusing if you use that.

The X and Y ones get sent when you try to drag a key, instead of clicking it.

I take it you've turned the volume knob all the way up on the synth? It's the knob above the display. It doesn't seem to do much for the first part of the turn, maybe depending on the patch.

You can also try the line outputs, next to the headphones socket, if you have an amp and the right cables or adapters. Either one to a guitar amp should work, for example.

@milododds Do you have Windows, and a USB-MIDI interface?

I did my first check of my new anyma phi with Virtual MIDI Keyboard, by Wouter Van Beek, which is free to use, and available here:

http://www.granucon.com/SoftwarePages/Vmk.aspx

All you have to do is start it up, press the Settings button (above the first B key from the left) and specify your MIDI interface that you want to use as an output. Then plug headphones into the headphones socket of the anyma phi, and a MIDI cable from the USB-MIDI interface on your PC to MIDI IN.

There are subtleties, like being able to set the velocity, and send two CCs for X and Y, when you drag a key with the mouse, but all you need to set at first is the MIDI output port, then start clicking on the virtual keyboard keys.

I wouldn't be surprised if the Akai keyboard wasn't compatible, because USB-MIDI has complications, and often needs drivers installed specifically.

I'm now using it with my Yamaha CBX-K1 - a three octave mini keys keyboard, with true MIDI Out. That's working fine.

I posted the patch I mentioned, with the internal piezo tap (or ext in) and an oscillator, in a thread where the ability to post a patch was being discussed. Here's a link to the patch:

Piezo or Play&.anymaphi-patch

@support_aodyo (120 seconds or more later, due to the posting speed limitation...) Yep. That seems fine. Thanks very much :)

Now we just need somewhere better to put them all together in one place.

@support_aodyo Testing... one... two...

Atmos Pluck&.anymaphi-patch (tweaked factory sound).

Piezo or Play&.anymaphi-patch (tap the case and/or play a flutey synth lead with MIDI).

@bibenu Thanks for checking.

Yes, the main problem with linking to files stored elsewhere is that they evaporate, after a while. It used to be common to put pictures on image hosting sites, to link to in forums, which was fine for a while, but then most of them disappeared over night, leaving a lot of broken links.

I see anyma phi patches are exactly 1KB - and I've definitely typed much more than that into this forum, just since yesterday :) So, attaching them shouldn't be a problem at all, once it works.

@bibenu Agreed. A new sub forum seems like the way to go. A single, long, thread in the General section would keep getting buried, if people didn't add to it for a while.

The name "Anyma Phi General" suggests there could be an "Anyma Phi patches", alongside it, but either way would be good.

I guess I could put a few patches on Google Drive, and link to them, but it would be more user friendly if we could just attach them. They're pretty small files.

Maybe I just don't have the privileges yet, because I only registered yesterday?

It seems we're meant to use drag and drop, into the edit box, to attach a patch? If I try that, I get an error saying that I don't have the required privileges:

"
Error
You do not have enough privileges for this action.
"

@support_aodyo said in Impressed:
What you can try if you want is set up a patch with the piezo as one input and use a regular oscillator as another input from a keyboard, so you can play both a melody on the keyboard (or run a sequence/arp) and at the same time play percussively with the piezo!

That occurred to me too, before reading this. I made a patch yesterday. based on one of the piezo tap ones, with a flutey synth lead added...

I'd attach it, but I can't figure out how. Are we supposed to link to a file stored somewhere else, outside the forum, instead?

@markusschloesser I was thinking something similar - I'd like a VST version of the editor, even if it's limited to only editing the current patch, without the ability to manage patches in the same way as the .exe.

I use Cantabile (Solo license version) mostly so I can add physical controls to things. If a VST editor has published parameters that can be controlled by a DAW (e.g. animated), then knobs or faders from a MIDI controller can be assigned to some or all of them. The VST then provides visual feedback when a physical control is moved, plus controls can still be moved with the mouse.

@join Is there a section specifically for sharing patches in, or do we just put them in any thread?

It would be good to keep them together in one place, if possible.

One of my first thoughts was "why are there only 14 factory patches?". I've since found there are two more (in the downloads section for the factory bank https://downloads.aodyo.com/anymaphi/factory-bank/), or three counting your tutorial one. People will probably want to try out a few more than that, when they get one.

@markusschloesser said in One handed menu operation - please make the Shift button toggle or lock on:

Or maybe double clicking the link shift turns hold on and off

Good idea... or there could be a setting added to choose between toggle and momentary shift modes, to keep compatibility with what it does now as an option.

There are a couple of things like shift+arrow keys that work quite well as it is, but I'd be fine with having to press shift then arrow then shift again, if it was in toggle mode.

FWIW, my anyma arrived today, and I'm currently using a guitar pedal daisy chain lead, to extend the 2.1mm/5.5mm DC power jack end of the provided cable. I've put pieces of silicone tubing on the unused power jacks.

I think it's possible to buy a cable that's just an extension for that end of the provided one, without extra jack plugs for use with multiple guitar pedals, as an alternative to using a USB extension lead.

@bibenu said in [Renaming a patch doesn't stick

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?

I made some edits to the factory patches, then tried renaming them, in the editor software. It appeared to work, but when I tried to rename another patch, the name I'd tried to change reverted to what it was before.

Each time I try, the name is updated on the screen of the anyma, but as soon as I switch to another patch, either in the editor or using the rotary encoder and buttons, it goes back to what it was originally.

I've tried turning the anyma off and back on to check it's not just showing the wrong name, and it isn't - the names haven't changed.

I thought maybe shift+right arrow, on the synth, was needed to make the change permanent, but doing that doesn't have any effect, after renaming a patch.

Is this a known editor issue? Is there any other way to rename a patch?

I'd be fine with a video game high score table type user interface, using the encoder and buttons of the anyma, but there doesn't seem to be any provision for doing that.

My question was answered by bibenu, in another thread - clicking the encoder below the screen, then turning it to select Diagnostics, then clicking again or pressing the right arrow, shows the firmware version.

It is also shown during boot, but so briefly that it isn't readable, and in such a small font that I hadn't even noticed it.

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

I see I can scroll through the menus using the rotary encoder below the screen, by holding the shift button down, pressing the top button, then keeping the shift button down while turning the encoder...

That's really quite awkward to do. Please make the shift function toggle on and off, so I can release the button, while I turn the encoder, then press it again to exit the menu.

If I tried to do it while holding a wind controller in one hand, it would be even more awkward to keep the shift button held down while I turn the encoder.

I just got mine delivered today, and tried a few patches, so far just with a keyboard, but I'm able to send CC2.

After the first time I send CC2, I am no longer able to play the same note twice in succession - it only sounds the first time. To play the same note again, I have to play a different note first.

I haven't yet found out how to check what firmware version I have, and I don't see it in the manual, so perhaps this has been addressed already?

I just got mine today. How do I check which firmware version it has now? I don't see it in the menus, or in the manual.