Anyma Phi v1.0 public beta
-
I've just uploaded v1.0b276 (links in the top post of this topic), with two new effects and two new modulator groups.
Here's what's new:
- Added a Bitcrusher effect (Timbre group) with continuous bit depth and sample rate reduction.
- Added a Ping-pong delay effect (Delay group), together with a sync variant.
- Added an Algorithmic modulator group, providing algorithm-based utilities to generate sequences:
- The Euclidean sequencer generates a large variety of rhythms whose beats are as evenly spaced as possible.
- The Hexadecimal sequencer generates a sequence based on the binary representation of a 32-bit hexadecimal number, with each of its 8 digits controllable individually.
- Added a Physics modulator group, providing physical models and simulations:
- Bouncing ball simulates the movement of a ball thrown in the air and bouncing over a hard surface.
- Ball impact simulates up to 8 independent bouncing balls thrown in the air and bouncing over a hard surface, and outputs their velocity where there are impacts, making it more suitable for modulating the expression of percussive oscillators.
- Spring-damper system simulates a mass attached to the input with a damped spring, making a "springy" or "bouncy" version of the input.
If no new bug surfaces before the end of the week, this will be the last beta version, meaning that the v1.0 release is imminent.
After the release, we will focus mostly on improving the documentation, tutorials and feature demos for a time. -
Thank you very much for the quick response - all the new features work perfectly - now Anyma's capabilities are comparable to the much more expensive NordModular
-
@join said in Anyma Phi v1.0 public beta:
What is the problem with the editor on Windows 8.1? Does the editor stay blank?
The computer seems to correctly identify the Anyma. At the start screen of the editor, I can select between 'AnymaPhi' as well as MIDI2 and MIDI3 ports (also associated with the Anyma) for in/out connection. I choose 'AnymaPhi' for both, as instructed. When I click on 'Connect', however, nothing happens.
Might be a driver issue?
-
If nothing happens when you click "Connect", it means the editor couldn't even open the MIDI ports. This generally means the ports are already open by some other application or driver, because Windows doesn't allow a MIDI port to be used by more than one application at a time.
-
@join said in Anyma Phi v1.0 public beta:
... because Windows doesn't allow a MIDI port to be used by more than one application at a time.
Slight correction: it's not that Windows doesn't allow this, instead the class compliant drivers included in Windows do not have multi-client capability. If you connect anymaphi to a multi-client capable midi interface (iconnectivity Mio10 or Mioxl, or rme), then more than 1 app /program can access the device at the same time.
I do this all the time. -
Didn't know that, thanks!
-
@join said in Anyma Phi v1.0 public beta:
If nothing happens when you click "Connect", it means the editor couldn't even open the MIDI ports. This generally means the ports are already open by some other application or driver, because Windows doesn't allow a MIDI port to be used by more than one application at a time.
Thanks a lot! This may solve other connection problems between my gear and laptop!
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.
-
This post is deleted! -
@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.
-
@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 Les noms courts des paramètres de la matrice sont parfois "grisés" (et un peu illisibles) pour indiquer qu'ils n'ont aucun effet pour le moment. Ca dépendra donc du patch sur lequel tu es. Pas de panique, le prochain item sur notre liste à la sortie de la v1.0 sont les documents/vidéos tuto/démo !
R&D Engineer at Aodyo / Ingénieur R&D chez Aodyo
-
@join Merci infiniment, je me sent tellement bête ^^ je pensais que c'était par ce que j'avais incorrectement installé la MAJ, mais c'est vous dire à quel point je suis dépassé et heureux d'avoir un exemple de création de patch, encore merci .
-
Hi, I think I found a minor bug in the Expression curve in the last beta version. When using a CC with any controller, the synth uses the CC value as velocity value (ok great that's normal)... unless the CC value is stable (no matter what the CC value is). If the CC value is stable, it uses the velocity value of the next note instead of keeping that CC as reference point. I had not noticed this behavior in previous versions. It is annoying with a modwheel for any value and even with the Touché if the value reach 127. Other than that keep the great work going! Amazing improvements!
-
I have the same problem - sometimes even when using an external arpegiator (it does not do this for all patches so it is maybe that it is a feature of the resonator when the feedback amplified weaker signals)
-
The Anyma tries to be smart when detecting whether the Expression CC is present or not (because that determines whether it uses or bypasses the Velocity Envelope), but doing so it expects the expression signal to be sent almost continuously. This is fine when using a wind controller, but not in your case.
I think it could be better to allow you to force whether the Expression CC is used or not, for instance with an option in the settings.
Or at least to set the "timeout"; i.e., the time after which the synth considers there isn't an expression signal anymore if it didn't receive any.
Would something like that be OK to you? -
@join I see. Indeed, it makes sense for wind controllers. An option where we can force the usage of the CC or the velocity would be great. Maybe something at the level of each patch instead of something global? Depending if the patch is intended to be played with continuous expression or with velocity?
-
This is just amazing. Thank you
-
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:
- Never means the expression CC will be ignored, and the velocity envelope will always be used instead.
- Values 100ms to 20s mean that at the moment an expression CC is received, it will be used instead of the velocity envelope, but once the specified delay has passed and no further expression CC is received, it will revert to the velocity envelope until another expression CC is received.
- Prg.Chg. means the expression CC will be used from the moment it is received, but when switching to another patch the synth will revert to using the velocity envelope by default, until another expression CC is received.
R&D Engineer at Aodyo / Ingénieur R&D chez Aodyo
-
Hi, im new to anima phi and updated to the last beta first.
I wanted to make a bass drum with fast pitchdown on start to get a click noise. So i attached a sdsr to pitch but it does no controllable pitchdown. I tried to assign an lfo and this works, what am i doing wrong or is it a bug?
Thanks for your Answers -
@josie The envelopes are unipolar, meaning that their output signal will be between 0 and 100%. If you just map the envelope output to pitch and don't change anything, the amount of the mapping will be +100%, meaning it will add the envelope to the pitch. So you would need to set the amount to -100% to remove the desired amount to the pitch.
I guess it worked with an LFO because LFOs are bipolar (their output signal varies between -100% and 100%), so even with a +100% mapping amount, the LFO would lower the pitch when in the negative part of its waveform.
-
@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:
- Never means the expression CC will be ignored, and the velocity envelope will always be used instead.
- Values 100ms to 20s mean that at the moment an expression CC is received, it will be used instead of the velocity envelope, but once the specified delay has passed and no further expression CC is received, it will revert to the velocity envelope until another expression CC is received.
- Prg.Chg. means the expression CC will be used from the moment it is received, but when switching to another patch the synth will revert to using the velocity envelope by default, until another expression CC is received.
Sounds perfect!
-
@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.
-
@join
Thanks for your Answer,
I found the problem,
I used arturia keystep in arpeggio mode with hold on.
I think the envelope didn not trigger .
If i turn off hold and arpeggio and use normal keyboard mode manually , it triggers the adsr envelope and so the pitch movement. -
Is there a setting to switch off the temporal zoom on the parameter values while changing them with the knobs? I find this feature rather inconvenient and would prefer the previous non-zooming version.
Similar for selecting patches. While the automated zoom out to the patch table might be useful, the loading of the 'selected' patch as soon as I stop turning the knob is far too quick. Here I would rather prefer to confirm the selected patch manually, e.g. by pressing the right arrow button.
Other opinions on these?
Thanks a lot
-
@deepsea You can disable the "Large type" option in the setting. As for patch selection, a manual confirm could be added as an option in future updates.
-
@join
Great, thanks for help. Found the 'large type' setting also described in the manual.And thanks for consideration of the other point.
Best wishes
-
@join GG et merci à tout ceux qui participent à ce projet ;)
