I have an issue with my velocity settings. Initially caused by me playing in a few too many bands, in different reheasal places, where some already have keyboards available. I use them as midi motherboards, and use Cantabile for all the real stuff. However, the velocity on these keyboards vary, which makes it difficult. I use Pianoteq, which has the build-in velocity map. But some of the presets use the velocity map as part of the “sound”, e.g. some of the rhodes sounds.
I have considered a few options:
Using the velocity maps in Cantabile. Would be my prefered option, but they don’t have the same flexibility as a real velocity mapper, they can just be S-curves or C-curves.
Using the velocity maps in Pianoteq, but loosing the flexibility to use them as part of the sound setup.
I will have to fiddle a bit with the state settings, to make it possible to select the right state at the very beginning of a rehearsal and keep it across songs, but that should be pretty straightforward.
Are there anyone who already addressed (and preferably solved) this issue? Suggestions are more than welcome.
Same situation here.
For Pianoteq I use Pianoteqs velocity mapping; with other instruments I use Cantabiles mapping most the time. The masterkeyboard is set to “linear”. - not sure if this is the best solution. It is not easy to compare since it also depends of the quality of the keybed the masterkeyboards have.
From what I can determine, midi velocity is is 1-127 and is an OEM proprietary exponential function of downward key velocity. This key velocity is measured by two switches that are a small but known distance apart. So distance between switches divided by differential time of each switch closure is the actual key velocity. This actual velocity is then converted to a midi signal 1-127 (0 is note off) via some internal function.
So… how does one measure and compare midi velocities from controller to controller? Here is an idea using items from may garage: 1) 1/2" ID pipe about 6" long (Sprinkler riser, in this case!), and 2) a 5" long 1/4" bolt marked at various distances. Note that the bolt has a rubber bumper glued on the bottom to protect the controller keys. A falling object velocity is related to distance fallen, not mass; however, mass has to be enough to press the key.
There are four markings on the bolt from 1-4 (1 is the bolt head). If this bolt and cylinder are held over middle C and the bolt is allowed to drop from the various markings through the tube, a relationship can be built. In the picture below, I’m holding the bolt at marker 3 with the tube over Middle C and will release the bolt and record the midi velocity at Cantabile.
For this keyboard and this weight/tube layout, the distance and recorded midi velocity relationship are as follows:
The system could be trial and errored to hone in on larger ranges, but this is a concept at the moment. My theory is someone’s favorite controller response could be measured using this falling object method. Then, another controller could be measured the same way. One could visually look at the curves, and trial and error to make the curves match. Given time, an excel sheet could be made to walk into a gig with a new controller, take a few measurements and enter into excel, then a new velocity curve could be calculated for entry into Cantabile.
I typically use my 88 key Kurzweil boards as my main “piano” keyboard, and I also have a Studiologic SL 73 for cramped stages or when I just don’t want to carry so much weight (the SL 73 is about 10 kilos lighter than the Kurz).
I use “input racks” to encapsulate my keyboards in Cantabile songs, so I have one rack “Main Keyboard” and another “Second Keyboard”. These take input from the logical MIDI ports and then filter and split it up to multiple output ports (Notes, MW, Aftertouch, Pitch Bend), so I can easily and flexibly route these event streams to different destinations if need be.
Within these racks, I can easily have multiple rack states using different velocity (and aftertouch) scaling, depending on the physical hardware attached. I set the rack state to NOT be controlled by the parent rack, so once I set it at the beginning of rehearsal or gig, the state remains set.
So I have a state for my 88 key Kurzweil and another one for my 73 key Studiologic main board, and I can adapt the settings so the translation between my touch and the resulting velocity is at least somewhat similar.
The default state is “88 Keys Kurzweil”, because that’s what I use for the majority of the time, but when I start a session with the Studiologic, it takes me two clicks to adapt my setup. Simple and “good enough”.
If you want to be more sophisticated about things, you can also put a third party velocity mapper plugin into your input abstraction rack - I haven’t yet felt the need to do this (Cantabile’s settings are good enough for me), but it depends on your specific needs.
Thanks, all, great advice and descriptions. I’ll go for something similar to Torstens setup, but I guess I’ll use the velocity mapper. And then I also need to revisit my piano rack to change the Pianoteq velocity.
