New features you want to Pianoteq (not instruments) (Page 3 of 3)

I am a big proponent of this.  Until we are granted TWO velocity curves (one for 'keyboard correction', and the other for 'creativity', then there are workarounds.  Here's what I discovered:

With the help of a friend, I found a separate software solution: MIDI Velocity Curve Changer by Trombettworks ( www.trombettworks.com ).  This is an older freeware utility whose only purpose is to be a velocity curve modifier. I use my corrective velocity curve here, feed that into an external virtual MIDI cable such as LoopBe Internal MIDI, and then feed that as the source into Pianoteq.  There is another program that does the same thing that I have not tried,

http://www.bewaryprods.com/software/pro … sMIDIfier/

as well as a 'hardware solution', an external processor box that plugs in between the keyboard and the computer, the velocity converter made by MIDI Solutions:

http://midisolutions.com/prodvel.htm  (look for products – velocity converter)

The downside of using a software solution as I indicated above is that it eats up some processor cycles, adding to your latency. Originally I thought this would not work, but then I made some modifications to my computer, a Windows Surface Pro4, that ran much more efficiently afterwards, allowing me to then "sneak in" the external velocity converter without having bumped my Pianoteq perceivable latency past the threshold that my brain finds troublesome. The downside of using a hardware converter, such as the MIDI Solutions box above, is that it is more money, costing approximately $120. In the future, I may go the hardware solution, but currently the software solution is working just fine.

You already decide whether or not you freeze velocities, via a single interaction!  Please, let's just keep some things as simple as possible until Pianoteq developers should decide for both a default curve and a preset curve on a drop down menu: for something, anything but an economical savings in manual er physical exertion at an interface, if you do your math!  But, let's see:

1.)  Per your manual you manually calibrate your keyboard or load a ready made keyboard velocity curve from the Pianoteq Keyboard velocity curves forum.

2.)  Name and save your keyboard velocity curve.

3.)  With it loaded, check to freeze velocity note-on importantly and note-off parameters optionally.

4.)  Click "Save as default," if needed.

5.)  Load a preset; when it loads it does with whatever curve you loaded right before you checked to freeze any velocity and clicked to save it as your default, necessarily.

Anytime you want to revert a preset back to its original velocity curve and other original parameters, you copy it to the A or B window just to keep any recent changes, press and hold your input device about two (2) seconds for your cursor to hover over the preset name.  Which afterwards will appear without the word "modified" showing in parentheses () alongside it.  With the recently changed preset having been copied to the other window, you may copy the original velocity curve from the preset reverted to its original state and apply that to the newly altered one  —fine!

MIDI overdub.

2 use cases:

1. You want to practise your left and right hand separately, or you want to play a piece for four or six hands.

2. Composition. Sometimes I come up with an idea when I am messing about at the piano and I want to layer something on top of it quickly so I can remember it for later. At this stage, I don't want to launch my DAW because it's too much of a distraction in too many ways. I just want to note my idea very quickly, using the sounds of just the one piano, so that I can get back asap to improvising and playing.

+1 to those ideas.

It would be interesting to see if they could do that stuff without substantial CPU hit though.

+1 from me as well, especially for point no.1.