It is amazing how a thriving on-line community can self-support a user community and help a product to grow.

I am an active member of many communities using different discussion systems, and the difference between those that function smoothly and those that creak along is striking.

The best systems seem to be those that are based on trust levels (new users earn trust by posts that get positive response and get correspondingly more capabilities). They seem to create communities where the users (happily) support the product, essentially freeing the developers of most of the support work.

Not sure where NodeBB stands in capabilities, but it might not be up to the task. I have had very (very) good experience with Discourse (https://www.discourse.org/), which is used to run the Cantabile forum, an outstanding user community ...

@Friedus My personal belief is that "really good internal sound" needs a really good (i.e. reasonably current) CPU, fast memory, and all the things that support that (power, bus architecture, etc.) After being "pretty" happy with the results from the VL70-m for almost 2 years, I jumped into the Audio Modelling / SWAM sound engine a few months ago and left the VL70 gathering dust. That's for the real-world emulation camp.

For the virtual, more "out there" sounds, there's the Lyrihorn, Respiro, EVI-NER type plugins, which may require somewhat less "oomph", but still (I'm guessing) far more than the CPU power of the Sylphyo.

Cramming a SWAM engine inside the Sylphyo would be ideal, except that it is likely impossible (unless we're talking NASA-sized budgets).

That said, I think the Sylphyo internal sounds are great for a backup, and I even recorded a production track (and sometimes play live) with the SynthBrass sound. I always maintain a low-tech signal path from the Link audio out to my output system that requires no laptop support to access - easy switch-over in case of a Wintel crash.

@reidid789 A tool for configuration of the Sylphyo would be great, and it has been suggested and discussed before. (I can't immediately locate the discussion).

I think the issue is that sending any data upstream to the Sylphyo would be a big development project in the firmware ...

@wwoodard8 said in Double note:

Yes, dynamic.

Excellent that re-pairing the Sylphyo with the Link works!

I did want to comment on the use of the "Dynamic" setting for [MIDI Mapping] / [Velocity] parameter. This is off-topic for this thread, but important info, I think ...

In my experience, which matches the advice of Aodyo (in particular Laurent Pouillard from March 15, 2019) ... the Dynamic setting introduces unnecessary latency. The amount of latency is configurable (the [Capture delay] parameter) and defaults to 20msec (and 20msec is very very noticeable to me).

If you are using a sound rendering component (VST, hardware synth, soft synth) that was designed for a keyboard, it will likely rely on the transmitted Velocity value sent with each MIDI Note On message. However, if you are your sound rendering component was designed for a breath controller or wind synth (e.g. the Yamaha VL70-m hardware unit, the SWAM modelling engine, the Respiro VST, the Suonopuro sample libraries, a DynaSample module (XpressO, Xpression, XO-Mini) ... these components rely on MIDI CC messages - typically CC#2 (Breath Control) or CC#11 (Expression) - that follow the MIDI Note On message. In that case I set the Velocity value to 1. I have also played with other values in a few cases where I had some synth that needed velocity - and this did not seem to bother the sound rendering components that use Breath Control.

I hope this helps!

@wwoodard8 I would, first, simply turn the Link unit off and on. That has cleared up some issues with me in the past.

Second, I would re-pair the Link with the Sylphyo. This is a typical cure (for me) in a gig setting when communications suddenly gets flakey (or stops entirely) just before the gig. This is scary, but performing a re-pair has always worked in this situation. The scenario is that I set up long beforehand, do the sound check, and all is AOK. Then, as people arrive, I am thinking that cell traffic increases dramatically and that may interfere with the Sylphyo-Link radio connection. This has happened to me maybe four or five times in two years. A re-pair operation has always cured it. I actually have a label on my Link that says "Both Buttons to Re-Pair" just to remind me.

Failing that, I would reset (i.e. Factory Reset) the Sylphyo ... AFTER writing down all your settings so that they can be restored ...

Hope this helps!

@wwoodard8 It appears to be a "Stutter" at the start of the A#3 note.

I have not experienced this on either of two Sylphyos ...

What is your setting for Velocity? Dynamic??

@wwoodard8 First time was nerve-wracking for me. Second time was a minor speed bump ... was back up in 4 minutes ...

@wwoodard8 said in Dangling Strands of Caulking:

to my proctologist

Would that profession be a Proctoewilologist?

@wwoodard8 said in Dangling Strands of Caulking:

And how did you take that photo?

It was comically tricky ... flashlight in one hand, point-and-shoot camera in the other, Sylphyo between my knees. I even had one of those Optivisor magnifying head-strap things on my head ...

I looked inside my Sylphyo "B" (not the one I returned for service) as I was about to swab it out and saw some dangling strands. With a flashlight, it appears to be caulking on the junction between two tubes. The calking is oozing out of one side and seems separated on the other and is dangling out as two strands of caulk.

Please advise what I should do ... nothing? Reach in with scissors and try to cut off the strand? Reach in with needle-nose pliers and pull off the strand? Anything else?

And is this possibly an indication of the failure of a water-tight seal between two internal tube sections??

Thanks for any suggestions / assistance ...