Integrated native plugin Chainer Insert (Steinberg official "wrapper"/Insert expander)

It’s time.

I think instead of Steinberg releasing their own VST Plugin Chain Wrapper, they design something that is just integrated into Cubase engine/Insert system.

  • It would allow users to insert Chain FX Presets into a single slot
  • Users could name their Chains/FX Chain Preset name would show as the insert name.
  • Fixing problematic source material can often take up all inserts on a source channel
  • It allows user to select multiple inserts with plugins on them, and condense them into a chain automatically ordered in the chain as they were on the insert bus, freeing up insert space.
  • It allows users to re-order multiple groups of plugins quickly, ie I’ll have multiple stages of processing on a channel and I organize those plugins with empty insert spacers.
  • It allows for A/B for multiple plugins and changes across multiple plugins, rather than only individual
  • It allows for easier copy/pasting/dragging of multiple plugins to other channels of which might already have other unrelated inserts on them.
  • It allows users to have a variety of chains templated/loaded onto for example, the Mains Bus of which they can quickly bypass audition different chains, re-order them, etc.
  • It allows users to create an Channel FX Chain Preset of multiple Insert Chains
  • It helps keep the MixConsole for users less cluttered with FX that are meant for single sources contained within their channel inserts, and leaves FX channels in MixConsole for more traditional multi-source FX (Room Reverb, etc)
  • Tied into Cubendos Plugin Manager/Lists

There’s very cool additional features that Chains could have integrated.

  • Integrated modulators
  • Hover over Insert plugin overview (would show you which plugins are contained and in order)
  • Input/Output gain for the entire chain (gain staging)(Auto-Gain akin to LetiMix GainMatch)
  • Mix Level for the entire chain
  • Mix Level for individual inserts within the chain
  • Integrated Internal Send/Returns
    • This would allow FX Chain Presets, to really be a complete sound “package”. Ie, a users post-processing on an FX such as reverb, doesn’t need to be serial affecting the dry.
  • Parallel/Serial processing
  • M/S Processing
  • L/R separated inserts
  • Complex matrixes can be created
  • Sends can be returned either to a return in the serial, or the final output stage of the chainer
  • Integrated Quick Controls

The current problem with Cubase is - what the user creates does not have an easy pathway to being contained and saved as a single entity…

  • You have FX on separate channels
  • You have modulators that are sort of an exterior controller not on the channel
  • If you run out of Inserts, you have to create a serial connection to a group channel.

Sometimes I have very complex processing topology that spreads across multiple channels, sends, group sums, etc. The only way to contain all of this is by using Track Archive which:

  • Isn’t integrated preset system that shows up in MediaBay
  • Annoying and complex to create from an existing project (channels might be all over the place)
  • Is not as cool, efficient, flexible, immediate, adaptable, transferable, saveable, loadable, versatile, instant, inspirable, motivational as what I have described.

This would improve things for

  • Mix engineers who do FX heavy mixes
  • Mix engineers working with problematic source material/restoration
  • Mastering Engineers
  • Sound Designers - Video Games/Post-Production/etc
  • Experimentation
  • Electronic musicians/producers
  • Everyone who has been asking for ‘Mix’ level per insert slot
  • Every who appreciates work efficiency, saving presets, templates.
  • Clients, getting them to hearing a variety of sounds faster which might have complex chains.

Thanks

Huge competitive feature, this would make other DAW users jealous.

To be able to quickly load a preset like this and instantly hear the sound, the thing you created that does that thing - and not have to use some unstable 3rd party wrapper which doesn’t have DAW integrated features… would be fantastic.

FX sends would get real fun. Sound-Design will be faster. Creativity will be faster.

4 Likes

No objections to this feature request, but, FWIW, I’ve had pretty good luck with doing most of what is outlined here on the functional needs with Waves StudioVerse Audio Effects.

The key thing that it probably couldn’t cover on the functional side is embedding modulators within a preset. You also can’t just hover over the plugin and have it show you what’s inside – you need to open up the plugin instance to do that. It also wouldn’t be able to use Cubase’s plugins that don’t conform to the VST3 standard, which is, in my view, a limitation of Cubase’s plugins more than the third-party plugin-hosting plugin. (I don’t personally use many of Cubase’s built-in plugins because I already had lots of third-party plugins prior to moving to Cubase from SONAR, and I’ve added quite a few since then.) But in can handle most of the rest, and it’s been very stable in my experience.

Kind of related, but one thing Waves instrument plugin cannot do, is load multiple EXTERNAL(not waves flavored) instruments in a single chain…Oh how I wish it could!

Other than that, it’s a great alternative.

Yup for sure, there are some good ones out there, they’re all pretty decent

-DDMF Metaplugin
-Nugen SIgMod
-BlueCats Patchwork

I haven’t used the particular one you’ve mentioned

But there could be all sorts of benefits to being integrated and deeper. Being tied into Cubases side-chaining system and having that integrated to all the inserts within a Chain. Tied into Cubases Plugin manager instead of depending on the 3rd Party VST Wrappers plugin manager/search.

And a more modern logical intuitive GUI, modern UX that is complimentary of the Cubase GUI/UX.

To be honest, I haven’t played much with StudioVerse Instruments, but I see that you’re correct that it can’t do non-Waves VST3 instruments.

I have used the StudioVerse Effects (and prior to that StudioRack), which can load third party VST3 effects (Instruments can also load the effects, but not the instruments) a fair bit, mostly for scenarios where I want a complex plugin chain and/or routing on a single instrument (or potentially audio) track, rather than having to have a bunch of effects and/or group tracks to do a similar thing.