Low Buffer CPU Optimization

[weezul]

Originally Posted by Darryl Ramm

Ugh Weezul, my apologies

It's all good, I feel your frustration if everyone with a 2i2 and a laptop comes in complaining about realtime performance, but I do know my machine well and I think RME PCIe is a good platform for testing in terms of eliminating badly written drivers. And yes this is completely different to what I've experienced in the past. Even at 128 buffer the CPU usage is just so high. Another oddity is when I was at 32 or 64, with the screenshot posted, the session playback head jerks, pro tools is 'playing' but the audio is choppy, with no error messages on playback. It just struggles on. I've ran PT on Windows on an i7 5th gen laptop with middling latency results and X-AIR18 interface, it was much better behaved than this. I'd try 2020.9 on my Windows partition as well but I don't have the installer file. I think the last version I tried on my windows partition was probably some version of 2019, which behaved as expected.

I also have a Steinberg UR824 I use in standalone with the RayDAT. I'll try installing the drivers for it and using that in the playback engine to see what happens. If you think I can grab anything else from the machine to help people then let me know and I'll grab whatever is needed next time I'm in Windows.

[Emi]

Originally Posted by JingleDjango

I would expect to see similar low buffer optimization on Windows if and when Carbon is qualified for that OS.

And that’s sad. It’s all about the money and interest.

[Ru_C]

Originally Posted by weezul

It's all good, I feel your frustration if everyone with a 2i2 and a laptop comes in complaining about realtime performance..

..I actually have a 2i2 on my home rig (which is an an ancient 5.1 Mac Pro). I just tested the new Mac Low buffer optimisations & it works great. Hallelujah! I can finally track guitars at home on sessions at 96k/64buffer that would have been impossible before.

Can't wait to try this on my main Native PCI-e rig in the next few weeks.

[arche3]

OMG. it is actually working at low buffer.... I cannot believe it.

[Daveporter33765]

Very low CPU usage at 32 Samples here! Finally the audio engine has been fixed!

[lesbrunn]

Originally Posted by arche3

OMG. it is actually working at low buffer.... I cannot believe it.

Happy for you! But it should work equally well on both major platforms. We pay the same $, don't we? So some people are being short-changed.

[Emi]

Originally Posted by lesbrunn

Happy for you! But it should work equally well on both major platforms. We pay the same $, don't we? So some people are being short-changed.

Yes, but Carbon is not Windows ready yet. I’m pretty sure you’ll have low buffer optimization once Carbon is

They have proven they could have had a very stable Pro tools Native. But they were scared hardware sells would have dropped. Anyway the market goes towards a more native approach because you have more and more powerful computers.

Anyway ����*♂️

[arche3]

Originally Posted by lesbrunn

Happy for you! But it should work equally well on both major platforms. We pay the same $, don't we? So some people are being short-changed.

I thought windows machines always worked better anyways for low buffers. Mac osX has been horrible for I don't know.... 7 years? It's been that long I can't remember.

Sent from my SM-G986U using Tapatalk

[ZEUSS]

It doesn't seem to be doing anything for my system. Maybe because I am still on Mohave? I arm a few amplitubes or load up 1 Kontakt and its still spike city. Even with the plugins current..

[Daveporter33765]

Originally Posted by arche3

I thought windows machines always worked better anyways for low buffers. Mac osX has been horrible for I don't know.... 7 years? It's been that long I can't remember.

Sent from my SM-G986U using Tapatalk

In my experience Macs were capable of very low latency and very efficient performance with every DAW but Pro Tools for a very long time. Now that Pro Tools audio engine has been optimized, it’s the same as all the other DAWs. So it wasn’t a Mac problem, but a Pro Tools problem.