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

[McLilith]

If I had to summarize certain posts in this thread it would be one word: "Entitlement".

I guess if Massive X had implemented all the features that people are demanding in this thread they would be complaining about high CPU loads now.

That, or they would just demand other new features be added. Some folks are just insatiable complainers and feel a need to attack anything that doesn't instantly place them into a pleasure coma.

[Reefius]

But tell me, please - in which sort of production would you use a 10th octave square wave audio-rate modulating something else? Honestly.

"Symphonies for Bats - An Evening in the Cave"

That's just cruel! Torturing bats with all that aliasing

[Functional]

Didn't someone mention that their cat didn't like sinewaves? Maybe it was the aliasing.

[BlitBit]

But tell me, please - in which sort of production would you use a 10th octave square wave audio-rate modulating something else? Honestly.

"Symphonies for Bats - An Evening in the Cave"

That's just cruel! Torturing bats with all that aliasing

Personal note for me: Reefius does not like distorted guitars but has a heart for bats.

[Reefius]

Personal note for me: Reefius does not like distorted guitars but has a heart for bats.

You know me better than I know myself

[Functional]

If I had to summarize certain posts in this thread it would be one word: "Entitlement".

I guess if Massive X had implemented all the features that people are demanding in this thread they would be complaining about high CPU loads now.

He isn't even demanding them. I doubt he has any kind of actual usecase in mind for audio rate LFO's that would benefit from anti-aliasing methods let alone any kind of usecase for audio rate LFO's going at C9 and above.

To me this doesn't sound like it comes from a practical perspective of using equipment to make music. Kind of like looking at something as an engineer without ever considering the practical appliances. An illustrative analogy would be something like this:

"Are you aware that this corner isn't perfect and it's way too round?" says the engineer
"But sir, this is a sledgehammer..." says the construction worker

[mladi]

But tell me, please - in which sort of production would you use a 10th octave square wave audio-rate modulating something else? Honestly.

"Symphonies for Bats - An Evening in the Cave"

Chapter II: Hang with us.

[pixel85]

If I had to summarize certain posts in this thread it would be one word: "Entitlement".

I guess if Massive X had implemented all the features that people are demanding in this thread they would be complaining about high CPU loads now.

Then it would have too much features and would be too complex.
Also:
- GUI (for as many reasons as many people exist)
- Lack of washing machine functionality
- Not enough 'X' type presets
- Too much of 'Y' type presets
- Wagtunes will not buy it because he have all the synths he need (+ 20 pages of explanation why, for people who still can't get over it)
- It's not Serum
- It's not Dune
- It's not [insert any vst name here, including effects because why not?]
- Still features 'X' and 'Y' are missing
- No character because aliasing is missing
- Too much of character
- MX contributes to global warming
- MX is responsible for flat earth and WWII
- Faders should replace knobs and knobs should replace faders
- Too complex for being a preset browser/rompler
- NOT ENOUGH LFO!
- 1 more oscillator would change it diametrically

Ok... no more ideas for now

[BlitBit]

But tell me, please - in which sort of production would you use a 10th octave square wave audio-rate modulating something else? Honestly.

"Symphonies for Bats - An Evening in the Cave"

Chapter II: Hang with us.

Not to forget the smash hit "Upside down I'm turning me".

[Reefius]

Then it would have too much features and would be too complex.
Also:
- GUI (for as many reasons as many people exist)
- Lack of washing machine functionality
- Not enough 'X' type presets
- Too much of 'Y' type presets
- Wagtunes will not buy it because he have all the synths he need (+ 20 pages of explanation why, for people who still can't get over it)
- It's not Serum
- It's not Dune
- It's not [insert any vst name here, including effects because why not?]
- Still features 'X' and 'Y' are missing
- No character because aliasing is missing
- Too much of character
- MX contributes to global warming
- MX is responsible for flat earth and WWII
- Faders should replace knobs and knobs should replace faders
- Too complex for being a preset browser/rompler
- NOT ENOUGH LFO!
- 1 more oscillator would change it diametrically

Ok... no more ideas for now

[pixel85]

Oh f* I just finished track with 99% MX in use. Now I need to put it into a trash because MX have aliasing. Entire day wasted. Thank you guys! Now I can put this ugly MX with aliasing put into a trash! What a waste! In
2...
0...
1...
9...
Synth with aliasing! IT CAN'T BE!!!!!!!!!!!!
That's enough! I'm going back to ProTracker.

Just rename ("alias") the track. Problem solved.

With steep HPF at 15kHz on Master Bus to just keep the real juice

[EvilDragon]

OK I must say I am confused now, Sadowick. I just set the Sin-Tri-Saw-SQ wavetable direct to output, WT position at max (so it's a square wave), bypassed filter and all, then did a 96 semitone pitch bend on it (because MX is crazy like that it allows you such huge bend ranges, pretty cool) and recorded the output. Here's the result:

https://app.box.com/s/z1vrk9p037ggh8nwlejz2iy6ir6ef0pt


It's a WAV file. Can ANYONE hear any aliasing here? Even SPAN doesn't show anything that's not at around -130 dB or so.

[Functional]

It's a WAV file. Can ANYONE hear any aliasing here? Even SPAN doesn't show anything that's not at around -130 dB or so.

Bats can, I'm sure.

[ghettosynth]

If I had to summarize certain posts in this thread it would be one word: "Entitlement".

I guess if Massive X had implemented all the features that people are demanding in this thread they would be complaining about high CPU loads now.

He isn't even demanding them. I doubt he has any kind of actual usecase in mind for audio rate LFO's that would benefit from anti-aliasing methods let alone any kind of usecase for audio rate LFO's going at C9 and above.

To me this doesn't sound like it comes from a practical perspective of using equipment to make music. Kind of like looking at something as an engineer without ever considering the practical appliances. An illustrative analogy would be something like this:

"Are you aware that this corner isn't perfect and it's way too round?" says the engineer
"But sir, this is a sledgehammer..." says the construction worker

Exactly! If you compare MX to other synths that have this feature, e.g., Bazille, MX compares favorably. Serum does exhibit lower aliasing on square waves than MX, but, when tested properly it's not like MX is unusable. My tests show the Aliasing components to be about -114 dB or so, I have pictures, I can't be assed to post them, also, I want to be careful to make sure that my observations aren't side effects of the testing scenario, more on that later. Serem is quite low, about -138 dB. But, Serum's oscillators are simple by comparison to MX, so it's a design tradeoff. Also, AFAIK, you can't listen to Serum's LFOs.

[AcrossTheSky]

wow Massive is now more massive - 1.6gb + 59mb lib....downloading....was 800mb before...hmmm