Massive X - the thread

[SteveWZ]

Here is an experiment in sound design.

This is a single preset done with Massive X.
It uses extensive controllers to allow live playing changes, some automated, some triggered.

As it plays, morphs, additions, subtractions of elements are done on the fly throughout.

This demonstrates the capability Massive X has to create unique, "outside the box" instruments with interesting controllers.

X-Game:

https://soundcloud.com/vintage-synth-pa ... -massive-x

I like what you've done there. It's wonderful, what can be accomplished with a single preset.

Yes, outstanding!

One question, are all the effects also part of the preset?

All effects are part of the preset.

That preset includes controllers for the effects, filters, tone, wave positions, Pulse width, individual OSC volumes, etc.

There are a lot of subtle changes that can be done due to the modular nature of Massive X and the controllers.

The effects actually don't sound bad.

Effects seem outstanding to me.

https://soundcloud.com/vintage-synth-pa ... -massive-x

Yes, the effects sound excellent.
Nice to see an example of something so deeply programmed.

The reverb sounds great for a synth.

[perpetual3]

Here is an experiment in sound design.

This is a single preset done with Massive X.
It uses extensive controllers to allow live playing changes, some automated, some triggered.

As it plays, morphs, additions, subtractions of elements are done on the fly throughout.

This demonstrates the capability Massive X has to create unique, "outside the box" instruments with interesting controllers.

X-Game:

https://soundcloud.com/vintage-synth-pa ... -massive-x

Damn, that’s amazing.

[ghettosynth]

They're not straight up ports of Reaktor filters. Sure some were used as starting points, but they're reworked/reimagined/updated.

Also Groian is apparently not a typo, I've been told. Not sure if it's related to the Grobian filter at all.

That’s what I thought. Just a basic osc → flt sounds so good.

As far as Groian vs Grobian, groian is a terrible name, might as well call it the crotch filter.

Right! I'd give em a pass for a misspelling, an intentional name that bad says something else entirely. I like "crotch fire" if we're going there though. Truth be told, I think I'd prefer filter names conceived backstage at the making of Talledaga Nights over those designed by the organization that inspired "The Office."

[SLiC]

The only reason I can surmise for NI’s claim that the synth will be developed for a long time and that updates are coming, is that it will be. I don’t recall them ever making a similar claim, perhaps for maschine but I stopped following that development.

Also, I made a big report at the NI MX support site and I received an email response that same day. That’s never happened before, and more to the point very unlike my prior experience with NI (which quite frankly sucked).

Interestingly there are very similar issues with Maschine, I recently got a Mikro V3 to take advantage of all the sound packs in KU12...just like Massive X it was obviously released under commercial pressure to hit for revenue quarters. The things that are missing with Maschine Mikro (and in my opinion MX) should not have been put in before release....for example, many of the features don't work within a DAW (including transport control) and the product still isn't even recognised by NI's own midi editor! I don't believe these are oversights, NI have just put revenue before quality control and it will ultimately affect their reputation (as can be seen from the Mikro thread on the NI forum and all the negative post on MX).

I am I fan of NI, been with them since the start and literally have the T-Shirt, but they are not really delivering in my opinion, Kontakt 6 was at best 'meh' and the tiny non scaling GUI's are really getting old....I think it all started going downhill when they droped Kore

[v1o]

The only reason I can surmise for NI’s claim that the synth will be developed for a long time and that updates are coming, is that it will be. I don’t recall them ever making a similar claim, perhaps for maschine but I stopped following that development.

Also, I made a big report at the NI MX support site and I received an email response that same day. That’s never happened before, and more to the point very unlike my prior experience with NI (which quite frankly sucked).

Interestingly there are very similar issues with Maschine, I recently got a Mikro V3 to take advantage of all the sound packs in KU12...just like Massive X it was obviously released under commercial pressure to hit for revenue quarters. The things that are missing with Maschine Mikro (and in my opinion MX) should not have been put in before release....for example, many of the features don't work within a DAW (including transport control) and the product still isn't even recognised by NI's own midi editor! I don't believe these are oversights, NI have just put revenue before quality control and it will ultimately affect their reputation (as can be seen from the Mikro thread on the NI forum and all the negative post on MX).

I am I fan of NI, been with them since the start and literally have the T-Shirt, but they are not really delivering in my opinion, Kontakt 6 was at best 'meh' and the tiny non scaling GUI's are really getting old....I think it all started going downhill when they droped Kore

