Korg VST3 plugins: Instrument Automation Device problems - all parameters are initially zero

Help, Support & Bugs
1

Description:

Re-enabling an instrument automation device seems to disable a VST instrument’s audio.

Program changes in the VST restore instrument audio.

Steps to reproduce:

  1. Open Renoise
  2. Load a VST instrument plugin
  3. Load an Instrument Automation Device pointing to that instrument
  4. Disable the Automation Device
    4a. Play the instrument to make sure it can be heard
  5. Re-enable the Automation Device
  6. Play the instrument

Expected results:

The instrument generates audio after re-enabling the Instrument Automation Device.

Actual results:

The instrument does not generate audio after re-enabling the Instrument Automation Device, despite generating audio as expected before the automation device is loaded, after the device is loaded, and after the device is disabled.

If the VST instrument undergoes a program change via its external editor, it then generates audio as expected.

automation device behavior

2

NB: I’m using Korg MonoPoly, which does not support program changes from Renoise’s plugin properties menu.

3

When enabling the device, it sends out all its parameter values. The parameter values don’t look like they are correct in your example. They are all zero.

So this is not a general problem, but a problem with a specific plugin.

I’ll check why the Korg plugin’s automation does not work, but this should work with other plugins.

1 Like
4

Just checked this with other hosts: on Ableton Live its also broken. Parameter values are not updated correctly when loading presets in the Korg VST3. In Reaper it somewhat works - maybe because they are manually updating the parameters.

The Korg plugins neither send parameter automation change via VST 3 SDK: EditController Class Reference nor in batch via VST 3 Interfaces: Steinberg::Vst Namespace Reference so host’s have no clue that some parameter changed in the plugin.

I’ll report this to Korg. There’s nothing we can do here (well, should do here) to fix that.

4 Likes
5

Thanks for the explanation and for reporting the issue to Korg!