I want to easily be able to pick a piano and make it sound like it would to me as the player if I was playing it.  I don't care about listening to what the audience would hear.  I want to hear what I am used to hearing when playing.  The keys on the left should mostly come out the left speaker and the keys on the right would come mostly out the right speaker.

I hope the answer isn't messing around with the microphones.  I am looking for a simple setting.  Thanks!

So far using midi to control the wah pedal frequency has been too steppy or zippered  sounding, is it possible to smooth this or somehow use 14 bit msb lsb messages?
I would like to avoid using external effects, but if needed I can just use an effects modeler unit I am currently using for my Pianet.

I'm seeking some wisdom.

Why does Pianoteq sound so much better through my Sennheiser IEMs than my Beyerdynamic 770 PRO X Limited Edition closed back headphones?

With the 770s chromatic scales sound rather too uneven despite levelling unison width and the other one, unison something (forgot what it's called!)
However when listening through the IEMs it's night and day! Such smooth chromatic runs.

Also, when playing through my Soundcore X600s, evenness, but when playing through my KEF LS50s, again, I hear great inconsistencies.

Could it be that the more expensive offerings reveal too much and the cheaper ones behave more forgivingly, or am I missing something???

So for now, I'll listen through the budget options!

Any ideas guys???

Warmest regards,

Chris

In the latest version of Pianoteq 9.1.2, the length of the Steinway D is listed as 2.70 m. However, isn’t the actual length of a Steinway D closer to 2.74 m?

This issue doesn’t seem to appear with the Steinway B or other pianos in the “String Length” menu.

Also, shouldn’t this parameter be called “Piano Length” instead? The strings themselves don’t have the exact same length as the piano, so the current naming feels a bit misleading.

Regards,

Olivier

Steinway D, Electric, K2

I am in the U.S..

I‘m new to Pianoteq and need help with this setup: In the Pianoteq app options I can choose the audient interface as output but not as device. Is this correct or should the audient also show in devices?

Thanks in advance!

Martina

I've been running Pianoteq on a Raspi for a bit (still amazed that it's even possible!) -- but missed having some physical controls, as my piano, a Korg D1, has no MIDI sliders nor rotary encoders.

So I built myself this pianoteq-in-a-box-with-knobs:

The interface you see has been working for a couple years for me, but it's only this week (and with LLM help) that I finally put the finishing touches on it.

It's written in Rust and FLTK for minimal CPU usage, talks to Pianoteq 8 (not tested with 9!) over JSONRPC and controls ALSA volume directly. The encoders are connected over the I2C bus.

I am not committing to maintaining the code, but thought maybe someone could still find it useful for their own setup, so here it is:

https://github.com/polymeris/uteq

Next goal: make a decent-looking enclosure

Bought Steinberg The Grand3 to find it cannot handle Half Damper sustain (full CC 0-127) pedal, only on off.

Stumbled across PT trial to find it does handle HD sustain. Immediately purchased PRO for this and all it's other goodness.

Emailed Spectrasonics about Keyscape. Keyscape, Halion, and SINE (Novation) does not handle HD sustain.

Googled "does sampled music libraries not support half damper sustain while physically modeled libraries do"? Answer according to AI (ugh!) "It is not strictly true that all sampled libraries lack half-damper sustain, while all physically modeled libraries have it, but the statement reflects a fundamental difference in how they handle articulation. Physically modeled libraries are naturally designed to support half-pedaling continuously, while sampled libraries often require complex scripting to simulate this effect, with varying degrees of success."

I do not yet fully understand all the diffs / foibles about this topic subject. Then I hear Gamechanger PLUS sustain pedal on Youtube. Sounds nice at least for guitar. I believe it works with some looping technique. I could not find a VST using the same technique / algorhythem. Reverb is not sustain.

Questions: Is there a fundamental differance about this topic sublect that may prevent or make algorithms difficult for sampled libraries to allow HD sustain? Would PLUS type algorithm based VST be a viable work around or sound too fake for polyphonic systems?

As mentioned love PT and encourage Modartt to contnue with other acoustic instruments.

If I connect headphones to the iPhone, the piano sound (Bösendorfer) is perfect.

However, if I connect speakers (M-Audio), while playing I hear some notes that sound out of tune, with a tone that oscillates like a wave.

Has anyone else experienced the same issue?

Thanks

To me, it's really as though a wider dynamic range reveals certain aspects of Pianoteq's modelling that remain a bit hidden with the 40 dB setting. It has made me realize that Pianoteq is even better than I thought.

Would it be an idea to include standard presets with a 47-50 dB dynamic range for all grand piano models? The Steinways have 45 dB presets but the default dynamic range for the grand pianos seems to be around 40 dB.

DAW: Ableton Live 11
Plugin: Pianoteq 9 (VST3) 9.1.2
OS: Windows 11

When using Pianoteq 9 as a VST3 plugin in Ableton Live 11, the Live set is marked as “modified” (dirty state) immediately after reopening, even if no changes are made after loading the set.

This only happens when a preset different from the default one is selected.

Steps to reproduce:

Create a new empty Live set
Add Pianoteq 9 (VST3) to a MIDI track
Do not change anything (default preset: NY Steinway D Classical)
Save the Live set
Close and reopen Ableton Live → Set is NOT marked as modified (correct behavior)

Now:

Load any other preset (e.g. “Model D – Sombre”)
Save the Live set
Close and reopen Ableton Live → Set is immediately marked as modified (unexpected behavior)

Thank you very much.

Massimo

I'm optimizing my laptop - which has a hybrid CPU with 6 p-cores and 10 e-cores - for hosting multiple instruments (our whole band) into a front-of-house / PA at low latency. For this i need full control of CPU affinity / core assignments. It seems that regardless of "multicore rendering" setting, Pianoteq doesn't stay on whichever core i assign it to, and jumps to whatever core it feels like at any time.

I was wondering if someone can explain to me the exact behaviour of Pianoteq regarding CPU assignment between the 3 settings for "multicore rendering" which are OFF, ON, and MAX. Does it do its own thread management, if so how and when?