Pro Tools Ultimate CPU Spikes.. come on!!!!

[SigFriedChicken]

I've found that doing stuff on the second display will invariably cause a spike.

[YYR123]

Originally Posted by toolz

.....I'm eagerly waiting on this critical bug fix, and maybe a 9 month refund on my support fee, as I had to spend two weeks uncovering this issue, that seemed to pass both Avid CS and Beta team....

https://youtu.be/z82ZrOE0Dq4

You pay to be a part of that team....that’s what that payment is.... for.

Seriously though, good catch!!!!

[685]

I need to keep an eye out for this one. Thanks!



I'm curious to know what Boot ROM Version is listed on you guys' system reports for your MacPro.

[SomeOtherGuy]

Interesting, I run my video on a second display, I'll have to switch that off and see what happens. Thanks.

[SomeOtherGuy]

Still getting CPU overloads and transport stops with a single video monitor. About 20% of the time I'll get an overload during a Bounce.

Again, this all started with High Sierra and 2018.1 PT.

[s.d. finley]

I have 2 video screens running on a single video card, no problems with that. I normally only get the buffer errors when I am recording or if the transport is engaged and I initiate a plug in, then I will get an error. I am using Sierra and 2018.3

[skizzo]

So I do not run Ultimate/HD versions currently but I discovered a new spike issue recently.

When I powered on my Ddrum DDTi, which is literally just a trigger interface for converting triggers/pads into MIDI data, I kept thinking this totally froze PT 2018.4

I kept getting the dreaded beach ball that would never go away. But finally after I accidently walked away for several minutes with it up....the beach ball stopped and the program began to respond again. It just took forever for it to be recognized.....but then more troubleshooting proved I needed to have the MIDI track armed for that beach ball hang up to happen.

The CPU % jumps to literally 100% from 39% with this issue. And it stays spiked like that even when PT begins to respond again.

I also noticed I could eliminate this totally if I run with 512 or more sample buffer rate. But that obviously is not ideal for tracking which is what I need the DDTi for. I normally run at 64 sample buffer rate, again, for obvious reasons.

One other thing that is a workaround is if I disable SD3 and then enable it the CPU spike goes away and doesn't come back....unless I power on/off the DDTi and/or disarm/rearm the MIDI track.

I did not have this issue going all the way back to PT 8LE so this is something related to my setup's compatibility to the newest version of PT

[toolz]

I'll be cheeky and say.. Avid need to sit with a computer running Logic, and witness their failings in the VI department, Logic goes forever!

Waiting for the next update, since 12.8.2 release on the 22nd of November 2017, that the code broke for me, on my supported Mac 5,1 and all Avid Hardware...

Avid replicated the bug! over two months ago!

Maybe I'm gonna invoice Avid! having wasted two weeks of my life pointing out problems with their release that a flagged critical bug, whilst continuing to pay for support and updates, that don't work for me. Totally hitting the wall with this!

All I can fathom is.. the very architecture on TDM (and having to integrate that factor), or however you dress it up as, has to be the biggest bottle neck of the software going forward.

I'm planning an open letter to Avid, if my computer won't run the next release.

[YYR123]

After invoicing don’t forget to charge late fees for non payment and accrued daily interest rates!!!

[SigFriedChicken]

Originally Posted by toolz

I'll be cheeky and say.. Avid need to sit with a computer running Logic, and witness their failings in the VI department, Logic goes forever!

Waiting for the next update, since 12.8.2 release on the 22nd of November 2017, that the code broke for me, on my supported Mac 5,1 and all Avid Hardware...

Avid replicated the bug! over two months ago!

Maybe I'm gonna invoice Avid! having wasted two weeks of my life pointing out problems with their release that a flagged critical bug, whilst continuing to pay for support and updates, that don't work for me. Totally hitting the wall with this!

All I can fathom is.. the very architecture on TDM (and having to integrate that factor), or however you dress it up as, has to be the biggest bottle neck of the software going forward.

I'm planning an open letter to Avid, if my computer won't run the next release.

I came to PT from Logic. Maybe it was just me, but I found that Logic was no better when it came to CPU spikes and general stability.