PT 2018.7 Only Accesses One Core?

[DFT]

Hi ... I haven't disabled hyperthreading on my new Win 10 PC yet, and while I intend to do so I am curious about this issue and whether among issues related to enabled hyperthreading is mine: PT appears to only access one core.

Or is this some other type known issue?

Thanks!

BTW, I do have active support, but thought I might get a quicker tip here.

[JFreak]

some processes only use one core but if you have multiple cores and multiple plugins it should even out somewhat

[DFT]

But it doesn't!

I have 10 physical cores and '20' with hyperthreading ... but PT loads up on one to the max and starts choking, while the others remain blissfully asleep without any apparent activity.

[Darryl Ramm]

And the critical question as Janne said is what plugin(s) and how many instances of it are you running? So... what plugins and how many instances are you running? (and it's a bit more complex... how many tracks do you have them on?)

And basic basic stuff... what IO buffer size and sample rate are you running at?

Open up a new empty session, create an audio track, stick 5 instances of DVERB on the track. Straight to main output, no bussing/complex routing. Duplicate that track 10 times. Now what do the CPU meters do?

Seeing only one core active is obviously not good. But general comments there: The CPU load will often never appear perfectly distributed. And especially with few plugins or deep chaining of plugins on few will favor some cores--that's Pro Tools trying to do what it want for CPU core/cache affinity. And it may not always be right, but it's also not true at the other extreme that you necessarily want to see apparently evenly CPU load (certainly not with hyperthreading).

Hyperthreading and CPU meters is pretty impossible to understand. It's largely all a fantasy/lie.

Looking at Pro Tools CPU meters can become an addiction that does not help solve problems. What is the underlying issue you are having? Actual AAE errors? What standard troubleshooting have you done?

And start troubleshooting by turning off dynamic plugin processing. Never seems to help and can cause problems.

[DFT]

Daryl ...

Thank you for the direction. I will attempt to work this through more systematically and detail what is happening. Then get back in a day or two.

I only initially wanted to know whether restriction to use of one core was a known issue associated with enabled hyperthreading. I take it you are not aware of this being known.

As far as the system meter, Win 10 resource meter mirrors the same results. I first noticed this when adding several VSTi in a proje ct to PT, including Kontakt and some Toontrack instruments. I have several other DAWs, Cubase Pro 9.5 and Studio One 3, and they do not display like behavior, so I'm confident it is not a general system issue.

I'll check back when I have my grist for the mill.

DF

[Darryl Ramm]

No its not hyperhreading messing you up here. It will almost certainly be the exact plugins and how you are using them (just like Janne said several posts ago)

Please be very clear what you are doing. If you are running VST plugins in/with Pro Tools... say exactly how are you doing that. If you are saying VST and mean an AAX VI, then slap yourself and don't do it again

[DFT]

Daryl ...

Thanks for "not hyperthreading" and your other input. I'm loathe to disable something that otherwise works well with my other software ... unless I have to.

I'll try to get back in a few days when I've done my homework.

DF

[DFT]

Originally Posted by Darryl Ramm

No its not hyperhreading messing you up here. It will almost certainly be the exact plugins and how you are using them (just like Janne said several posts ago)

Please be very clear what you are doing. If you are running VST plugins in/with Pro Tools... say exactly how are you doing that. If you are saying VST and mean an AAX VI, then slap yourself and don't do it again

Thank you Darryl et al.

As best as I can determine Blue Cat AAX hosting a couple of VSTi plugins was the culprit.

All seems otherwise well without disabling hyperthreading.

DF