Modartt user forum - Reaper automation of piano parameters - Online rendering only

Re: Reaper automation of piano parameters - Online rendering only

null@example.com (olimoth) — Sun, 21 Mar 2021 07:09:02 +0000

I contacted support about this issue, and the suggestion was to use fewer automation points.

In Bitwig Studio I was able to achieve this by quantising the automation

The top modulator modulates the second one (red arrow) which quantises its input to eight steps instead of continuously.
This sounds the same to my ears and renders faster than realtime.

Re: Reaper automation of piano parameters - Online rendering only

null@example.com (tom_) — Sat, 18 Apr 2020 13:40:12 +0000

I tried a little more. For example, if I automate "Strike Point" by LFO in Reaper and no other Pianoteq parameters, it works. But if I e.g. automate "Strike Point" and "Blooming Energy" with LFOs each, this bug will occur: "not rendering, ETA infinity" -> rendering window freezes

Then only online rendering works. But this is too slow for me.

I tried it with the latest Pianoteq 6 Pro version (tested with the VST3 and VST version) and the latest Reaper version.

UPDATE: It does not seem to crash completely in offline rendering mode, but to render extremely slow (90x more time than the rendering process takes if I automate only one parameter via LFO). After a longer time the rendering window also refreshes itself and looks normal (but freezed).

Reaper automation of piano parameters - Online rendering only

null@example.com (tom_) — Wed, 08 Apr 2020 15:20:14 +0000

Automation of individual piano parameters with Reaper DAW allows for online rendering only.
Offline Rendering crashes Reaper if individual piano parameters of Pianoteq are continuously changed via automation.
Is this a bug in Pianoteq? This is costing me a lot of time.