Some seem to shoot curves. 

Have you all foregone completely now, the Pianoteq forum section set aside for velocity curves specifically?

I’ve a link to it: ”Keyboard velocity curves”!

Hi Amen,

In answer to your question, not at all. In fact, I posted the above curves in the forum's velocity curve thread when I posted the above!

Warmest regards,

Chris

Have you all foregone completely now, the Pianoteq forum section set aside for velocity curves specifically?

I’ve a link to it: ”Keyboard velocity curves”!

Lid 0.71 Bluthner Concert BA Preset

Note for note volumes levelled

Medium (default) Touch in P515

This is my latest curve, groovy. It seems pretty smooth throughout the register and velocity range. I'm going to look at your velocity curve tomorrow.

Warmest regards,

Chris

Here's the curve I'm currently working with.  I've set the touch to 'Hard1.'

Velocity = [0, 20, 39, 56, 64, 73, 93, 105, 116; 0, 18, 36, 54, 64, 74, 96, 110, 127]

Regards,
Shosh

I'll check out your curve shortly.

Here's one I created this afternoon for use with 'Soft2' on P515

Velocity = [0, 39, 75, 111, 127; 2, 2, 64, 127, 127]

Velocity = [0, 20, 39, 56, 64, 73, 93, 105, 116; 0, 18, 36, 54, 64, 74, 96, 110, 127]

Regards,
Shosh

Immediately above ^ to be copy and pasted into Pianoteq's Velocity Curve pane

Below, for use in Cantabile's Velocity filter

Velocity = [0, 13, 94, 127; 2, 2, 127, 127]

Use P515's 'Hard1'Touch Setting.

Don't really need 1st and last points in either case, but it just looks neater.

Hope someone will test and advise,

Warmest regards,

Chris

I shall post my latest attempt, which I love, shortly. It is to be used with the P515's 'Hard1' Touch Setting,

Warmest regards,

Chris

Would be interesting to see, how your curve compares to the suggestion of Pianoteq's calibration assistant (when used together with the unknown Soft-1-curve of the P515).

Yes groovy.

I'd very much like to know what other P515 users think of the curve and how it might be improved,

Warmest regards,

Chris

There you go guys. See if you like it and what needs improvement. Copy and paste into Pianoteq Velocity Curve pane

(Select Touch 'Soft 1' on your P515)

Warmest regards,

Chris

Thanks to groovy for the inspiration!

sigasa wrote:

post Ptq.

Remappings of MIDI velocity values have to be done pre Ptq's soundgeneration. Whether the remapping is done in external hardware, external software or internally in Ptq, the resulting sound will be same.

One thing to consider is the latency and "jitter"of those MIDI-events. Every data processing needs time.

Is Ptq's internal velocity-mapper always ON, even when mapping is identical (x=y)? Then we can't avoid this latency in the first place.

Further MIDI latency (and jitter?) is added by external devices, like MIDI Solutions Velocity Converter.

MIDI Routing and remapping with something like Cantabile or VelPro costs time and inaccuracy too.

Maybe those added latencies and jitters are neglectable, but as long it is not measured, it is safe to use just Ptq's internal velocity mapper.

Thank you groovy, I didn't realise this regarding velocities. It stands to reason though! I understand now, after what you just wrote in your last post above, that altering the Ptq curve in the velocity pane must of course alter the resulting midi arriving at the Ptq output. How silly of me not to realise this. It also makes me realise the importance of mapping a curve for Pianoteq users based on the Ptq pane.

Thank you groovy, I'll see what I can do.

Warmest regards,

Chris

post Ptq.

Remappings of MIDI velocity values have to be done pre Ptq's soundgeneration. Whether the remapping is done in external hardware, external software or internally in Ptq, the resulting sound will be same.

One thing to consider is the latency and "jitter"of those MIDI-events. Every data processing needs time.

Is Ptq's internal velocity-mapper always ON, even when mapping is identical (x=y)? Then we can't avoid this latency in the first place.

Further MIDI latency (and jitter?) is added by external devices, like MIDI Solutions Velocity Converter.

MIDI Routing and remapping with something like Cantabile or VelPro costs time and inaccuracy too.

Maybe those added latencies and jitters are neglectable, but as long it is not measured, it is safe to use just Ptq's internal velocity mapper.

Amen Ptah Ra wrote:

Guys, check out this software: VelPro.

This is a simple and great piece of software.  It provided the answer for my want of having a fixed programmable volume curve to use for both Pianoteq and my Native Instruments software.  This also meant that I no longer had to monkey with the volume curve within Pianoteq to match my keyboard, freeing it to vary with different instrument presets so that it could be used for creative purposes, rather than to 'correct' my keyboard (which is now done by VelPro, which starts with the computer, and just stays in the background.  Adrien Anselme, who created it, I believe, has been quite good to deal with when I had some questions.

Thank you David, very helpful,

Warmest regards,

Chris

Guys, check out this software: VelPro.

This is a simple and great piece of software.  It provided the answer for my want of having a fixed programmable volume curve to use for both Pianoteq and my Native Instruments software.  This also meant that I no longer had to monkey with the volume curve within Pianoteq to match my keyboard, freeing it to vary with different instrument presets so that it could be used for creative purposes, rather than to 'correct' my keyboard (which is now done by VelPro, which starts with the computer, and just stays in the background.  Adrien Anselme, who created it, I believe, has been quite good to deal with when I had some questions.

I prefer yamaha CLP685

I'm a Kawai MP11SE man. So, the Yamaha P515 is of no interest to me. But, now that you mention it, I'll take one of those CLP695GPs.