Solved Massive presets saved with v 1.5.9 (R78) not opening in M+

I updated to the latest Massive version on my computer and now I have problems opening patches made/saved with it in M+ standalone.

Anyone else experiencing this issue?

I found a workaround - I can create a new Maschine project in the software, open up the preset in Massive, save and copy the project to M+ SD card, but this doesn't add the patch to my M+ user library, so it's nowhere ideal for me.

Is there a way to downgrade my Massive installation? Having patch compatibility with M+ standalone is more important to me than running the latest version.. The new VST3 version doesn't even support MPE so I see no reason to upgrade at this point.

 

Hey tetsuneko,
Please get in touch here, we can provide an installer for an earlier version of Massive: https://bit.ly/NISupport_Synth

 

Yea this is the same issue with Kontakt and I'm guessing other instruments. You can't save a version that's newer than what's on Maschine Plus. This is kind of worrisome because once the Maschine Plus isn't supported anymore in however long (conceivable to use this device for 20 years), you have to have an older version of Konakt or Massive. The issue is older versions of Kontakt or Massive probably won't work on whatever new OS we're running then. It's different on MPC because the instrument formats are literally just text files so you can always edit them no matter what.

Also, the Maschine sound format and group format need to be open sourced so we can translate other formats to it. I don't know why you would ever have a binary format for this kind of stuff. As a developer that would never make sense.

 

Thanks, report sent! I will be more careful with updating FM8 & Massive in the future

 

Got in touch with NI support. Apparently, the version number of your desktop software must match with the version number of the same plugin in M+. In my case, my M+ shows Massive 1.5.8 so that is the version I should also use on my desktop for best content compatibility. I'll hopefully get DL links to Massive 1.5.8 soon..

Also noticed that there were actual updates for my Kontakt & Reaktor instances in M+ standalone (you can find these from Settings/Library/Show:Udates) so updated them both. I now have the exact same version number on Kontakt, both inside M+ and on my desktop, so time to do some more tests to see if I'll be able to import my Kontakt patches successfully this time! For some reason, I have never gotten a single Kontakt patch to load in M+ before; such a version mismatch might have been the culprit (?)

 

Ok, I downgraded to 1.5.8 but my problem still persists. I will need to do more tests as I'm confident the earlier version did work.. However, what is now amazing is that I CAN FINALLY IMPORT MY 3RD PARTY KONTAKT PATCHES TO MY M+!!
This is a game changer for me and something I hoped to be able to do ever since buying Maschine+. THANK YOU NI!

 

This is really odd IMHO.

First of all, Massive has been stable with a fixed feature set for many years and thus is very unlikely to need changes to the preset file format. I’ve been using and porting preset files between several systems and versions for almost ten years and never had any compatibility problems.

Second, an update which increments the last position of the version number (1.5.x) should never introduce incompatibilities (this is a widespread convention for versions). In case it does, the users should be warned about missing backward compatibility in the release notes.

 

I still haven't found out the exact reason for custom patches not importing anymore. Since downgrading to 1.5.8 didn't help, I am not ruling out user error or some other undocumented issue causing my problem. It's just odd that prior to upgrading to 1.5.9, all my patches imported perfectly with 0 issues.

And coming back to the topic of Kontakt — While I can now load my user Kontakt patches on the M+, I get the same issue I used to get with Reaktor ie, "no sound is output on project reload" bug. I wonder if it's related to a similar authorization issue as with Reaktor in M+? That time, NI CS did something to my Reaktor licence data and the issue disappeared..