Is Cubase ever going support third party Midi Plugins?

If someone can point me to some candidates..I see the value but on a ladder of priorities; its not very high esp when even cheap hardware already has it built in. I would rather see really important workflow improvement, proper api that can handle full automation, mixer with snapshot and state morphing, modular routing and more professional ui/ux with docking with a better and easier integration with hardware tbh…I use reaktor and it has wild midi control. There are already decent modules in midi right now if you spend some time studying…but point me; I’ll have a look. I use ableton and I think cubase offers more midi built in…a midi version of xphraze would be cool…I thought modulators expand scope hugely .but yeah a lot more pro upgrades where it counts…

Just my 2c

there is a lot of useful stuff there, I could have them preloaded in lots of tracks in my template.

maybe you could just let us ask for the feature we need on our daily work

just my 2c

“My advice is to stop looking to machines to do it for you…learn to play and your music will feel way better…”

Why would a technical requirement of mine, such as MPE to poly aftertouch, which Steinberg’s MIDI plug-ins do not cover, and likely never will, equate to not being able to play? I’m not asking for a one-finger symphony.

You didnt read my posts…I particularly mentioned MPE as being valid. When Ableton finally got MPE I thought…great! But unless I have a Roli etc the expression it offered was for realtime so please, educate me with some examples? eg place a link to some audio that displays the need and how it stops your work; are you simply collapsing MPE to single channel for non MPE plugs or? Would be interested to know

Thanks for the link…back to the OP that framed this thread: This, from what I can see already works by using a proxy track?

That plugin still works as a script for kontakt…? The main use seems to be tympanic rolls;

My point is resource for Cubase is scarce…I would happily sacrifice one of my votes for really important stuff. MPE might be worth but…Im not sure how it compares to the features I mentioned…convince me and you get my vote but this seems to be about realtime vs eg mixing…mixing stuff like snapshot state would get all my votes because even the concept is misunderstood and its results are revolutionary…pity it started with Kore which was so totally misunderstood…3 decades ahead of its time

I am collapsing MPE to a single channel for a hardware synth that is non-MPE, but poly aftertouch.

Yeah that is totally fair. An additional utility module for the latest upgrades (well not so “latest” now lol) to the spec.
Steinberg should have definitely done this by now

Definitely bread and butter need

there are many useful purposes for midi plugin support that have nothing whatsoever to do with being capable or not capable of playing a keyboard midi controller.

I did play around with using AI agents and investigating the ages old midi sdk… and was able to get something working and learn about how that Api is designed. It would be really useful of Steinberg either resurrected this SDK or brought this capability officially into VST.

What I can say about that older SDK is: first the publicly available version of that SDk is not up to date. Cubase itself is attempting to make some calls into these plugins which are not documented in the current publicly available SDK. yes Steinberg is still using that SDK for their internal midi plugins. And its possible to use the old version of that SDK to make a midi plugin and it will show up in cubase, I haven’t tested extensively to see how well everything works, but also Cubase seems to be looking for more information that is not documented any public version of that SDk..just some old archives are all I can find.

secondly, in order release a midi plugin into the wild, you need license agreement with Steinberg for this particular SDK, which they don’t appear to be giving out anymore. So yes, there was an SDK…yes it was possible to make plugins, still somewhat possible, but since then they have pulled back from supporting public access to that SDK and so they have their own built in midi plugins, but there is no official way to get a license to use the most up to date version of it…I mean you can always write them and ask of course.

Third, the Api shows it’s a substantially different approach to midi manipulation compared to how VST midi plugins work. It actually offers a great deal of built in midi functionality that VST does not. Its also not as granular as VST…VST is accurate down to the sample…the old midi plugin Api is not as granular, but it’s more designed specifically around how to handle midi events in a variety of ways. It does not handle midi2 nor MPE…maybe their internal newer SDK might, we don’t know.

I think the truth is most people would prefer to make midi plugins using VST because then the resulting plugins can be used on a wide variety of hosts. Whereas this plugin format absolutely only would work inside Cubase. But it’s also true that the VST api is not meant to do extensive midi manipulations, its meant to receive midi input and use for generating sound, with a reluctant ability to also output some midi. People are making midi plugins anyway, despite those limitations in VST api,…and well it would be nice to be able to use those plugins in Cubase inline with other instrument plugins for sample accuracy.

I think it’s very unfortunate they have overlooked this need and desire for so long. Insertable AUmfx midi plugins are used all the time in the LogicPro world.

Another question would be “Will Steinberg ever let MIDI Plugins out of ‘Pro’ jail?”