Pianoteq 6.1 (Page 3 of 4)

I agree, check your energy profile.
It should be set to performance. Also disabling turbo boost or other powersaving settings in the bios can help.

You're right. I guess I should get some sleep

I did check using the Pianoteq keyboard, tapping the keys with the mouse, and the F4 is MUCH louder. I unplugged peripherals, did a virus scan. My computer works great in every respect except for 6.1.1 and 6.1.

beakybird, some container or cavity around your workstation must be resonating F4.

I do not have critical-anomalous notes ..

Weird indeed.  I think that I have a similar issue with B5 through, which has been present through each version of Pianoteq. It didn't seem to be caused by my QRS PNOscan reader calibrations, and didn't occur with other VSTs (Native Instruments, for example).  I eventually just ignored it, so now it doesn't bother me.  ;-)

It looks like Niclas showed me an easy fix for my problem. With 6.11, the volume of one note, F4, was through the roof even with low MIDI velocity - regardless of Pianoteq instrument, regardless of MIDI controller.

I didn't realize that with Pianoteq Standard, you can change the individual note volume, but you can by double clicking the volume meter. When I saw the individual note volumes, one was turned up to maximum - F4. I brought this down in line with surrounding notes, and everything sounds great. Then for safe keeping, I froze volume in the freeze section.

I still get a warning of large fluctuations on the performance index, but the software, in fact, plays fine now. In fact, I'm not getting some of the performance issues I had before, like dropped notes. Thanks, Niclas.

That’s a strange setting to change on an update. Is there any way you could have done it accidentally?

My feelings on the update here.
This 6.1.1 version is really an improvement, the expression is more dynamic and vivid!

However, as others already mentioned earlier in this thread, the sound is somewhat stronger and my ears are not as comfortable as when I was playing 6.0.3 version. So, I tried adjusting EQ and Reverb settings but those tweaks were not that satisfactory. Now, I am thinking that the change is fundamental, so it is not easy to regain the state of the former sounds.

Also, I feel that the characters of some instruments have changed. Bluthner in 6.0.3, was a kind of Basso Profondo, now in 6.1.1, the tones lost some percent of richness, especially in lower notes. I miss the timbre.

I have an idea, how about adding a slider or button which modify sound quality from dullness to sharpness (or at least something like that)? It is similar concept with condition slider which we already have. With it, we can adjust piano sound from Mint to Worn out very easily.

Anyway, I am trying to adapt myself to the new version, I really appreciate the effort Modartt has made.

Overall I want to heavily promote RME audio interfaces. I'm a recent Babyface Pro owner - hassle-free playing Pianoteq on 48 samples buffer (while watching YouTube), all on a 6 years old i3 3220 processor PC. There is actually everything amazing about RME stuff, but especially in regards to Pianoteq it has the best drivers latency/performance/stability-wise on the market. Downside - they are rather expensive.

Does anyone know if the RME interfaces work well in Linux (or whether they depend upon Windows or Mac software drivers)?

RME Babyface works on Linux in class-compliant mode, as reported by many. Probably their other audio interfaces, too.

Just a follow-up. Once I restarted Pianoteq after the CPU Overload warnings - where I mentioned that the CPU wasn't actually overloading - Pianoteq 6.11 has been stable on my system. Even when having volume unchecked in the freeze pane, I'm no longer getting the loud F note, and I'm no longer getting a CPU overload warning. I'm getting a performance index of 90 ... 111 which is probably not right.

Anyway, I'm pretty picky. There are two problems I have gotten with some Pianoteq instruments and/or presets. One is a synth-like resonance and the other is convolution - where the notes sound too mushed together when playing chords with pedal down. Some of these problems are less apparent with my speakers than they are with headphones.

For now, I really, really like the Grotrian instrument, and I was playing the Model B, and it sounds just fantastic. The Bluthner sounds very realistic, but it's not a sound I'm drawn to.

Ideally, all the models would sound perfect to me, but for me to have the Grotrian and the Model B to play with and they both sound just gorgeous, and compellingly piano-like, I'm a very happy camper. So with all caveats aside, Pianoteq is my favorite VST.

Overloads - had this today as well, had the computer running, playing (Model B), doing something else, playing, doing something else, etc. then I switched to U4 and playing CPU load went up dramatically.
On my system (Surface Pro 3, Win 10 Pro) I saw an increase in Tracktion CPU-load from 24% to 32% roughly .... (same settings, CPU on max setting - everything else at same setting. So, even if the numbers are incorrect, they indicate an increase).
So, definitely more CPU hungry (in my case not critical) - not sure about the CPU load today - if that is to be accounted to Pianoteq or other components - did not have that before. (but normally I play and then I quit, not letting the computer running)

