Pianoteq 6.1 (Page 4 of 4)

same here regarding Model B of 6.1.1.
same here on going back to 6.0.3.

not only that, but all the models I tried, of several different pianos, seemed to sound almost equally over-bright and loud and bad.

Since so many people in this thread really like 6.1.1, my theory is that on some systems, there is some kind of software setting or control that gets reset incorrectly in 6.1.1, causing bad sound on some systems.

Also, the sounds I was hearing when playing 6.1.1 were unacceptably BAD, whereas the online comparative demo provided by Pianoteq sounds fine (comparing the same pieces of music played by 6.1.1 vs 6.03) did not sound drastic at all, those demos sounded fine.

I'm on a 2017 iMac.  All previous versions of Pianoteq have always been terrific. I've been a consistent champion and advocate of it. But 6.1.1 was a wreck for me.

Well, I have to admit that my initial reaction to 6.1 on first playing was ‘aagh, that’s a bit strident….’, but after adjusting performance settings and modifying some presets it dawned on me that I also needed to pay closer attention to the behaviour of my input keyboard (in my case, a Roland FP30). Monitoring the output levels on the velocity map as I played, it soon became evident that it was far too easy for me to reach near-maximum velocity. With the increased realism of 6.1 this becomes a crucial issue. Think about it: if you’re intending to play forte and it’s actually sounding fortissimo (plus), it’s never going to sound right. And what about when you really want to play fortissimo? No piano (or any instrument, for that matter) is going to sound at its most elegant when it’s being driven really hard. Trying to adjust the velocity curve wasn’t quite doing the trick for me, so I increased the ‘heaviness’ of the key touch setting on the FP30 so that I would have to make more physical effort to play a genuine fortissimo. Suddenly all the ‘harshness’ was just swept away and the true character of each piano revealed in vivid detail. Much to my delight I’m even enjoying the K2, a piano that never quite convinced me before – now I’m actually playing it, not just fiddling about with it. So yes, 6.1 requires a bit of thought and effort to get the best out of it, but IMO it’s 100% worth it. I can’t imagine wanting to downgrade to the old version.

I think so...that might have a lot to do with the terribly loud sounds I was hearing when I was playing through a bunch of presets after installing 6.1.1.  I spent a few quick minutes trying some different velocity curves I already had on file, but I have not taken time to find the perfect settings. Have not even done a velocity reset within Pianoteq yet... I am just annoyed since it played great before, but all of a sudden - big problems. But I do appreciate your account of how your resets paid off in delight and playability.  When I have time I will get into it deeper: velocity settings, send files to Pianoteq support, etc, etc. Till then I will use 6.0.3 or other software pianos.

Just want to confirm FWIW that my CPU and crackling is not noticeably different after the update.

Also confirming no bad sounds or worse sounds. Quite the opposite as I'v posted elsewhere.

I've had edge-case issues with software over the years but I have every faith in Modartt to solve for individuals, do the right things etc. given that the user gives time and effort to engage with support.

Hmm, don't know if it has an effect on that OS, but your images show no valid comparison:

* Upper image shows Current polyphony 76, lower image 147.
* Upper image shows % Utilization over 60 seconds, lower image over 30 seconds.

Hard to get the right snapshot with windows' snipping tool. I was basically sliding the mouse over the lower notes, average polyphony was comparable.

The CPU graphs are more representative, just look at utilization over the last 5 seconds (snipping tool's max delay before taking a snapshot). You are right that I did change the graph update frequency in between shots.

There's also the "(MAX)" next to "Multicore rendering" in the 2nd pic.