it’s finally Friday and a new 2.1.20 Pre-Release of VST Live is online. You can download it here. You also can find a Version History there. If you found new bugs or bugs which are not fixed, please create a new thread and title it with [2.1.20].
This Pre-Release contains two new features
Layer: Added SysEx Control
You’ve asked for and here it is. Use the “E” control to enable the Layer to send its SysEx Message. Click to SysEx Message Display to edit the message.
Hi,
VST instruments will not sound from the external keyboard. The same project in VST Live 1 is perfect. And also in 2.1.19.
I had the same problem in 2.1.14. But you solved that.
Thank you
I just experienced the same thing. MIDI is received in the Layer, but it does not come through to the VST Instruments. Even the internal on-screen-keyboard of the VSTs does not produce any sound (VSTs in the project work if I install 2.1.19, but they don’t work anymore in 2.1.20).
Unfortunately, I still can’t get the bulk dumps to work properly, no matter the number of milliseconds I write in Preferences.
For each song, I have a Midi Track containing a clip with a bulk dump that configures my hardware synth. Each dump is made of 43 lines of SysEx messages. When I play the song from the very start, everything works fine. Now if I set a Start Time to let’s say 3.1.1, the SysEx seems to be chased at a too high speed, and then the configuration of my synthesized fails.
Maybe I’m wrong and the new SysEx Delay setting only acts on SysEx in layers… It would be annoying in my situation.
Once the update is done, I still can’t find the MIDI files associated with the channels I created, even with this version. Once I re-associate them, it works.
Moreover, and even more importantly, with this version, the sends to the stacks from the tracks suddenly disappear, and in the stacks, the outputs disappear. Then, at some moments, they reappear and then disappear again. This does not allow for the correct use of the project.
Additionally, for the SysEx, when I don’t have the hardware connected to directly check the functionality, I still can’t see the activity in the relevant layer when a command is sent.
What exactly do you mean by that? You create a MIDI track and import a MIDI file, then save, exit, load again? Did you move the project file maybe?
Could you please elaborate on this? What exactly do you do, and what exactly happens, or does not happen as expected?
Best would be a description how to reproduce:
I confirm that even with version 21, the stacks are not working. Basically:
I open the project
I click on one of the songs
I click on one of the tracks that already had a stack assigned as output in Global
I see the assigned stack as output
I click on another song in the project
I click on a track that had a stack assigned as output and I don’t see anything
I go back to the previous song (see point 2)
I click on the track where I had seen the stack as output and I don’t see it anymore. The same happens for all other songs
Additionally, it can happen that suddenly the outputs that were always assigned reappear and then suddenly disappear again.
Unfortunately, when the outputs are not visible, the tracks outputting from the global stacks are not heard. This makes the project unusable live.
Anyway, it doesn’t follow a linear pattern. In fact, sometimes it happens that suddenly one of the tracks shows the assigned stack as output and the others don’t, or that the others show the stack output and one doesn’t. It’s all very random.
Unfortunately, I also tried reassigning all the outputs to the stacks in global for the tracks, but I just wasted a lot of time because the same problems reappeared afterwards.
