MPC Vintage mode emulation hack not working for me in 1.7?

MPC-Tutor wrote:

THE ADVERSARY wrote:Did you see the post about having to get it working on 1.6 first before going to 1.7?

Yes, I was responding to Hellfire's recent post about it working just by re-scanning and rebooting 1.7 - thats not working for me.

There has to be a way to avoid requiring going back to 1.6 temporarily. I'm wondering, installed plug ins are listed in the MPC.settings file which is just a plain text file. Each plug entry looks like this:

Code: Select all<PLUGIN name="Maschine" format="VST" category="Effect" manufacturer="Native Instruments GmbH"
              version="V1.8.2.0" file="/Library/Audio/Plug-Ins/VST/Maschine FX.vst"
              uid="4e694d55" isInstrument="0" fileTime="138ecbbc508" numInputs="8"
              numOutputs="32" isShell="0"/>

So perhaps the vintage VST info could be manually added here?

When I went back to 1.6 all my VST's were there already including the Vintage Mode VST's. I then downloaded 1.7, this time I didn't rescan all plugins like I did the first time I ran into this problem. So basically switching from 1.6 to 1.7 without rescanning all plugins will keep the Vintage Mode plugins if you had them in 1.6.

Hey Andy curious question, when you were previously running 1.6 with the hack did it affect your stability?

When I had it enabled it made things freeze up a couple of times so I did away with the hack.

It doesn't work in 1.7 for a fresh install
If I do a ReScan all they disapear.
The way to go for me is:
Install 1.6 over 1.7 (Don't have to delete anything, just install it.Do it at your own risk)
Do the hack
Update to 1.7
Only use Scan New.

Sorry BornElevation I didn't see your post.
Mine says the same.

Been trying out a few things, including installing old versions of the vintage plugins, messing with the MPC.settings file (back it up first....), renaming the plugins etc.

Nothing doing , so I assume based on what people are reporting it is related to the functionality of the 1.7 plugin scanner itself, so I doubt there's any way around that other than to set it up in 1.6, update and then only ever use Scan New in the future when adding additional plugins.

THE ADVERSARY wrote:Hey Andy curious question, when you were previously running 1.6 with the hack did it affect your stability?

When I had it enabled it made things freeze up a couple of times so I did away with the hack.

When I was on PC, these plugins were causing instability for my projects and even some got corrupt. Haven't had any issues on Mac.

DJ Hellfire wrote:

THE ADVERSARY wrote:Hey Andy curious question, when you were previously running 1.6 with the hack did it affect your stability?

When I had it enabled it made things freeze up a couple of times so I did away with the hack.

When I was on PC, these plugins were causing instability for my projects and even some got corrupt. Haven't had any issues on Mac.

Was on a WIN7 system that it acted up on so maybe it's a Windows thing?

THE ADVERSARY wrote:

DJ Hellfire wrote:

THE ADVERSARY wrote:Hey Andy curious question, when you were previously running 1.6 with the hack did it affect your stability?

When I had it enabled it made things freeze up a couple of times so I did away with the hack.

When I was on PC, these plugins were causing instability for my projects and even some got corrupt. Haven't had any issues on Mac.

Was on a WIN7 system that it acted up on so maybe it's a Windows thing?

Yeah, Windows 7! And this also led to another issue where the MPC software would crash and close but the process wouldn't quit, so I was unable to reopen the software until the process ended, which took like 4-5 minutes. And it wouldn't let me end the process manually. So it was either wait or reboot. Annoying as ****!

TT_Lab wrote:It doesn't work in 1.7 for a fresh install
If I do a ReScan all they disapear.
The way to go for me is:
Install 1.6 over 1.7 (Don't have to delete anything, just install it.Do it at your own risk)
Do the hack
Update to 1.7
Only use Scan New.

Yeah. Only reason why I did a clean uninstall/reinstall was because I had a corrupt plugin that was causing all my music apps not to load. I thought AKAI was the culprit, turned out to be an old DIGI midi driver.

I then encountered the same issue as the OP so I just simply told him what I did to resolve it.

MPC-Tutor wrote:Been trying out a few things, including installing old versions of the vintage plugins, messing with the MPC.settings file (back it up first....), renaming the plugins etc.

Nothing doing , so I assume based on what people are reporting it is related to the functionality of the 1.7 plugin scanner itself, so I doubt there's any way around that other than to set it up in 1.6, update and then only ever use Scan New in the future when adding additional plugins.

Yeah the hack is patched in 1.7.

DJ Hellfire wrote:

THE ADVERSARY wrote:Hey Andy curious question, when you were previously running 1.6 with the hack did it affect your stability?

When I had it enabled it made things freeze up a couple of times so I did away with the hack.

When I was on PC, these plugins were causing instability for my projects and even some got corrupt. Haven't had any issues on Mac.

I was actually just using them yesterday on a joint. Windows 7 x64, 32bit 1.7 no problem. Can't get them to scan in the 64bit version tho.

EDIT:not sure why the damn pic wont show.. So here is a link
https://drive.google.com/file/d/0B3KVo_ ... sp=sharing

I'm running Windows 8.1 64-bit; but I run the 32-bit MPC software for all my projects, hack works. I believe like the previous poster mentioned that the hack only works in 32-bit mode.

It appears the plug in scanner is the root cause of several of the problems we are currently experiencing.
Explains we the hack is fine as long as you don't rescan your plugs.