best

Hey there

1. I forgot to subscribe to this topic ... I thought it would be automatic subscribed, damn ... sorry for the late reply.
2. I know that the FL CPU meter does not show the real CPU usage. Still: a) the meter show different values for 6.0.1 and 6.1.1 - so at least the relative difference shows that the new version is higher and b) higher CPU usage in the FL meter is still bad and let me less or none headroom when using Pianoteq in an orchestral setup.
3. I still did a test with both versions after redownloading the v6.1.1 again ... and .. ehrm.... did the devs did some changes afterwards? Here are the test results:

v6.0.1
    FL CPU: 23
    Win CPU: 7,5 %
    Max poly: 48
    no internal effects

v6.1.1
    FL CPU: 23
    Win CPU: 7,7 %
    Max poly: 32
    no internal effects

v6.1.1
    FL CPU: 27
    Win CPU:  8,8 %
    Max poly: 48
    no internal effects

So did the devs changed the installer since my last post? These CPU differences do not seem that much any more to me like in my first tests.

Version 6.1 is really nice to play, so I try some tweaks, about it I saw that all the original settings of the dynamic (difference between pp and ƒƒ) were mostly set on 40 db, sometimes less, is there someone Using a higher amplitude?

After an initial disappointment to find my carefully nurtured preset of the model B had changed, I am now getting used to using this new version and enjoy the improvement in clarity. My favourite model B prelude, with some adjustments for my set up is even better!

One way to conserve resources, if you’re really pushed, would be to avoid or modify presets with more than 2 mics. Admittedly this may be a problem for Stage users, who do not have access to mic settings. Perhaps somebody could do a list of presets with gradings to show light, medium or heavy CPU usage. Some of the Bluthner presets, for example, use 4 mics, and some of the Grotrian presets use 5.

I ran into performance issues with 6.1 on my i5, 2.2gig laptop as soon as I loaded Erard 1922 Recording (4 mics) and played a few chords with pedal, which was no trouble at all in 6.03 with my previous settings. So I’m having to tinker with the performance settings to get it to behave nicely. Also I need to rethink some of the presets, especially the amount and type of reverb (Erard 1922 seemed to me very boomy in the lower end; a drier reverb setting helped to reduce that effect). A bit of work is required to get some of the pianos sounding their best with my equipment, but I’m sure it will be worth it in the end.

The historical (pre-1900) pianos, for me, always seem to need a lot less tinkering than the modern ones, just set the velocity curve and maybe change the tuning or tweak the reverb, then I’m good to go. They were pretty good in v.5, now they’re just incredible! Once again I have to thank Modartt for making these superb instruments available and so satisfying to play.

Odd, I've never had any issues with PT (ver 5 or 6) running on a Surface Pro 4 until the latest update. Now I got a bunch of crackles and CPU overload detection. Never saw that before ...

I've always had my sampling rate set to 44.1, with 256 samples. Last night I was testing glissandos up and down the keyboard and it was consistently throwing CPU overload warnings. I toggled to 512 samples and then back to 256. Now it seems fine ;0

+1. IMHO, YC5 is the worst model of all modern grands in Pianoteq (and so the only I didn't buy). Too synthetic. But I like Yamaha sound, it same as Kawai, pretty bright but not harsh. I miss a good Yamaha/Kawai model in Pianoteq.

U4 is slightly better, but also too synthetic. I still waiting for improvements.

Agreed. I had the pleasure of being able to test Yamaha C1, C2, C3 against the Kawai RX1, RX2 and RX3 at the same dealer when shopping around. (Some years' ago obviously) I respect peoples' choices either way of course, but for me I quickly abandoned the Yamahas. Would have bought the RX3 but didn't have the space. Thoroughly enjoyed my RX2 until I downsized and went digital.

A Pianoteq Shigeru would be very welcome ..................

Just mouse-clicking the virtual sustain-pedal (while all notes are off) drives the Audio load / CPU usage from 1 % to 35 % on my system v6.1.1. - That's hungry, isn't it?

Arbitrary Steinway D Prelude (unmodified preset):

@beakybird@Ross
I dont think YC5 is bad at all. It remind me of a Yamaha I played every week many years ago. I like it. Sound is so clean, kind of elegance, stylish. I have listened so many times to the YC5 demo ”So long california”, it is excellent. To get opinions about Ptq are of course good for Modartt. And different opinions in this forum can help members too. I think i could buy YC5 using next coupon from the video contest this year. Well, thats what I think about it.