@Peter-Ostry said in Dual Sylphyo Setup:

Each time a player switches on his/her Sylphyo, it should connect to the same Link=Synth.

Yes, good point. That's the way it should be ...

@Laurent_AODYO said in Dual Sylphyo Setup:

I would have used Sylphyos on my side.

From my (American English) perspective, I'm liking "Sylphyo" as the plural of "Sylphyo". That would make it a linguistic "invariant" (or "invariable") like "fish" and "aircraft". To my eyes / ears, "Sylphyos" is a bit clumsy.

@Laurent_AODYO Thanks for the info ... that clears things up.

So it sounds like the warm standby setup would be two Sylphyo ... (what is the plural of Sylphyo ... Sylphyos? Sylphyo? Sylphyae?) ... two Sylphyo and two Links with a MIDI-merge downstream of the Links. This would provide as hot a standby as I would like. It also opens possibilities with potentially other players, students, and prospective purchasers (except for sanitization issues ... hmmm ... another topic).

One more question:

I am guessing a Link only remembers one pairing connection? Unlike other devices I have that remember some (small) number of paired devices and recognize whichever ones are in the vicinity ...

I am wondering what the setup would be for two Sylphyo instruments. Assuming both are paired with Link units:

• Does each Sylphyo and each Link need to be on separate channels?

• If they happened to pair on the same channel, what would be the symptoms? I imagine this could happen if I had to re-pair "under the gun" (i.e. at a performance) and they wound up on the same channel.

• Might there be a way to configure a Sylphyo / Link pair to use a specific channel?

Alternately, if I wanted to use a second Sylphyo as a "warm standby" (powered off, but ready to be turned on ...), I would like both the main and standby Sylphyo to be configured to talk to the same Link unit ... is that possible? Only one would be powered on at a time ...

I do find myself drawn mostly to the LUB (Less Updates are Better) camp, so @Peter-Ostry pretty much said it.

I had a well-meaning update by a developer of a hardware unit of mine cripple the unit for me (possibly irrevocably) and it is now out of my rig and garnering dust. Sad. Frustrating. Expensive. Such a fate cannot happen with the Sylphyo or I'll be totally SNAFU.

That said, critical bugs that prevent use or cause crashes need updates. Also, I would welcome additional fingerings, which are unlikely to disturb existing users.

For me, the question is more what we can do as a community to enhance the instrument. This forum does feel a bit thin compared with other vibrant message boards. Some things that come to mind ...

• Suggestions / experiences with cleaning
• Has anyone experienced the issues with salt on their fingers causing fingering issues.
• Experience interfacing with units X, Y, and Z.
• Experience with various settings and why you use them.
• Playing videos, educational videos, getting started videos.
• Routing possibilities with the Link (its a real goldmine, I have found).
• Latency discussions
• Rig setups
• What happens when the battery wears out

... and on and on and on.

I'm guessing that prospective purchasers visit this forum to check out the community activity and enthusiasm. If they see a thin message board, they may be turned off ...

@join Among the many forums I frequent, the system by Discourse.org does seem to me to be the best. It uses trust levels mete out posting capabilities to members based on the reactions of other members to their posts (which are initially very limited).

This is used by the Cantabile group, which is a single-developer project with a large and loyal following. The community provides almost all the user support, courtesy of its most experienced users / participants. Assistance from the developer regarding real issues is only occasional, and only in the most dire problems.

I believe that building a robust user community is a major component to a successful and long-lived product, and the forum software I think is a big part of that.

@peter-ostry I suspect that Robkoo is targeting seniors - folks with a history of playing wind instruments, but can no longer deal with the weight or the embouchure and mechanical issues of a physical instrument. At least that is the suggestion of Calvin Chong, the primary English-language demonstrator and commentator of the R1 on YouTube. It's worth a look at his (so far) three excellent videos on the instrument.

For the senior market, this might be an ideal instrument. As it has worked out, the workshops we host for Native American flute players largely attract an older crowd (avg age 63), probably because the instrument is very light and requires the same breath pressures as talking and novice singing (we did a full-blown study on intra-oral breath pressures across a wide range of ethnic wind instruments). Many of these folks are overjoyed at the opportunity to be musically creative without many of the physical challenges of more mainstream instruments.

Personally I think that the Sylphyo is also ideal for this elder-musician audience, albeit at a higher cost.

The latency of the R1 likely stems largely from the BLE link, which I have seen quoted as having typical latencies of 10-20 msec. (That quote also implies a 10msec jitter, which I think would be even worse than the latency).

@fanch35 From what I understand, the Sylphyo does not have the processing power to do the kind of sound generation that Respiro achieves. I recall that Johnathan commented once (somewhat off the cuff) that a CPU with 10x the processing power would be needed ...

@fanch35 Yes, typically when I plug in an audio interface on a USB port to my laptop or desktop and install the drivers, then the available audio channels - input and output - of the audio interface will shop up alongside the pre-configured audio channels in Windows. (I think that is what you are asking).

Full disclosure: I do not use a Focusrite interface. It is a popular unit that I found a nice picture for the diagram ... I typically use RME interfaces - Babyface and UCX, specifically.

@jjaylds At this point, fingerings can only be added / modified by Aodyo and distributed in a firmware update. The ability for users to add / modify fingerings has been requested and discussed, but there has been no action so far (that we know of).