[Bug Report] Reaktor controls "set to default": Value does not change in the plugin host

anzbert

Problem:

When you map a Reaktor knob or fader to a control in a host program like Ableton 12 or Maschine 3.0, both control move in tandem. When you move the knob in Reaktor, the value changes in the host, and when you move the control in the host, it changes in Reaktor. So far so good.

When you double click the control in the host, the knob moves to the default position, as expected.

The problem occurs when you set the value to default within Reaktor, either by double clicking or by right clicking and selecting "set to default". In that case the value remains stuck in the host.

The same also happens when you use a secondary control in Reaktor (for example with IC communication) which moves the original knob. The host control also remains stuck then. This is particularly annoying, since it makes patches that have multi-parameter controls very unreliable, as host values remain stuck on outdated values.

In other NI plugins, like Massive X or Guitar Rig 7, this works as it should. Setting a value to default also moves it in the host. That kind of tells me that this is a Reaktor-specific bug.

For context: I am on macOS Sequoia and am using Reaktor as a VST3 plugin.

Any help is appreciated!!

Thanks!

anzbert

I am trying to submit a bug report in the NI support system, but I've been waiting for the support ticket email for days now 🤷

edit: received the email now and submitted a bug report to NI.