Bypass automation of stomp effects in the Amplitube 5 plugin doesn't work

[M1000]

The automation of the bypass of stomp effects in the Amplitube 5 plugin doesn’t work in Cubase 14.0.10. It is written but ignored by Cubase. The automation of other parameters works.

• Bypass automation of stomp effects works in Ableton Live 12 with Amplitube 5.

• Bypass automation of stomp effects works with Amplitube 4 in Cubase.

So I guess it has to be a Cubase problem.

[Nico5]

@M1000

Bypass automation of stomp effects works with Amplitube 4 in Cubase.

Wouldn’t that imply that something changed between Amplitude 4 and 5?

When you’re comparing the various scenarios, are all of them using VST3 or is there a difference when VST2 and VST3 is used?

It may still be a Cubase problem, but your description also leaves the possibility that it’s an Amplitude 5 VST3 problem?

[M1000]

@Nico5

When you’re comparing the various scenarios, are all of them using VST3 or is there a difference when VST2 and VST3 is used?

All are VST3.

@Nico5

It may still be a Cubase problem, but your description also leaves the possibility that it’s an Amplitude 5 VST3 problem?

@M1000

Bypass automation of stomp effects works in Ableton Live 12 with Amplitube 5.

[Nico5]

Your point about it working in Ableton wasn’t enough of a hint by itself, since - at least in theory - your Ableton project might have used the VST2 version of the same plugin, while Cubase 14 is likely to use the VST3 version. – So your confirmation, , that both Ableton and Cubase are using the VST3 version is a meaningful piece of info.

Also: I’m not questioning your experience or the severity of the bug. I’m merely trying to help pinpoint the exact circumstance of the bug.

While I’m just another user, I know enough, that bugs that can be easily and reliably reproduced tend to get fixed faster.

[M1000]

Just tried in Cubase 13.0.50 and it works flawlessly, so it clearly is a Cubase 14 problem.

[Nico5]

Related thread:

Automation has no effect although seems to be read correctly

One thing that changed from Cubase 13 to Cubase 14 on Windows, is that Cubase 13 defaulted to allowing VST2 plugins, and Cubase 14 defaults to exclude VST2 plugins. So my theory currently is: It’s possible that the different behaviour is caused by the same Cubase project using the VST2 plugin in C13 and using the VST3 plugin in C14. – This may not be obvious unless you specifically look for it. So if the Bypass handling has to be programmed slightly different in VST2 vs VST3, it’s possible th…

[M1000]

Not in this case. I also used the VST3 Version of Amplitube 5 in Cubase 13.

[SzhamplerPad]

I figured this out. I think It’s Cubase’s fault. Cubase is assigning the wrong type of automation lane to Amplitube’s parameters so the values aren’t being read unless they are written just right (unless the Amplitude plugin reports the parameter incorrectly, but Cubase should allow for changing the lane type regardless). The automation lane should be a simple on/off binary lane with only 0/1, but it’s acting like a regular midi 0-127 value lane.

To get it to work you have to put your automation points on the first y-axis increment from the center (when you see the ‘value’ property in the editor info bar change) for on or off value that you want (correct value is inverted though).

I haven’t found a way to change the automation lane type, I know for other automation lanes the type can be changed, but not here unfortunately. I hope Steinberg makes the lane-type editable so this doesn’t require a permanent work around.

[M1000]

Meanwhile I’m on Cubase 15.0.30 and Amplitube 5.10.9 and can’t reproduce the problem anymore. Everything works fine now. Maybe something has changed in Cubase 15, can’t pin it down exactly though.