Hi all,

The (just released) version 9.0.3 should address these issues with the sustain pedal (and automation in general) in DAWs.

Yes. Just tested here in Bitwig Studio 5.3.13, and balance has been restored to the universe...

Working perfectly in the manner of version 8 before.

Thanks so much to all of the developers for this fix.

Greatly appreciated.

The (just released) version 9.0.3 should address these issues with the sustain pedal (and automation in general) in DAWs.

it seems like my sustain pedal was in a opposite mode, sustain trigger off but not on.

the solution was to right click on velocity window

reset all velocity curves to default value

that worked for me.

Upon upgrading to Pianoteq 9 from 8, I instantly noticed some anomalous behavior with CC64 Sustain that was completely different from 8.

It's been extremely difficult to diagnose, but it appears that CC64 in PTQ-9 is behaving like it's bipolar modulation, rather than the usual unipolar...

Unique to this update too, is that it seems to be something peculiar to Bitwig Studio, while in REAPER, I'm not seeing this exact same behavior.

In the context of REAPER, I've looked at the MIDI logs using MIDI ReaControl, as well as the MIDI page in the PTQ standalone, but have not been able to identify why it's behaving differently in BWS than REAPER and the standalone, otherwise I would've issued a bug report already.

Was glad to see this post and that it's being addressed by the devs, as I've not been able to use version 9 in Bitwig Studio due to this anomalous and different behavior with the sustain pedal.

Hi all,

We are aware there is an issue with the pedal in the plugin version. It is a bit complicated but we are working on it.

its also the standalone version too FYI

We are aware there is an issue with the pedal in the plugin version. It is a bit complicated but we are working on it.

I have the same random sustain issues with Ableton Live 12 and Pianoteq 9.

Perhaps it is a wider issue then with the VST? Any ideas on how to resolve or report?

sustain pedal doesn't work on windows 11, Ableton 12

Do you have any idea why? Is this something we can report to modartt?

No I can see the gradual increase and decrease in the UI in Ableton, so I wonder if it is an issue between 9 and Ableton live.

Okay so the pedal response is visually correct which means the pedal messages are making it into the VSTi unaltered, but the audible damping response is not correct?

Pianojazzableton wrote:

For some reason, the sustain pedal only intermittently registers full sustain and other times only goes to around 64 on the midi reading wtih Pianoteq 9.

So if you just slowly and steadily cycle the pedal down and up repeatedly with the Pedal Curve displayed in Pianoteq's UI, you don't see the level indcators move steadily up and down between 127 and 0?

I definitely can't repro that. I would think it was a hardware issue except that you report it continues to work as expected in the v8 VST3, and in the v9 standalone.

I can't imagine what would explain all of that. I can only suggest to try the VST3 in the free tier of Sonar (very few limitations vs. the paid version) or some other DAW to confirm it's not just some interoerability issue between v9 and Ableton, specifically.

Thanks for the reply. No I can see the gradual increase and decrease in the UI in Ableton, so I wonder if it is an issue between 9 and Ableton live. I will revert to v8 for now as I have limited time at the moment to consider other DAWs.

For some reason, the sustain pedal only intermittently registers full sustain and other times only goes to around 64 on the midi reading wtih Pianoteq 9.

So if you just slowly and steadily cycle the pedal down and up repeatedly with the Pedal Curve displayed in Pianoteq's UI, you don't see the level indcators move steadily up and down between 127 and 0?

I definitely can't repro that. I would think it was a hardware issue except that you report it continues to work as expected in the v8 VST3, and in the v9 standalone.

I can't imagine what would explain all of that. I can only suggest to try the VST3 in the free tier of Sonar (very few limitations vs. the paid version) or some other DAW to confirm it's not just some interoerability issue between v9 and Ableton, specifically.