Please don't hesitate to report anything pertaining to your freezes or crashes to support@aodyo.com.
Posts made by join
-
RE: Anyma Phi - shift to the alternative version of the matrix
-
RE: Anyma Phi editor software
Please make sure you've updated your Anyma Phi to the latest version (you can find it here). There was a bug on the Windows version of the editor where the dialog boxes didn't appear, but it should be fixed with the last update.
-
RE: Maxforlive device?
At some point we would like to allow bidirectional edition of any patch parameter via NRPNs, maybe with a few accompanying SysEx messages for passing requests like getting parameter names, etc. No ETA, but that's something that we want to do, and when it's available someone will be able to make something like the M4L device you want.
-
RE: Anyma Phi v0.8.90 pre-release update
Etant données l'ampleur de la tâche et la petitesse de notre équipe, nous n'avons pas prévu de faire une version française du manuel pour le moment. Mais ça ne doit empêcher personne de proposer des traductions…
-
RE: How to map controllers to specific MIDI CC?
This is described in the "Settings" chapter (p.48). You just need to go to the Settings (press the display encoder), and to "CC mapping". There you can modify the CCs for Expression and controls A/B/C/D.
-
RE: Anyma Phi v0.8.90 pre-release update
The update is now available on the official Anyma Phi page.
-
RE: preview from editor
This is something we could decide to do at some point, but we haven't planned it yet, because there are third party tools that do this well. If there is enough demand, we might consider it.
With macOS, there is MidiKeys, and for other platforms you can use something like VMPK. Just tell the program to output on the Anyma Phi port (to send the MIDI to your Anyma Phi, not the editor) and you should be good.
-
RE: Anyma Manual
Thanks for the feedback, Christian, this is really appreciated.
We'll add some more details on all that in the upcoming version of the manual, but I can already answer the Artin part (as it will likely not make it to the manual, as you'll understand shortly).
The oscillators prefixed with "Artin" are based on the well-known family of macro-oscillators found in Mutable Instruments' Braids module, originally made by Emilie Gillet.
As per Emilie's guidelines on derivative works, we couldn't refer to Mutable Instruments or to the module names (Braids, etc.) in our distributed material, so we've prefixed all Braids-based oscillator algorithms with Artin, the name of a mathematician who discovered braid theory, so that people familiar with Braids can still have a way to look for familiar modules. -
RE: Anyma Phi : Midi trough?
At the moment, forwarding the MIDI messages received from the DIN MIDI input to the DIN MIDI output is not possible.
However, on the USB-MIDI device connection (that's normally used to connect to your computer), sending MIDI data to the second output port "DIN" will result in this data being sent through the DIN MIDI output.
We're planning more flexible MIDI routing in a future update. Don't hesitate to share details about your needs, uses, or requests here.
-
RE: Renaming Editor Patches ??
Thanks for the info @Nelson_Baboon. With your info my hypothesis is that the specific issue relates to the fact that the input system of macOS issues a "right click" when doing a right click on a mouse, trackball, or a two-finger tap on the trackpad (when the trackpad is setup for doing so), but a ctrl + "left click", which should be functionally equivalent (since it was the only way to do it in the 80's when Mac mice only had a single button), are translated as "Ctrl + left click" and not "right click". The Cocoa toolkit (and some others) handles that difference just fine and shows a context menu either way, but a few GUI toolkits (especially when they're cross-platform and the macOS version is more of an afterthought) don't. Ours, in fact, offers you both choices, but I didn't know it until the issue was reported by you guys :).
-
RE: Edit morph layer in the editor?
You can morph between matrixes in the editor too! In the "GENERAL" section of the editor (first column), the two last modules are "MTX" and "MTXalt", respectively the normal and "alternative" version of the matrix you morph to when controlling the Morph control (which is located in the "MTX" module but not in "MTXalt").
-
RE: Planned time-line
As long as the amount of user requests doesn't exceed what a human can reasonably read or comprehend, it's better that we don't offer any voting feature, because to do the feature right it's important to have an idea of why someone wants it, what's their usage context, etc. The day we're overwhelmed with requests, we'll see :)…
As for patch storage, that'd be a nice idea, but it's a service we're unable to handle for now. However, I've just allowed Anyma Phi banks and patches on the forum, so if you'd like to share patches, just create a post and drop a patch, it should upload fine, just like the patch below. Once there are more than a few patches in the forum, we might create a specific category for them.
Thanks for submitting your experiences, ideas, feature requests, and patches!
-
RE: AnimaPhi Editor Import Patches / Bank doesn't work
Merci pour tes encouragements :) !
-
That nothing happens when clicking "Import patch" or "Import bank" on Windows is a problem, it's supposed to work. While we're fixing that, you can still drag and drop patches and banks from the Windows Explorer to the Editor window and it should still work.
-
The MIDI input and output you need to select in the Editor are those that correspond to the Anyma Phi. If you want to use your keyboard while still plugged into your computer, you would need to use a program such as MidiOx (or MidiPipe on macOS) that can forward a MIDI input to another MIDI output. Or you can simply plug your MIDI keyboard directly to your Anyma Phi. The Editor is a kind of remote control for the Anyma Phi, nothing more.
-
This looks like a Windows limitation, and if so, there's nothing we can do and it's indeed infortunate. Again, something like MidiOx could help because you could duplicate the MIDI data onto two different ports.
-
-
RE: first few minutes - GREAT, but a few annoyances
@nelson_baboon USB being backwards-compatible, it won't be a problem.
-
RE: Renaming Editor Patches ??
OK, we'll fix the editor so that Ctrl+LeftClick does the same as a RightClick on Mac.
-
RE: Renaming Editor Patches ??
@bibenu OK, so when you say "right-click", you are always doing a ctrl-tap/click, right?
-
RE: Unable to get a sound on Patch 7 (Piezo Pling) on Anyma Phi and also unable to get case percussion to work
If you plug a microphone or an instrument into the LINE IN port, its sound will replace that of the internal piezo behind the case, and will be used as well in the Piezo Pling patch. Can you get any sound with this method?
-
RE: Planned time-line
You will always find the release notes in their own chapter in the manual.
New versions will pop up on the Early Adopter page, but we'll certainly also announce them here or on a newsletter.A few new patches are close to being released soon, and our sound designer is working hard on the next batch.
For modules and software features, we don't give timelines because we can't guarantee we'll finish them on time (our software development team of one can only do so much at a time). However, if there's vocal request for feature so-and-so, those'll tend to be the kind of features we'll prioritize in our to-do list.
So don't hesitate to suggest features and tell what's important to you! -
RE: first few minutes - GREAT, but a few annoyances
Sorry for the annoyances!
I can just say the security questions on the forum are very necessary, unfortunately, because we're constantly hit pretty hard with spam and bots.
And for the power cable, you can also use a USB A extension cable. -
RE: Renaming Editor Patches ??
We don't use anything special to make the context menu appear, so it shouldn't be problematic.
I certainly never had the issue (macOS Mojave, with Mac mini and MacBook Pro), but it could be something inherent to the GUI toolkit we're using.Please give me any detail that could help with the diagnostic: OS and version, where do you right-click, whether right-click works better in other zones (e.g., on a virtual knob, on a module title bar, on a scope).
Also, if it happens on other apps, which ones?
Thanks!
-
RE: Perchè AODYO non risponde?
Armando, I've sent you an email that should answer your request.
-
RE: Anyma Phi frozen at start issue
For issues like this, it's best that you send a mail to support@aodyo.com.
You will need to try again with updating until it succeeds.
On some operating systems, it's normal that the copy freezes for about a minute, but it completes eventually, and only then should you eject the
ANYMAPHI
disk. Ejecting the disk is also very important, as some operating systems wait until ejection to actually write the information on the disk.
Anyway, you can get information about what's really going on on the display of your Anyma Phi, which will show progress bars as well.If you still don't manage to update, please try with another mini-USB cable, and with another computer or operating system, and please report back to us at support@aodyo.com what you tried and what worked and didn't, with details for your computer and operating system.
-
RE: Anyma Phi Volume control issue
For issues like this don't hesitate to send us a mail at support@aodyo.com, we'll answer much more quickly.
The volume knob normally has a small "dead zone" at the beginning and at the end, but nothing that large.
This could be fixed by recalibrating the knob (in the settings), a possibility we're thinking of offering in a future update.
-
RE: Request; Save Sylphyo settings
A way of sending/receiving a SysEx dump of the settings could be possible in the future…
-
RE: Anyma Phi editor software
@mickglossop Normally the editor app shouldn't have any problems running from Mac OS X 10.9 up to the latest version. Please send us a mail at support@aodyo.com with details on what you're experiencing with Catalina.
-
RE: SRC2
Typically, "Source 2" would allow you to make a secondary timbre appear, on top of the main sound you're playing. For instance, it could be a sub or bass (like in Resozen or Muta Flutes), or some harmonics or differently timbred sound that adds to the sound (like in Laraaji +)…
The name "Source 2" is deliberately generic because what's best as a secondary sound source is really different for each patch, as with "FX 1" and "FX 2".
-
RE: Discovering Anyma... 1st impressions
Thanks for your feedback! On the MIDI front, what kind of info do you think is missing? We might add some additional (fixed) ways to edit the patch using NRPNs and other CCs (esp. for controlling the matrix) on a specific channel, so any clarification on how you'd use that is welcome.
-
RE: Feature Request: Turning PC out off.
@peter-ostry Yes, we will add the option to block the Sylphyo/Link from sending Program Change messages in a future update. We cannot commit on a time frame for this feature, but we'll get in touch as soon as a beta version with your feature is available.
-
RE: rock plus roll on CC76?
Apologies in advance if I've misunderstood something or say something inaccurate, this is straight off the top of my head.
The angles the Sylphyo outputs come almost straight from its inertial measurement unit (IMU), with some postprocessing related to smoothing the response and correcting discontinuities where possible. That's probably why Ian gets the same kind of outputs with his own accelerometer.
Now, I guess the crux of the matter is the way we usually describe the orientation of the IMU, which is by giving three angles, one for each of the three axes (Euler angles), as if we applied successively a rotation around each axis from a given starting position.
It's a very useful way of describing a rotation, because it's very easy to map an angle to a particular physical movement, but it's unable to guarantee that the three angles stay independent at all times due to a problem called gimbal lock, which leads to some angles evolving in the same way despite applying a rotation to a single axis in particular situations, and other interdependencies like the one you've labelled "yaw" (which, by the way, would be really nice to exploit, even if it's really more of a side effect than an intentional feature!).
Depending on the order of the axes you choose, the lock happens in different conditions, and it's been a long time since we've done the movement system of the Sylphyo, but I think at the time I tried all the possible orders and went with the one that was the most conducive to being easily used in a Sylphyo performance.By the way, due to this problem, the Sylphyo first offered only two angles (elevation and roll), and we later added the third (compass) due to popular demand, but as a "beta" feature, because the gimbal lock becomes really obvious when manipulating all three angles. Another reason for the "beta" status of the compass angle is that it's tied to our IMU's magnetometer, which has the bad habit of taking a long time to calibrate, and once done the compass angle might seem to "jump" in place. It's a common problem with IMU's, and it's also why your phone sometimes has trouble reporting your orientation correctly when you're using a GPS app.
Now, there's a way to escape the gimbal lock, which is representing rotations with quaternions, and fortunately our IMU is able to output quaternions. With this and a handful of formulas, it's possible to reconstruct a correct set of rotation angles, and it's clearly one of the next big things we would like to do in the movement area.
I tried doing so before we released Syphyo firmware version 1, but I was unsuccessful and we didn't have time for another try.
I will, at some point, but as people did get used to the angles as we have them, maybe we'll have to support both ways of representing things and let the users choose.
As for separating yaw and roll altogether, well that might need even more work :), but maybe switching to a quaternion representation first will help. Anyway, we'll see when we're at that point.There's also a ton of other things we could derive from the IMU data, but this requires a good amount of research and development to get done right. In the past I've experimented with some movements like "elbow shakes" (using either hand to swing the bell to the left or to the right), but it didn't really prove very easy to perform :). Any good idea is up for discussion :).
@ijfritz, if you have any technical question you'd like answered, please contact me directly next time. Pedro did speak to me about this, but didn't really give any detail. As we're still deep into the Anyma Phi release, I don't often sweep through the customer support mail myself, and I don't visit the forum very often either, so I just saw your link to the video here. Pedro will call me at the end of the week to talk about your discovery.
-
RE: Bug depuis dernière mise à jour
Pouvez-vous nous en dire plus sur le comportement erratique de votre Sylphyo ? Notamment, quels sont les réglages de réactivité des touches avec lesquels le comportement est erratique, et est-ce qu'un changement de ces réglages résout le problème ? Merci.
-
RE: Link jitter/latency
The Link uses the same frequency band as WiFi, Bluetooth, and other consumer electronics devices. It might be that your WiFi router and your Sylphyo/Link are trying to compete for the same channel, in which case the loudest wins (certainly your router). To improve things, you might want to try to pair your Sylphyo and Link again, so that they will settle on another channel. Unfortunately, the Sylphyo and Link cannot "see" the busy channels in the frequency band, so they settle on a channel if they manage to communicate successfully during the pairing process. You might need to try a few times before finding a channel far enough from your WiFi router.
-
RE: Octave issues
You might want to try the following beta version:
- for Windows: https://downloads.aodyo.com/sylphyo/beta/sylphyo-windows-1.4.8b10.exe
- for Mac: https://downloads.aodyo.com/sylphyo/beta/sylphyo-osx-1.4.8b10.zip
I added a "More sensitive" option in the Keys section of the settings menu. Once enabled, the octave keys should respond a bit differently, in such a way that it's pretty impossible to reproduce the issue observed in this thread with my Sylphyo.
You'll also find a parameter called "R.time octaves" that allows you to increase the reaction time when passing from an octave to another, which should help masking the undesired passing notes, for instance when switching from the high C to the low D of the next octave with the Sax fingering.Let me know how it works for you.
-
RE: Octave issues
It could arise if you use a light touch and move slowly on the octave keys, but it depends on the player and some Sylphyo are more forgiving than others. Generally it's recommended to push your thumb a bit more and move a bit faster, which effectively could require a bit of training. With the Sylphyo I have on hand, the issue (spurious note stuck) is apparent with an exaggeratedly slow thumb movement when I set the 5+2 mode, or better, a fingering where the thumb can change the note, like Recorder. Maxence can't reproduce the issue on his Sylphyo. @ijfritz If you don't mind, may I send you an email to discuss your issues in more detail and figure out something to mitigate it?
-
RE: Sylphyo Font Folio
I LOVE this project, huge thanks to you Clint!
I like that the font could display "don't care", "half-hole" and "trill" alternatives. However, I share your concern about how easy it would be to sight-read the fingerings with the "don't care" symbols on it. Maybe something like a dot inside the circle would make it easier?
Also, I'm not an font expert, but I'm wondering whether it would be possible to offer any possible combination of fingerings, limited to open and closed states, which would amount to 512 different characters. This could help facilitate discussions over future fingerings and changes over existing ones by providing a way to quickly create fingering charts. This would also be beneficial for fingerings that offer many alternatives for a single note, such as the EWI.
In the same vein, would it be possible to compose a fingering using a succession of Unicode code points? I'm thinking about fonts like FF Chartwell that cleverly interpret characters so as to layout a drawing. Again, not a font expert, but I imagine it isn't that simple, and maybe limited to formats like OpenType? -
RE: Support for high-resolution MIDI?
Chiming in a bit late…
Breath control resolution is somewhat of a tricky subject. It's very easy to assume that a 7-bit MIDI signal isn't enough, but often I've found the problem lies in the perceptual mismatch between the breath signal produced by the performer and the perceived sound intensity of a sound produced by a synth.
Because we're very sensitive to that "jitter" between "no sound" and "a very faint sound", the synth should ideally increase volume/intensity veeeery gradually in the very low range (when the CC is 0, 1, 2, etc.), even if the curve can be steeper after that.
Having more extreme curves on the Sylphyo side would be a good idea (even regardless of this particular issue), but I don't think it would really help mask the perceived discontinuity in the very low range in most cases: if the sound is too loud at CC value 1 compared to CC value 0 (silence), then it's not good.
A 14-bit signal would help a little in this case, but I'm not sure it would be practical anyway because you would need a tremendous amount of accuracy to produce a smooth signal using the breath. And it could also bring in the timing issues Laurent talked about.The synth will be smoothing your breath signal regardless of its resolution, and it'll do it at least over 32 bits, so it'll create the intermediate values your 7-bit or 14-bit signal lacks. The real question is how the synth smooths the signal: is it a good tradeoff between no perceived discontinuities and reactivity?
To me, the solution indeed lies in the volume curve, as Clint proposed. We're very sensitive to the difference between CC values 0 and 1, but I've yet to come across people complaining that there isn't enough steps between CC values 80 and 81. Bending the synth's volume/brightness curves to our perceptual expectations is more likely to bring about the desired results, in my opinion.
Have you found a good solution for this?
If not, you could try using some kind of program (like Max from Cycling 74) to produce the MIDI data needed to play the synth at a desired breath CC level, and check whether you hear a large discontinuity between 0 and 1.
If you do, then there should be some curve bending work to do on the synth side. If not, then we could try adding some new, more extreme curves on the Sylphyo side and see if it solves the issue. -
RE: Flying with Sylphyo
I've also had my share of "what's that thing" and improvised 30-second demos for airport security officers :), but I never had any issue, be it with our without a case. As it contains a battery, you need to take it in cabin.
I also fly with some of our weirdest electronics prototypes without their enclosure and with wires everywhere, but it hasn't raised any concern so far. -
RE: EVI and EWI Alternate Fingerings
Great work!
You're both right, in that generally the Sylphyo fingerings are described by a set of fingering-to-note mappings (fingerings being encoded as a series of closed/open/don't-care choices for each key), but in the case of the EVI and EWI fingerings they're actually generated based on the rules described in the manual, so there's no "unassigned" position (that would have resulted in continuing with the most recent pitch, as Clint correctly guessed).
A few technical details might be useful here. The Sylphyo firmware represents a fingering as a table of 512 entries containing relative pitch values. Each of the 512 entries corresponds to a finger position, with 512 = 2^9, as there are 8 keys plus whether an octave key is pressed or not. The tables are generated from YAML files, such as the ones Clint is working on (huge thanks!) for upcoming fingerings, that list finger positions (and includes a "don't care" state in addition to open and closed for each key) and their corresponding pitch. These files are later processed with a set of Python scripts that allow me to generate the data for the Sylphyo firmware, as well as check whether there's any error, missing position, or double assignment if needed.
Some years ago I've had a brief stint during which I tried making transpositionally-invariant fingerings based on intervals like major and minor thirds, and on this occasion I've enhanced the scripts with tools such as Hamming distance computation in order to be able to suggest optimal finger positions for a given melody, or to find what would be the best "standard" finger positions for these new fingerings. As I was soon hit with more urgent things to do I haven't gone further on this, but maybe I can share a few insights (or maybe small pieces of code?) with you guys if it can help.This kind of work is obviously very interesting too for people with disabilities, maybe as a starting point. In the past two years we've been working with a former trumpet teacher on a one-handed adaptation of the EVI fingering (currently not available to the general public), and one of the lessons was that generic solutions only go so far.
-
RE: Le piège du pouce qui déborde avant d’arriver sur le bord haut du slider
C'est une idée intéressante et ça serait en effet bien pratique. En gros, il faudrait que si le pouce arrive sur une zone ignorée, on puisse contrôler le bord haut quand le pouce se déplace dessus, sans avoir à lever le pouce, c'est ça ?
En tous cas, c'est noté et ça pourrait faire l'objet d'une amélioration dans une de nos futures mises à jour.En attendant, peut-être qu'une façon de contourner le problème pourrait être de mettre une "Taille du pouce" plus grande pour donner plus d'espace aux zones "haut" et "bas" du slider ?
-
RE: Control from Link
First of all, thanks for your support.
External control of Sylphyo settings is a very nice idea, and there would be no hardware limitation preventing this, however we would have to take some time to develop this feature as it would rely on the Link sending back real-time information to the Sylphyo (to transmit the data from the MIDI pedal/controller), and this specific use case would require many changes and testing, so we really cannot offer an ETA for this.
More generally, having the Link being able to influence the Sylphyo is something we have on our roadmap, so we're interested in supporting your use case eventually, it's just that we cannot tell when it's going to be ready.As for controlling the drone of Braveheart, assuming you just rely on the Link's audio output and not that of the Sylphyo, you can connect any MIDI controller that sends MIDI CC 1 (or whatever is configured in your Sylphyo for the slider) and use the controller instead of the slider, and it should work on the Link.
-
RE: Doigté mode MIDI "brut" (sans interprétation)
Cette fonctionnalité paraît simple, mais le diable est dans les détails… Pour que cette proposition puisse avancer, il nous faudrait un peu plus de contexte sur la façon dont cette fonctionnalité pourrait être utilisée, et la façon dont elle s'intégrerait avec le reste des réglages du Sylphyo.
- Est-ce que ça doit être vraiment un doigté ? Dans ce cas, que se passe-t-il avec le synthé interne ? Comment peut-il interpréter les touches ?
- Quelle est la finalité ? Avoir accès aux informations de touches pour qu'un programme ou un script (ou un patch Puredata ou Max) puisse utiliser ces informations et transformer tout cela en MIDI plus "raffiné" ? Dans ce cas, ne vaudrait-il pas mieux envoyer des CC ou des SysEx particuliers, vu que ça demande à peu près le même effort pour les traiter et que ça peut être envoyé en parallèle des autres informations que le Sylphyo envoie déjà, sans obliger le musicien à activer ou désactiver ce mode en fonction des besoins ?
- Ou alors, est-ce que les notes MIDI iront directement dans un synthé ou instrument virtuel sans traitement ? Dans ce cas, j'imagine que chaque utilisateur aura son idée du "mapping" idéal des touches vers les notes.
- Est-ce qu'il est également utile d'avoir des informations sur la proximité du doigt avec chaque touche ? Parce que c'est possible, mais ça implique aussi beaucoup plus de données MIDI qui circulent.
Pour pouvoir répondre à toutes ces questions, il nous serait donc très utile d'avoir le plus d'informations possible sur les contextes d'utilisation imaginés et vos besoins.
-
RE: Updates for Linux users / Mises à jour pour utilisateurs Linux
(English answer at the end)
Quelle technologie de machine virtuelle utilises-tu ?
Pendant la mise à jour, le Sylphyo et le Link changent de "personnalité" (classe USB) plusieurs fois, oscillant entre périphérique MIDI et périphérique USB HID. Cela peut poser des soucis à quelques moteurs de machine virtuelle car c'est comme si le périphérique USB représentant le Sylphyo se déconnectait et se reconnectait.
En général, nous avons toujours réussi à faire fonctionner les mises à jour dans une machine virtuelle, mais il faut dire à la machine virtuelle de connecter immédiatement tous les périphériques USB au lieu d'en laisser certains pour l'OS hôte.
Il y a ensuite des problèmes spécifiques à la version de Windows utilisée. La première fois que tout le cirque des mises à jour se déroule, Windows peut prendre un peu (voire parfois beaucoup) de temps à reconnaître les différentes "personnalités" du Sylphyo pendant la mise à jour.
La première chose que je vous conseillerais est d'essayer plusieurs fois, en faisant des redémarrages entre les tentatives, et si ça ne va toujours pas, de changer de version de Windows ou de moteur de machine virtuelle. Je réalise bien que ce n'est pas l'idéal. Des retours que nous avons eu, le peu d'utilisateurs linuxiens que nous avons s'arrangent en général avec un PC Windows ou Mac à côté pour faire les mises à jour.Tout cela n'est pas simple, et malheureusement nous n'avons pas assez de ressources pour fournir le support nécessaire pour le fonctionnement de nos outils logiciels sous Linux, car il y a trop peu d'utilisateurs intéressés.
Nous utilisons également Wine pour tester notre version Windows (cross-compilée depuis macOS avec mingw-w64), mais comme vous l'avez remarqué le support MIDI dans Wine n'est pas encore très complet (pour cela, nous utilisons aussi une machine virtuelle).Pour ce qui est de produire une version Linux native de notre utilitaire de mise à jour, le plus court chemin pour nous serait de proposer un outil en ligne de commande, mais il nous manquerait une couche MIDI fonctionnant sous Linux, ainsi qu'un pipeline de test pour Linux, mais nous sommes encore trop petits pour pouvoir pouvoir assumer ces développements en parallèle de nos priorités actuelles.
J'espère que ce post attirera de nombreux utilisateurs sous Linux, ce qui nous amènerait à remonter la priorité du support Linux dans nos priorités de développement.
Which virtual machine technology are you using?
During the update, the Sylphyo and the Link change their "personality" (USB device class) several times, switching between MIDI and USB HID device. Concretely, the switching is as if an USB device disconnected and reconnected several times during the update, and it can be problematic for some VM engines.
Up until now, we always had success with VMs, but with some we had to tell them to always connect new USB devices to the VM, not to the host OS.
Then, there are the Windows-specific problems, and they can differ depending on the Windows version. Notably, the first time the update dance occurs, Windows might take a little (sometimes a lot of) time to recognize and register the different USB "personalities" of the Sylphyo during the update.
As a first course of action, I'd recommend you to try again several times, rebooting the VM and/or the host in-between attemps. If it still doesn't work, it might be useful to try with a different version of Windows, or a different VM engine. I know it's far from ideal, but from what we've been told, the few Linux users we had generally managed to use a Windows PC or a Mac to run the updates.That's far from simple, and unfortunately we don't have enough resources to provide the level of support necessary to make our software tools work on Linux, because there simply aren't enough interested users.
We also use Wine to test our Windows version (cross-compiled in macOS using mingw-w64), but as you've noticed, MIDI support isn't that great on Wine (that's why we also use VMs for our tests).As for making a native Linux version of the update tools, the shortest path for us would be to offer a command-line tool, but we're missing a Linux-compatible MIDI layer, as well as a Linux test pipeline. Unfortunately, we're too resource-constrained to be able to develop this while continuing to pursue our current priorities.
My hope is that this post will allow many Linux users to be heard, and if so, we could increase the priority of Linux support in our roadmap.
-
RE: Importer les sons du sylphyo Bench dans le link et le sylphyo.
Pour l'instant les sons du Sylphyo Bench ne sont pas disponibles comme sons internes dans le Sylphyo et le Link, mais nous pouvons réfléchir à cette possibilité à l'avenir.
-
RE: Link power supply
The Link is powered by USB (5V and a few hundred mA), so you won't be able to plug it to the Ojai (which issues 9V). However, being USB means you can power it using any available USB port you have: on a computer, on a USB hub, on a USB charger, etc.
Le Link est alimenté par USB (5V et quelques centaines de mA), donc il ne sera pas possible d'alimenter le Link avec le boîtier Ojai (qui sort du 9V). Par contre, vous pouvez le brancher sur n'importe quel port USB : sur un ordinateur, un hub USB, un chargeur USB, etc.
-
RE: vibratto again sorry
In the latest release we've been doing some of the groundwork to make the finger vibrato possible in the future. Not everything is ready for it, but we've been making progress in that direction.
-
RE: New here Part 2
Yes, it's always good to share knowledge!
Don't set your expectations too high! This is not an acoustic instrument, and the academic and technical understanding of what makes the sound of an instrument so unique to its performer is nowhere near complete. So it won't be at the level of a sax, but we feel the Sylphyo still has something special in this regard and we're working towards making our internal sounds even more unique and versatile. Certainly, we're already amazed when we see other artists appropriate some of our sounds and make them sound veeery different just because they are different persons. It also depends on the sounds, some are more "fixed" and others are designed to be more "versatile". Personally, I find that it's very easy with the Sylphyo to incorporate the different ways to articulate and modulate sound into my playing (vibratos, tonguing techniques, bends, etc.). And if you pair the many expressive controls of the Sylphyo with an awesome physical modelling synth like Respiro, well, that's a killer match!
As for the fingerings, if you come from the saxophone, you'll find that there'll be a period of learning to compensate for the missing keys. It's something we want to address (e.g., making a B flat by half-fingering the B key or by fingering the B key and half-fingering the A key as you suggested; or having alternatives for the palm keys) but we're not there yet (we're very open to discuss the fingerings with users). If you have experience with other wind instruments you might want to try the different adaptations we made for their fingerings, and select the one you're the most familiar with.
We don't have many Linux users, and we don't officially support Linux as a platform (it might be a problem for applying updates, though they work great in a Windows VM), but the Sylphyo and Link are USB-MIDI class compliant so everything will work great with your existing stuff. Please feel free to report on your experiences with Linux!
-
RE: Bord bas du slider : Portamento (contrôle le temps de transition continue entre deux notes)
Pour annuler le glide, on peut toucher le bord bas du slider avec le pouce, remonter le pouce un petit peu et le redescendre jusqu'à dépasser le bord du slider. L'important est de commencer le mouvement depuis le bord bas du slider, pas depuis un autre endroit.
-
RE: Hello dear Aodyo Team, I am waiting now for years for a mouthpiece for the Sylphyo. Is there any chance to get one in the near future ?
What did you hope to use the mouthpiece for? The Sylphyo has evolved a lot in two years. Have you tried shake vibrato and doing pitch-bends using the slider?
-
RE: Hello dear Aodyo Team, I am waiting now for years for a mouthpiece for the Sylphyo. Is there any chance to get one in the near future ?
As our mouthpiece project is still in the research phase, it is best not to expect it in the near future, sorry. For now our development focus in on an editor for the internal sounds.
-
RE: Double MIDI note transmission with Sylphyo and Link
We have had another report of this issue but haven't had enough returns to determine if there are particular settings that aggravate or mitigate the issue. Do you have an XpressO? If so, a trace from a MIDI monitor utility demonstrating the double notes would be very helpful.
-
RE: Comment règler le Sylphyo pour avoir au moins 5 Octaves
Beaucoup de gens utilisent les 2 octaves supplémentaires, ce qui est déjà plus confortable.
Si vous souhaitez essayer une version bêta qui permet d'avoir le système qui était disponible avant (9 octaves en tout, au moins 5 si vous n'utilisez que les trois touches d'octave), n'hésitez pas à nous envoyer un petit mail à support@aodyo.com !