|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
|
Thread Tools | Search this Thread | Display Modes |
#21
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
I'm still getting it w/nothing on the masterbuss but things on regular tracks...I'm unclear...is everyone else past this? because I couldn't even get 2018.4 to launch...went back to .3 (came from 12.x)...still constant 9173...1 audio track and 3 midi tracks...the error comes up when the 3 midi tracks come in...am I so clueless that everyone else has fixed this? avid to me to freeze track it...1 audio track and 3 midi tracks....kontakt may be the biggest problem but am I not supposed to use it? how does it work for other people but not me??
|
#22
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Quote:
|
#23
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Quote:
I was also interested in this and have tested it. its not the same. (but you can get the same when bounce "Track"). Thats my result: 1. bouncing a mix with the 16 bit dither on the "Masterfader" -> to the Master "Output" Your File is has 16 bit depth 2. bouncing a mix with the 16 bit dither on the "AUX" (mix) bus -> to the Master "Output" Your bounced File has full bit depth 3. BUT when you are bouncing the Track (its called Trackbounce = right Click on the AUX Track -> bounce ....) you get the same result as with dither on the Masterfader. Your File is has 16 bit depth when I print my mixes I always bounce the AUX (mixbus) Track by right clicking. For me this is the best way. In this case the Masterfader has no function. I have a room correction plug in (ARC) on the Masterfader and this is not included in the bounce. |
#24
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Hi Franklyn
Have you tried cascading your master bus into multiple auxes? I alway "master" during my mixes so i'm using CPU hogging Native plugins like Ozone, T-Racks and lots of UAD. Anyways, on my HDX2 system, i've found that when I stack a bunch of plugins on a single master aux, it kills my CPU. However, if i cascade multiple auxes and place just one or two plugins on each aux, the CPU usage and 9073 errors reduce dramatically. It was a revelation when I found this solution. Logically it doesn't make a lot of sense to me, as its the same amount of processing, but for some reason it seems to share the load better across my CPUs. These days I'm using 4 auxiliaries at the end of my mixes. I don't get a lot of 9073 errors and my sessions are quite massive, often with the CPU floating around 90%. Forrester MacPro 5,1; HDX2, PT2018.4, OSX10.13.2 |
#25
|
||||
|
||||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Quote:
|
#26
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Quote:
|
#27
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
I tried this and it made no difference what so ever as far as I could tell. I experience the same frequency of AAE 9173 errors and CPU spikes, unfortunately.
The real challenge here is that a) AAE 9173 is a periodical error and hence it's really difficult to establish causality and b) the AAE 9173 error is not very helpful. Troubleshooting PT is unfortunately rather difficult. Which I believe the one of the explanations why this issue is debated here in the forum again and again and again and again… Over the years.
__________________
Rgds https://soundcloud.com/1iveowl/ Pro Tools 2018.4, Windows 10 Pro x64 (w/ latest update), i9-7980XE, ASUS TUF X299 Mark II, 64 GB Memory, Samsung 850 2TB SSD, UAD Apollo Twin II TB, RME Fireface USB, UAD-2 Octo PCI, Plugins: UAD Waves, Softube, FabFilter, Lexicon, NI Komplete 11 Ult, Celemony, Slate Digital, PSP, Arturia V Collection 6, FXPansion, iZotope, SoundToys, Spectrasonics... |
#28
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
Quote:
|
#29
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
This sounds interesting. Do you know this as a fact? Is this is the documentation or somewhere else published by Avid?
__________________
Rgds https://soundcloud.com/1iveowl/ Pro Tools 2018.4, Windows 10 Pro x64 (w/ latest update), i9-7980XE, ASUS TUF X299 Mark II, 64 GB Memory, Samsung 850 2TB SSD, UAD Apollo Twin II TB, RME Fireface USB, UAD-2 Octo PCI, Plugins: UAD Waves, Softube, FabFilter, Lexicon, NI Komplete 11 Ult, Celemony, Slate Digital, PSP, Arturia V Collection 6, FXPansion, iZotope, SoundToys, Spectrasonics... |
#30
|
|||
|
|||
Re: „AAE -9173 error“ - the biggest pro tools workflow killer over the last years
I was told this by a fairly big plugin company. You can try it or yourself if you create just one track in the session and put some heavy plugins on that track, then check system usage. It will mainly use just one core/thread. Pro tools will use some of the neighbouring cores for the mixer etc..
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
-9173 Error Pro Tools 12.6 | PowerofEight | Pro Tools 12 | 5 | 09-13-2016 08:01 PM |
Pro Tools AAE-9173 Error with Antelope Zen Studio | Dusan | Tips & Tricks | 1 | 06-28-2016 04:09 AM |
Pro Tools 11.1.0 AAE-9173 Error | justus1900 | Pro Tools 11 | 4 | 12-22-2015 02:46 PM |
Pro Tools ran out of CPU power - Error Code AAE-9173 | dewmi | Pro Tools 12 | 1 | 10-24-2015 10:58 PM |
Pro Tools 11.3.1 Error Codes -9171 -9172 -9173 -9129 -9093 | priyatsomo | Pro Tools HDX & HD Native Systems (Mac) | 11 | 02-27-2015 06:23 AM |