AAE error -9173 stronger than ever on PT 12.5

[YYR123]

3gb is nothing

Make it 5gb...there is no way your computer is using more than 13gb for its processing tasks

[Burbree]

Looks to me like you're hitting close to 100%.

Hyperthreading off: CPU at 68% in same session. -9173's in similar way when moving between memory locations.

Over a 4 minute period 12.4 only -9173'd 5 times whereas with 12.7.1 lost count at 20

3gb is nothing

Make it 5gb...there is no way your computer is using more than 13gb for its processing tasks

Moot point I would have thought on this session as with cache set to 3GB only hitting 8% on cache meter.

[TOM@METRO]

Originally Posted by Burbree

Hyperthreading off: CPU at 68% in same session. -9173's in similar way when moving between memory locations.

Over a 4 minute period 12.4 only -9173'd 5 times whereas with 12.7.1 lost count at 20



Moot point I would have thought on this session as with cache set to 3GB only hitting 8% on cache meter.

While I don't see quite as many, I do see an equivalent proportion between 12.4 and the latest builds.

[esmallwood]

Originally Posted by Blackers

Well,with sistem usage at 24 % i must say 12.5 is a complex update.This message appears a lot the last couple of days.And stills is crashing here and there.Windows 7 i7 intel m ausio project mix io as interface.
Anyone familiar with that?

http://protools.ideascale.com/a/dtd/237818-3779

As of 04-01-2016, 05:00 AM? It is now Feb. 22 2017. And a few upgrades later.

[WorldStudios]

I get a lot less 9173´s with 12.7.1 They are not completely gone, but down by a factor of 8 (just making up a number that seems about right), so a few each day instead of a few each hour

[Nomad76]

Hi. I am just going the club. I get consistent AA# -9173 on Playback.

Arg! I started on Pro Tools. Left for awhile and dated Logic. The relation ship was awkward because I kept thinking about Pro Tools, and the way she used to respond to me. Frustrated, I tried Studio One, because she promised better features. But I soon found that the grass is not greener, so I called up Pro Tools to rekindle my old flame. But back when we used to date, there was no AAE -9173. Since then, I've upgraded my package. Even though my equipment is bigger and better now. Why are we having these problems? Please don't make me run back to Logic. Logic has gone through some significant changes for the better. But I want to use Protools.

iMac 3.1 GHz, i7, 16GB Ram, Internal SSD, Session On Glyph connected eSATA through Thunderbolt Port.

[martinaston]

Originally Posted by Nomad76

Hi. I am just going the club. I get consistent AA# -9173 on Playback.

Arg! I started on Pro Tools. Left for awhile and dated Logic. The relation ship was awkward because I kept thinking about Pro Tools, and the way she used to respond to me. Frustrated, I tried Studio One, because she promised better features. But I soon found that the grass is not greener, so I called up Pro Tools to rekindle my old flame. But back when we used to date, there was no AAE -9173. Since then, I've upgraded my package. Even though my equipment is bigger and better now. Why are we having these problems? Please don't make me run back to Logic. Logic has gone through some significant changes for the better. But I want to use Protools.

iMac 3.1 GHz, i7, 16GB Ram, Internal SSD, Session On Glyph connected eSATA through Thunderbolt Port.

Harrison Mixbus 32C keeps on tempting me but she is a cruel mistress too...Pro-Tools remains King DAW. Despite the frustrations and sillyness and annual upgrade plans and -9173's. 12.7.1 seems stable, my -9173 blight has diminished recently and PT12 has been behaving better than ever, so although I have lost me rag a time or two, used some norty words and even de-installed it, I am back on board, untill it misbehaves again that is

[Steviebhoye]

I am currently running 12.6.1 on an iMac 8GB of Ram. Using VI's would always cause the dreaded -9173 errors especially after first launching PT. I recently discovered that by consolidating all midi clips on the instrument tracks to 0 in the EDIT window seems to have solved it - at least for me I have not had a single -9173 since doing this. May be of help to some. S.

[Goombot]

Originally Posted by Steviebhoye

I am currently running 12.6.1 on an iMac 8GB of Ram. Using VI's would always cause the dreaded -9173 errors especially after first launching PT. I recently discovered that by consolidating all midi clips on the instrument tracks to 0 in the EDIT window seems to have solved it - at least for me I have not had a single -9173 since doing this. May be of help to some. S.

That's great that you got things going but most people who have that issue aren't dealing with MIDI at all. It's a code issue, or at least everything really points to that, and Avid doesn't seem to want to address it.

[matheooo]

Hey guys,

i got the same 9173 issues, +70 track session with a lot of sends, groups, aux, vca's, each track with kind of 2-6 plugins. And the cpu usage is about 60-70%, buffer is at 1024samples.

But i find out some quiet interesting on my machine:

When i got the edit or mix window open and active, it stops with 9173 after a few seconds, quietly more in the edit. But when i start the session and quickly minimize both windows (to see e.g. the desktop or some less moving "intense" graphic) it plays the whole session without a drop! Same on lower resolution, i ran my mac on the highest res without external monitor. And this is an issue i can reproduce.

Maybe this is a graphic issue on this type of macbook because this model i got is a single GPU model and the graphics had to be rendered additionally on the cpu?

Anybody an idea?

Greetings,
Matheo

____________

PT 12.5.2
UAD-2 Satellite Thunderbolt Octo
Focusrite Saffire Pro 40
MacBook Pro 11,2
16 GB Ram
Thunderbolt Recording SSD
OS X 10.12.3