Well, the latest Cantabile Lite (free) does allow morphing (and randomization), but I can't see any way to attach it to a cc. I'm not sure how it's controlled or timed. But it apparently lets you morph either a specific slider or several, and lets you set the exact start and end points for the change, or morph to an entirely different preset.

To access the morphing settings, open the interface for the vst instrument and, at the top, click on Edit\Morph tools.

(If you download the Cantabile lite program, be aware that the big Download button at the top of their main download page downloads the 32 bit version. To get the 64 bit version, which is needed if you use the 64 bit version of PT, scroll down and look to the right side of the screen.)

If there were a way to automate all parameters without such interruptions, you would have your morphing Pianoteq.

Philippe: Automation?  How exactly would be that?

I'm not using it myself (not enough time) but there are other threads in the forum mentioning automation, and maybe you can get help from users here.

What about start only with the hammer hardnnes morphing? Hammer hardness do not present noise, if we change while palying pianoteq.
We set two hammer hardness adjusts, and set a progressive pedal to control between adjusts. Halpf sustein would get a intermediary value from one set to another.

Maybe a adapted version for test, for just some of us test and comment.

Evildragon:  In case of crossfade is made during a moment of sustein, the second piano, that will emerge, needs to be on sustein for some time, otherwise his sound will enter without the ressonances created from sustein.
It's like when we run a midi to play pianoteq. If we stop the midi, even from a short time, and restart, the piano sound got different since the resonances were cut and restarted latter, loosing the ressonance that was emanating before.
Since the morphing is not predictable, as someone would choose use when he wants, both pianos would need to computating all the time.

Well, it would take two times processing power, sice the ressonance would require that both painos would be working, even than one it's not listened, otherwise the other would start from zero each time the switch from one to another.

Not really, it should take higher CPU load only when the crossfade is happening. When only one or the other piano sound plays, CPU load should return to normal. It can be made that way.

Maybe Modart could start with morphing possibilities to simpler things, like hamer hardness. We set two hammer hardness settings, and choose a pedal to switch between both.

Two instances of pianoteq could be interesting, but it's not able to be like a real morphing piano, cause would be separated pianos, separated ressonances.

I bet if you would do it you wouldn't notice THAT big a difference. It's all just crossfading. One is crossfading parameters directly, the other is crossfading sound globally. It's nonetheless very usable.

To answer your first post ;-) Yes it's is possible to run multiple instances of Pianoteq (both stand alone as VST) at the same time. I did it on my computer. Running it within a VST host gives you more control though.

Cheers,
Herman

To comment on your morphing idea- IF it's possible to load multiple instances of Pianoteq at once, say in a sequencer on different midi channels, it may be possible to use a footpedal or fader to smoothly fade from one to another.

This would depend on your keyboard controller of course, and on whether or not Pianoteq can run more than one instance at the same time. Does anyone know?

Regards,
Michael