Dubstepforum.com

So here is my problem...

I have a project on the go with a few different channels using massive as the synth. Everything was working perfectly in my project. I had the project saved and it's half complete. Yesterday I reopen the project and, randomly and suddenly, the channels containing the instance of massive are no longer playing the previous synth presets. They are reset to default completely and the channel is just sounding like garbled garbage. When I open the instance of massive my previous synth settings are all gone.


Now I tried opening and closing the project several times and restarting my computer but no luck.
Also, tried opening other projects with massive as a synth and they work fine!!!

Another strange thing I noticed is that I have my 2 basslines grouped together. However, the group channel doesn't seem to register the bass sounds volume when played. I can even turn the group on and off but the bass still plays.


Something fishy is happening here, please help me I really want my bass line back.

I would like to note that this is a cracked version of massive. However I have been using it for years and have never had this problem. If this problem is related to that fact I will go buy a legit version right away.

I've never had this problem with a legit version.

Yeah for real hey....
I mean I got this version when I first started producing several years ago not wanting to shell out the big bucks right away
Clearly a worthy investment now

try resetting the permissions on the massive app maybe

try with batChmod
http://www.lagentesoft.com/batchmod/

Have you tried:

Deleting the Massive Database in Native Instruments under AppsData on PC
Reinstalling Massive

elyhess wrote:try resetting the permissions on the massive app maybe

try with batChmod
http://www.lagentesoft.com/batchmod/

Thanks I will give that a go!

rockonin wrote:Have you tried:

Deleting the Massive Database in Native Instruments under AppsData on PC
Reinstalling Massive

I did try deleting the database but I did not try reinstalling it, I will give that a go.

krispy wrote:

rockonin wrote:Have you tried:

Deleting the Massive Database in Native Instruments under AppsData on PC
Reinstalling Massive

I did try deleting the database but I did not try reinstalling it, I will give that a go.

Just buy it, give the developers some support, after all it's their job and they need to earn a living producing all this software for us

JackSawyersMusic wrote:

krispy wrote:

rockonin wrote:Have you tried:

Deleting the Massive Database in Native Instruments under AppsData on PC
Reinstalling Massive

I did try deleting the database but I did not try reinstalling it, I will give that a go.

Just buy it, give the developers some support, after all it's their job and they need to earn a living producing all this software for us

I bought it, I bought it
I promise

Wait before you said "I mean I got this version when I first started producing several years ago not wanting to shell out the big bucks right away"

Now you say you bought it? So you bought it after you started having this problem?

Sorry but I highly doubt you're gonna be able to recover the patches

dubunked wrote:Wait before you said "I mean I got this version when I first started producing several years ago not wanting to shell out the big bucks right away"

Now you say you bought it? So you bought it after you started having this problem?

Sorry but I highly doubt you're gonna be able to recover the patches

Correct, I bought it last night so that this problem doesn't happen again and to support the company. I have already accepted the fact the patches are lost. If anything this experience had inspired me to legitimize my operation.

krispy wrote:If anything this experience had inspired me to legitimize my operation.

I've had this happen before... the part about the presets sounding like garbled bullshit for some reason once you reload the project. What I did in Ableton was to simply highlight the track that the problem synth was located on, duplicate it, then delete the old one. Now the new track plays the settings perfectly. I actually just opened a project that used to do that a few hours ago and for whatever reason it no longer does it, so the cause is a mystery. But the fix is a simple one.

any luck with permission reset? just curious, that seemed to fix all my problems

elyhess wrote:any luck with permission reset? just curious, that seemed to fix all my problems

No luck, that seemed to be a Mac based thing and I'm on PC