Massive (not Massive X)

Personally, to me it seems having both is a little cumbersome.

I would like to see Massive X have some kind of legacy mode that will load and playback classic Massive patches and still sound the same. This is all many of us need. The we can simply move on.

Hey there,

it's probably an ancient history for all of you but is there by any chance someone here who still has a Massive with batch converter for ksd -> nmsv files and would help me to convert my soundsets? I would also be happy to hear about such converters - unfortunately I have not been able to find anything on the net, even after a long search. I am happy about any hint... Thank you very much. 

Hey @Kymeia , thank you! I actually did so and installed older Versions of Massive, but I somehow couldn't find the right version where the batch processor is still activated. (Maybe it was also because I could not complete the activation process due to the outdated Control Center and it only makes the batch processor accessible after successful activation.)

Either way, can you give me a version number where it still exists? Thanks a million!

Changing values are visible during the playing of the automation.

I am happy with Maschine lock States possibilities for saving CPU turning on new instruments while turning OFF ones that don't need. And by Triggering Lock States via notes now so I can play them like anything in keyboard mode and I can place Lock States on linear Time Line in Pattern or Arrange mode which is amazing.

One MIDI 5pin Cable from out to in on Maschine Plus and selecting Maschine plus 1 to Empty group and Pad and in settings turning ON Maschine on IN and OUT and on the next page choosing Lock States and note or chose Selection or Scenes. It's amazing Feature.

Yeah its impossible at the moment, but if they added the legacy Massive code, then it would be possible.

Of course, that could end up bloating the synth, but it's all in how you approach it. If you do it as an either/or kind of thing then you'd only have to run version of the code at a time. It could be doable.

Then you could add a "migrate" style of feature and do their best with the translation. But warn users that it may not sound the same. They then make the choice whether they want to bring a patch forward. However, since its possible to do this without affecting the original patch it shouldn't be a big deal.

This way Massive gets a UI update, the two synths can be one which simplifies a few other things and people can move forward without having to worry if NI will drop support for the original. NI, other hand, will get to simplify things on their end and will ultimately only have one synth they need to keep updated... after they've put the initial hard work in.

It's a win-win from my perspective. Unless I'm missing something.

Emphasis: Then you could add a "migrate" style of feature and do their best with the translation. But warn users that it may not sound the same. They then make the choice whether they want to bring a patch forward. However, since its possible to do this without affecting the original patch it shouldn't be a big deal.

----- ----- -----

So, if you import a patch that uses 3 OSC in Massive to Massive X, how are you going to do this? Just throw away the third OSC and import it? The two won't sound anything close to similar. The entire sound engine is different. The two synths aren't really designed to be the same thing.

Like I said, Massive is a Virtual Analog Synth that used Wavetables. It's like Sylenth1, but as a wavetable synth. Massive X was never really designed to be that. It's more comparable to something like Serum or Vital. The sonic signature is different. There are scenarios where you would use Massive over Massive X even if they both had the same feature set, because of the sonic signature disparities between these two synths.

There are too many differences between the two. Users are better off just continuing to use Massive for what it does/have to offer. It's still supported.

There are WT synths that deliver sound aimed at where Massive was, but they aren't made by Native Instruments and I'm not going to mention them again. Massive X was a reaction to Serum, not an attempt to deliver an "actual" upgrade to massive. It simply uses the Massive branding for clout and marketing boosting.

Yeah I do understand. You can actually add a third somewhat limited oscillator in Massive X. With a bit if upgrading it could support more.

But this is why present it as a "choice". it's the user decision. Even then if they try migrating a patch and it sounds terrible, then just keep using the original in legacy mode. It's not like you have to destroy a patch by giving it a shot. Plus if they are adding a legacy mode, it may be possible to tap into some of those algorithms from the modern mode. Its just an idea.

Just ask yourself how long are they going to keep the original Massive around. It keeps costing them money to maintain and it's not like they can pay for it with sales revenue since it's no longer being sold. Native Instruments being who they are I can seem them closing it down at some point, maybe soon.

I'm just attempting to come up with some kind of solution to an impending issue. It's not perfect, but its better than the alternative.

I hope you're right, but this is Native Instruments you're talking about. So I have rather strong doubts.