Issues with Massive Audio Units plugin within Logic Pro

Hi,

I am having the same problems, regarding Massive forgetting my custom preset. Logic 8, MacBook Pro 2.16, Massive 1.1.1.

 

There's an update in testing at the moment; if I remember, that's one of the fixes. It should be out soon.

ew

 

I am having similar problem.

When I load up a song in logic 8 where I used massive plugin the preset dosent sound the same as before or it just does not play anything.

Also there seems to be an issue with tempo syncing the step sequencer as it sometimes goes out of time.

Logic Pro 8, G5 dual powerpc 1.8 , Leopard 10.5.2.

 

Hi EW,
So, I don't see this ever being addressed. (My Massive Presets are not saving either).

I was hoping that it would be. I have updated to 1.1.3 and I still have the same problem 95% of the time and it really sucks. What is the solution. It happens on both my computers, any suggestions?

Thanks. It makes it very frustrating to use Massive (basically it makes it so it doesn't work).

Travis

 

was this ever addressed?

 

It's probably part of the 1.1.4 update that's going into testing. When I get the changelog, I'll find out if it is.

ew

 

It has been 2 years now since this thread was started. Is there any sign yet of the update that fixes the "forgotten settings" bug?

For 2 years, even after fresh reinstalls on new machines, I have never been able to venture beyond Massive's presets for fear of losing my work.

 

When you make a new sound in massive, go to File and then Save. Then just name your sound. If it does not appear in the list of sounds, just go to File and Open, and then open the sound from where you saved it and all parameters will be the same as when you saved it, longer but works... There's some really deep stuff you can do with Massive, after you get over the initial learning curve. Just remember to always save your sounds in a user folder, do not save in the main database folder since when an update is brought out I think the folder is redone again, so any presets you save in the massive library folder will be deleted on an update. Just keep an eye out for any new updates on massive since that may solve the prob. Have you tried reinstalling? That sometimes works for me when this kind of thing happens.
---
Alternatively if you own Kore 2, you could open Massive as a VST in Kore 2 and then use Kore 2 as an AU in Logic. I havent encountered a problem with the VST in Kore so this could be a temporary solution also.