Multicore feedback

Please give your feedback here of how multicore has helped (or hurt) your systems performance. I've been seeing a few guys on the FB group saying they are now able to playback projects that they could not in 1.6. Just curious to see the results everyone is getting. This is out of my personal curosity!

One thing Pete did mention to us is not to really be overly concerned with what the CPU meter is doing but more concerned with the ability or inability to be able to do more.

so with a little experimenting on older projects that spike my cpu to the point of crackling...
if i brought my core number down from 8 to 2 it performed better. honestly the software is way more unstable now. i def get the crash after removing instruments from programs (every time) even threw software. and it crashes on closure. I'm not seeing an improvement with multicore but the opposite. I REALLy like the work flow improvements of 1.7. its great, but the system is very unstable now. stable like 1.4!


no animosity just please,please get the 1.7.1 out as soon as possible. we really want to use and push your new software.

thanks

pk1 wrote:so with a little experimenting on older projects that spike my cpu to the point of crackling...

This is what I got as well.
Didn't make a difference if I was running 64 or 32.

I can't say that multicore has made a huge difference YET.

Most of the stuff I have cooked up in the MPC software has been standard fare that wouldn't even tax 1.6.

Once I get some of my 4k tracks loaded up, some with MIDI, plus some VSTs, I can make a better analysis.

same here

Yes, I'm on the a Mac Mini Intel Duo and most of my projects are crackling on playback (Can't get my play-start vibe going). I was on 1.6 and It was stable on one-core. The workflow is improved but stability issue are arriving as I expected; No software is perfect reminds me of when pro tools went from 8 to 9.

man..i **** love the mpc! new update is the shit!
i love that i can now live record plug ins then unload them! because i have a shitty laptop so my laptop would freeze if i tried to do too much! hopefully it just keeps getting better and better!

My cpu is high it's messing with projects.How can I fix that .

I had the same issue. The performance was much better after I set it to the # of actual cores(2 in my case on my I5, disregarding the hyperthreading) I also noticed that the cpu meter will sometimes stay high after starting a blank project after a "problematic" project without closing and re-opening the software.

pk1 wrote:so with a little experimenting on older projects that spike my cpu to the point of crackling...
if i brought my core number down from 8 to 2 it performed better. honestly the software is way more unstable now. i def get the crash after removing instruments from programs (every time) even threw software. and it crashes on closure. I'm not seeing an improvement with multicore but the opposite. I REALLy like the work flow improvements of 1.7. its great, but the system is very unstable now. stable like 1.4!


no animosity just please,please get the 1.7.1 out as soon as possible. we really want to use and push your new software.

thanks

I also get a crash whenever I remove an instrument. The workaround I've been using is to delete the program in the project folder. It doesn't crash the software when I do it that way.

clasickbeatz wrote:

pk1 wrote:so with a little experimenting on older projects that spike my cpu to the point of crackling...
if i brought my core number down from 8 to 2 it performed better. honestly the software is way more unstable now. i def get the crash after removing instruments from programs (every time) even threw software. and it crashes on closure. I'm not seeing an improvement with multicore but the opposite. I REALLy like the work flow improvements of 1.7. its great, but the system is very unstable now. stable like 1.4!


no animosity just please,please get the 1.7.1 out as soon as possible. we really want to use and push your new software.

thanks

I also get a crash whenever I remove an instrument. The workaround I've been using is to delete the program in the project folder. It doesn't crash the software when I do it that way.

When you scroll back to PGM < none> from the plugin, you'll get the same result from the hardware.

It prevents crashing.

silent76 wrote:I had the same issue. The performance was much better after I set it to the # of actual cores(2 in my case on my I5, disregarding the hyperthreading) I also noticed that the cpu meter will sometimes stay high after starting a blank project after a "problematic" project without closing and re-opening the software.

I get similar results in Pro Tools 10. I have 16 cores available, but Pro Tools seems to perform extremely better on 12 cores than any other amount. So I imagine it would be a similar case with all apps that let you manage cores. What I love about Pro Tools 11 is all cores are used and managed automatically.

so far my software seems to be running better and smoother - less crashes, etc etc

im diggin it!

a few random random crashes but i cant recreate them

UPDATE

Ok, so I downloaded all the new content as I had previously did it from within the MPC Software.
I reinstalled all the software, drivers and content from the download plus I also didn't install the Studio driver just the Ren driver.

After doing this my CPU meter has again dropped to a minimal level and there are no more pops or clicks.

Still get the message that it was unable to create a backup of the 1.6 Project, but the CPU is now under control.

Nice!