The best comparison would be to feed the velocity mapper with 128 discrete values from 0 - 127 and compare the remapped values (Velocity = [0, 33, 82, 104; 0, 34, 97, 127]) received from Mainstage vs. Pianoteq's internal velocity mapper. In your case one single different mapping would be sufficient as proof.
Unfortunately the remapped velocities of Pianoteq cannot be send to a MIDI output for comparison -- but I'm not 100 % sure about at the moment. So a real verification might be impossible ...
]]>max22 wrote:Important note: This works beautifully, but only through MainStage. I tried replicating the exact same curve in Pianoteq’s Velocity editor, but the result isn’t the same — MainStage likely handles interpolation between points differently, with a smoother response.
Final setup: P-525 Touch = Medium → MainStage Velocity Processor with the curve above → Pianoteq with a linear velocity curve.
If the Yamaha P-525 outputs MIDI velocity as you suggested, that's good news. Your curve translated to Pianoteq syntax: Velocity = [0, 33, 82, 104; 0, 34, 97, 127]
Could you verify, that the MainStage tool interpolates the remaining 124 value differently to Pianoteq itself? My guess is, that Pianoteq "draws" a line between two known points and rounds the point on that line to one of the nearest 128 discrete values.
I did some testing, and it seems that MainStage does not behave the same as Pianoteq in this regard.
In MainStage, the Velocity Processor appears to remap the full 0–127 range in a smooth and continuous way, with well-distributed intermediate values.
In Pianoteq standalone, using the same curve points, the result feels different — more like a simple linear interpolation between the defined points, with values fitting into the 128 MIDI steps in a more rigid way.
So yes, it looks like MainStage is effectively recalculating the curve over the whole range, while Pianoteq follows a more direct point-to-point interpolation. That would explain why the same curve does not produce the same playing response.
Important note: This works beautifully, but only through MainStage. I tried replicating the exact same curve in Pianoteq’s Velocity editor, but the result isn’t the same — MainStage likely handles interpolation between points differently, with a smoother response.
Final setup: P-525 Touch = Medium → MainStage Velocity Processor with the curve above → Pianoteq with a linear velocity curve.
If the Yamaha P-525 outputs MIDI velocity as you suggested, that's good news. Your curve translated to Pianoteq syntax: Velocity = [0, 33, 82, 104; 0, 34, 97, 127]
Could you verify, that the MainStage tool interpolates the remaining 124 value differently to Pianoteq itself? My guess is, that Pianoteq "draws" a line between two known points and rounds the point on that line to one of the nearest 128 discrete values.
]]>Hello everyone,
After a lot of testing, I finally found a velocity curve that solves all the issues I mentioned in my previous post. I’m sharing it here in case it helps other P-525 users.
The problem: With the standard curves on the P-525 or inside Pianoteq, I struggled to control soft dynamics and had to use excessive force to reach a natural fff.
The solution: I now run the P-525 through MainStage as a MIDI host, using the "Velocity Processor" MIDI FX plugin with these values:
0,0 33,34 82,97 104,127
How it behaves:
0-30: Linear response. The ppp-pp range (20-40) is stable and easy to control.
30-100: Expanded usable range. The key point is 82 in → 97 out — it lightens the mf-f area without making everything loud.
100-127: Reaching full fff is effortless. From 104 input it ramps straight to 127, so you don’t have to strike the keys too hard.
With this curve I can go from 0 to 127 smoothly and musically. Pianissimos are easy to dose, and f-fff comes out naturally without physical strain. For classical repertoire it’s the perfect balance I was looking for.
Important note: This works beautifully, but only through MainStage. I tried replicating the exact same curve in Pianoteq’s Velocity editor, but the result isn’t the same — MainStage likely handles interpolation between points differently, with a smoother response.
Final setup: P-525 Touch = Medium → MainStage Velocity Processor with the curve above → Pianoteq with a linear velocity curve.
If anyone with a P-525 wants to try it, let me know how it works for you. I’m happy to share the MainStage patch as well.
Thanks everyone for the previous suggestions!
]]>I’m using a Yamaha P-525 as a MIDI controller for virtual piano instruments, mainly Pianoteq.
I’ve noticed that the default velocity response is not fully ideal for my use. Soft dynamics can be a bit difficult to control, and I often need to play quite firmly to reach a full and open sound, which sometimes feels less natural than expected.
My setup:
Yamaha P-525
Mac
Pianoteq (main instrument)
Focus on classical music and piano practice
What I’m looking for is a velocity curve that:
slightly expands the usable range between 30 and 100
makes it easier to reach higher velocities (100–127) without excessive force
still preserves good control in the soft dynamics (20–40 range)
feels musical and stable rather than overly artificial or extreme
I have already tried basic curves (linear and mild soft compression), but I would really appreciate advice from users who have experience with the P-525 and Pianoteq and have found a well-balanced and practical setup.
Any suggestions for velocity curves or MIDI settings would be highly appreciated
]]>