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

Spirit2017 wrote: Thu Jun 27, 2019 7:55 pm Big synth developers produce bad sounding synths in the last years and this is a fact!I'm disappointed about that plastic sound :(
Get a new pair of ears, pronto. :)


What you say is not a fact, it's a subjective opinion (that's also wrong).
Last edited by EvilDragon on Thu Jun 27, 2019 7:58 pm, edited 1 time in total.

Post

Spirit2017 wrote: Thu Jun 27, 2019 7:55 pm Big synth developers produce bad sounding synths in the last years and this is a fact!I'm disappointed about that plastic sound :(
...what "plastic sound"?

Post

I can understand the "character" thing. Massive X sounds modern, and doesn't have loads of character. The sound is great nonetheless. it just doesn't have a immediate distinction.

Post

With Monark filter it doesn't have to sound "modern" at all, tho. :)

Post

EvilDragon wrote: Thu Jun 27, 2019 7:57 pm
Spirit2017 wrote: Thu Jun 27, 2019 7:55 pm Big synth developers produce bad sounding synths in the last years and this is a fact!I'm disappointed about that plastic sound :(
Get a new pair of ears, pronto. :)


What you say is not a fact, it's a subjective opinion (that's also wrong).
im pretty sure if you add the "!" its does actually become a fact.
:ud:

Post

"Did you ever automate 30 parameters at once from a single plugin in the same track? Like, honestly."


I wouldn't with a mere synthesizer. Massive I was doing 6 or 8.
I do over 30 with BFD3 and VSL Synchron. These have mixers. I automate 0 of the former that isn't fr. a mixer, except for CC for variable hihat(s).

Post

On the macro naming thing. I posted on this earlier and after more experimenting I found the following:

If you map a new new macro the name changes on Massive X but it remains Macro x on maschine.

If you remap an existing macro, again, the name changes on Massive X but it remains whatever it was prior on Maschine.

If you double click the name and manually edit it, this updates Maschine.

Post

EvilDragon wrote: Thu Jun 27, 2019 7:57 pm
Spirit2017 wrote: Thu Jun 27, 2019 7:55 pm Big synth developers produce bad sounding synths in the last years and this is a fact!I'm disappointed about that plastic sound :(
Get a new pair of ears, pronto. :)


What you say is not a fact, it's a subjective opinion (that's also wrong).
Can it be wrong if it is subjective?

Post

buzz1 wrote: Thu Jun 27, 2019 8:04 pm
EvilDragon wrote: Thu Jun 27, 2019 7:57 pm
Spirit2017 wrote: Thu Jun 27, 2019 7:55 pm Big synth developers produce bad sounding synths in the last years and this is a fact!I'm disappointed about that plastic sound :(
Get a new pair of ears, pronto. :)


What you say is not a fact, it's a subjective opinion (that's also wrong).
Can it be wrong if it is subjective?
not usually, but hes just broke the laws of opinion physics.
:ud:

Post

jancivil wrote: Thu Jun 27, 2019 8:03 pm "Did you ever automate 30 parameters at once from a single plugin in the same track? Like, honestly."


I wouldn't with a mere synthesizer. Massive I was doing 6 or 8.
I do over 30 with BFD3 and VSL Synchron. These have mixers. I automate 0 of the former that isn't fr. a mixer, except for CC for variable hihat(s).
Yep, it does make sense with plugins that have their own mixers, like drum samplers.


Thanks for confirming my point :)

Post

Vortifex wrote: Thu Jun 27, 2019 7:30 pm
ghettosynth wrote: Thu Jun 27, 2019 7:22 pm
Vortifex wrote: Thu Jun 27, 2019 7:18 pm
Functional wrote: Thu Jun 27, 2019 7:17 pmDon't quote me on this but I don't think you can
WTF? That seems like a pretty big omission to me.
Not at all. It's a mono path up to the effects stage where it becomes stereo. To do otherwise would either force the modular signal path to be stereo which would double the CPU for all of the other poly modules, or complicate the path by making the modular environment stereo and then having the modules either default to mono with one connection or be stereo otherwise.
Icarus, Hive, Dune and Synthmaster manage it just fine. Ah well.

Edit: quoted wrong person but point is the same.
If you're panning oscillators before feeding filters then the filter is stereo, full stop. So if those synths "manage" it then it's because it's a choice to have a stereo signal path. Hive is designed to be easy on the CPU, it does not sound as good as the Monark filter, full stop. Synthmaster is fun, but not even close to being in the same league. I don't think Synthmaster even registers on my CPU meter.

It's a design choice.

Post

EvilDragon its a fact!

Post

see, he did use the "!" :)
:ud:

Post

Spirit2017 wrote: Thu Jun 27, 2019 8:15 pm EvilDragon its a fact!
It's not a fact without a PROOF. Where's your proof that can be independently verified or disproved? Other than just randomly rambling about it, and, yes, ending your sentences with an exclamation mark?

It's not a fact :)

Post

EvilDragon wrote: Thu Jun 27, 2019 8:00 pm With Monark filter it doesn't have to sound "modern" at all, tho. :)
With modern i mean... bright, high end, precise. It has the Monark filter, but, as far as my ears tell me, Monark has a lot more saturation going on. You can add that to Massive X, of course, but... to me, it rather sounds modern, precise. And fat. ;) Not the thin, boring, bland precise and clinical, which some other modern synths do.

Locked

Return to “Instruments”