I’ve encountered a bug in Cubase 14 involving plugin automation. When automating the bypass state of Replika, the Read indicator shows the changes correctly, but the plugin’s effect isn’t audible when it should be active.
The issue resolves temporarily by manually toggling the bypass off and on in the plugin interface, but this workaround is impractical with multiple plugins and automations.
I have noticed this also with other plugins i was experimenting with, but never seen it in the past. Anyone else has this issue?
Unless I’m missing something your pic looks normal to me. At the Cursor position the automation is a 1, meaning that the Bypass is enabled. And when Bypass is enabled you shouldn’t hear the Insert. You probably want to invert the automation?
Yes, that’s correct as it is. The plugin is bypassed and should only be enabled when the curve dips (the insert visually turns ON and OFF as expected during playback). However, while the visual automation works, there’s no audible effect.
If I manually open the insert, toggle it ON and OFF, and then play it back, the effect is applied to the sound.
See images below please notice the Reverb channel meter activity while the plugin is ON (sorry that’s very little in the image)
File opened:
After turning ON and OFF the insert manually ( I think i actually also have to turn OFF and back on the Read Automation in order to make it work properly)
Hi, no I just put the plugin in the slot and draw the automation.
Deleting the plugin and using a new instance works but that’s not a viable solution especially cause I noticed this behavior also with other plugin i was experimenting with (don’t remember which ones though), Replika was definitely the last one I tried and I realized it was effectively a real problem and not a fluke.
Hope someone takes a look into it.
I’m just another regular user, but I know enough, that bugs that can be easily pinpointed and/or reproduced by the developers have a much better chance to get fixed quickly.
My questions are entirely motivated to increase the chances of getting this fixed - and not to downplay your experience and the severity of the bug.
In that spirit:
Is it only automation for Bypass or also other VST automation parameters?
If it’s only for Bypass, that could be a big hint for developers to look in the right place.
I’m asking because just yesterday someone else also posted a problem with VST automation for another plugin - but that was specifically for Bypass, while other parameters seemed to work ok.
Again: This is not to question the severity - but to potentially help pinpoint the bug, so it gets fixed faster.
I don’t have that plugin, but the only problems I’ve had in the past with bypass automation was related to iZotope plugins. My impression is that this is a problem with 3rd party companies not programming correctly. You should reach out to this company and ask them about it.
Yeah it would also be cool if someone from Steinberg could confirm this is not about Cubase, I had the impression that from the replies in the this post and the other about Amplitube with the same problem was maybe something that regarded the host rather than the plugin itself.
Anyway I will try to reach out NI to see if on their side too.
As a workaround, you might want play with using Replika via SENDs: automate the sends level on your track, or the volume level of the effects track, where Replika is located.
Can confirm I too have been facing this issue almost every time I write plugin bypass toggling on/off, regardless of what plugin it is. Since Cubase 13.
Yeah I do have workarounds, what is annoying is that I paid for both software (Cubase especially I buy the update every single year at launch date) and no one of the manufacturers is giving sign of listening.
But if it only affects Cubase since version 13, then also Steinberg must have changed something. Maybe raised the compatibility level from VST2 to VST3, or something similar.
Yeah, that’s the ticket I submitted today. I sent them a video and the project. I’m pursuing this issue to get to the bottom of it, but just for context, I’m not a musician, and my job has nothing to do with audio. Honestly, I could replace Replika with something else since I’m just experimenting.
What’s really disappointing, though, is the stark difference between this support forum and the Cubase support forum. Please don’t get mad, Steinberg folks. I’ve always had a soft spot for you. I keep buying Cubase even though I hardly use it (in fact, I made zero music with Cubase 13 last year). But when it comes to support and customer care, there’s clearly room for improvement compared to this forum.
For instance, take a look at the first six posts in my other support request here (I also linked it in another topic, it’s a Mac issue as well, not just Windows). To me, it seems like a pretty legitimate request. I didn’t ask for Cubase on Linux or anything major, just for a blatant functional UI bug to be addressed.
I get that fixes aren’t always straightforward. I’m a programmer myself, working on large codebases, so I know the challenges. But at the very least, acknowledging customer requests goes a long way compared to outright ignoring them.
I´ve experienced this issue many times while automating sends, with different plugins. When I create the automation wverything works fine but then at some point it just stops working. Everything looks fine but I can´t hear the changes.
