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

It would be good to be able to gather patches together into user-defined types, e.g. Bells, Keyboards, Percussion, etc.

Yes, that would be a massive improvement,

@andyhornblower said in Feature request - some tips:

An electric piano model would be good too.

That gets my vote.

@andyhornblower Is it possible that there is interference on the USB cable that's causing the problem ?

Reason I'm asking is that I've had some gear misbehave, even fail to boot up properly, when connected via USB. It was eventually pinned down to a noisy electrical environment. I found the problem could be avoided by either using the manufacturers supplied USB cables (Elektron) instead of random brands, or else by moving away from the area in my home with 3 computers.

Might be worth it in your case, since you're tied to your computer, to try and find cable with good shielding ?

@deepsea It worked for me alright. But I didn't make recordings and check against the migrated patches, so I couldn't say if they're absolutely 100% the same.

All the same, I'd be cautious and take a backup of the patches first.

@peter-ostry Have you updated to the 1.0 beta yet ? There are midi updates for sure, not sure of the specifics, but there was something in the manual about different settings for midi merge related to thru.

@join re "expected behaviour" yes, I can totally understand how it came about, but as you say, it's not ideal ... particularly with the change in the mapping which is away on another 'screen' you're not looking at. It's a completely unexpected change in the scenario I outlined. I thought that first note in the chord was not being detected and I started messing with keyboard connections, before I discovered the real cause.

@jls I find I can download without being logged in from the links in the post above:

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

Get it there: (v1.0b256)

Windows package (≥ Windows 7, 32 bit)
macOS package (≥ 10.9, Universal Intel & Apple Silicon)
Linux package (64 bit, limited support)
User manual (PDF)

After updating, it's important to turn your Anyma off and on twice.

I found this problem while exploring paraphonic setup. Steps to reproduce.

First, select a new patch, so OSC1 defaults to Sine. Then remove mapping 1 and follow these steps for paraphonic setup.

Then, go to OSC1 and change the type, turning the encoder all the way anti-clockwise to NONE, and then clockwise back to sine.

Result: Paraphony configuration is now broken because

• OSC1 pitch is now set to CTRLR and not CHORD1
• on the mapping for Chord1 to OSC1, the TO.PARAM used to be EXPR, but is now '?'

I found this very confusing, took a while to figure out what had happened. Easy to repair once you know, but it can make exploring different sounds in paraphonic mode a bit tedious.

EDIT: It seems that scrolling through the oscillator types without a pitch (Bow, Wind, Strike, White noise) is what causes the OSC1 pitch to reset.

EDIT 2: It seems that turning the OSC1 type to 'none' is what causes the mapping to reset.

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

make a mapping from "Chord note 1 velocity" to "OSC1 Expression", and so on for OSC2 and OSC3 (so 3 mappings, one for each oscillator).

It would be useful, when doing this manually, if the default 'amount' on a new mapping was +100%, rather than the current default, 0. I think that would be a useful default for all cases wouldn't it ? Maybe for most mappings the final 'amount' will be much closer to 0 (the current default), but defaulting it to zero means nothing is happening by default and you have to then figure out what is missing in your patch.

I must be missing something, I'm finding it hard to figure out how 'AND' would work with the TRIGC modulator .... I'm focusing on 'AND' because I'm thinking (possibly incorrectly) that these triggers are almost instantaneous, and thus will almost never occur together, so the 'AND' of two triggers would therefore (almost) never happen.

I could understand it if we were combining gates, but not for short duration triggers.

I must have misunderstood something I guess, but I'm not sure where. Also, I have no experience with modular, so maybe this is obvious in the modular world, but unfortunately, not to me right now.

I can see how 'OR' would be useful to combine two sources.

Any explanation, or example of the use of 'AND' would be welcome.