Massive Update to 1.1.5

Just wanting to know, does the new update fix the bug when Massive is run as a VST inside Cubase 5.1? A lot of Cubase users have been having the crash issue, and the kore2 route also yields the same result, if you open Massive in Kore 2 as a VST in cubase it crashes when presets change.

 

I couldn't say; it hasn't gone into testing yet.

ew

 

I am just now searching on this issue. So Massive crashing in Cubase 5.1 is a known issue? If so, this will ease my mind because it is frustrating me that I cant use it for longer than a few moments before it crashes.

J

 

I guess it's now in the beta testing phase. It would be nice of them to fix the RTAS issue I'm having where all the presets that use the performer sequencers don't have the POS engaged.

 

Massive in Cubase 5 works like a charm for me

 

What version of cubase 5 you got? I have got 5.1.1, which came out recently.

 

I also got Cubase 5.1.1 and I use the 64-Bit version

EpikureeR

 

hi guys im using massive in cubase studio 4.5 and live 8 and getting crashes on both daws when going through presets

 

I am having this problem in Live... If I let the preset load and wait 10 seconds before loading another preset, it will not crash... But when I am scrolling through presets for ideas, it crashes without fail.

 

Same problem here too This is really really bad.

 

Can you possibly give any other hints as to how you might be able to replicate the problem? I'm using Live 8.1 and Massive 1.1.4 on Mac OSX 10.6.2, no problems browsing though Massive presets in Live. Also, I'm using the Audio Unit version of the Massive plugin.

Edit - just tried it on WinXP, Live 8.1, Massive 1.1.4 VST, couldn't reproduce the crash then either.

 

Use Massive in Cubase 5 and never had a crash. In fact the preset search is my favorite of vst's cause I can use keyboard arrows to move between presets.

 

Don't confuse Cubase VST 5.x and Cubase 5, folks. I'm not at all surprised that Massive works well in Cubase 5 - they're both recent programs. But I have Cubase VST 5.x. It's old, but I like it and it suits my needs. However...

I have just bought MASSIVE, REAKTOR 5 and FM8 via recent NI promo. No problems with the purchase and registration of products. But oh heck: Why oh why does MASSIVE keep crashing? I could understand if that happens in dear old Cubase VST 5.x, but it crashes as a standalone too!

I'm going to uninstall it completely and see if a reinstall solves the problem. If not, any ideas, please?

Thanks,

John.

 

i'm hoping to see better massive behavior with logic 9 & snow leopard.
a little...moody as it is right now...

 

Obviously I'm not the only one having problems with Massive !
I bought Komplete 6 a few weeks ago, where everything works fine, but Massive always crasches as soon as I hit a key on a MIDI keyboard.
I'm using it as standalone, on a Win XP machine and tried the original ASIO driver of my DMX6fire soundcard as well as ASIO4all.
With the ASIO4all even the computer restarts.
Even re-installed Massive 3 or 4 times now.
The support team also hasn't answerd yet.
Good that I still have the other synths working fine, but nevertheless: sehr schade, jungs, or in english: very shady, guys!

 

Cubase 5.1.1 here and I have random audio tearing issues with Massive.
Unfortunately I'm not able to reproduce them, it's pretty random. But most of the time scrolling through presets causes it.
All other (NI) VSTi's work as expected.

 

It's pretty crazy and disheartening that I cant use Massive in Cubase. I have the latest and greatest. sigh...

 

Massive and Cubase have never been the best of friends, but I found that rebuilding the database manually in the standalone version made a big difference. It still needs handling with kid gloves, I always load up a different VST first and never try changing patches while it is making any sound, and if it goes silent try and save asap and then hammer the little ! midi panic/reset button. But aside from that it actually works, which it never used to.

YMMV of course and it is a bit of a fuss but definitely worth a shot. I think NI are aware of the issues so maybe we will be lucky with 1.1.5.

 

Yes, I have this problem too. Massive 1.1.4 on Cubase 5.1.1 32bit (PC, XP x86, Quad Core CPU).

Basically, I've found that it happens if you have too many instances of Massive in the project. It also has something to do with selecting presets - as changing the preset in one of your new instances of Massive can cause the problem.

Essentially the problem manifests itself like this:
1. Open new instance of Massive on an instrument track
2. Duplicate this instrument track
3. Change preset
4. Sound suddenly goes all choppy on the new instance of massive (it's not related to CPU usage)
5. Try to unload that 'choppy' instance of massive, or delete the instrument track or close Cubase - all have the same effect (ie. they are all 'unloading' Massive in some shape or form)
6. Instant crash

I have sent in a support query, so I hope it's fixed soon - I can't continue with any of my projects as they're all so 'flaky' just now... :-(

Breame

 

Same here when I use an instrument track, it even crashes on a single instance when changing presets through the top preset selector. When I duplicate the track and switch the presets of the 2nd instance I get audio tearing. The 1st instance keeps stable though.

But when I load Massive in the instrument rack (Cubase -> F11) it seems pretty steady. I can switch presets without tearing audio nor strange lock-ups.