That doesn’t make any sense. The Mikro V2 and V1 implementations were already mature and working well with the NI software ecosystem. The V3 hardware is just an iterative update but with less controls than V2. And none of the Maschine Mikro V3 reviews both written text and YouTube videos mentioned any of these glaring issues.

[recursive one]

How do I assign the same macro to more than one parameter? The Massive X quickstart says

Drag and drop the Macro icon (1) from the Header onto the modulation slots of both Feedback and Freq. Then click and drag the modulation slot upwards to increase the modulation amount. By playing a note and turning Macro 1 you can control the two parameters on the Frequency Shifter at once.

https://www.native-instruments.com/en/m ... massive-x/

But i can't seem to do that, I can only drag and drop Macro1 to one parameter and when i try do drag and drop the same macro to something esle, it erases the first assignment

[chk071]

Are you dragging it to the parameter itself (knob/fader/whatever), or the modulation slot below it?

[Mokafix]

Are you sure you dropped it on the knob mod slot and not the knob itself?
Macros can either be used to control a knob 1 to 1, or as any modulation source where it works as an offset then.

[recursive one]

Are you dragging it to the parameter itself (knob/fader/whatever), or the modulation slot below it?

Thanks a lot! When dragging it to the mod slots it works

[chk071]

[perpetual3]

Well, I’m still feeling frustrated over the lack of a direct osc output that bypasses the global unison engine. To me it’s just a weird limitation, and one that’s seems relatively trivial to implement. Serum has it, and so does the free synth Helm.

Also, I’m not really feeling the use of mods as osc sources. I agree with the critique that their use is already constrained by the lack of band limiting. Ok, so no big deal for a sub osc necessarily. But tuning the osc is a pain. And if I want to use a filter, I still have to use up an insert effects slot.

Am I missing something here?

[SLiC]

The only reason I can surmise for NI’s claim that the synth will be developed for a long time and that updates are coming, is that it will be. I don’t recall them ever making a similar claim, perhaps for maschine but I stopped following that development.

Also, I made a big report at the NI MX support site and I received an email response that same day. That’s never happened before, and more to the point very unlike my prior experience with NI (which quite frankly sucked).

Interestingly there are very similar issues with Maschine, I recently got a Mikro V3 to take advantage of all the sound packs in KU12...just like Massive X it was obviously released under commercial pressure to hit for revenue quarters. The things that are missing with Maschine Mikro (and in my opinion MX) should not have been put in before release....for example, many of the features don't work within a DAW (including transport control) and the product still isn't even recognised by NI's own midi editor! I don't believe these are oversights, NI have just put revenue before quality control and it will ultimately affect their reputation (as can be seen from the Mikro thread on the NI forum and all the negative post on MX).

I am I fan of NI, been with them since the start and literally have the T-Shirt, but they are not really delivering in my opinion, Kontakt 6 was at best 'meh' and the tiny non scaling GUI's are really getting old....I think it all started going downhill when they droped Kore

That doesn’t make any sense. The Mikro V2 and V1 implementations were already mature and working well with the NI software ecosystem. The V3 hardware is just an iterative update but with less controls than V2. And none of the Maschine Mikro V3 reviews both written text and YouTube videos mentioned any of these glaring issues.

Your right, It doesn’t,

Read all about it if your interested https://www.native-instruments.com/foru ... 575/page-6

You can download NIs midi editor yourself and you will see that there is no editor for Mk 3, but there is for 1 and 2....it’s been out over six months now...

[chk071]

I just had a bug with the GUI, when i left the MX GUI opened in Studio One when i went for dinner, and, then i came back, and none of the controls was reacting, while the parameters surely changed, as i heard from the sound. The knobs just stayed at 0, when i moved them. Opened and closed the GUI then, and everything worked fine again. Weird stuff.

[perpetual3]

So, correct me if I’m wrong here, but the LFO in osc mode, sawtooth, set to mono routed to the monophonic area direct output (bypassing effects) reacts differently to unison then the other osc???

[pdxindy]

I just had a bug with the GUI, when i left the MX GUI opened in Studio One when i went for dinner, and, then i came back, and none of the controls was reacting, while the parameters surely changed, as i heard from the sound. The knobs just stayed at 0, when i moved them. Opened and closed the GUI then, and everything worked fine again. Weird stuff.

I've had a few weirdnesses like that in Bitwig... but nothing repeatable...