@clint Thanks for all the technical details. For your concerns, I don't think you need to be worried unless you are being particularly harsh with your headphones and the Sylphyo! People have been using the Sylphyo for almost 6 years and we have had very very few complaints about the 1/8" connector or the USB port.
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.
@steviek Hello! You need to change the buffer size in Logic Pro and Mainstage. Set it as low as possible so that you don't get any CPU overload and reduce the latency.
If you have a powerful computer you can get away with settings like 64 or even 32. If you also reduce the sampling rate (down to something like 44.1khz) that should also help with latency as you will then be able to reduce the buffer size.
@clint so far the durable SLA seems to work well, it's quite rigid and is holding up to daily practice. The 2.3mm was a bit too narrow for the sensor, it produced some held note behavior from the back-pressure with certain articulations. I think the next size up is going to be my keeper. Thank you again!
Thanks Maxence ... yes, I've got that ... but the "3" in "C3" could mean (as I've found out recently) many different things depending on the octave numbering you use. The Sylphyo (from my examining the MIDI stream it puts out) puts out MIDI hex 3C = decimal 60 for "C3" which is Middle C. That's the same standard that Kontakt, Apple Logic, Cubase, Steinberg, and Yamaha keyboards use.
However, the ISO standard that is used by Korg, Roland, and most of the piano tuning and composing world (and also the Native flute world) use "C4" for Middle C. That's why I was always off by an octave before I understood these issues.
Cakewalk Sonar actually uses C5 for Middle C, which is really confusing!
Well, I’ve tried the new firmware, and indeed it is a huge improvment. Any way I slide my thumb the octaves snap cleanly into place. Great job!
That being said, I still occassionally get the stuck notes in an actual playing situation. This means my thumb must must be coming off the pads. Clearly I need more practice. I’m used to having mechanical switches, which are very forgiving.
Still, I don’t see why your code allows a discrepancy between fingering and note output (except momentarily, of course). My code always checks and waits multiples of the reaction time until there is agreement.
A discovery I made about 40 years ago is that it works really, really well to use a longer reaction time for any interval that involves a register key. It doesn’t seem to hinder performance significantly — presumably, as woodwind players we learn to anticipate the extra delay.
I think your fingering chart has some really good ideas in it.
Especially Rule 6: Raising the L1 for higher octaves would faciliate the work of the left thumb on the octave keys greatly (lifting/shifting). This should also work for the whistle fingering, or?
Hi Bernard, the XpressO and the Roland as inprinciple the same age: they both use samples. The Vl70 uses mathematical models of the instruments, wwhich means they react the same as the akoustic instrument. Like on the real instrument, when you blow to hard is overblows, generates the same overtones, so sounds more realistic. The learning phase is also a bit more than compared to a sample instrument..
Though rather old, people still come to check wat synth i used for some sounds..
Yes! For my current use - Sylphyo => Link/MIDI => Cantabile => Kontakt 6 - the facilities for drawing response curves has been the complete solution for handling this issue. This was suggested and discussed in detail in this thread on the Native Instruments forum:
... and I have found that the flexible envelopes (drawn, rather than the table option) are a straightforward and complete solution. I have recently been using envelopes for other purposes - controlling parameters on modular synths using elevation and roll (have not tried compass yet) and that is a fantastic alternative to expression pedals.
For other scenarios that do not have the flexibility provided by Kontakt, I am not sure the solution. MIDI filters do not seem to be the answer, since they are translating MIDI to MIDI, not extending the bit depth of the MIDI stream itself.
There might also be an issues for sound libraries that are encrypted (locked) by the vendor, rendering the curve inaccessible - but I'm not sure about that.
... and Thank You@join for the amazing amount of detailed information!
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.
You are not doing anything wrong.
The up/down buttons are only providing this next/previous feature when NOT paired with the Sylphyo. When you are using the Sylphyo this is achieved by the Sylphyo keys instead.