Hi there! I'm running Mavericks, and I just downloaded Massive 1.3.0 ASSiGN. Ran the installer, copied the vst & component files to their respective folders. But when I open up Massive in Ableton 9.1.1, it prompt me to register the product. What did I do wrong?

Or are there any other cracks of this? This is the only "working" one I can find on audioZ.

Thanks in advance guys, this is an amazing community I hope to contribute to further in the future

 

Open up the terminal and type: sudo chmod -R 755 (leave a space after the last "5") and drag and drop into the terminal the app (applications/native instruments/massive/massive.app) and also the component and vst fles.

Hit return and enter your password. After that nothing should happen and then just type exit and hit return again. This should do it.

 

Did you mean drag and drop the Terminal icon from the dock? I'm trying to do that but it just shows a tiny white cloud next to the Terminal app and it doesn't do anything. Thanks for the reply, looking forward to getting this done with your help!

 

Ah I get what you meant. I dragged and dropped the 3 files (app, vst, comp) into terminal, entered my password, then typed exit and hit return and it said "Process Completed" but when I open up Massive in Ableton, it still shows up as the demo version

 

Download the newest version:
and if you still have the problem, it could be the massive preference file

 

I downloaded, installed the 1.4 over my 1/3 installation, copied vst/component files, batchmod'd the .app file, and still no results. How do I go about tinkering with the preference file?

 

Ok, after you gave the right permissions to the files delete the "com.native-instruments.Massive.plist" Located in : ---Library/Preferences/Native Instruments/

 

and I give permission to the app, vst, and component, yes?

 

At least you could tell what plug-in causes the trouble there are at least two variants in live, isnt it? (AU,VST,VST3)

a crack that nags for authorization isnt cracked or not for the architecture youre on!
it has nothing to do with preference files nor permissions

you have two locations where vst are stored and two locations where components are stored:

system plug-root :
-> /library/audio/plug-ins

userspace plug-root :
-> /users/username/library/audio/plug-ins

live even allows custom locations ... afair

! always install into system plug-root -> /library/audio/plug-ins ... except you know what you do


your host will only accept one version of component and one version of vst and one version of whatever else it accepts VST3? , which one depends where it hits first/last during plug-in scan

there should be only one VST and one COMPONENT of the plug-in / never multiple versions active at same time

tricky it is with VST as you can arrange plug-ins inside folders ... its possible to have /library/audio/plug-ins/vst/ni/massive.vst + /library/audio/plug-ins/vst/native instruments/massive.vst + /library/audio/plug-ins/vst/my supa faves/massive.vst

now the host will only take one of the above three and if its not PROPER/ ... then it's nagger time

get comfortable with your plug-in folders and reinstall the PROPER files ^_^