Modulator Management/Integration/Protocol (Currently there is no way to save complex setups)

There’s many conundrums with Modulator Integration:

Saving a plugin preset does not save modulators assigned to it.

None of the following restores Modulator assignments:

  • Saving a plugin preset does not save modulators assigned to it.

    • Because there is a limitation of 8 Modulators, this creates a conflict if there are already modulators on the channel at hand, what would happen if Plugin Presets did store Modulators.
      • This begs the question, if Modulators shouldn’t only be channel based, but also isolated to be plugin-shell based as well.
  • Import Tracks From Project

  • Import Track Archive

  • Save Track Preset

  • Duplicate Track

  • Individual Modulator Presets don’t store/restore Assignment Values, which could be integral to the users developed “effect” of that modulator.

    • Modular Presets should restore Assignment values and show the missing assignment as Red text, allowing the user to understand what the Assignment was assigned to (plugin name, parameter name) and then they can make those reassignments manually to the same plugin, or to a different plugin (many plugins have the same parameter - for example, frequency cutoff)
      • There could be an amenities to resolve this further:
        • Quick Re-Assign Missing Assignments button/feature to connect all Assignments to a selected plugin in a list, (if it’s the same plugin it would be 1:1, if it’s a different plugin the user would to manually choose parameters)
        • If the plugin doesn’t exist, the software offers to add the plugin for the user to the first available slot and automatically make the assignments.
  • There is no Preset System for the entire Modulator Chain/Bank

    • There is a fair amount of creativity in making internal Modulator Assignments to other Modulator parameters - but it can’t be saved.
    • Loading a Modulator Chain/Bank preset should offer the same Modulator Preset amenities as described above for individual Modulator Presets.
      • Again, the contention conflict is if users already have inserts loaded and there isn’t enough room.

The end result of the current Modulator paradigm is, once you create something cool… It is essentially stuck there. There is no way to save/recall it, transfer it, or duplicate it… You would have to do it manually, parameter by parameter, assignment by assignment.

There is also a bug in which Modulators disappear which is making me second guess if I should implement them at all into my work:
There is also a bug: Modulator assignments disappear from projects?! - Cubase - Steinberg Forums

Solutions:

Thanks

Interesting points.

I’m currently using Cubase 13 and I can’t perform the following test, but i’m curious to know how do the modulators and their modulation assignments behave when being saved as Cubase track presets ?

in my tests, destinations are not saved with Track Presets but I’m not sure if this is a bug or a lack of integration/

Sounds like a lack of integration to me. I would expect the modulation assignment to remain intact with track presets for sure.

a thread on that specifically

Modulators Don’t Save Destinations with Track Preset - Cubase - Steinberg Forums

Yeah, the Cubase track presets should function similarly to Ableton Live’s racks or Bitwig Studio’s containers.

unfortunately it seems, many do not use Modulators… so it has been very hard to troubleshoot these problems and get them attention.

I was very pleased to see them implemented into Cubase. But it certainly seems like there are some issues that need to be addressed.

Can only hope :crossed_fingers:

There more I sit on this and think about it, the more baffling it becomes to me.

From a development perspective, how can this even happen?

This is literally a definition case example of “adding features on paper for the sake of saying the software has them, that in use border on non-functional”

I’d almost call it a vapor feature. It’s as if it is a software-demo download where save is disabled and a bunch of features are missing… Except I’ve paid for it.

If I were a new user to Cubase and bought the version that added modulators in order to use modulators - my impression of Steinberg is that they have a sloppy development team, buggy broken software, bad top-down leadership oversight/development philosophy, and that they fraudulently add vapor-features to get money out of a new group of unknowing people every year. At the most, I would be rating the software 4/10.

That would be my impression as a new user seeking to use Modulators.
If also factoring in this bug: Modulator assignments disappear from projects?! - Cubase - Steinberg Forums I would be asking for my money back. It was one of the reasons I upgraded, and there has been no comment from anyone at Steinberg on the bug nor the integration problems.

It really makes the notion/sentiment more real, that Steinberg releases half-baked features and then takes years to set them straight, if ever (VCA’s anyone), and instead of fixing them, releases more half-baked features.

Bugs happen, but lack of integration is no excuse.