Massive presets sounds weird / no sound since 10.0.2

[antoineferon]

Since the 10.0.2 update, NI Massive presets sounds weird (No sound, only left channel, sounds weird..)

Everything worked fine before the update.

Anyone else?

CONFIG
MACOS Sierra 10.12.6
Last version of NI Massive (1.5.1)

[jestermgee]

Fine for me

Win10

"Latest Massive Version" or to be specific: 1.5.1

[miyaru]

I read your post, ran upstairs, and tried my Massive.... Nothing strange in my system, just runs fine. I'm on a Win10 PC, and it works OK.

Maybe someone with MacOS and Massive can chime in, and see what happens.

In the meanwhile contact Ableton if this is a known issue.

[Zenek]

Yeah, same for me. Massive respond very slow and glitchy. And not just Massive, all my Roland Cloud plugins are slow and sending erratic and intermittent MIDI data making impossible to play with ANY patch.

Worst update ever 10.0.2!

I’m on macOS with last version of High Sierra.

[antoineferon]

Thank you @Zenek, I will contact the Ableton support to have more info about this.
I have exactly the same issues !

And my Serum VST/AU have the same issues than Massive

I will downgrade to Ableton 10.0.1 to see if I still encounter the same issues.

Keep you posted !

[[jur]]

Please report to support@ableton.com
sorry for the hassle,
thx!

[oratowsky]

same issues here

something I noticed is that when opening a new set and changing nothing, it prompts me to save the set.

I noticed that under undo actions I have the following actions:

Change "Release Variable"
Change "Output Trim"

edit:

this is happening with Serum, Massive, and Spire. opening up the plugin windows, all kinds of parameters are switching to random values.
reverting to 10.0.1 fixed it.
I am on macOS 10.13.4

[Stromkraft]

Have you tried running the VST version only?

[iloyd2]

Having random presets sound bad as I scroll through them both with Massive and Repro-5 AU versions when I upgraded to 10.0.2. Even when presets are loaded from plugin's own browser.

[Stromkraft]

presets sound bad

Meaning specifically?

[iloyd2]

presets sound bad

Meaning specifically?

They don't properly load. Many settings are wrong thus the patch sounds bad.

[cane creek music]

Yes i fired up a project which contained my goto Massive Hoover/Reese bass preset and it sounded bloody awful,
I had to reload the present again.

Ive also found i can't play chords with Diva/Repro5 it just wipes out the CPU something id not noticed before which is $hit as I've just received my Kordbot.

I also have one project that was almost finished that won't open at all.

I didn't realised they had been a new Live update, i installed a new SSD last week done a clean install and just installed Live from the website.

[fuzzyhead]

Same problem here, will roll back to 10.0.1 and check..

[Stromkraft]

presets sound bad

Meaning specifically?

They don't properly load. Many settings are wrong thus the patch sounds bad.

Improperly loading presets indicate more serious issues, like permissions.

I'm on macOS 10.12 "Sierra", but I doubt this is a Live 10.0.2 specific issue. Since Live 9.7 or so I've had to obliterate preferences multiple times after an update, both for Live and for certain plug-ins. Lately this have been Waves but also others previously.

So first of all, try to reset Live and make a mint install of problematic plug-ins.

[oratowsky]

Hey guys

This is without a doubt a problem with the 10.0.2 update

Support told me they know about the bug

Downgrading to 10.0.1 fixes the problem

It affects only AU versions of plugins. You can also use VST versions as a workaround