my massive preset collection

[ogunslinger]

Oh, so this guy, who's made some synth patches with a crappy synth gets soooooo many thanks a likes, but me, a guy who replicated Datsik bass from a fucking snare drum sample, gets hate.

Yeah, way to go DSF.

two things

1. no you didn't

2. stop crying

[GRAYSKALE]

I was gonna do this the other day with my Alchemy presets (not on this forum actually, somewhere else) but then I re-formatted my HD and they were the ONE thing I forgot to copy accross :\

Ah well, always good to get a fresh start.

I don't use massive myself but hopefully some newbies will find this helpful, nice one man!

You mean to say . . . there are other forums???

On a serious note, I did this the other day and lost about £50 worth of tunes, just dragged everything from my downloads folder onto my memory stick, forgot that when I first got the laptop I put everything into individual artist folders in my music folder when I first got the laptop and was adamant I was gonna keep this computer organised . . . didn't last very long.

[GRAYSKALE]

Oh, so this guy, who's made some synth patches with a crappy synth gets soooooo many thanks a likes, but me, a guy who replicated Datsik bass from a fucking snare drum sample, gets hate.

Yeah, way to go DSF.

two things

1. no you didn't

2. stop crying

I really can't tell if Chad is for real . . .

[rolltide629]

this could mean that your standalone massive is 1.1.5, but your VSTi version is still 1.1.4 or lower. Click the NI symbol on the top right of massive when in your DAW to check if it's 1.1.5. That's the only reason I could think of that it wouldn't work, hope that helps

Thanks! The one inside my DAW isn't 1.1.5. So how do I get my VSTi veriosn update?!?! I mean, I already have massive 1.1.5 and the file thingy is inside my DAW folder. So wouldn't that massive be exactly the same as the "stand alone"? How is it different. Lol. This is super confusing....

In FL Studio, go to Channels>Add one>More, down in the right corner it says refresh, then click fast scan. Unmark the massive that is already marked, and mark the other one, if that made any sense ;p

Okay i am having this same problem blastfome is having and it is veeeeery frustrating. does anyone know how to fix this in ableton live? like massive works as a standalone just like blastfome but when i open ableton and then try to open massive it is still the same old version i had before and not 1.1.5