Piano V3 bug: top velocity is zero when reloading

[James Adamson]

When a project with Piano V3 is reloaded in my DAW (FL Studio or Ableton Live- doesn't matter) the velocity graph is slightly messed up such that the highest velocity on the keyboard will produce no sound. Slightly dragging the last point on the graph will fix it.

This has been broken like this for quite a while but I'm only just submitting a bug report. I have checked with the Arturia Download Centre that I'm using the latest version.

I'm on Windows 10.

[Audiosexual]

I have the same issue, and it happens also if you open up the plugin in its standalone version.

Loading another patch (and optionally returning back to the original patch) fixes it, but it will happen again on next load.

[ottonis]

I have exactly the same problem: When opening the standalone Piano V3 (connected to Keylab 88 mk 2), then loud notes simply won't play - they get muted. When I hit the keys softer, everything is normal.
Interestingly, this didn't happen when I started Piano V3 for the first time: it first did its automatic velocity curve calibration and then let me play as loud as I wanted - without any problems.
The next day, when I loaded/started Piano V3, this problem occurs, and ever since...

I definitely have the most recent software version since I downlaoaded and installed everything last weekend (=3 days ago).

THis bug is extremely annoying as it doesn't let me properly play this instrument at all.

Any kind of help would be terrific!

[Kim Jinkings]

Same thing here...standalone and as AU. For now my workaround is using Apple Velocity Processor on Logic and Mainstage to avoid the top 127 velocity. Let's hope for a permanent fix