AAE error -9173 stronger than ever on PT 12.5

[eaccin]

I'm amazed at how unstable this PT12 is. I'm a PT user since 2001, it's ridiculous how bad the software is behaving. I've lost several hours of work for the past 2 weeks (since I got PT12) because of these bugs. Session crashes just by using clip gain, some plugins spike CPU usage, Propellerhead Reason not working properly, unfreezing tracks make session crash and so on. I've done everything support has told me to. Hope Avid releases an update soon!

[eaccin]

Even the crash report crashes HA HA

[rmoat]

I had to downgrade back to Pro Tools 12.4.0 because Pro Tools 12.5.0 starting giving me constant AAE -9173 CPU Ran Out Of Processing Power errors. Regardless of changing the samples, and unchecking Dynamic Plugin Processing it would constantly do it.

Running a core i7-2600 with 16GB of RAM couple with the MBOX Pro 3, I had never dealt with this before until Pro Tools 12.5.

Watching the processes in the task manager, none of the cores even come close to being at max with 12.4

Anyone experience the same?

EDIT: The only plugin I am running is Vienna Ensemble Pro. I removed every single AVID plugin that comes with the Pro Tools 12 subscription. Perhaps Vienna needs to release a new plugin (not positive). I guess for now I'll stick with 12.4.

[Drywsef]

Also very buggy here. This may be the buggiest PT i have used to date.

[MediaBrain]

Just lost 2 hrs work due to a beach ball. For some reason the auto-save just stopped working 35 minutes into reopening the session (after another repetitive crash). What's the point of having an auto-save if it just randomly quits? This isn't a professional product. I expect my income earning tools to work.

[dankin]

Originally Posted by MediaBrain

Just lost 2 hrs work due to a beach ball. For some reason the auto-save just stopped working 35 minutes into reopening the session (after another repetitive crash). What's the point of having an auto-save if it just randomly quits? This isn't a professional product. I expect my income earning tools to work.

I have the auto save set to 3 min here. With one of the crash's I had today, I lost about 15min or so worth of work. So I'm thinking something is wrong with autosave in 12.5.

[Nearlymen]

Same here and if you trawl through the forum it seems a lot of others are having similar problems. Best to stick with 12.4 if its working well and wait to see what happens.

Cheers

Clive

[unkJE]

These are the latest versions:

Vienna Ensemble PRO 5 – build 5.4.14074 – released Feb 6th, 2016
https://www.vsl.co.at/en/Software/VEPRO_5



eLicenser Control (eLC) updated to Version 6.9.3.1185 – released February 29th, 2016
http://www.elicenser.net/en/latest_downloads.html
Supported operating systems:
Windows 7 (32/64-bit), Windows 8 (32/64-bit), Windows 8.1 (32/64-bit), Windows 10 (32/64-bit)
Microsoft .NET Framework 2.0, 3.0, 3.5, 4.0 or 4.5 is required!

Mac OS X
Mac OS X 10.8.x, 10.9.x, 10.10.x, 10.11.x

[Extreme Mixing]

When you uninstall and then install a new version of Pro Tools, I believe that the default setting is with auto save disabled. How crazy is that. I'm pretty sure your lack of a recent back up is caused by that FACT. And do you know how I know that? Right. It happened to me too. Who is designing this software anyway? The level of common sense that is present is shockingly low.

Steve

[noiseboyuk]

I've posted a few times now that 12.5 is "one of the good ones" for me. But even allowing for the forum effect of skewing problems, there are clearly some relatively common issues that are causing havoc for some, and I'm one of the lucky ones. So repeatable diagnosis is the holy grail here.

I find Avid's support frustratingly slow, and a number of times I've simply given up after months of back and forth on an issue. But I have had successes too - my issue of the video engine hanging when selecting less than a frame was duly logged only a couple of months ago and fixed in 12.5. So what I'm saying is - however frustrating the process is, taking issues to Avid support has to be the way to go, as opposed to just screaming "FIX IT". But the DUC can certainly help there - it can be far, far quicker to crowd-source what triggers a problem by pooling resources than relying purely on Avid Support. Then hopefully you can go to them with solid reproducible steps on a particular system.

Hope those who are suffering can isolate some triggers that cause instability sooner rather than later.