As I want to create a bigger Expression map within Cubases, I cannot use notes, as I don't want them to be in the playable range of the keyboard. Well, then I thought, I'd use program change, but doesn't seem to work due to a VST3 limit (Steinberg actually denies that, well ...).
Well, I am flexible, so I thought, why not take an unused CC insead, like CC 0 or 127. I got a lot of strange result with my expression map, which should have actually worked and I thoroughly learned how to build them by the manual. It took me half a day to figure out that it was actually VEpro that is changing the order of the CC and the note that is coming in! That is why every articulation change that is sent just befor the note (like it happens with attributes, or when you click on a note in the key editor) is being put after the note by VEpro. I could verity that by sending the midi to a midi monitor out side of Cubase. There, the order was as it is supposed to be, but looking at it within VEpro (Kontakt midi monitor) the order is reversed! There probably were good intentetions why to prioritize notes over CC data, but it makes the expressionmaps totally unusable to me.
I am all for a quiet and respectful communication here, but as a long time customer, I must say I am really getting annoyed by all these limitations and malefunctions. It is not only VSL, but also Cubase and partly some plugins. I put days of work into figuring out how I can build a usable and intuitive template, but always something seems to be in the way of working as it actually should. Dear people form VSL, with all respect: Could you please comment on that. Why must you influence the order of midi data sent? Why cant that be played back as it was received? Thank you