Cpu load balancing

[killah_trakz]

Using 2018.7 and have noticed that for some reason PROTOOLS keeps attacking core 2 of my cpu while 1,3, and 4 are just idling around WAITING to be used for something.

This is always causing me a lot of errors when trying to use beefier plugs. Anyway to make Protools spread the work amongst all 4 processors ?

Thanks.


Sent from my iPhone using Tapatalk

[Emi]

Willing to know also.

[Darryl Ramm]

There is nothing you can really do about CPU scheduling, stop worrying about it, ignore the meters and focus on proper setup and standard troubleshooting. How many instances of exactly what plugins? Are you mixing or tracking? At what IO buffer size?

What exact errors do you get and what standard troubleshooting steps have you tried? “help us help you”, top of each DUC web page. If you need more help clear exact info on what you are doing and systems info will help.

Make sure you disable dynamic plugin processing, ignore errors is *not* checked while troubleshooting, run with the largest IO buffer size you can, use freeze/commit to reduce load, make sure disk cache is set to a size,... and do all the standard systems optimization steps.

[killah_trakz]

Plug giving issues: Anything Acustica Audio.

Problem is always consistent.

Cpu 2 is higher then all my other cpu.

Have done EVERY cpu trick on planet EARTH!

Buffer 1024 using Apollo twin duo.

I’m mixing.

I still can’t believe this is still an issue.

F, I gotta learn reaper man and give up on protools and this stupidity.

[arche3]

Originally Posted by killah_trakz

How am i to stop worrying when the daw I’m “ renting “ is giving me more issues then I should be expecting in 2018.

Plugs I’m trying to use “ ANYTHING ACUSTICA AUDIO “. Why in REAPER it gives me NO glitches and in PROTOOLS my CPU shoots up so fast and stops my workflow.

It’s sad that even with my 2x Octo’s protools still give issues. And it’s NOTHING wrong with my laptop.

So BACK to my question, can protools handle cpu loading across the board or not ?

If no, then I’ll cancel my sub and move on. I have work to do, not troubleshoot.


Sent from my iPhone using Tapatalk

No. It always has issues with CPU balance. But most guys deal with it because the other options are not better.

You really need a maxed out computer. 12 core mac pro with a high end video card and minimum 64 gigs ram to be honest. Fastest mac you can get your hands on.

[killah_trakz]

Originally Posted by arche3

No. It always has issues with CPU balance. But most guys deal with it because the other options are not better.

You really need a maxed out computer. 12 core mac pro with a high end video card and minimum 64 gigs ram to be honest. Fastest mac you can get your hands on.

Smh........ I just have to find something else. Thanks for your help btw.


Sent from my iPhone using Tapatalk

[Darryl Ramm]

Originally Posted by killah_trakz

Plug giving issues: Anything Acustica Audio.

Problem is always consistent.

Cpu 2 is higher then all my other cpu.

Have done EVERY cpu trick on planet EARTH!

Buffer 1024 using Apollo twin duo.

I’m mixing.

I still can’t believe this is still an issue.

F, I gotta learn reaper man and give up on protools and this stupidity.

OK you just want to wine about it, and don’t want help? You are still fixated on the CPU meters.

We cannot guess what you have actually tried, or have any clue what computer you are even running on. And you are not providing much information. The place to suspect first if you are having CPU errors is the plugin itself. Stop fixating on the meters/load, you can’t change that. But there is a pile of other stuff you can do.

[killah_trakz]

It’s no need to wine. Protools is the issue. It was already answered.


Sent from my iPhone using Tapatalk

[albee1952]

You say anything from Acustica Audio? Go to the plugins folder(C:>Program Files>Common Files>Avid>Pro Tools>Audio>Plugins). Find anything from Acustica Audio and move it out of the Plugins folder(drop it/them on the desktop is fine for testing). Now open a session and try the stock MiniGrand VI and test that. If its now good, then you know its the Acustica plugins to blame. If MiniGrand has the same (too much) latency, then you should come back and post a Sandra Report on your computer. That might reveal a hardware issue. Blaming Pro Tools is easy, but since many of us make our living with it, its most likely not Pro Tool's fault. I track bands all day long at the 64 buffer, tracking up to 32 tracks at once, WITH instrument tracks with MiniGrand, DB-33, Lounge Lizard(Wurly). As said already, cpu loads are not balanced, but things work fine(I am running an Avid-approved PC).


I have some power hungry VI plugins that can(and often will) cause the rig to choke and throw an error(like Spectrasonics KeyScape). My solution there is to use a VI that has lighter needs while tracking(like MiniGrand). Once tracking if done and I have the midi on the instrument track all ironed out, I switch from MiniGrand to KeyScape and commit the track.

[JFreak]

if a single plugin or plugin vendor is what causes you trouble, please contact them with your issue and expect them to fix their plugin. some vendors just wrap vst code to aax and think it's alright, but it's not.