Loading VST Effects?

Is it possible to load VST effects in MixKey? If not, are there any plans?

Adding compression or EQ to a microphone would be useful.

Hi,

No, this is not possible at this moment.

I’m sorry, I’m not allowed to talk about the further plans.

For future reference, that statement tells us exactly what you’re not supposed to say. If adding support for plugins was NOT something Steinberg is currently working on, you would have either said something like “We’re always interested in hearing what features customers would like to see. I’ll pass along your suggestion.” or took note of the post and moved on without commenting. Since VST is Steinberg’s format originally intended for the longest running DAW in the game (Cubase) and the current version is VST3, we can surmise that Steinberg is currently working on (or at the very least, at the planning stage of) adding VST3 plugin support for MixKey.

I feel like a dick for not being able to stop myself from pointing that out because I’m worried that you might get in trouble over the comment. So, I need to make 2 things clear.

  1. I’m literally a genius. My 166 IQ isn’t just a number. At the age of 5, I taught myself Latin by memorizing the words in both the English and Latin Catholic masses my grandma used to drag me to, to gather an extensive Latin vocabulary and understanding of the rules of Latin grammar, which I then used as a translator to understand and speak in Latin.
    Recently, I taught myself to code in the JUCE version of C++ by first writing out “If _, do _” logic for an advanced plugin that I needed for my work as a certified Dolby Atmos engineer but didn’t exist. Then, I spent 2 or 3 weeks looking up the proper formatting to translate it to the JUCE version of C++. Its been nearly now, as I get ready to release it, but my game-changing plugin for stereo and immersive only took me 2 weeks to develop by myself with absolutely no knowledge of coding beforehand. The only thing making it take so long was that I didn’t know how advantageous it would be to design the GUI before coding, I’m a perfectionist who spent most of the year designing the GUI elements in GIMP3, learning about servers, developing my own licensing system because PACE wants too much money, I had a terrible idea to make the forum login unified with users accounts (which I abandoned because it was buggy and created security vulnerabilities for the accounts which are hosted by the API server I used for licensing), and the biggest hold up is not being able to hire anyone for little things like 3D modeling and web design because I invented several new tools that I’m holding off on patenting until I’m ready to launch so that I can earn the obscene money I need to pay to patent in every country before the provisional patent expires. That’s what matters most because one of the patents is so essential that what will blow your mind isn’t that I figured out how to do it, but rather the fact that something so seemingly obvious didn’t already exist. Steinberg will know of it in about a year, after I’ve secured my patents and begin licensing it to every software and hardware company out there.
    My point isn’t to brag. Its to inform anyone above you that its not fair for your boss to reprimand you in any way. You didn’t reveal anything. I’m just abnormally good at figuring things out.

  2. The moment Steinberg announced an audio mixer for streaming, VST3 support became a no-brainer. VST support for OBS’ mixer is the top requested feature by anyone who streams studio-related content and VST is a Steinberg product. So, you guys would have to be morons to create a mixer for OBS streamers and not offer VST3 support. In fact, the only logical explanation for not offering VST support on day1 is that either you rushed to market to beat a competitor to it or VST3 support will, for some reason, require a lot more work than it seems and Steinberg wanted to make sure there was a market for it before investing in the man-hours required to do it. I would say there’s the third possibility that Steinberg is reserving that as a feature for an upcoming MixKey Pro release, but the sensible thing for that would’ve been to launch the pro version on day1 so that customers don’t feel manipulated and rage about you giving them something free to get them reliant on your product and then charging them to get the features they want later. Of course, that still may be the case if VST3 support ends up being a paid add-on to get paid without making users turn on you. However, that would still be a bad idea if the license to integrate VST3 support is now free, like the license to develop VST3 has become because it would allow your competitors to make a knockoff version that supports VST3 at a lower price.

So, your boss should know that while the cat is out of the bag because of your comment, its not your fault. You technically didn’t break your NDA and they should’ve waited another month or so to release with VST3 support on day1 if they wanted it to be a surprise.:wink: