Hello,
I have a problem with actions and shortcuts.
I want to control “Marker1” using a program change command. Unfortunately, it doesn’t work.
If I control “RTZ” with the same program change, it works.
So, my device (Behringer FCB1010) sends the program change correctly, but VST Live doesn’t respond for “Marker1.”
If I use the keyboard shortcut, it works.
I’m not sure, if you can assign the same MIDI command to 2 actions. I think, the first one will win.
@Falfango Thanks for the tip.
But the image is just for demonstration purposes. In my real environment, I only assigned one action to ProgramChange (either RTZ or Marker1). And with Marker1 it does not work.
… we will check it,
Michael.
Works fine here with Note On, or controller.
Make sure to have no doubly defined action MIDI data.
Also checked with Program Change, sent from Layer. Note that PGM CHG data is often enumerated from 0 to 127, but also often from 1 - 128.
Hello @musicullum ,
I tested the whole thing again thoroughly on my Windows computer.
It doesn’t work.
I deleted all actions so there can be no duplicates.
Then I set RTZ to Program Change 2. It works.
Then I reset the entry and set Marker 1 to Program Change 2 (same setting as RTZ). Result: It doesn’t work.
I also tried it with controller data (also from another device). Same result. It works with RTZ, but not with Marker 1.
In the MIDI monitor, I can see that the MIDI data is being sent correctly.
How so?
See picture. This is
Note the offset, in Layer PGM CHG starts at 1, not zero (user request), Actions and shortcuts always shows “raw” MIDI Data, where Data 1 “0” refers to Program Change “1” in Layer.
Once you got that, replace VM with real ports. Still no go?
Also tried like you said, RTZ works, set RTZ MIDI to (“Undefined”) and apply same values to Marker 1, works just as well as RTZ.
If all else fails, send us your project with Marker 1 set as desired, just the .vlprj file is sufficient.
Here is my project (I created a new one for testing with only one midi-track).
Test.zip (10.0 KB)
This is the configuration for RTZ:
Thanks for helping.
OK, now it is spuky.
I tried out with “start”. It works also like RTZ.
Then I set the configuration back to Marker1.
And now Marker1 works too.
Same configuration as before:
I had the same phenomenon on my other computer.
What I’ve noticed now is that in many cases, I have to send the ProgramChange command multiple times to get Marker1 to jump to. However, in the MIDI monitor, I can see that the ProgramChange command always arrives correctly (although it’s probably not always processed).
And one other question: is there an actions to jump to the StartMarker?
no, but yes. You can put a PART division there (and dial via Action)
or navigate from and back to the song (via Action)
(or put the LEFT-locator there)
Thanks.
We found the problem. Connected an FCB1010, and it would sometimes not work.
There is a periodic function in VST Live that checks the timeline time if it matches specific positions like Marker 1, Marker 2 etc. When this intercepts the action accessing the same value, it resets the value while the action just tries to activate it.
We added a blocking function for these cases. Sorry that we couldn’t reproduce, it’s a timing issue that only shows its ugly head under certain conditions.
I recorded a short video showing the problem: I often have to send many program changes before VST Live sets the cursor to Mark 1.
In the video, you can see me starting and then stopping the song. Then I try to set the cursor to Marker 1 using a program change. In the MIDI monitor, you can see that the program change message was always sent correctly. However, VST Live only responds after a few commands.
and that ladies and gentleman, it’s dedication!!! Thanks Musicullum for not giving up on first (few) tries 
Thanks for the analysis. Will there be a fix for this?
or do you mean "We added a blocking function for these cases. " that this is the fix for the next version?
Yes, exactly, that was supposed to say “it will be fixed with the next version” in programmer nerd words
Sorry again, and thanks for helping!
Thanks for great support!
