• When importing a patch, it seems necessary to manually select a new empty patch slot,. Otherwise the current slot will be overwritten. Please make the import command automatically load into a new empty slot.
Good point. Import Patch has now been added to the context menu for each patch slot, so you can say where to put it. That works for me, but maybe it should now also be taken off the File menu, so you have to specify where you want it to go.
@Clint Thanks for all the very detailed analyses you made. As soon as I get a sizeable chunk of free time, I intend to carefully read them all from the beginning and contribute tests that can help us understand what's going on and get to the bottom of this.
@steviek Nobody else of Aodyo can comment on this particular issue, unfortunately, but we're reading everything posted. It's just that I can only do one thing at a time, and such a question deserves proper treatment and will take time to answer. Sorry that we've not been very good for giving a sense of where we are and where we are heading to. I hope we'll be able to communicate a bit more often from this point on.
We have a few new things for a new Sylphyo update but couldn't yet find the time to finalize them. This post offers a bit more perspective on what's been going on for us in 2021.
While I'm sure 2022 comes with its own set of challenges, the wrap-up of the v1.0 of the Anyma Phi will likely free us some time.
The last public version (v0.8.107) offers a set of MIDI routing options (in the Routing submenu of the MIDI section), including DIN Thru.
When this option is enabled, everything on the DIN MIDI input port will be copied as-is to the DIN MIDI output port, with the lowest latency possible.
However, as this could result in MIDI messages being interleaved if several things merge onto the DIN MIDI output, the v1.0 beta offers an additional Safe merge option that ensures all MIDI messages are output without any possible garbling/interleaving.
I am wondering if anyone has looked into the suggestion of @vincent (earlier in this thread) that
it was not moisture as such, the problem, but salt one.
I have had one situation where I started getting erratic notes. I swabbed down my fingers and all the finger pads on the Sylphyo with a slightly damp cloth. It worked immediately and completely to resolve the erratic behavior. However, since it was only a single test, I have not reported it before.
In other cases of erratic notes - they only happen when I first turn on the Sylphyo and I usually just "wiggle my fingers" for maybe 5-10 seconds and the erratic notes disappear and never return during play.
Would love to hear if other have experimented with this ... as @vincent points out, erratic notes could be a real show-stopper ...
@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.
You will hear the selected internal sounds of the Sylphyo. If you want to hear sounds from the DAW, connect headphones to your device on which the DAW is running. See Midi Routing in the User Manual. See also "Rig Schematics" here on the forum.
Just released the Chill Nite album from this concert – free for streaming and download at ClintGoss.Bandcamp.com.
I played the first five tracks live over a sparse nature soundscape. I played the last three tracks live, supported by the recorded music of my mentor, David Darling, pianist Alexander Nakarada, and the drone sounds of a particular species of “drumming fish”.
Virtual versions of real-world instruments include Native American flutes, clarinet, oboe, cello, mandolin, tubular bells, chimes, Armenian duduk, bansuri, and silver flute. I also played virtual-only instruments: Heaven Bells, Respiro (Desert Wind), EVI-NER, Marble, and Matt Traum’s IndiaFlute and Beauty.
@tsukaï-ban Comme l'a dit @bibenu, une recalibration pourrait améliorer les choses. D'ailleurs, si vous pouviez noter les valeurs qui étaient présentes dans l'écran de calibration, ça me serait bien utile ! Merci.
@support_aodyo yes, the pearl edition really looks cool...It has that kind of a 'classic instrument' touch.
But I wonder if there might be any drawbacks compared to the standard model? According to the manual the keybend feature seems to be not yet introduced for the pearl edition. And as there seem to be cutouts in the housing for the pearl pads what about dust and liquids entering the housing?
If a note Off is delayed, then there is a moment that two notes are ON. This might cause a mini legato / glide in Respiro.
If the Respiro note transition is set to Synth mode then you will have less pops versus when you use the Real mode.
I would need to dig into the Sylphyo to understand the way it deals with key glitches. But typically when using certain fingering transitions, glitches can occurs due to the changing keystroke (not all fingers in sync). I think this is why the Key / Reaction time parameter exist. Typically keystrokes less than 20ms are glitches. Therefore setting this value to 1ms will probably not filter glitches keystrokes and provide a more snappy response to your fingering BUT it demands that you master your fingering technique...Respiro is responding super fast to note changes and a glitch note during playing can result in a create a pop.
With other words, if you set the reaction time to 1ms, then I would advice Respiro in Synth Mode and increase the value till pops are gone...
Yeah, these are good solutions too. Many times during design I've pondered whether to do solution 2, but I wouldn't because it is sort of complicated to pull off right… but now that we're seeing that mitigating the downsides of the simplest way (sequential evaluation) could be complicated too, maybe it's worth a shot after all.
I'll think about it. Don't hesitate to shoot ideas, I won't hesitate to steal them :).
edit: Evaluating mappings in the reverse order could maybe also work with minimal effort. For modulators, an evaluation in the correct order is better, but there will be cases where you want to add something in the middle of a series of transformations, and the problem will show up again.
@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.