Hi team,
after some time spent using two VL projects in two different musical contexts, I realized how the management of MIDI control messaging, implemented via Layer or via midi track to manage external instruments, responds to different needs during a live performance (or a simulation of it) or during a band’s rehearsals.
As it was designed, currently the management of MIDI control messages, activated by a Layer on the selection of a Part or by an event placed inside a midi track, I would say that it is satisfactory when VL is used in a live performance.
On the contrary, I found myself in incongruous situations when VL was used during band rehearsals; I ask you if the following hypotheses can be taken into consideration:
-
Currently the chasing of an event contained in a midi track is activated exclusively on the play of a Song: it is possible to have the activation of the chasing and therefore the relative sending of any chased events on the relocation of the position within the Song does not matter whether via Left Zone or Transport Panel (practically similar to what happens with Cubase on relocation in the timeline)?
-
In order to increase usability, would it be possible for the user to decide whether the management of MIDI control events occurs exclusively during Song playback or also on relocation via Left Zone/Transport Panel?
What do you think? 
Hoping for your feedback, thank you in advance. 
There was another comment explicitly liking that chased events are only output during start
So a preference may be needed as you suggested.
Hi @musicullum,
you are absolutely right and I am very impressed by your observation! 
In fact, initially I appreciated the fact that the MIDI messages to my external devices were not sent to a new position in the timeline (for a question of minimizing the MIDI messages sent), but at the moment the Song was played.
But with the use of the software in this mode I realized, during band rehearsals, the disadvantageous situations it can cause.
In conclusion, yes, the best would be to have the possibility of using one of the two modes by choosing them, according to the use cases, from the application preferences.
Thank you very much for your consideration and I hope it will be possible to add this feature soon with reasonable effort. 
We have added a preference with the next version.
1 Like
Hi @musicullum,
unfortunately, from a first test performed, it seems that we didn’t understand each other at all about what my hypothesis was. 
My request was not to completely enable or disable chasing of midi control events, but as I wrote in my previous post to decide the moment at which chasing is applied.
Let’s say that I was expecting something more like this in the preferences:
Chase Event Mode:
- On start
- On relocation (Cubase style)
- Disabled
I’m sorry I wasn’t clear enough, I hope it can still be remedied. 
Disable we don’t have, but the preference should switch between the other two modes you just said, no?
Yes, my initial hypothesis was to be able to switch between the two options On Start (first implementation of the Chase Event in VST LIve) and On Relocation (current implementation of the Chase Event in Cubase).
To remove any doubts, I re-tested the behavior of the software in the Pre-Release 1.3.20 version and what I get can be summarized:
- With the Chase Event On Start preference enabled
- I position the transport on the timeline immediately after a control midi event contained in a midi track
- The control midi event is not transmitted as expected
- I execute play and the midi event is transmitted as expected
- With the Chase Event On Start preference disabled
- I position the transport on the timeline immediately after a control midi event contained in a midi track
- The control midi event is not transmitted differently than expected
- I execute play and the midi event is not transmitted as expected
In practice with the current version what I get seems, with the Chase Event On Start preference disabled, to correspond to the disabling of the Chase Event.
As always, thank you for your support and patience. 
You are correct, chase when not “on start” is set doesn’t work correctly. Fixed next version.
1 Like
Hi @musicullum,
I had the opportunity to try this new fix and it seems to work perfectly in the two foreseen scenarios.
Thank you for your consideration and for the work done! 