CPU usage meter/buffer settings...

[WKG]

I am seeing a significant spiking in the CPU usage meter at idle/playback on lower buffer settings vs higher. I've seen a few posts indicating some are seeing no difference in the CPU meter at idle/playback regardless of the buffer setting.

My understanding of the new input/output buffering is that the input is set via the Playback Engine/Setup App and output is automatically set depending on the session sample rate, in this case 44.1.

I would expect to see significant CPU usage at a 64 buffer when tracking but on playback or at idle shouldn't it reflect lower CPU per the higher auto setting for output? It drops significantly if the Ignore Errors During Playback/Record box is ticked which looks like the Hardware buffer setting is locked to both input and output.

Anybody else seeing this?

[WKG]

Am I the only one experiencing this? Seems odd given the new buffer system...

[Bharath]

One thing that is not very obvious is that the device is still operating at your chosen hardware buffer size. Spiky meters usually indicates underlying issues (mostly DPC latency) that could be choking AAE <--> Device data transfers.

[mykhal c]

Originally Posted by WKG

I am seeing a significant spiking in the CPU usage meter at idle/playback on lower buffer settings vs higher. I've seen a few posts indicating some are seeing no difference in the CPU meter at idle/playback regardless of the buffer setting.

My understanding of the new input/output buffering is that the input is set via the Playback Engine/Setup App and output is automatically set depending on the session sample rate, in this case 44.1.

I would expect to see significant CPU usage at a 64 buffer when tracking but on playback or at idle shouldn't it reflect lower CPU per the higher auto setting for output? It drops significantly if the Ignore Errors During Playback/Record box is ticked which looks like the Hardware buffer setting is locked to both input and output.

Anybody else seeing this?

you might have checked this already but make sure you have 'run as admin' checked for PT. i've seen the playback setting panel/settings have issues when this is not checked...especially with ASIO drivers. hope that helps.

[WKG]

Originally Posted by Bharath

One thing that is not very obvious is that the device is still operating at your chosen hardware buffer size. Spiky meters usually indicates underlying issues (mostly DPC latency) that could be choking AAE <--> Device data transfers.

It the total CPU meter that bounces around a lot, the core meters are pretty stable if higher than expected given an idle state with no input. I don't get any errors, clicks or dropouts at all. Interesting though, if the new output buffer is automatically set by PT but still subject to the device settings then what is the benefit?

Originally Posted by mykhal c

you might have checked this already but make sure you have 'run as admin' checked for PT. i've seen the playback setting panel/settings have issues when this is not checked...especially with ASIO drivers. hope that helps.

Thanks for the tip. I thought I had that checked but did not. Seems like it may have helped a bit.

[kelco83]

I had a nasty pop sound through my monitors, turned out to be an IRQ issue. I wouldn't say conflict, as theyre supposed to share, but apparently, my interface refuses to.

latencymon and dpclat were very happy once that IRQ issue was addressed.

[Holly73]

Originally Posted by Bharath

One thing that is not very obvious is that the device is still operating at your chosen hardware buffer size. Spiky meters usually indicates underlying issues (mostly DPC latency) that could be choking AAE <--> Device data transfers.

Could you shed some more light on how this input buffer/output buffer thing works?

I don't get it somehow. Avid ads said it is the input buffer that is set in the playback engine. But in the Reference Guide it sounds the same like in prior versions. And also in tests Russ did over at pro-tools-expert.com the performance changed when changing the buffer. But if it is an input buffer, there should be no changes when not recording, or am I wrong?
What you mean by saying "the device is still operating at your chosen hardware buffer size"? How PT then does the output buffering?

Btw, I also have these spiking meters, but I'm on a Mac. They are at around 20% average but sometimes jump to 100% and then I get -6101 and -9173 errors.

[WKG]

Originally Posted by Holly73

Could you shed some more light on how this input buffer/output buffer thing works?

I don't get it somehow. Avid ads said it is the input buffer that is set in the playback engine. But in the Reference Guide it sounds the same like in prior versions. And also in tests Russ did over at pro-tools-expert.com the performance changed when changing the buffer. But if it is an input buffer, there should be no changes when not recording, or am I wrong?
What you mean by saying "the device is still operating at your chosen hardware buffer size"? How PT then does the output buffering?

I am curious about this as well.

Maybe a PT 11 Sensei can shed some light on this?

Bharath?

[WKG]

Bueller...?

[WKG]

Beavis...?