Native Instruments Massive X Synth - Sequel to Massive (Out Now!)

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Locked New Topic
RELATED
PRODUCTS
Massive Massive X$199.00Buy X-Squared For Massive X

Post

Kian Russell wrote: Sat Jun 29, 2019 7:38 am looks like sadowick has pulled his videos about massive x from youtube without explanation
thats the last time i will listen to him.
i've updated my rating from 100% to 0%.
:shrug: Still visible to me.
"I was wondering if you'd like to try Magic Mushrooms"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"

Post

I'd like some reese presets for massive x? Can you share?
100 High Quality Soundsets: Omnisphere 2, Dune 3, Tone 2 Synths, Pigments, Uhe Synths, Halion, Spire, and others.

TTU Youtube

Post

Kian Russell wrote: Sat Jun 29, 2019 7:38 am looks like sadowick has pulled his videos about massive x from youtube without explanation
thats the last time i will listen to him.
i've updated my rating from 100% to 0%.
Honestly if he realized that he messed up and pulled them off, that's actually a point for him. Maybe some damage was caused by him in terms of customers who would have loved MX not getting it but I personally was worried about long-term impact if those videos stay floating forever and turn into top results in Google or something.

Even if he doesn't make an explanation video, it's still a good move on his behalf to remove them. The central problem with those videos (besides some of the actual outright wrong claims) was the whole "this is unacceptable" part.

So yeah, hats off for him. If he's going to make another one of these, I hope he at least attempts to contact the company first and ask about various things. In fact, he could have made quite an interesting video if he consulted NI about their design choices and explained to people why, for example, audio rate LFO's don't have that level of anti-aliasing that normal oscs do.
Mushy Mushy wrote: Sat Jun 29, 2019 7:50 am
Kian Russell wrote: Sat Jun 29, 2019 7:38 am looks like sadowick has pulled his videos about massive x from youtube without explanation
thats the last time i will listen to him.
i've updated my rating from 100% to 0%.
:shrug: Still visible to me.
He pulled them off from being public, now they read "hidden". This is quite common practice; effectively it still means that the video is less likely to reach new viewers at least through search engines and youtube algorithms.

Post

digidennis wrote: Sat Jun 29, 2019 7:23 am Where's the scope on this thing? Come on, a tiny scope in the top bar or in the patching area is all I need
Tiny scopes are useless.

Post

Functional wrote: Sat Jun 29, 2019 7:54 am
He pulled them off from being public, now they read "hidden". This is quite common practice; effectively it still means that the video is less likely to reach new viewers at least through search engines and youtube algorithms.
Ah, gotcha.
"I was wondering if you'd like to try Magic Mushrooms"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"

Post

No real show stoppers for me as it suits me well, but there are two points might been discussed previously (it is a long thread I didn't read all):

1. Is there internal oversampling (like in u-he Diva or RePro for example)?
Maybe the low CPU is due to there is none?

2. Why they have used the GPU? There is also about 20% of usage to my nVidia card! Which is a lot for nothing going on! I mean I understand if there is a constant update for animation, but there is nothing really (20% on idle on init preset! See the image! Just to load the synth GUI make the GPU usage jump from almost nothing to 20%!):
You do not have the required permissions to view the files attached to this post.
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.

Post

Touch The Universe wrote: Sat Jun 29, 2019 7:50 am I'd like some reese presets for massive x? Can you share?
https://gyazo.com/7578d39f1191c63e276a85b6259a7774

This is my first sketch and I'm pretty much set with this. This isn't how you normally make a reese because you'd normally detune 2 oscs but given the structure here, I didn't bother with routing insert osc. If you want to do it that way, you could do something like 1 insert osc (with saw) at 0 pitch, then the wavetable ones at +12 and you detune the wavetable ones -15 cents and +15 cents respectively.

If you do the reese like that and go lighter on the unison detune, it sounds less harsh when you open the filter cutoff. This one sounds quite harsh when you open the filter cutoff, but I don't really do that. I like these heavily filtered reeses and they're part of my staple thing.

Do note, if you copy these settings, you will need to highpass the sides or else you will have ton of stereo information at sub frequencies which is something you DO NOT want.

Post

EnGee wrote: Sat Jun 29, 2019 8:03 am 1. Is there internal oversampling (like in u-he Diva or RePro for example)?
Maybe the low CPU is due to there is none?
Yes it's internally oversampled (which is why it doesn't need a HQ mode as it's already there)

Post

EnGee wrote: Sat Jun 29, 2019 8:03 am2. Why they have used the GPU? There is also about 20% of usage to my nVidia card! Which is a lot for nothing going on! I mean I understand if there is a constant update for animation, but there is nothing really (20% on idle on init preset! See the image! Just to load the synth GUI make the GPU usage jump from almost nothing to 20%!):
They used GPU to save CPU, of course. The GUI is rendered by Qt, so it's using Direct3D or OpenGL depending on platform.

This is in line with other more recent FX plugins released by NI, going all the way back to Replika, IIRC.

Post

aMUSEd wrote: Sat Jun 29, 2019 8:06 am
EnGee wrote: Sat Jun 29, 2019 8:03 am 1. Is there internal oversampling (like in u-he Diva or RePro for example)?
Maybe the low CPU is due to there is none?
Yes it's internally oversampled (which is why it doesn't need a HQ mode as it's already there)
Oh that's great then! So it is a clever coding then! Or maybe this is why they used the GPU as a 'helper'. I suppose a good video card is not for games only anymore!
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.

Post

EvilDragon wrote: Sat Jun 29, 2019 8:08 am
EnGee wrote: Sat Jun 29, 2019 8:03 am2. Why they have used the GPU? There is also about 20% of usage to my nVidia card! Which is a lot for nothing going on! I mean I understand if there is a constant update for animation, but there is nothing really (20% on idle on init preset! See the image! Just to load the synth GUI make the GPU usage jump from almost nothing to 20%!):
They used GPU to save CPU, of course. The GUI is rendered by Qt, so it's using Direct3D or OpenGL depending on platform.

This is in line with other more recent FX plugins released by NI, going all the way back to Replika, IIRC.
Great! Thanks for the info :)
Using: Cubase Pro 15, Reason 13, Tascam US-4x4HR, MODX6, DM12D, LaunchKey 49, Yamaha guitar(Pacifica 612v) and bass (BB234) and some virtual instruments and synths.

