MassiveX Hardware Requirements

I deliberately omitted the space from 'Massive X' in the thread title because, when I searched the forum for Massive X, it said X was too short and would be ignored. So of course what I am really trying to find out about is Massive X system requirements or Massive X hardware requirements!

About two months ago, I read somewhere on the NI web site that Massive X was going to require a processor that supported ???, an acronym I did not know about. In subsequent searches to check whether Massive X is actually going to run on my powerful and not very old computers, I have found nothing whatsoever about Massive X system requirements or hardware requirements. Perhaps NI have taken the information off their web site?

Any information would be appreciated. Thanks.

Simon

 

I don't think anybody here can tell you that. We will know more about system requirements "from the horse's mouth" closer to Feb 2019, I'd say...

However if your computer is "not very old" as you say, it could very well be just fine for Massive X. Which CPU is in your computer?

 

I run NI software on two computers.

Workstation purchased January 2017
Processor: Intel Xeon E5-1620 v4, 4 cores
Processor Speed: 3.5 GHz base frequency, 3.8 GHz max Turbo frequency

Laptop purchased in May 2017
Processor: Intel Core i7-7500U, 2 cores
Processor Speed: 2.7 GHz base frequency, up to 3.5 GHz with Intel Turbo Boost

 

That Xeon will def perform better due to higher base clock and higher max CPU frequency.

 

Yes, though current NI software runs very well on both computers.

I have downloaded the full specifications for both processors from Intel. If that mysterious acronym resurfaces, I will be able to check whether it will be a problem.

As the acronym (I did not imagine it!) seems to have disappeared, perhaps the Massive X developers got cold feet about requiring hardware that might overly restrict the user base. This is all speculation of course. As you say, we just have to wait for further official announcements.

 

There should be no mysteries. It's either SSE (which is commonplace) or AVX (which is starting to get more usage in plugins lately - not all of them, but some).

 

Thank you! It was AVX. If that eventually becomes confirmed as a requirement for Massive X, I am covered on both my computers. Here are the relevant lines of the specifications.

Processor: Intel Xeon E5-1620 v4
Instruction Set Extensions: Intel AVX2
All my older NI and other plugins work on this computer. So it surely supports SSE too, even though SSE is not mentioned in the specification.

Processor: Intel Core i7-7500U
Instruction Set Extensions: Intel SSE4.1, Intel SSE4.2, Intel AVX2

 

Of course, now I know what I am looking for, I have found the documentation:
https://www.native-instruments.com/en/products/komplete/bundles/komplete-12/specifications/
It says:
"Note: MASSIVE X requires an AVX-compatible CPU to run."

 

Which command I've to use the sys show me what AVX my computer carries? Win7pro

Found out 12 processors i7-3930K 3.2 GHz
Wikipedia wrote this processor works in Sandy Bridge E cpu with AVX

 

Hello Paule,

Glad you figured it out. For anyone else with the same question:

If you don't know the processor model, your computer should be able to tell you.
On Windows 10: Control Panel\System and Security\System

Once you known the processor model, you can look up its specifications on the manufacturer's web site:
the heading where AVX will be mentioned if supported will be 'Instruction Set Extensions' or similar.

For example, the specifications for Paule's processor are here:
https://ark.intel.com/products/63697/Intel-Core-i7-3930K-Processor-12M-Cache-up-to-3-80-GHz-

Cheers,
Simon

 

hi heres my chip--

ntel® Core™ i7-5820K Processor
15M Cache, up to 3.60 GHz

on the intel site it says its avx2 does that mean massive x ill run ok with it?

https://ark.intel.com/products/8293...rocessor-15M-Cache-up-to-3-60-GHz-?q=i7-5820k

 

Yes, you've the double capacity you need to drive Massive X

 

thanks paule for your help..have ni gave a proper release date for massive x?

 

There are many CPUs nowadays that have AVX, so that shouldn't be a terrible problem for most people. Unless they really have ancient machines, but at that point you should ask yourself why would you want to do that to yourself

 

I just optimized my pc
https://www.native-instruments.com/...test-high-end-machines-omnibus-thread.343659/

 

That sucks as that leaves out those of us who run Mac Pros earlier than the iTrashcan. For reference here's a page with the various cpu's in Macs and other info some of which should also work for those on Windows machines: https://en.wikipedia.org/wiki/List_of_Macintosh_models_grouped_by_CPU_type

 

Don't be so dismissive of older computers. There are plenty of us who run 2012 and earlier Mac Pro's that get a LOT of work done in studios the world over. Not everybody needs new machines when the older stuff properly set up work just fine.

I just don't understand why NI went stupid with this requirement. Guess I won't be buying this as I was looking forward to it considering how well the original Massive has worked for me. Couple this with what NI did with Kontakt 6 I'm glad I didn't waste money on the K12 upgrade.

 

AVX is a really good thing, since it enables CPUs to process more stuff in a single CPU clock. Otherwise the same action would take roughly 2-3x more CPU. Think about this a little bit. It's not about "going stupid", it's about actually putting things that modern CPUs have had for years to good use instead of just not using it and making your product work slower because of that. Bummer that your twin Xeons from 2012 don't have it - AVX was introduced in 2011 BTW, on Sandy Bridge CPUs.

 

How many speed give an AVX2?

 

AVX2 is expanding the registers to 256-bit, from original AVX's 128-bit. The idea is that you can do the same operation on several vectors at once, for the cost of a single operation instead of <number of vectors>. So this doesn't easily translate to "speed", it's more about how much data can be processed in a single operation. For some things this can be a great performance boost.

https://en.wikipedia.org/wiki/Advanced_Vector_Extensions

Consider it as next level SSE.