C14 Modulators broken - added in a plugin window

When I’m adding modulators like LFO in the instrument’s window (3rd party plugins), it’s completely broken, like it would be disabled.
To activate it, I must add another modulator (only Mod Scripter and Envelope Follower do the trick). After removing 2nd modulator, the first one doesn’t work again.
Tested plugins: Massive X, UADx PolyMax, Wavestate Native.

No problem when the modulator is added from the bottom tab or Inspector. Also, no problem when I’m adding a modulator from the Retrologue window.

The issue occurs on both PC and Mac. 100% reproduction rate.

Tested on:
Win11 Pro OS build 22631.4317, HP ZBook Fury G8
Basic Mac Mini M2, OS Sequia 15.1

What you mean by “broken”?

I’ve not tested it thoroughly yet, but modulators in Cubase are per-track and also probably can’t be mapped to devices pre- or post the one they’re attached to. Or maybe there’s a functional difference between mod added to the device, vs. one added to the bottom panel? Maybe that’s what you’re experiencing? It’s a bit confusing to have them on device, in the bottom panel, in stand-alone windows. The user manual isn’t very helpful either :frowning:

Please elaborate.

Broken like in the picture. LFO doesn’t work at all.
Like I said above, when I’m adding modulators from the Inspector or Bottom Tab, it works as intended. Only when I’m adding them from the plugin (top) window, LFO doesn’t work.

Wherever you add them, modulators will appear in all three places: the plugin top window, inspector and the bottom tab. Of course, as long as you modulate the instrument’s parameter :slight_smile:
EDIT: there’s no functional difference. You have just 3 different places where you can add modulators, depending on which way you prefer and yes, modulators are per track.

Yes, I’m experiencing this too. I add an LFO and it just does nothing. As if it’s switched off. As pointed out by the OP, when I add an Envelope Follow or a Scripter, suddenly my LFO’s kick into life! I’ve only tried modulators using the lower zone so far. Something’s not right!

Haven’t delved into it heavily as yet. Perhaps it’s user error but I don’t think so.

I’m running MacOS 14.5, M1 MacBook Pro.

1 Like

Please also list exactly which 3rd party plugins exhibit this behaviour.

I have this issue even if using no 3rd party plugins at all. Even just creating an LFO modulator without linking it to anything displays the issue for me (in a brand new project with a single audio track and no plugins at all).

2 Likes