No support for MacPro 5,1? AVX Compatible processor required...

Can't download it from Native Access as it says that an AVX compatible processor is required.

So....guess I'm out of luck then?

Peachy.

 

This was stated on the product page months ago.

 

Bad decision. Hope neither NI nor other Vendors follow this direction.

 

I hope that isn’t a trend either, though I don’t begrudge them the decision.

However I really don’t recall seeing that when it was announced as part of the K12 launch though, and Massive was a big factor in my decision to update from K10U since I owned most of the added synths already. I could have missed that detail though and if I did, it’s on me.

Anyone recall if AVX was always a requirement or did it emerge later?

 

AVX CPUs have been out there for about 8 years now. You don't expect those 5,1s to last and be supported forever, do you?

AVX requirement for Massive X was mentioned straight away with initial bits of info, IIRC.

 

Why shall one change a powerful running system? (from your side: to run 1 softsynth) makes no sense for me.

 

Nobody forces you to change it, but I reckon at some point you will change it, no?

 

Sure. If the system slows down my workflow or gets broken. Not for just 1 plugin. Other words: never thought about a hardware upgrade for years, because it wasn´t needed. As long as my Sequencer supports the current macOS there is no reason... so, maybe in 3-4 years.

 

No of course not. But I can still be disappointed, yes? Like I said, I missed the AVX requirement so to be waiting this long and anticipating the release only to find ON THE DAY of release that I can't run it, is a let down. Even if it is my own fault.

On the other hand, the system is still chocking away filling most needs with little complaint. Lord knows that between Bitwig's Grid, VCV, and Phase Plant I have more than enough to keep me busy...for years really.

Massive just looks and sounds like it will be pretty damn amazing. Just sorry I can't partake is all.

 

I was pretty shocked. Don't recall seeing that requirement. I have two Xeon X5670 processors that handle everything I've ever thrown at them with ease. Yes, it is an older processor, but still...

 

The various flavours of AVX can dramatically improve the performance of certain instructions including those that are used by VSTs.
The same was the case with SSE and FP in the past.
By building a VST around modern CPU instruction extensions you can really push the envelope.
But if you keep backward compatibility, the risk is that people with older hardware will have a really bad experience.
So isn't it better to develop software that is forward looking and keeps the oldies out of the loop rather than stagnating development?
Developers don't like to limit their audience but after 8 years or so it seems fine to draw a line in the sand.
How many people with 8+ year old systems are still spending a lot of money on new software?

I'm curious which aspects of MX use AVX!

 

Given that among some of my personal reallife mates there's 6 5.1 Mac Pro owers, all still keeping their machines as up to date as possible, I'd gather it's at least quite some folks (myself included as well). These machines are still able to take a lot of things you throw at them with ease, in Apple land you will at least need a fully upgraded new Mac Mini to get the same performance (at least in terms of multithreaded tasks).

Now, I can pretty much understand that a software company known for innovative products will not be able to take too much care about what likely has to be rated "yesterdays technology" (at least in terms of CPUs). Then there's Apple rendering those 5.1 machines obsolete in around 2 years as well (Mojave will be the last officially supported OS to run on them). And while that is another case of artificial obsolescence (there's no technical reasons for it), it will still sort of end the lucky years of 5.1 owners eventually. And from all I know, apart from those very Mac Pros, there's rather little AVX-less CPUs in the audio world left.

Still a sad thing because personally, I have pretty much zero plans to buy a new machine (well ok, maybe a Windows convertible, but that won't become my main audio machine) any day soon. I will rather freeze this machines status quo and keep working.

Anyway, I'm wondering if it would've been all too tough to also come up with a non-AVX version of Massive X - maybe along with a big badge going like "Yes sir, I will run on your machine but I will possibly make it choke!".

 

Asteroids were out there 8 years ago too but none have hit me yet. Those bits of info you mention, were they listed on the buy page when upgrading Komplete? Link? You "act" like this news is something we should have all known about just because you did. Might want to rethink that cause its a foolish thing to suggest, especially to people who bought into the upgrade and now can't use it, but can run every other VST and DAW out there.

 

The AVX requirement has been in the system requirements section--generally at the bottom of the page in boldface--from the get go, at least since last fall. If you didn't bother checking or your gut told you different, that's your business. Likewise if you didn't bother checking whether your CPU was compatible.

 

It's true... Nobody forces us to change and use Massive X ! Long life to early N-I plugins: Absynth, FM8, Guitar Rig Pro54, Battery 3, etc.. old things are better.

 

Not in every aspect (other than you can run them)

 

Oh, I don't doubt that it was listed on the bottom of the 9th page of the newspaper right after the Obits. So "generally" then, can you also show me the link on the buy page for the update where the disclaimer "in BOLDFACE" was listed also, so that people could see this before clicking the buy button? My beef is that this information should have been on the purchase page in BOLDFACE as well. Yes, we missed this and it was our fault for not reading every detail as good lawyers always should. But now they (NI) has also created a distrust of their next upgrade/update if they do not fix this I'm thinking. We will see. Folks will now be leary of something they didn't read or didn't see before forking over another $300 bucks for a promised synth that won't run again. But hey, its no skin off your nose. Best of fun to those who saw this at the "bottom" of the page in boldface before the purchase and was astute enough to know what it even meant. Others like me will get by without it, and "in general" future, a few NI updates as well.

 

yeah.. pissed off also. Massive X is the whole reason i got the komplete upgrade. dont think ill buy any updates anymore.

it really felt more like lying thorugh ommision.

yes... maybe it was stated somehwere , that poeple that work, deal with NI would find.. but for the average normal user AVX is meanilingless in the audio world conext... and at most for us the AVX was at most a "additional" thing if they had AVX. not a "your computer is useless for this plugin".

 

For my taste: these old syn-things (as Massive V.1) sounds better ! I can't explain why.
Maybe it's like the good mature wine.
(But, "tous les goûts sont dans la nature..."

 

My opinion on this one as I am a developer myself:
If you don't use new features then you get stuck in the past. Nobody complains about buying a new graphics card to play newer games. Everyone checks whether the game needs DX12 or whatever support. NI made the logical step to harness the power of modern cpus (and AVX is available since 2011)

So everyone here is complaining that they didn't read anywhere that AVX is required. Shame on you for not reading properly! Going to K12 specs&requirements page is the least you can do. Same as when trying to use a product without reading the manual first and then give a bad rating because it "doesn't work".
Take your time, may that be a lesson for you. Yes, NI could've made it *more* obvious, but in the end they didn't hide it.