Massive Update to 1.1.5

Great news! I got a reply from NI supportsaying that they can indeed reproduce the problem!

"Hello Chris Breame,
this is not a known issue but I could reproduce it. I have informed the development department to fix this in a future version. We appreciate your understanding."

Awesome!

 

That definitely shouldn't be happening. One of my interfaces is an EWX 24/96 (same drivers as your 6Fire); it definitely doesn't happen here. System specs?.

ew

 

me 2... i'm very annoyed about the sluggish behavior of massive within logic 9...

 

Same here !
I have not problems when I make my own presets, only when I use factory pressets or when I scroll them ..
Cubase 5.1.1 32bit, Windows 7 x64....
I think there must be problems with pressets database , because Reubuild DB does not work...

 

I'm afraid I was to positive in my last post. Massive even tears the system down in Cubase's instrument rack.
Hope there will be an update soon because this starts to get very annoying :angry:

 

i'm kinda glad that i'm not the only one who's getting these weird crashes with Massive.... finally bought a copy yesterday but the constant crashing and odd behaviour in Live 8 makes it pretty unusable. i'm having the same choppy sound out of massive when flicking thru presets as above, and i'm also getting a total crash of Massive & Ableton when i try and assign any LFO/Envelopes to anything on the synth, the second i drag and drop they both disappear and im back to just a desktop.

i did some searching and came across a fix of sorts. seems to be working for now but not sure if thats a coincidence or not. anyhow, if you wanna give it a try and your running on a PC then try going to C:\Documents and Settings\[UsernameHere]\Local Settings\Application Data\Native Instruments\Massive and delete the Massive database file, then open the standalone and let it rebuild the database. seems to behave after that, but like i said it's a bit too early to tell how stable it will be on the next run!

i'm just hopin that 1.1.5 fixes all this cause Massive makes some seriously nice sounds... just a shame i can't put any of em to work yet!
---
ok, scrap that, back to choppy sound already.... how frustrating is this? im guessin since 1.1.5 isn't in the final stage no one knows when NI plan to release? how do you get to be a beta tester?

 

Did This Update Help Others?

I bought KOMPLETE 6 about 3 months ago and never ever have been able to open massive and use it, EVER! been back and forth with support, no answers, thougth it was my mother board being so weak.. but it loads everything else fine..
each time I load massive standalone or vst, i hit a midi key, MASSIVE crashes instantly! Still haven't resolved this issue and it's going on 4 months. Guess I bought K-6 without massive, what a rip off..and very dissappointed to not beable to use it.! HOPE THIS UPDATE FIXES IT.
we'll see..

 

What are your system specs?

 

i dont know how significant this is, if at all, but i recently installed Windows 7 Ultimate on my tower and thought id try my luck with Massive. i was using XP SP3 before and had the same crash issues as everyone else. not that i wanna jinx things, but i haven't had a single prob running Massive in Win 7, and i've been doing all the things that would make it crash (zipping thru synth presets, copying an instance of Massive and pasting it on another track) and it's still running happily..... would be intersting to know if anyone else has made the switch from XP to Win 7 and seen the same change in it's behaviour?

 

I don't understand your "everyone else" statement here, never had that problem with none of my computers using Vista/Windows XP SP2&3 Single/Dual Core AMD and Intel CPU with onboard sound & ASIO4ALL as well as with PCI, external USB and Firewire Interface...
Since this is a rather rare problem, it would be nice to get the complete specs of your systems so someone might be able to isolate the problem, otherwise I'd guess you're not exactly interested in solving it.

 

That's great, but what sequencing software do you use?

 

It's not restrictd to Cubase 5 and Windows. I have Massive crashing while changing the preset on OSX + Cubase 4 and NI said in August 2009 it was a known issue and they are working on it.

 

I was refering to the standalone crashing problem ony, due to my workflow I'm not able to help with sequencer problems...

 

Ah okay
dj_dunno was referring to Live and Cubase users as "everyone else"
I don't know if it goes for everyone else, but fact is, a great part of Massive within Cubase or Live users encounter the same type of crashes once in a while.

 

I bought Massive last weekend and came here to report that I'm pretty much running into the same issues that are being reported here. I'm running 64bit Win 7 and Live 8.1.1, although I switched back to my install of Live 8.0.8 and things seemed okay for one night, then nothing but crash after crash the following night.

At first I assumed Live 8 was responsible for the majority of these crashes since it's pretty well known and documented that Ableton is scrambling to make 8 more stable and reliable. But until I got Massive I wasn't crashing anywhere near as often as I was without it. I've used a lot of third party VSTs over the years - including NI's Absynth 5 and FM8 - with no major issues. Sure, I always had the odd crash now and again, but nothing like I'm experiencing this week when trying to incorporate Massive into my work.

 

Maybe this post of Palgone could be of use for you:
http://www.native-instruments.com/forum/showpost.php?p=609595&postcount=32

Also check out the Technical Issues area, there seem to be more Live users with problems.
here: http://www.native-instruments.com/forum/forumdisplay.php?f=135

 

Thanks, and I did see that first post you recommended and will definitely try that tonight.

I also read in another post around here, I think ew suggested that following any type of Ableton crash, Live's preferences file can get corrupted so forcing it to rescan the plug in folder can clean it up. After a string of repeated crashes last night I remembered that tip, tried it, and for the next half hour or so didn't seem to run into any problems, but I'm not sure I used Massive enough to say it was a true remedy form my problems. I should have more time tonight to find some of this out. All of this was in Live 8.0.8 so I may try to use my install of Live 8.1.1 again with both of these tips, then do a lot more rigorous testing to see if things start falling apart again.

 

apologies for the confusion, i didnt mean every single massive user, i meant the people who are involved in this thread and having the same issues.... it does seem to be a widespread problem tho as i've heard plenty of people mention how unstable Massive is in the past when used within certain DAWs. of course im interested in getting the problem solved, i didn't spend near on £200 on a VSTi i can't use. personally, i don't think spec has anything to do with it as i've known people who are using Mac's who have the same issues but i will happily raise a ticket with NI containing a detailed rundown of my spec if it will help solve the problem, i just figured there was little point when judging from this thread and the countless others they are obviously aware of the issues some of us are having. at the end of the day, we are all here to try and help eachother, we all want the same outcome which is a stable VSTi that we can use.

 

If someone is having problems with the standalone version it can't be a simple host incompatibility, that can occour when software is being updated independently, it's rather something system dependend, that's why I asked tintala for the specs. I guess I got a bit confused with your answer that probably had nothing to do with my post...

 

As i was reading your post, I thought I wrote this! Your problem is the exact replica of mine... I have had Komplete 6 for about 5 months now and have never ever been able to use massive , standalone or vst in Cubase. I got this due to the fact it had massive in it... now i wil never beable to use it. It crashes each time i hit a midi key... and windows wants to send an error report...

TEch support hasn't come up with a solution nor has anybody in any forums, I have been submitting this problem since I bought it. But have had no luck rectifying the problem. IF anyone can help out with suggestions , or if I am missing an update for massive?