Anyma Phi - shift to the alternative version of the matrix
-
The manual says "H - Shift button
While in the matrix, press the button to shift to the alternative version of the matrix."I can't get this to work at all now. If I select a new factory patch , then hold down the shift button, the display doesn't change and turning the 4 encoders does nothing. Sometimes, after doing this, the entire front panel will lock up, which then means I have to re-start the synth.
I can't work out if I'm doing it wrong, if it got broken with the latest firmware, or if I have broken hardware.
-
Okay, i have discovered that to get the shift button to work it needs a very short stab, not a longer press.
BUT .... the anyma phi front panel now locks up within a minute or two of restarting - I have to constantly switch off and on again.
-
@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.
-
@andyhornblower said in Anyma Phi - shift to the alternative version of the matrix:
I think, quite likely, the firmware is still just in an early release stage, with some fairly critical bugs.
I'm thinking the same thing.
-
Please don't hesitate to report anything pertaining to your freezes or crashes to support@aodyo.com.
R&D Engineer at Aodyo / Ingénieur R&D chez Aodyo
-
@join Thank you. If I had something that was concrete and reproducible, I would do that. Unfortunately I can't tell what set of circumstances are causing these freezes at the moment.
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.
-
@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.
-
@andyhornblower said in Anyma Phi - shift to the alternative version of the matrix:
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,
I agree with that.
I mean, the firmware is not even a 1.0 release yet. I accept that there might be firmware bugs that need to be shaken out, and to me it makes sense to share experiences here.
EDIT: here on the forum somewhere ... not necessarily in this thread :)
-
@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.
-
@andyhornblower said in Anyma Phi - shift to the alternative version of the matrix:
is there still an "early adopters" section
There is, but it's not terribly interesting. Two threads. One feature request (now implemented) and a thread titled "My very first Anyma Phi track !". Last update June 23rd.
-
@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 :)
