Hi
I have just spend the last 2 hours trying to understand this problem:
I have a French Horn patch from Spitfire Symphonic Brass with a Marcato articulation.
I have created a VST expression map for the patch in Cubase with all the art. present, among other this Marcato art.
This art. is triggered by UACC 52, that means a key switch: C-2 with the vel. on 52.
Should be so simple.
If I load this patch in Kontakt running locally in Cubase it plays fine, but if I load the patch in VEPro6 - nothing.
So I installed a midi-monitor and here is what I found: The patch in VEPro6 doesn't receive velocity 52, but 51!!
Now I tried to adjust the velocity of all the notes in the part to 52, and gues what: The MIDI monitor in Kontakt running inside VEPro6 shows 51!
So eventhough the VST map sends out vel. 52 or a note is played with the velocity 52, the result in VEPro6 is 51!
I tried the set-up in Logic, everything is fine.
Then I switched to the VE VST2 and now the Marcato art. was triggered just fine. I have just updated to the latest version: 6.0.17226
My conclusion is that it must be the VST3 plug-in that somehow causes the problem.
-
VE VST3 version corrupts velocity values?
-
-
Just to clarify! ;-)
My first post was looking a bit weird and the same text was repeated over and over again, so that's why Paul replied as he did.
Sadly the problem hasn't gone away , the VP VST 3 plug-in has some problems with velocity 52!
-
This seems to be much worse than expected.
I have created a midi part with 128 notes going from vel. 0 to vel 127.
This is the velocity values that doesn't make it to the Kontakt plug-in running inside VEPro6, connected by the the VE VST3 plug-in. The numbers in bracket are the values that are replacing the correct.:9 (8), 13 (12), 18 (17), 26 (25), 36 (35), 52 (51), 72 (71), 104 (103).
I ran the same test now with a Kontakt that runs native in Cubase 9.5, everything is fine.
Then I ran the test with the VST 2.4 plug-in connecting the same Kontakt in VEPro6 everything is fine.
I conclude that there is a serious problem with the VST3 plug-in.What do you think?
ps. This will have serious consequences for the use of Spitfire libraries with UACC KS!!!
-
Super!
In the meantime I will edit the VST maps for Spitfire I have to use CC instead.