How can i trust ProTools - why should i ever trust ProTools?

[chris.d]

How can i trust ProTools - why should i ever trust ProTools?

Mac Mini M2 Pro
OS Ventura 13.2.1
ProTools, 23.03.0.89 lastest, approved for ARM
RME Madiface USB


I just had my first 2 sessions
Nr. 1
Ordinary song recording session
In two days i had 2 DAE errors that ended recording in the middle of a take. (8 Tracks, 0 plugins used)

work around:
curse
appoligize
redo takes

Session Nr. 2 was a live-in-the-studio recording session. The band plays improvised sets of 30min.
DAE Error stops the recording after 22min into the first set.
(16 Tracks, 0 plugins used)

work around:
react fast
hit record again
5 Min later DAE error again
hit record again
after the set:
curse
appoligize
install reaper (2min)
have no problem for the next two days
(except that i know ***** how to handle the program and feel like a total dumbass)



was testing the previous PT version (rosetta .bla bla, don't remember the numbers...) with no issues
2 hours straight recording
64 tracks

192khz
32bit float
128 (smallest buffer)
64 reverbs on tracks



The first PT version i saw was 6.1
From 7.1 i used PT professionally as my main DAW, aprox 22 years


time and time again i've seen new PT versions and systems useless until somehow one finds the 'magic' combinations and tweaks.



In 2023, despite compability charts recommendations ProTools is basically useless in a live recording situation.


Why do we have to go through this?

With every single version update?



Once again I'm UTTERLY disgusted (for lack of original expressions)



AVID:
why don’t you get? its 2023!
we use 7GB/s writing speed SSDs
teraflop CPUs

[Sardi]

Not downplaying issues you’ve encountered, but can I ask why you need 64 reverbs when tracking?

64 tracks would mean you have a reverb plugin inserted on every track. What for?

Your machine can probably handle it, but…


Sent from my iPhone using Tapatalk

[sw rec]

Agreed, first thing I’d consider is a better way to handle my workflow.
And it would help if you’d post the exact NUMBER of your DAE error…..

[thin ice]

I feel your pain with what you hoped would be a perfect setup, but never judge any new piece of gear immediately.

Follow the trouble shooting help on this forum and watch that activity monitor to see if anything is hogging resources. "mds_stores" is Spotlight, which probably works hard on a new installation for a while.

[its2loud]

Originally Posted by Sardi

Not downplaying issues you’ve encountered, but can I ask why you need 64 reverbs when tracking?

64 tracks would mean you have a reverb plugin inserted on every track. What for?

Your machine can probably handle it, but…


Sent from my iPhone using Tapatalk

The 64 reverbs were on the test session that actually worked for two hours without issue. That probably wasn’t the issue.

On the flip side, I ran a record with 2023.3 for 2.5 hours with 64 tracks. Not one issue. So 2023.3 works. Every situation is different.

[Sardi]

Originally Posted by its2loud

The 64 reverbs were on the test session that actually worked for two hours without issue. That probably wasn’t the issue.

On the flip side, I ran a record with 2023.3 for 2.5 hours with 64 tracks. Not one issue. So 2023.3 works. Every situation is different.

Yes you’re right. I misread that.

Apologies.


Sent from my iPhone using Tapatalk

[chris.d]

Originally Posted by Sardi

Not downplaying issues you’ve encountered, but can I ask why you need 64 reverbs when tracking?

64 tracks would mean you have a reverb plugin inserted on every track. What for?

Your machine can probably handle it, but…


Sent from my iPhone using Tapatalk

simply to check the limits of the system...


to make sure that whatever i'll throw at it in the future that it will be up to the task!
e.g. a bloody simple 16 track live recording

[chris.d]

Originally Posted by sw rec

Agreed, first thing I’d consider is a better way to handle my workflow.
And it would help if you’d post the exact NUMBER of your DAE error…..

i had no time to note, to screenshot, to 'whatever' as i tried to save the recording... went back to record ASAP!!!

[chris.d]

Originally Posted by thin ice

I feel your pain with what you hoped would be a perfect setup, but never judge any new piece of gear immediately.

Follow the trouble shooting help on this forum and watch that activity monitor to see if anything is hogging resources. "mds_stores" is Spotlight, which probably works hard on a new installation for a while.

it's not excactly that the mini had no time to adjust...
i installed OS and data (400GB of stuff on the intern, no external drive) weeks ago. worked seemlessly for all previous testing with the former PT 2022.


The Mini was on for at least 24 hours with PT2023 before the session / failure

[gives]

RME is not my wheelhouse, but I assume you have all of the drivers updates etc.
It's the little things that can cause each unique system setup go off the rails.
Just a suggestion, since I know it's probably not, but you never know what has been done by other users.
https://www.rme-usa.com/downloads.html

G