@join This is super excellent news !!! Day long LFOs... I've been wanting these since my 1st day with this gear... MIDI CC matrix control !!!! So great !
Well... Looking forward to the beta... of 2.0 !!!
Thank you so much for the feedback. I am new to this kind of analysis / testing, but I really want to understand how this all works to get the best control over my sound ...
Settings are provided below. Key settings I guess are:
** MIDI Mapping
Breath rate: Low (125 Hz) -- Based on the XpressO and Ingo's advice
Capture delay: 20ms
Reaction time: 20ms
Breath rate is Low / 125Hz because of the XpressO, which was choking (for a while, at least) on Medium and above.
Velocity = Dynamic because many of the VSTs I use depend on that. My VL70-m is fantastic, but I currently have a (very) hybrid rig (still in the expansion / exploration phase with my rig).
Key Feature would be a way to re-configure the Sylphyo via MIDI program changes. I could then switch settings when switching sound rendering modules or VSTs. Without that, I am really stuck with the "least common denominator" across all my sound rendering tools.
I am not sure what your term "key debounce time" is ... is it Keys / Reaction time?
I will use 15 - Cheap Tunes in the future for testing ... (that sounds the most immediate to me of the choices you suggested).
I never considered that the sound triggering mechanism might be other than MIDI. But, of course, analog synths use CV and that's a whole 'nother world ... would love to understand how this actually works on the Sylphyo!
All the settings I used for latency tests:
Clint's Configuration Settings for the Aodyo Sylphyo
Firmware version: 1.4.8
As of 11/27/2021
* MIDI Mapping
Breath: CC 2
Breath rate: Low (125 Hz) -- Based on the XpressO and Ingo's advice
...per CC: On
Delay notes if needed: On
Capture delay: 20ms
Max. velocity: 127
Slider ctrl. CC 1
Top slider ctrl. CC 12
Btm. slider ctrl. CC 13
Elevation ctrl. CC 75
Roll ctrl. CC 76
Compass ctrl. CC 77
Key-bend ctrl. CC 78
Program change >
Send Bank Off
Bank (MSB) ---
Bank (LSB) ---
Note-off delay 10ms
Octaves: 5(+2) octaves
Invert ocatves: Disabled
Left pinky: -1st: Disabled
Right pinky: +1st: Disabled
Replay same note: Disabled
Reaction time: 20ms
R.time octaves: 20ms (If [Reaction time] is 0ms, then this must be 0ms)
More sensitive: Enabled
Key-bend (BETA): PB+
Key noise (BETA): Disabled
Function: Ctrl (latch)
Top edge: Bend -
Btm. edge: Ctrl.
Edge size: 9mm
Shake to move: On
Shake vibrato: On
Elevation control: On
Range: +-35 degrees
Roll control: On
Range: +-20 degrees
Compass ctrl. (BETA): On
Range: +-20 degrees
Always on: Off
* Base Key: A3
* Output: MIDI ch. 1
* Invert Display: Off
* Receiver device: Connected CH 23
* LED: Off
Not quite a rig schematic, but a rigging schematic, somehow :-)
This is the first part of my Sylphyo interface to play with software instruments.
Originally I wanted it in Logic or Mainstage or another DAW I own, but the basically simple task went more complicated than I had expected. So I decided to make my own Sylphyo DAW in Max and enjoy the graphical possibilities.
Top left, Sylphyo MIDI comes in through moving faders and is routed by a 12x12 matrix. Horizontal top is incoming, vertical right matrix border is outgoing. Each matrix output can be scaled, slowed down (Glide) and can have a curve applied. The right side of the screenshot is the graphical live display and shows all used Sylphyo messages after processing. Breath is the filled circle, blue background is Elevation, the two lines are Roll and Compass.
The screenshot tells that the Sylphyo is blown with medium force (thin outer circle is maximum). The instrument is held down and slightly rolled to the left with a bit of left Compass. The played note is a G4 with velocity 115. All other values are also shown in several colored faders.
Have not played much yet, but it seems to work well. Not many refinements needed, just a little technical elegance is missing (you have to look at the backside of the screenshot to see that).
Click on the image to show it in original size.
Next part to do are connections and mappings to a handful of virtual instruments.
There is no audio input directly on the Sylphyo, nor Bluetooth connectivity (primarily for latency reasons), but there are a few things I can recommend you, having been doing this myself when practicing with iReal Pro and the Amazing Slow Downer.
You can play the backing track on the iPhone speakers or on Bluetooth speakers, and get an inexpensive battery-powered speaker with AUX input only (a bit hard to find, but generally all Bluetooth speakers tend to have outrageously high latency even with the AUX input).
But when I want to practice at the local park, I use a headset cable splitter, which has a male TRRS connector and a headphone and a mic female connectors at the other end.
With this, I plug:
the TRRS end into your iPhone,
your headphones or speakers into the headphone port of the splitter,
and a minijack cable connected to your Sylphyo into the mic port of the splitter.
Then, I use the Audiobus 2 app on my iPhone to monitor the mic input, so that I can hear the Sylphyo on the headphones, in addition to whatever play-along app I use.
It's not as straightforward as having a direct AUX input on the Sylphyo (which we might consider for a future version), but in practice its no big deal.
I always have my cables and headphones ready to use in my backpack, so I just have to plug the thing to my iPhone and Sylphyo, open Audiobus and my play-along with a few taps, and I'm good for hours of being the weird guy having fun blowing into a silent thing in the middle of the park :).
This is definitely not expected behavior, and to my knowledge not related to the firmware, and none of the sounds are remotely close to the CPU load that would result in audio dropouts in any situation (we aggressively test against this before releasing each sound). As Matthias is investigating the issue with you by mail and will try to determine where the problem comes from and what we can do about it, I hope you don't mind that we close this topic here.
More generally, is there a list of compatible mini keyboards anywhere on the Anyma site? I cannot find one.
On the assumption that the MPK isn't going to be able to be supported anytime soon, I would like to get an inexpensive one, but fear buying another brand that won't communicate with the synth – as there seem to be many that don't work at the moment.
@origami23 I didn't noticed something that strong but I agree it's slightly unstable in the timing.
Also something that would be great is to be able to have all the values for the pitch. I tried to set up on 5st but it's impossible. It jump from 4.9 to 5.1st. And it the case of complexes harmonics ratios, frequencies are beating in each others a lot... Would it be possible to have every single float values (by steps of 0.1)? I also tried to modify it on the synth and in the Editor and it just seems to jump from odd value to the next odd value (0.1 > 0.3 > 0.5 > 0.7 > 0.9 etc).
Thanks : your advices will be very usefull. looking at the warbl default fingering i realize that i will need to invent a new fingering to get # and b notes and this is not easy ... and may be sylphyo offers more possibility on that. Probably there is already a best choice which has been adopted by most other recorder players...(?)
The motivation is different in my case. I'd like to do sound design with the Anyma Phi as a standalone device, no keyboard (in whatever location I want, sofa, park), then when I'm done, connect a keyboard.
You can kind of hack round this using the piezo with envelope follower rise and fall as ADSR type controls, but that's not really the same thing.
@andyhornblower Thanks for your suggestion.
The issue with that, is that we designed the physical model to play well in a certain range. And while we could feasibly extend it a few semitones lower, it becomes a slippery slope, as we need to rework the physical model to include lower tones, which then prompts people to ask why we can't go even lower, etc.
I hope this makes sense, we will consider your request as much as we are able but can't promise anything to that end. Let me know if you have any further questions.
@jay-ayliff There are two ways to play the middle C in the recorder mode (assuming you are in base key of C), first with the index finger of the left hand (OxooOooo_), and second with the middle finger of left hand and the octave thumb (XxooOooo_). If your thumb is incorrectly pressing the octave key you might be accidentally playing a C instead of a B?
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.
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.
while I generally agree, Sysex and Ableton is still problematic, as in, you can only do sysex via a maxforlive device. Ableton itself has no knowledge whatsoever about sysex (when it comes to external instruments)
I'm the programmer. Once the arpeggiator is done and the current bugs are ironed out, we'll release a v1.0.
But don't get too hung up on version numbers, they're just numbers and don't mean much. What matters more is that you're satisfied with your Anyma as it is.
I'd like to support SysEx-based loading/saving/renaming of patches some day, for the reasons you describe.
We don't plan to end support of old operating systems for now. In fact, I'm fiercely opposed to that due to the waste it generates, and I hope we'll be able to continue supporting old systems (Windows 7+, OS X 10.9+) as long as we realistically can.
Any detailed info about your crashes/restarts are very welcome (descriptions, videos, specific circumstances, any reproducible steps if possible; send to email@example.com and say they're for join). Our personal Anymas don't crash, and they can run for days without freezing in any way. If yours do, this is something we need to fix. As opposed to some other "reliable" bugs, these ones tend to be nasty because they don't appear reliably, every time you do a particular thing, so it's very difficult to observe them and find where they come from. Some aren't even software bugs, but hardware defects, which makes the problem even less trivial. Hence, the more data we get, the better the chance to catch them.
I want to upload @Broken-Gadget 's patches, how do I bulk import them into the editor? Drag and Drop would be great as well!
I made a start on them, then got distracted. I'll get back to it... However, I figure if it's not a problem to have the PC/Mac editor connected at the same time as the instrument or keyboard you want to try them with, it doesn't matter much because you can import one, try it briefly, then import another, and so on.
Again, could you please show the current version with a version number?
I've been thinking it should show the version number on the update download page. Otherwise, the only way to tell for certain if it's a new one is to download it and open the zip.
I've been wondering how we'll know when there's a new release, unless we haunt this forum regularly. I don't see any way to ask for a notification, or to get notified of new threads, for example in the "anyma phi general" sub forum.
4 I seem to have lost my great patch, although it was definitely shown as saved. What happened here? (Windows)
After finding the problem with renaming, and finding the workaround for that, I've been doing the same with each patch edit, to make sure I don't lose it. I don't know if that's needed, but it seems like the best bet:
Use File->Export, so you have a backup in a single patch file
Use File->Import, to import the same patch back again - because that's currently the only way I can be sure it's saved permanently on the synth.
The philosophy seems to be that changes are only saved from the front panel of the synth (with Shift+Right arrow), which personally, I don't think fits well with using a PC/Mac based editor. I'm not sure if there are other exceptions to that, but File->Import always works.
The patch-specific internal arpeggiator (the Arp parameter of the matrix that's currently unused) is the only feature missing before we can release a v1.0 firmware. We have no release date to offer, but it's in the high priority list.