STILL NO MPC VST3 TO OPEN WITHIN DAW

DISCLAIMER :
This post is not about ability of MPCs to open VST3 plugins. It is about control and use of MPC hardware from within a DAW.

I thought MPC XL release would be perfect timing to release long awaited MPC VST3 plugin. No Christmas yet...

MPC VST2 does still open into older Nuendo / Cubase iterations but not anymore into latest versions.

If anyone has info about MPC VST3 release or if it will never happen, please share

Desktop is still missing the arranger and is so god damn buggy and lacking in so many QoL features.
Kind of amazed it got like not a single mention in the patch notes for 3.7
Its been out for 8 months now and has like one update nothings improved.
It messes up basic stuff like double clicking on a project file will open the software but it will load the default template and not the project you just double cickled on.
Or how windows positions and sizes are not saved and everything reverts to default.
which means several times a sessions I will be adjusting all these things as the software loves to randomly crash.
They shoved a alpha program out the door.

karlack26 wrote:Desktop is still missing the arranger and is so god damn buggy and lacking in so many QoL features..

Very interesting remark.

As MPC VST 2.15 plugin exactly reflects MPC 2.15 Desktop, it gives hope they will release MPC VST3 plugin once MPC3.x Desktop won't be in beta anymore.

One more thing which gives hope : MPC Tutor, who is "in the know", did not comment about MPC VST3 plugin will never happen

I’m waiting for it also since majority of my work flow is using it as a VST in Logic and Ableton.

Insane Mixaken wrote:I’m waiting for it also since majority of my work flow is using it as a VST in Logic and Ableton.

Makes absolutely no sense as to why this isn't an available option when we used to be able to do it in 2.15. Almost like they're weeding out legacy (older model) users out and using the new Gen as a selling point to grab the new gear. We'll see..

I've spent way too much time trying to transfer project stems from the MPC One to Reaper on my computer because the functionality of saving stems is broken. Just release the damn VST so I can return to the workflow I had back in 2.0 already. You got time to release new toys, you got time to fix your firmware OS and and proper software.

Cinetrax wrote:One more thing which gives hope : MPC Tutor, who is "in the know", did not comment about MPC VST3 plugin will never happen

I'm not 'in the know' over Akai's future plans, they don't tell me anything. At best, as a member of the user beta testing group I am given a release candidate a couple of weeks before public release. And in those cases I am under an NDA, so even if I'm 'in the know', I cannot comment.

MPC-Tutor wrote:as a member of the user beta testing group I am given a release candidate a couple of weeks before public release. And in those cases I am under an NDA, so even if I'm 'in the know', I cannot comment.

Good to know they might have humans working on it

Zlornick wrote:

MPC-Tutor wrote:as a member of the user beta testing group I am given a release candidate a couple of weeks before public release. And in those cases I am under an NDA, so even if I'm 'in the know', I cannot comment.

Good to know they might have humans working on it

All we know is that they have been releasing beta updates for the DAW, so they are definitely working on the MPC Software 'project'. The 3.7 update of MPC Software is a big improvement on 3.6, lots of features back in, but sof course still loads of stuff missing. Whether they eventually create a VST3 version of the MPC is anyone's guess.

I'm disappointed that this is taking so long, computer integration used to be such a huge selling point, but these days it's obviously very low priority for them. I assume that the number of people using the MPC Software is likely tiny compared to standalone users.

MPC-Tutor wrote:All we know is that they have been releasing beta updates for the DAW, so they are definitely working on the MPC Software 'project'. The 3.7 update of MPC Software is a big improvement on 3.6, lots of features back in, but sof course still loads of stuff missing. Whether they eventually create a VST3 version of the MPC is anyone's guess.

This is very interesting.

It seems creating a VST3 from a Standalone software is not so costly, at least for a company such as InMusic. Do I miss something here ?

My best guess is they would make it when MPC Software v3 would be considered complete.

there are some interesting vst-bridges out there. i used to use one a few months ago, but cant remember the name.
works like a proxy, you load this as vst3 plugin and it can also load vst2 plugins, which you can use then.

https://ddmf.eu/metaplugin-chainer-vst- ... x-wrapper/
metaplugin. its awesome.

Cinetrax wrote:It seems creating a VST3 from a Standalone software is not so costly, at least for a company such as InMusic. Do I miss something here ?

VST2 is officially dead. Steinberg has stopped issuing licenses years ago.

So what Akai is holding back is the API changes from VST2 to VST3. I'm not an audio plugin engineer so I don't know how much work this is for a single plugin. Maybe it is more complicated for a multi-channel plugin.

But given the slow progress of the desktop software as a whole I assume the team is rather small. Which means lack of developing resources is IMHO the main reason.

personM wrote:https://ddmf.eu/metaplugin-chainer-vst-au-rtas-aax-wrapper/
metaplugin. its awesome.

I use Metaplugin wrapper since many years. I tried in every possible way to open MPC VST2 (including through Metaplugin ) within Nuendo 14 but as soon as MPC VST2 is inserted, Nuendo 14 crashes (same with Cubase 14).

For now I am stuck with Nuendo 12 which is the last Nuendo version to not crash because of MPC VST2

MPC-Tutor wrote:

Cinetrax wrote:One more thing which gives hope : MPC Tutor, who is "in the know", did not comment about MPC VST3 plugin will never happen

I'm not 'in the know' over Akai's future plans, they don't tell me anything. At best, as a member of the user beta testing group I am given a release candidate a couple of weeks before public release. And in those cases I am under an NDA, so even if I'm 'in the know', I cannot comment.

I knew you were in the know