Background:
Not all devices can be switched with MSB, LSB, Prg.
For example, my Yamaha GENOS2 keyboard.
A sysex command is required to access a registration file stored on the GENOS2 with all title-relevant settings.
Of course, I could also enter the sysex command in a midi track, but this would only be executed when the song is started.
A layer carries out the switching when the Song is selected.
Or does anyone have another solution?
Herbert
Great! I had absolutely no idea of that! It could solve a problem I had and mentioned in another post, but unfortunately, the delay between each chunk of the chased SysEx data is not respected, so they are fired too fast and my synth won’t have enough time to digest them. Of course, I’m talking about whole bulk dumps and not just short strings for a few parameters.
I don’t know how you could slow down the transmission speed for chased SysEx. Maybe by adding a SysEx delay time setting in Preferences, or by analyzing the absolute H:m:s.ms position of each SysEx event and firing them with the same interval.
But the decisive factor will be what is hidden behind the (“E”).
We users should be able to store a list of sysex lines.
Another highlight would be if there was a small comment field after each SYSEX line. This could be used to briefly describe the action performed.
So that even after two or three months you can understand what the Sysex actually controls.
Hello,
after the VSTLive update [2.1.20.] was released on Friday (2024.11.16),
I tested the new SYSEX integration in a layer object for 5 hours on Saturday.
I need two SYSEX command lines for the sound selection of my Yamaha GENOS2 keyboard. Unfortunately, you can only store one SYSEX command line in a LAYER.
I solved the two-line problem by first setting a layer with the file call for the Yamaha GENOS2 and storing the activation process of the first registration button in another layer.
This meant that switching the sound setting (layer 1) on the GENOS 2 did not always work reliably. The activation (layer 2) of the first registration button on the Genos 2 also works according to the blinker principle. (works, doesn’t work, doesn’t work at all…)
From my observations, I had the impression that the keyboard was being flooded with data.
As we now know, the global setting option for delaying SysEx data transmission did not work in version [2.1.20.xxx].
Fortunately, the development team released a new [2.1.21.xxx] pre-release on Saturday (2024.11.17). This means that calling up Yamaha Genos 2 registration banks works perfectly and the selection of the correct registration button also works.
A small note on the use of the “E” button:
I find the function of the integrated “E” button particularly successful.
It allows you to quickly switch off a particularly long SysEx string for test purposes without having to enter it again. Great.
You should also use this type of use in the layer object for sending “MSG, LSB, Prg Change” if this fits into your VSTLive concept.
Note to Yamaha GENOS 2 players.
I use the following setting to call up the registration bank and then activate one of the 10 possible registration buttons.
Go to Menu: Edit → Preferences ->Midi
Chase Event On Start = Enabled
SysEx Delay Time = 25 ms
I take the liberty of marking this call as solved, in the hope that Jihem’s problems with Sysex are also solved.
Many thanks to the development team for such a quick solution for me.
This is unprecedented. I am well on my way to becoming a VSTLive fan.
Thank you very much.
Herbert
