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

[Stefken]

I wish I can purchase only synths coded with AVX now!

Well, I expect to see it more and more, until it will be standard stuff (at what time the next evolution will already be knocking on the door ).
Several devs have already upgraded existing synths to AVX.

[Stefken]

NI should be a lot more explicit about what processors have AVX.
I read - and assumed - that working on Mac OS 10.12 as the minimum suggested would ensure I would be partying with Massive X... but no!!
My 2010 iMac that runs like a dream doesn’t have AVX... which I just found out after upgrading to Komplete 12:( Bummer!
So as a warning... Macs earlier than 2011 won’t work with Massive X.

I don't think it's NI's responsibility for users to know what kind of computers they have and what's in them.

How many mac users do you think know exactly what hardware they are using?

[perpetual3]

NI should be a lot more explicit about what processors have AVX.
I read - and assumed - that working on Mac OS 10.12 as the minimum suggested would ensure I would be partying with Massive X... but no!!
My 2010 iMac that runs like a dream doesn’t have AVX... which I just found out after upgrading to Komplete 12:( Bummer!
So as a warning... Macs earlier than 2011 won’t work with Massive X.

I don't think it's NI's responsibility for users to know what kind of computers they have and what's in them.

How many mac users do you think know exactly what hardware they are using?

This Mac user is hyper aware of his hardware configuration. So, at least one.

[el-bo (formerly ebow)]

NI should be a lot more explicit about what processors have AVX.
I read - and assumed - that working on Mac OS 10.12 as the minimum suggested would ensure I would be partying with Massive X... but no!!
My 2010 iMac that runs like a dream doesn’t have AVX... which I just found out after upgrading to Komplete 12:( Bummer!
So as a warning... Macs earlier than 2011 won’t work with Massive X.

I don't think it's NI's responsibility for users to know what kind of computers they have and what's in them.

How many mac users do you think know exactly what hardware they are using?

A huge amount

[FapFilter]

To be fair, i think AVX is more of an unknown feature that most people aren't / weren't even really aware of until now.
The processor's frequency and RAM size you knew when you were evaluating your purchase. With your OS version number you are confronted every single time you boot it up and are also aware since like forever that a specific version is required, or at least recommended.
I don't know about Mac OS, but at least on Windows you can, at least according to my experiences, more often than not use software labeled as “Windows 7/8/10“ (or higher) with lower version numbers than stated without any hickups. At least when Windows 8 was still the thing i had no trouble with anything “requiring Win 7 or higher“ on my XP system.
Everyone knows i5 is nice affordable technology, while i7 and i9 are cutting edge, for a price.
AVX might very well be a thing that was in every CPU since like forever, just like MMX and other stuff noone is even talking about anymore.
I haven't been in the game for a new CPU for almost a decade, but how big was and is the fanfare about AVX? Is “sporting AVX super duper ultra mega techology“ printed on every box in big letters?

[Stefken]

NI should be a lot more explicit about what processors have AVX.
I read - and assumed - that working on Mac OS 10.12 as the minimum suggested would ensure I would be partying with Massive X... but no!!
My 2010 iMac that runs like a dream doesn’t have AVX... which I just found out after upgrading to Komplete 12:( Bummer!
So as a warning... Macs earlier than 2011 won’t work with Massive X.

I don't think it's NI's responsibility for users to know what kind of computers they have and what's in them.

How many mac users do you think know exactly what hardware they are using?

This Mac user is hyper aware of his hardware configuration. So, at least one.

I think there might be more. I've heard there is also one in California.

[midi_transmission]

I absolutely LOVE the accelerated knobs approach -- first discovered it on my new Arturia Microfreak (which I'm spending most of my time with these days), and it really helps, either when you're using encoders on a synth, or a mouse in a PC-based GUI.
...

So the conclusion is that there is not a one fits all solution for the mouse speed knob thing. We need control about the accelerated knob and knob speed behaviour.

Bering a hater about the slow speed + acceleration thing, I think it could work for me to have a negative acceleration at very very very low mouse speed just to dial in small increments. But this should never interfere with normal knob tweaking for modulating sounds.

But in case of doubt I just take a linearish knob speed with a modifer knob for high resolution like in the past.

This kind of UI control issue is always a dilemma: one gets used to certain habits and norms, and if anything breaks same, it feels intrusive and alien at first, until it, too, becomes habitual.

Question here is whether this is just a TBD or intended as working. We’ll see!

Yes and no. You're right that it sometimes like this.

But sometimes things worked just fine before and you don't want that something that works great for you does change to something that doesn't work. I never had a single problem with the standard 'usual' knob speed in most other plugins. The funny thing, for the next person it maybe the other way around...

Sometimes there is just no one fits all solution. And it's quite arrogant sometimes (not meaning you here!) to think that only because the change works great for you that it works for everyone.

I don't think that this regard was a TBD. The knob speed worked great for the developers so they thought it is great for others too.

[chk071]

Good follow up post here on the aliasing thing: https://www.native-instruments.com/foru ... st-1807029

Maybe we can finally take it to rest (although i doubt it... ).

Regarding the AVX: Ok, i also think that people weren't aware of that, i wasn't either, until it was mentioned here. But, the moment i read it, i checked if my CPU supports it, and it did, like almost every other CPU in the last 10 years. Apple notoriously hoax their users, so, i'm not surprised at all that even the most expensive Mac's from 9 years ago don't have a AVX capable CPU.

[Maeldron]

It’s such an unfinished product it’s not even in a beta state. I take it as an offense they released it like this.

1. There is a search icon next to the preset browser. It does not work. You can’t search. It’s only decoration.

2. There is no undo/redo function.

3. The presets are a bad joke. All my software synths sound better. Not because they all have a better sound engine for sure, but because I don’t buy synths with as garbage presets as Massive X has.

4. When you edit the envelopes, the graphical presentation (blue area) does not change. (I edited Env 2) Again, it’s not even a beta software stage.

5. There is a filter below OSC 1. It seems like some kind of LP filter, but if you turn it to zero, there is still sound coming through it. It’s only "tone control". The filter is right from the oscillators. It’s easy to find it because, by default, the tone control is labeled as "filter", and the filter is labeled as "Asimov".

6. What annoys me the most is that there is no numeric feedback about any of the controls. (Same as Massive. Probably that’s why I don’t use it.)

If I tweak something, I have near to zero chance to put it back to the same position. If they don’t want to display meaningful values (for example, Hz for a filter), then why can’t they display an abstract number? Something between 0 and 100 or -100 to 100. u-he synths do it, and most of the time it’s perfect. Having no feedback is just stupid. I wonder if I have or ever demoed a single software synth, outside of NI, that had no feedback about the tweaked control. Even my hardware synth has it.

7. There is no right click function in it. There is no context menu at all. Not on the controls, not on the presets. Nowhere. Thanks for making automation as uncomfortable and time-consuming as possible.

In about one year, it might be a finished product, or at least a stable beta release.

Now I’m wondering if I can find any other reason why I upgraded my Komplete 11 Ultimate to Komplete 12 Collectors Edition.

Don’t buy it without a demo.

[chk071]

It’s such an unfinished product it’s not even in a beta state. I take it as an offense they released it like this.

Lol... i stopped reading right there.

Think i need a break from internet forums.

[BlitBit]

I wish I can purchase only synths coded with AVX now!

Well, I expect to see it more and more, until it will be standard stuff (at what time the next evolution will already be knocking on the door ).
Several devs have already upgraded existing synths to AVX.

There's already AVX-512 which can operate on registers twice the size of AVX: https://en.wikipedia.org/wiki/AVX-512. Because it's newer than AVX there are obviously fewer CPUs that support it.

I think AVX is a good choice. It's 10 years old and therefore supported by modern CPUs.

[vurt]

time for a musical interlude

[Sinisterbr]

I agree, requiring AVX was the right choice. It's an almost 1 decade old technology and brings big advantages, aparently. Can you imagine how big would be the CPU hit without using it?

[Stefken]

I wish I can purchase only synths coded with AVX now!

Well, I expect to see it more and more, until it will be standard stuff (at what time the next evolution will already be knocking on the door ).
Several devs have already upgraded existing synths to AVX.

There's already AVX-512 which can operate on registers twice the size of AVX: https://en.wikipedia.org/wiki/AVX-512. Because it's newer than AVX there are obviously fewer CPUs that support it.

I think AVX is a good choice. It's 10 years old and therefore supported by modern CPUs.

Yep, my vote goes to AVX as well. See, my CPU doesn't support AVX-512, so it's a bad choice.

[McLilith]

It’s such an unfinished product it’s not even in a beta state. I take it as an offense they released it like this.

As someone who has worked on multiple private alpha and beta testing teams, and who used to be the head tech support person for a developer, I find your statement offensive. It's patently false.