Does multicore support really work in maschine 2?

It seems like it's only running on one core. I have a quad core i7 2.4 Ghz processor and 12 GB RAM. The CPU meter inside will max out when my task manager will say it's at like 30 - 40%. I don't understand why it does this. I've messed around with my audio buffer size and sample rate but it doesn't help.

 

Works extremely well here on my i7. I see multiple cores working and I can get it over 80% in task manager before any spikes occur. Keep in mind you want to look at each core in resource monitor. The load is distributed per sound similar to how all DAWs distribute the load per track. So if you have a plug-in or series of plugs on a single sound, it can only be processed by one core.

Pure processing power is only part of the equation. Other bottlenecks occur such as your sound card drivers. If you are using your on board card on your mother board then it won't get you the best performance. No matter how much CPU power you have it will not make optimal use of it. There can be up to a 400% difference in low latency performance between some of the better pro audio cards like RME or Lynx and what you get stock on your MB.

There are drivers and processes that may be running in the background that is hurting your audio performance. If you did not get your rig professionally built by a DAW builder or do some standard audio tweaks to the OS yourself, you are likely not going to get the best performance. Most off the shelf computers have applications and drivers that will cause high DPC that will really hurt audio performance. Also, some bios settings may need to be turned off to prevent CPU throttling. NI have an article on some common tweaks to help optimize your PC for pro audio. http://www.native-instruments.com/e...2/windows-7-tuning-tips-for-audio-processing/

 

yeah, i would say that the multicore support is by far the best feature of 2.0

 

Works really well for me on my old 2010 C2D macbook, I can run projects I never could pre 2.0. Best feature of 2.0 for me also.

 

Working well on my quad core i7 OSX 10.9.1 installation

 

I'm trying all of those steps. I'm running the Latencymon software and it's telling me I have a group of 8 cores on the CPU but only one has a ISR count, whatever that is. What is going on?

 

Well I just checked my resource monitor and all if my 8 of my CPU virtual cores are being used after all, but 3 of them are barely being used. So why does it only use a little bit of my half of my total CPU still and Maschine says it's maxed out?

 

Like I explained, if one of your sounds is drawing more load then one of your cores can handle then it will peak and cause dropouts regardless of how many other cores are idle. One sound can't be distributed across more than one core. Also, there is not necessarily a 1/1 of what you see in task manager and what your asio driver can handle without dropouts. They are two different things that related but not fully.

 

i've been wondering the same

diva synth supports multicore and it needs it. major cpu hog!

 

Kontakt does as well, and also Maschine when used as a plugin. Though they seem to be the exception rather than the rule.

 

I actually don't even put that many plug ins on one sound. I might have a few Maschine effects and maybe one Komplete effects on some sounds but I route audio into another sound or group for a lot of effects.

 

Routing is the key here, if you route from one pad to another, that route can only be run on a single core, so any routing you do is in effect removing multicore support through that route.
Now before anybody thinks this is poor design, it is actually exactly how you want it, it can be designed in a different way but the other way is horrid and adds so much latency that Maschine (Any DAW) would become unusable.

 

Does this also apply to routing sounds on a Mac? i.e. if I route some sounds, say pads 1 and 2 into pad 16 as an aux bus, will this restrict all three of these pads (1, 2 and 16) so that they all only running through a single core?

My Maschine seems to be peaking and spiking on the CPU meter, but I don't have loads of FX on each pad (at least I don't consider I do), and I'm running on a pretty high end MacBook Pro Retina 2.8GHz - Intel Core i7 - 16GB Ram - 1TB SSD.

I don't really understand why it is peaking some much on Maschine when activity monitor barely shows any usage on my CPU...

Any advice would be really appreciated!

I have already tried optimising all of the settings recommended on the NI page to no avail (http://www.native-instruments.com/e...01/mac-os-x-tuning-tips-for-audio-processing/), and I have experimented with various sample rates and latency settings...

 

Open activity monitor and press cmd+2 you will see meter for all your cores.
Do you have dual or quad-core? If your MBP is 13" it's dual so you will see four meters. Odd meters (1st and 3rd) are real cores, even are virtual. So you'll see if all are working.
Analogously – if you have 15" you'll see 8 meters.

 

Sorry, I should have stated its a Quad Core 15" Mid 2014 model.

Yeah I've got the activity monitor running so that I can see the graphs of my cores and they only seem to get up to about 50% tops on the odd meters and much less on the even ones.

 

I really would like to know this either.

 

Run it as a plugin in a DAW and you throw all that out of the way, almost all DAWs will use a single core per channel. VST3 support would make things better both inside Machine and as a VST 3 host itself (will save CPU cycles when it does little or nothing, IF implemented well). Sonar in fact has an exclusive trick which will move the plugin to the least used core I believe which is quite useful.

 

Actually, Maschine 2 vst is one of the few plugins that is multiprocessor aware. It will multi-process it's hosted plugins independent of your DAW. It is not as efficient at doing this compared to most DAW's though.

 

Happy to be corrected, but from what I understand though the DAW effectively kills off this option even if selected. Normally it's one core per channel in the DAW. Having said that I've never tested it.

 

How are sends / groups handled ?