I do not like to ask a question which has, in all probability, a very simple answer . . .I could ask Google of course, but I've typed this now . . . . .shrug so; Anybody?
Just drag it onto the pianoteq GUI.
Just drag it onto the pianoteq GUI.
I thought the velocity curves were given in coordinate form . . .I have a rather nice one to upload.
Hi peterws,
an FXP is a complete preset, but the velocity curve by itself is not an FXP file.
If you set a curve of your own in a preset, saved the whole thing out as an FXP "Peter-piano.FXP", that would contain the curve and every other setting you change
But, still the best way we have right now to set a velocity curve is by copy/paste I think.
Actually, if you 'Save As' for a velocity curve, it will save it like an fxp in whatever folder you were in when you saved it. I discovered this by accident! But if you would like to upload a velocity curve, the best way is to use the text format 'Velocity = .....'.
My preferred method for importing fxps in general is to have a special folder within Presets (I call it 'Imported fxps'). I open this (the little folder icon next to All Banks in Preset Manager) and then just paste the new fxps in there. Pianoteq has to be re-launched before the new presets are visible in Preset Manager.
Thanks dazric,
the velocity curves have '.mfxp' for the extension - I tend to save my own custom ones in the interface (without even seeing the files or the extension there) but always just copy/paste others and edit by hand in the interface.
Maybe the Velocity Curves page could be upgraded though (like the FXP Corner) at some point?.. but copy/paste is so easy, it just may not justify that complexity. Probably just simpler than downloading a file and remembering where it is (just a guess at the reasoning).
....
For new readers, anyone not encountering this before, here's what it looks like when you right-click in Pianoteq's "Velocity" box in the main interface showing the normal default velocity curve, then choosing "copy", then pasting it as text..
Velocity = [0, 127; 0, 127]
And more complex curves like "fast keyboard"..
Velocity = [0, 5, 15, 30, 49, 72, 98, 127; 0, 0, 2, 7, 19, 40, 75, 127]
You can drag dots around by sight, or type in values, or just edit text for precision.
Definitely a good velocity curve makes a profound difference to how well the engine talks to your fingers