CPU usage different with 2019.5?

[jrtme]

Very Cool. 24 bit I assume?

[mattrixx]

No.. With 32 bit floating

[Basstian]

Originally Posted by mattrixx

I have to say that I am so far extremely impressed with how well this runs!!

Running at 32samples @ 48kHz... on a session with about 40 tracks, with track punch active!!! Really smooth!

(MacPro 2013 6Core)

Same here. The new engine is way more powerful. I tried a 32 bit 48 kHz Session on 32 samples buffer. Pretty loaded already. It is already a final Mix. I added new tracks, put them in record. No single hiccup when recording at the low buffer. Would have not nearly been possible with 2018.12. Then I starte adding Auges with Altiverbs on the. I could manage to add 8 Instances of Altiverb without getting an error. Number 9 hit the ceiling though. But that is ok for me. That is far beyond my hopes.

All without any VIs though.

[justinhill]

Originally Posted by Basstian

Same here. The new engine is way more powerful.

Well this all sounds like really good news. Everything coming through on the DUC so far about 2019 sounds positive.

[Jamie Mac]

I'm still getting the same random -9173 errors when CPU load is 8% every once in a while.
Not only that, but it creates a small audio glitch which was not there in the previous version.

Other than that it runs as smooth as 2018.12. No noticeable difference here.

[ALowe]

Originally Posted by Blinkofani

Well, I'm not a Power PT user and sure don't have the most powerful Mac but it took less than 2 minutes before I got a -6101 error and playback stopped. PT CPU usage shows a 24% usage. Everything seems well under control but that error message popped up quick.

Also, on the first opening I got the message that PT is not optimized bla bla bla. So, business as usual here with PT 2019.5, nothing to see move along...

Blink

The AAE-6101 error is killing me!! Almost literally. If it continues I will definitely lose some jobs. I work in a HEAVY RF environment, and even when I think I have it figured out at home/studio, it comes out and makes me look like a Pro Fool. I have Logic going as a backup, and now becoming plan A.

Running a Mac Mini with 16gb of ram, 10.14.16 and PT 2019.10. No extra plugins on that machine. System on internal and running one SSD drive for sessions. But I am pushing (2) 250mw transmitters in the block 22 and (2) 300mw transmitters in 216 as well as some extra when they are needed. All around my Mac.

But Logic is solid. Unfortunately, I'll have to go back and redo the sessions I have in Pro Tools for delivery. But better than it stopping play at $200/min or work time with all eyes on me. Oh the horror stories I cannot tell you about. I still cringe.

[Emi]

Originally Posted by ALowe

The AAE-6101 error is killing me!! Almost literally. If it continues I will definitely lose some jobs. I work in a HEAVY RF environment, and even when I think I have it figured out at home/studio, it comes out and makes me look like a Pro Fool. I have Logic going as a backup, and now becoming plan A.

Running a Mac Mini with 16gb of ram, 10.14.16 and PT 2019.10. No extra plugins on that machine. System on internal and running one SSD drive for sessions. But I am pushing (2) 250mw transmitters in the block 22 and (2) 300mw transmitters in 216 as well as some extra when they are needed. All around my Mac.

But Logic is solid. Unfortunately, I'll have to go back and redo the sessions I have in Pro Tools for delivery. But better than it stopping play at $200/min or work time with all eyes on me. Oh the horror stories I cannot tell you about. I still cringe.

That's not cool. Anyway, maybe a more powerful machine would be the answer.

I'm running a Mac mini late 2012 with 16b of ram too and it's rock solid. But I don't have nothing running in the background.

Also, maybe increasing the buffer size would help.

[ALowe]

Originally Posted by Emi

That's not cool. Anyway, maybe a more powerful machine would be the answer.



I'm running a Mac mini late 2012 with 16b of ram too and it's rock solid. But I don't have nothing running in the background.



Also, maybe increasing the buffer size would help.

I run the buffer at 1024 with Pro Tools.

Literally trying to play a 2 track mix. I have 2 other machines that have experienced the same issue. A 2017 Mac Air i7 and a similar one i5.

I have a 2012 Mac Mini that’s loaded out and runs Ultimate, but it’s an assembly and mix rig, and does not go into the same environment as the other 3 rigs. It’s been solid and has been using an Apollo 8 as it’s interface. Man they sound good!!

Logic has been super solid and running a buffer of 128. Going to test 64 today.

For assembly of the mixes, I’m prepping a Logic session and a PT session. On a set I’m much more comfortable with PT because that’s what I’ve used for the past 10 years on sets. But glad to get some use with Logic as well, even though I’ll be stressing a bit. I’m pretty good with Logic so it shouldn’t be too bad.

I have a shoot this Friday and will report back.

[danyg]

I run the buffer at 1024 with Pro Tools.
Literally trying to play a 2 track mix.

last week...

PT Ultimate native or Logic - 152 tracks in a song both solid on a mid 2010 cheese. Buffer 256 - same session runs on a Mac Book Pro 2016

... so I'm happy with both