Hello,
does anybody know if keyboard velocity can be assigned to any parameter? Or is it "hardwired" to only a few parameters, like the filter frequency, etc.?
Regards, Digifex
MPowersynth - Assign keyboard velocity
-
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
You can assign it to any parameter. Take a look in the midi tab (bottom right of the plugin).
You should be able to work it out from there, but if you still struggle, come back here and I will help you in more detail.
You should be able to work it out from there, but if you still struggle, come back here and I will help you in more detail.
Jason @ Melda Production
-
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
Not sure what "Note index" is. But don't worry about that as it's not what you're looking for. Go to the middle tab named "Notes" this is where you can assign parameters to keyboard tracking.
Jason @ Melda Production
-
- KVRist
- Topic Starter
- 126 posts since 14 Dec, 2010
Thanks, you're my hero today.
But is it possible to adjust the intensity of keyboard tracking? In some other softsynths one can adjust a curve for keyboard tracking. Would be fine if this would be possible in MPower Synth too.
But is it possible to adjust the intensity of keyboard tracking? In some other softsynths one can adjust a curve for keyboard tracking. Would be fine if this would be possible in MPower Synth too.
-
- KVRian
- 587 posts since 8 May, 2012 from E.U.
It's possible, you need to first map your parameter to a multiparameter (which has adjustable transformation shapes), and then map that control to velocity as described above.
Unfortunately, you may not get smooth results. To understand what i mean, first use the filter's built in velocity control and you'll get smooth results......then, disable that and make your own velocity control in the way i described. When you do it via the midi section, firstly, it'll be monophonic, so polyphonic playing will be weird, and secondly you'll hear that the filter will take a split second to jump to the new value (which doesn't happen in the filter's own velocity section). I'm using filter freq as an example, but you'll hear the same problems with any parameter. So basically the synth isn't acting clever and saying,
"i'll wait to see what the next velocity value is before setting that parameter next time there's a note on".
it's saying:
"note on, right, let's do that first.......holy shit, note on velocity is telling me to change that parameter to something different, quick, change it, damn, too late!"
Along with Zebra, MPowerSynth is the most advanced VSTi synth there is. So hopefully some of these weirdnesses / short-comings (there are quite a few more) will be ironed out or improved in a future version.
Unfortunately, you may not get smooth results. To understand what i mean, first use the filter's built in velocity control and you'll get smooth results......then, disable that and make your own velocity control in the way i described. When you do it via the midi section, firstly, it'll be monophonic, so polyphonic playing will be weird, and secondly you'll hear that the filter will take a split second to jump to the new value (which doesn't happen in the filter's own velocity section). I'm using filter freq as an example, but you'll hear the same problems with any parameter. So basically the synth isn't acting clever and saying,
"i'll wait to see what the next velocity value is before setting that parameter next time there's a note on".
it's saying:
"note on, right, let's do that first.......holy shit, note on velocity is telling me to change that parameter to something different, quick, change it, damn, too late!"
Along with Zebra, MPowerSynth is the most advanced VSTi synth there is. So hopefully some of these weirdnesses / short-comings (there are quite a few more) will be ironed out or improved in a future version.