Hi Team,
when using some external devices controlled via Control Change, I realized, even with the support of Midi Monitor, that apparently the Chase Event mechanism does not seem to work for the CCs present in a midi track and included in the range 64÷69 (Data 1).
In particular, while during the execution of the Song these CCs are regularly sent, moving along the timeline, with Song stopped and Chase Event On Start preference disabled, the CC64÷CC69 events seem to be ignored.
Is this a desired behavior or a symptom of a bug?
Thanks in advance for your feedback.
Yes and no.
These controllers (sustain pedal etc) are reset on stop, so they are omitted.
However I see that could be a problem if you deliberately want to set them to a specific value, like you want to start out with an activated sustain pedal. Surely not what you’d normally do, but of course it should be possible, will check.
Hi @musicullum,
I understand the reasons that led you to ignore the CCs in the range 64÷69 from the Chase Event mechanism.
But I will explain my specific scenario.
I have a Line6 Helix that is controlled via Program Change for the selection of a specific memorized Preset, but then with a CC of type Hold 2 (value 69) for the selection of the Snapshot within the selected Preset.
In a partial execution of the song (such as what can happen during rehearsals), the fact of jumping in the timeline to a particular point of the Song, before going to play, often determines an incorrect selection of the Snapshot, compared to what was programmed and what is obtained with a complete execution of the Song.
At the heart of the matter I believe is the fact that the range 64÷69 of the CCs is used by many devices, for the automated control of the same, in an alternative way to the function suggested by the name of the CC.
I thank you for the feedback provided and await your further consideration in light of these additional details of the problem posed.
We’ll add a preference to “MIDI/Chase Pedal Events”.
1 Like
Hi @musicullum,
I can confirm that the new preference, if enabled, perfectly solves the problem posed.
Once again thanks!
PS: unfortunately in the tests carried out a new problem emerged that I described in the appropriate post [2.1.12] Problem with Chased Events on Transport Stop - VST Live - Steinberg Forums