Post

Functional wrote: Sat Jun 29, 2019 7:43 am
Caine123 wrote: Sat Jun 29, 2019 7:34 am As massive is used a lot for bass etc i find massive x presets lacking and not impressed. But in pads, bells etc there are so awesome patches and they learbed me how to make some nice modulations.
Design your own!

Seriously, at least if you're into reeses, you will LOVE MX reeses. I'm a huge reese fan and I finally think I have the perfect solution for everlasting reeses after making just one with MX.

if you're into wubdub stuff then I guess tough luck, but there's plenty of ways to make them happen in MX. For instance, you could try the gorilla mode. I wasn't all too excited about it after testing it out mostly because it was clearly oriented towards wubdub stuff
Come on what a bad reply about ui. Im no ui designer but ni has lots of money for it. As a consumer i can have neg feedback.

And i love reeses. Hopefully i can hear/use some very soon maybe from you too ? :)
I dont like the wub wub much im and old dnb lover
DAW FL Studio Audio Interface Focusrite Scarlett 1st Gen 2i2 CPU Intel i7-7700K 4.20 GHz, RAM 32 GB Dual-Channel DDR4 @2400MHz Corsair Vengeance. MB Asus Prime Z270-K, GPU Gainward 1070 GTX GS 8GB NT Be Quiet DP 550W OS Win10 64Bit

Post

Probably why AVX is needed too

Post

Caine123 wrote: Sat Jun 29, 2019 8:15 am Come on what a bad reply about ui. Im no ui designer but ni has lots of money for it. As a consumer i can have neg feedback.

And i love reeses. Hopefully i can hear/use some very soon maybe from you too ? :)
I dont like the wub wub much im and old dnb lover
I posted above (or in the previous page) the preset (a picture of a preset anyway) I use currently for my reese. But it's bit more tamed than what you'd have in oldschool reese. Here's where I used that preset:
Functional wrote: Sat Jun 29, 2019 1:44 am https://picosong.com/wN8sc/

had some fun with Massive X although it's just that underlying pad playing the filtered supersaw and the filtered reese. But I'll be honest, I have absolutely _never_ been able to get a reese like this out of a synth without any additional processing. The only thing I did there was just monoing lows with the reese. The filtered supersaws are another story, but still, they got that staple & standard supersaw sound without costing an arm & a leg CPU-wise
Everything relevant for the patch is shown in the picture. The only thing that is missing is the envelope 1 settings. Just have enough of attack timing to not have a click (unless you want the click, I practically never do) and that's about it.

Post

Although the discussion about aliasing has started to annoy me as much as anyone else, I feel there is one more thing to be pointed out.

I did my own tests and found that, in general, aliasing in oscs and filters is a non-issue.
There are however two exceptions: Gorilla mode and PM.

Now, I'm well aware that PM is inherently susceptible to aliasing so I don't complain per se.
BUT: From my tests It looks like the level of aliasing is the same no matter if my host's samplerate is 48kHz or 96kHz. How can this be?

The quality roughly corresponds to Serum processing at 48kHz in Draft mode (not oversampled), which is rather awful. Can somebody confirm?

So, my request to NI would be to add a HQ mode to PM which does oversampled processing.

Locked

Return to “Instruments”