By foxes
Mon Aug 02, 2021 9:44 pm
foxes wrote:Hi Guys,
I downloaded and installed update MPC V2.10.0.82 and I have been using MPC V2.9.1.4 with no issues on OS High Sierra 10.13.6. (I also have MPC Beats v2.8.3 installed as well)
After installation I’m only able to boot up MPC 2 in standalone.
Even though the AU (component), the VST and the AAX are in their correct folders I am unable to use it as a plug-in.
In Logic Pro X 10.5.1 (AU), MPC 2 does not show at all in the but MPC beats shows up fine.
In both Propellerhead Reason 10.4.1 and Reason Suite 11.3.9 (VST), trying to load MPC 2 gives me a message “Failed to open file” but again MPC Beats opens fine.
And in Pro Tools 2021.6 it causes Pro Tools to hang during the plug-ins scan and I have to ‘force quit’ PT then remove the MPC 2 AAX file from the PT plugin folder in order to boot up PT. And again MPC beats loads fine in Pro Tools.
I running OS Mojave 10.14.6
There definitely seems to be something wrong with AU, VST and AAX components on MPC 2.10.0.82
Is this a known issue or something else?
Thanks
The quote above is my post here on this thread and also what I sent to Akai support.
Below is the answer I got back from them:
Thank you for your support request, I’m sorry to hear you’re having trouble with your MPC software.
Firstly I try completely removing the MPC 2 software including plugin files from your computer and performing a fresh install using the file in the link below.
MPC 2.10 (Mac)
If this does not resolve your issue could you please try installing the previous version of MPC 2 to see if this restores functionality for you.
zip icon MPC 2.9.1 (Mac)
If you could please try the above and advise on the results, with this information we will be able to assist you further.
I haven't tried what he has said as yet due to time restraints, but checking the V2.10 MPC file he has asked to me to download, it is exactly same file as I originally installed 2.10 with (same specific version with the same 'created' and 'modified' date as the original I have), I'm wondering is it worth all the deleting and re-installing as I feel I will get the same issues that some many of us on here are suffering?
I replied to him stating that the plugin issue is happening to everyone too (Windows & Mac OS) and sending him a link to this thread. It is definitely a bug with AAX, AU & VST plug-in components in this version.
Hopefully Akai will see this and get a fix quickly.