Unstable 2018.12

[Venshield]

Let's hope Pro Tools 2019 is more stable for me. It makes no sense to have an annual subscription and all we get are unstable updates and last minute compatible versions with the Latest MacOS. I've been using 2018.7 because it was more stable than 2018.10 or 2018.12 but as soon as I updated to High Sierra, I have been dealing with constant crashes in 2018.12 while doing simple audio edits. Seems like while I'm in the middle of an undo while a session is playing, I get a crash at least once a day now... I think I'll go back to 2018.7 and use it for all of my non-recording tasks.

Which version of 2018 do you guys find to be the most stable?

[Venshield]

And let's not talk about using Elastic... Whenever I use Elastic audio, a crash is guaranteed within 5 minutes in all of the 2018 versions I've used

[jeam25]

Hi friend sorry to hear that ! I have to ask , Do you have all the optimizations done ? How tare you recording . Another second dedicated audio drive ? Same one ? At least me didn't have any that type of problem on my systems . Maybe an outdated plugin ? Is pace interlock updated ? Thinking hard here ...

[Venshield]

Interestingly enough, I haven't had a single crash since I posted this

[jeam25]

Great !

[SDDP]

Originally Posted by Venshield

Interestingly enough, I haven't had a single crash since I posted this

You should post more often for the rest of us

[gives]

I have had no trouble at all for months.. Scoring and also mixing and producing here another project for an artist, Lot's of live parts at 96khz and midi 67tracks. HD Native. Still running old Sierra NOT High Sierra.

All good here. I mostly work at 48khz, but not really have any problems at all.
I have notice just one thing that might be of help. If you are bouncing to disk High Speed, I have had some CPU stuff happen if I try to do something immediately after that bounce. I will sometimes peak the cpu to red or something strange. I usually can fix it by just closing the session and or quitting protools and re-launching. MY ADVICE is to just wait about 5-10 sec and then do the next task. I see this sometimes in other operations, but very rarely.
Another thing that used to happen was moving Plugins sometimes would cause a crash, but that seems fixed now.

Just thought I'd throw these things out there-:)

G