Plugins creating cpu overload within maschine 2 software.

Hi all, funny enough I had issues on 2 Setups ... the double Xeon but also my Elitebook 8560W which is an I7 2860QM.
On both setups the same problems: M2 CPU Overload (not real CPU) when Projects were getting too big or when I used a lot of VST's.
You know I'm no preacher, so do with the given info as you all please, squible about it if that's what you like .
Facts are that on both platforms I don't have any stability or latency problems anymore.
Since my AtariST I haven't had a more stable system.

Have a look on one of those DAW manufacturers user forum:
http://forum.cakewalk.com/Turn-off-Hyperthreading-m73123.aspx
http://forum.cakewalk.com/Hyperthreading-Yes-or-No-m870799.aspx
http://www.tomshardware.co.uk/forum/45607-63-disable-hyperthreading-bios
http://steamcommunity.com/app/2870/discussions/0/648812917525467136/?l=german

Bye and good luck all

 

That thread is old when hyper threading was on p4 based platform. However if your system is running better with it off then leave it off. Just wanted to point out that this is not the norm on i7 systems.

One thing is HT will generate slightly more heat, if your system is not adequately cooled then this can cause it to throttle down the CPU and therefore the spikes. On an optimized and properly cooled system the throttling is turned off in a way that this never becomes an issue. Also note that my experience with i7 is with 4cores and higher. For laptops starting with sandybridge and not the previous 2 core that you have so that can be a factor just like the Xeon. Like I said, usually it's better on but it depends.

 

But how do you explain the same phenomenon on my 8560W then? or were you addressing that by the sandy bridge step?

 

Other than my above guesses I can't explain it. But before I continue I am going to test this out with a project with HT on loaded nearly to the peak and see if turning off HT is worse or better on the same project and allow me to load more plug-ins. I did do a brief test like this before but there have been lots of changes under the hood since then so things could be different.

 

Okay, I just ran through some test.
I loaded up 16 instances of Amber to one group. The CPU meter was near the top so I stopped there and ran a pattern where each instance plays a single note, each one at a time with two of the instances playing some chords. I chose DCAM Amber due to it's unique voice architecture that creates a constant CPU load based on the set voice and poly setting regardless if notes are played. The pattern played back fine and I added more instances to a new group. When I got to 4 more instances I got crackles so I pulled it back. 17 instances played back okay but I got an very occasional distortion so I pulled it back to the 16.

I then saved the project and created another project but this time I used 4 instances per group x4 groups. I then did the same thing spreading the notes among the groups with a couple playing chords. I then saved this project and proceeded to load more groups. I noticed you get a little more mileage when you spread instances out to different groups as I was able to get reliable playback with a little headroom with 5 groups (20 instances of Amber each @ 4 voices 2 unison.)

I restarted Maschine and successfully played back all projects. I then rebooted and got same results and checked TM to see the cores looking to be distributed fairly even at about 80%.

I then rebooted and disabled HT.
Results was I was not able to play either the 16 instance in one group or 16 instance over 4 groups projects that I saved. After reducing the single group project to 12 instances it played back reliably. The 4 group project played back nearly reliable after removing the 4th group and readjusting the pattern notes to fill. I restarted Maschine and got the same results. Rebooted computer and got same results.

I then rebooted and enabled HT. All projects played back reliable including the one with 5 groups.

Results:
HT on gives at least 25% and beyond performance increase over it being off. This is the same as when I tested a real world heavy Maschine project before that the HT would handle fine but off it could not. Same as when I tested in Cubase a while back.

 

Are you using the same audio interface on the 8560W?

 

Im trying to use the massive plug in and it says massive does not support this samplerate. How do I change it to the right one I'm using asio4all and the newest version of maschine

 

Go to settings/audio settings then control pannel then you can change it. But it's really unusual that it doesn't work cause massive supports every sample rate.

Uwe

 

Oh with maschine and asio4all you have to change it I'm maschine prefs and I guess it's the same for every other host or even massive stand alone.

Uwe

 

its at 8000 sample rate and I cant change it

 

Ok but how do you use it as plugin? In a daw or in maschine? And have you tried to start it as admin even if i don't think it solves the issue but just a try.

Uwe

 

Same here since MK3 and update, even old projects clipping and lagging from CPU increase. I followed NI Support Windows Config and no better.

 

the mk3 is usb and defaults at 24 96 512, it likely will clip your projects if they contain cpu demanding effects. usb uses your cpu on top of that. it you want to use the 24 96 audio on the mk3, you will not be able to run much on any computer at a useable latency. even my mac pro stumbled on this running waves plugs, but using another non usb card it worked fine... i am not a fan of usb audio, i believe only RME has been able to get it to a good performance level. it is just the way usb works.. you sacrifice performance for compatibility. remember, even it you set it at say 16 44, the computer will still process the effects at 64bit... in maschine, that is the play back rate.. now in cubase, this can affect the way the whole project is processed ...



you really have to set it up for your system and work form. set it at the best you can. if you cannot hear a difference between 16 44 and 24 96, use the 16 44.. it will still process the files the same.. these settings are just for the audio card for output. for input, you may have to change these on the fly , like recording the vox at 24 96 and then changing it to 16 44 after you are done recording.. on the mk3 you can change the audio prefs on the controller.. this is a huge plus...

 

Thanks for your help I have figured it out