VST3 Bug Automation - Subsequent 37

[m0tabh]

Hi guys,

Since Moog release VST3 editor for subsequent 37 i can't write automation on VST3 version.
Its very strange.

I'm using Cubase 12 on a mac. The VST version works, but not in a way that I'm looking for.

I have a "External Instrument" on Cubase, that already link audio input and output to a track. In this track I'm using the Subsequent 37 VST FX.

If i try to record the automation moving moog faders by hand, it record only midi cc, not VST automation, even the VST showing the knob moving when i change something on hardware. I don't know if is a real issue since midi is sending to my daw from moog.

So, if i use VST3 version, another thing happens: I can write an automation using the VST knobs with mouse, but if i assign something to control that knob on VST, nothing happens. The knob change parameters to assigned controller, but the assigned controller don't change the VST knob... very weird.
And in this case, the automation make by VST don't work, don't do nothing. Only automation created by MIDI CC Control like in VST version.

Has anyone experienced this?

[oli@sub37]

Just hit the same problem today. It used to work fine in earlier Cubase version, but automation of most parameters is. broken after recently upgrading to Cubase 13.

[oli@sub37]

I did some more tests today and found that the automation still works fine in the VST2 version of the Editor, but does not work in the VST3 Editor or Editor-VI.

[oli@sub37]

Even more testing revealed: In my case the problem only happens with version 1.1.1 of the Subsequent 37 VST3 plugin. I also encountered severe problems with proper recall of presets. After reverting to version 1.1.0, everything seems to be working fine again.