Thanks for the info. Whilst I’m grateful for now knowing this, I must say I think you should address this limitation in a subsequent release, as it is totally undocumented and not at all apparent from the user interface that this limitation exists.
I would suggest either forbidding CC7 and CC10 in the Init switch (with explanation in the UI), or enabling their use by overriding the signals used by the mixer.
Also, as you can see in the screenshot attached, there is no indication in the mixer that a particular CC change is initiated at the start of playback by the mixer. The only information displayed is that MIDI information is being fired onto the particular track, not which signals, or which CCs.
Its not obvious how to use this “MIDI” fader in the mixer to set control change parameter values, but I can do that without issue by drawing them in on the Play screen. The context of the issue is setting initial CC values automatically for a large orchestral template, having to manually set the values for every track is not a long-term solution!
For the time being I’ll change the CC parameter that the plugin uses for volume so I can manipulate it via a different CC, but it would be interesting to know your thoughts as to the long-term solution to this.