MPC 2.11 vst not working on Mac

Hello

Just installed MPC software 2.11 and neither S1, Ableton or cubase are able to scan the updated MPC.vst plugin.

Have you this issue ?

Thanks

Please give more info, macOS , intel or silicon etc

Big sur last version on Intel i7 2020 MBP

Similar here! No VST!

Windows 10|
intel i5
Reaper 6.64

As a DAW, the software works wonderfully even after the update. I can integrate my Mpc One as a controller.
But I can not use it as a VST. What happened there? Does anyone know advice?

Cubase and Live can scan and open it fine here, but there is no text in the plugin, or even the standalone application anywhere on macOS Ventura beta 2 hah. The weird part is, I just installed the 2.11.3.5 update, and even in the installer, there is no text in the boxes on screen after you select your MPC model heh.

Wonder what Akai is doing differently that no other developer seems to be doing that made all the fonts in both the installer and application disappear. Every other plugin and installer I've run on Ventura is perfectly normal as it should be.. What the hell is Akai smoking over there?

Monotremata wrote:Cubase and Live can scan and open it fine here, but there is no text in the plugin, or even the standalone application anywhere on macOS Ventura beta 2 hah. The weird part is, I just installed the 2.11.3.5 update, and even in the installer, there is no text in the boxes on screen after you select your MPC model heh.

Wonder what Akai is doing differently that no other developer seems to be doing that made all the fonts in both the installer and application disappear. Every other plugin and installer I've run on Ventura is perfectly normal as it should be.. What the hell is Akai smoking over there?

You’re not really surprised it doesn’t work on a beta release of an apple OS are you?

It barely holds together on a non-beta OS as it is.

Thought I'd add to this. I'm experiencing exactly the same since I updated to Ventura 13.0

Strange I am having the same problem for awhile now with cubase 12 and maschine software.. I cannot load the vst it hangs I have to move it out of my plugin folder weird.... sorry windows 10 user

Well I figured it out my DAW is normally offline I signed into ilok and and can load in my DAW now..

Hello

I found the solution

0/Remove from blacklist in your DAW the MPC Plugin and close the DAW

1/Rename the Expansions folder and Content folder before the plugin scan of your DAW.
Folders are in :
MAC
/Library/Application Support/MPC/
~/Library/Application Support/ MPC
Windows
C:\ProgramData\Akai\MPC

2/Start the DAW and make the plugin Scan

3/Open the MPC Plugin

4/Close the DAW

5/Move back the Content and Expansion folders to their original name

6/ Restart your DAW and load the MPC Plugin

All is working as it should be.

I have a similar issue. The MPC 2.11 software is showing empty text as per your screenshot. Im just testing the software as we considering buying an MPC One again. This is putting me off - any ideas what causes the problem? Im trying open the MPC software on a MacBook Pro 14" M1Pro. I've tried deleting all the MPC software on my computer and re-installing, but same issue exists.

I don't yet have the MPC hardware and couldn't understand your steps regards getting it to work via Ableton. I am just trying to get the software to work standalone outside of a DAW.

robleighton22 wrote:I have a similar issue. The MPC 2.11 software is showing empty text as per your screenshot. Im just testing the software as we considering buying an MPC One again. This is putting me off - any ideas what causes the problem? Im trying open the MPC software on a MacBook Pro 14" M1Pro. I've tried deleting all the MPC software on my computer and re-installing, but same issue exists.

I don't yet have the MPC hardware and couldn't understand your steps regards getting it to work via Ableton. I am just trying to get the software to work standalone outside of a DAW.

Are you completely up to date with the software? They mentioned in one of the 2.11 releases they fixed the 'no text' bug in Ventura, despite not labelling Ventura as supported. I just opened it and it looks fine here on 13.1, says I last opened 2.11.5 for that must be when they fixed the bug.

yup that was it - newbie error. thanks 2.11.1.7 works with Ventura.