Page 2 of 2

Re: problem with massive

Posted: Wed Apr 24, 2013 4:08 am
by subfect
grimsin wrote:Thanks zosomagik I'll give that a try later. @simulant. I can't update the latest version. I don't have internet on my computer at the moment. :( hell i just got internet on my phone today. First thing i did was get on dsf ;)
Yet you say you've had this problem for a while. I smell a pirate ;)

Re: problem with massive

Posted: Wed Apr 24, 2013 4:33 am
by _helix
Instead of fighting it try saving the patch with your DAW. For example Studio One or Cubase you can do this instead of saving the patch via Massive.

Wait are you even saving your patches?

Re: problem with massive

Posted: Wed Apr 24, 2013 4:53 am
by grimsin
Hey zoso. I can't find what your talking about. Which doesn't surprise me my computer is a mess!!! But ya i can't find massive.exe anywhere.

Re: problem with massive

Posted: Wed Apr 24, 2013 4:58 am
by grimsin
It's a bought copy, Although i have had the problem since i installed it. You said to save it via my daw, but i didn't know you could do this :dunce: im using fl studio 10. And as far as i know I'm saving the patches, but it does it with presets too

Re: problem with massive

Posted: Wed Apr 24, 2013 5:08 am
by zosomagik
thats a bummer dude... that would irritate the F#@$ out of me. ill go back and see if anyone else said anything about it.

Re: problem with massive

Posted: Wed Apr 24, 2013 5:19 am
by zosomagik
so the only other solutions i can think of would be
A. bounce everything to audio when you have a good sound but fuck that because you might want to change it later
B. try creating a separate folder for your custom sounds and reload them if massive resets itself but that would still kind of be annoying but this is what i would try before option C
C. would be finding out what version you have and if its not the most current update it or
D. hit up native instruments support but ive had problems with them getting back to me in the past

Re: problem with massive

Posted: Wed Apr 24, 2013 1:29 pm
by charles1
zosomagik wrote: D. hit up native instruments support but ive had problems with them getting back to me in the past
if you bought it, you should do this. if they don't get back to you, email them again. you're probably entitled to their technical support. don't let that go to waste.

Re: problem with massive

Posted: Wed Apr 24, 2013 2:21 pm
by _helix
zosomagik wrote:A. bounce everything to audio when you have a good sound but fuck that because you might want to change it later

On the plus side this might actually be a positive.

Re: problem with massive

Posted: Wed Apr 24, 2013 3:06 pm
by VirtualMark
zosomagik wrote: D. hit up native instruments support but ive had problems with them getting back to me in the past
Me too - I wrote a big long email detailing everything I had tried and exactly what problems I was having. After a few days I received a standard template email telling me to update to the latest drivers and other basic things that I'd already tried, and had already told them. They make great synths, but their support is among the worst I've used.

Re: problem with massive

Posted: Wed Apr 24, 2013 6:28 pm
by zosomagik
_helix wrote:
zosomagik wrote:A. bounce everything to audio when you have a good sound but fuck that because you might want to change it later

On the plus side this might actually be a positive.

i personally do bounce all my synth stuff to audio but it would still suck that he wont be able to have the patch.

i think its pretty unanimous that you should hit up NI support. just be persistent and theyll get back to you.

Re: problem with massive

Posted: Thu Apr 25, 2013 3:29 am
by grimsin
I bounce them to audio. That's the only way I can use them. I usually make the patch record it. then if i want duplicates i just use the same patch, and alter it.But it does suck because that's all I have. That's all if I wanna duplicate, we'll I can't. Idk why tech support didn't cross my mind, I figured it was a simple issue. Maybe I put my stuff in the wrong places that kind if thing. Thanks for the tips zoso, and everyone else :4: just out of curiosity because I wasn't aware of this. How is bouncing to audio a good thing? I mean I didn't think it was bad, but I didn't think it mattered.

Re: problem with massive

Posted: Thu Apr 25, 2013 10:02 am
by VirtualMark
OP - have you tried adding a folder to the library? If you go to File > Options > Browser, you can add a folder. Try creating a couple of patches and saving them there, see if it helps.

Bouncing to audio is great, but it would annoy me if I didn't have an option to save patches.

Re: problem with massive

Posted: Fri Apr 26, 2013 8:13 pm
by grimsin
Called tech support. Was on hold for an hour. Finally they ended up telling me that my massive presets are pirated and that's why they don't work. That's true ill admit it I wanted some crazy dubstep wobbles to play with, but i dont see what that has anything to do with massive. if massive was pirated I would understand, but they kept insisting this was the problem even tho it does it with any patch I make as well. So I deleted the pirated patches completely off the computer, and guess what I still have the same problem.... What a joke.

Re: problem with massive

Posted: Fri Apr 26, 2013 8:58 pm
by blinx
If everything is legit id recommend reinstalling your OS and starting clean. IF this has not worked form the first install your PC may just need some serious house cleaning and a rebuild.

Re: problem with massive

Posted: Fri Apr 26, 2013 10:52 pm
by charles1
grimsin wrote:Called tech support. Was on hold for an hour. Finally they ended up telling me that my massive presets are pirated and that's why they don't work. That's true ill admit it I wanted some crazy dubstep wobbles to play with, but i dont see what that has anything to do with massive. if massive was pirated I would understand, but they kept insisting this was the problem even tho it does it with any patch I make as well. So I deleted the pirated patches completely off the computer, and guess what I still have the same problem.... What a joke.
I mean, is it illegal to "pirate" patches? I was under the impression that sharing patches with people or downloading them from the internet was totally fine. You should call back and not mention anything remotely illegal or related to file sharing / pirating. Just say that you bought the program and the only presets you have are the ones that came with it and ones that you made yourself.

Re: problem with massive

Posted: Fri Apr 26, 2013 11:26 pm
by grimsin
Pirated patches are obviously illegal. The tech guy actually hack my computer (with my permission) and that's how they came about that whole thing. They just wanted to make sure I had my stuff in the right place without any confusion (guess that happens a lot) anyways it doesn't help that I had the folder labeled massive patches from pirate bay :u: it's funny too I usually don't do pirate bay. I like to buy all my producing tools, but I couldn't help myself. I wanted them so I could see the mechanics. Help figure out how to use massive. Dumb idea cuz now they won't help. So looks like I'm gonna wipe the OS. Bout time anyways. It's such a mess. Anyways thanks for the help guys. :Q:

Re: problem with massive

Posted: Sun Apr 28, 2013 5:08 am
by charles1
grimsin wrote:Pirated patches are obviously illegal.
I don't get why they would make patches illegal (assuming we're talking about patches that weren't designed by NI, of course). I mean, it's not like NI sells patches (or do they?), so sharing patches isn't causing NI to lose any money. in fact, it only promotes the VST, which in turn makes it more popular and causes more people to end up purchasing it, so I don't see why they would ever make it illegal to share patches. Don't get me wrong - I'm not saying you are incorrect, I'm just surprised

Re: problem with massive

Posted: Thu May 02, 2013 6:15 pm
by grimsin
Idk I had a bunch from the vengeance stuff mostly, and they had a pretty big problem with it, but whatever

Re: problem with massive

Posted: Fri May 03, 2013 6:05 am
by Electric_Head
search for massive.db.
Delete the file.
Open standalone massive and rebuild database.