Constant 9173 error's PT 12.6 *solved*

[clausiii]

I have the same problem! Will check my plugins too


Gesendet von iPhone mit Tapatalk Pro

[Darryl Ramm]

Originally Posted by cshaw

Debug your problems with a copy of the session

- Shift-click on the session copy so that it opens with all of the plugins deactivated.

- open the system usage window and control-click each plugin to activate them.
- take note of the system usage as you add in each plugin and you should be able to deduce which plugin(s) are spiking your cpu. Remove those from the session then close and reopen it with the plugins activated and see if you still have spikes. Make sure that the plugins that are causing cpu spike are up to date. Also remove any plugins that you don't use that often.

Make sure that copy is a "Save Copy In" with all separate media, so you are not risking damage to any content files.

[TOM@METRO]

If you're going start doing a lot of install/uninstall, it will be a good idea to image your system drive first.

[Matt Hepworth]

Originally Posted by Studio Llama

...then will spike to 100% and 9173 comes up, then everything is distorted requiring a reboot.

All you have to do is change the buffer to a different setting. No reboot or anything like that required. I just switch between 512 and 1024 back and forth as needed.

[Southsidemusic]

Originally Posted by Matt Hepworth

All you have to do is change the buffer to a different setting. No reboot or anything like that required. I just switch between 512 and 1024 back and forth as needed.

Same weird workaround here aswell. Change buffer size to anything doesn't matter and then back again solves it for us. Have no clue why this is still happening though

[amagras]

Originally Posted by Southsidemusic

Same weird workaround here aswell. Change buffer size to anything doesn't matter and then back again solves it for us. Have no clue why this is still happening though

I've seen this in Logic, should try for the weird spikes in PT

[albee1952]

Originally Posted by Studio Llama

By removing plugins will I lose all the settings in this mix I am working on? What will happen later when I unfreeze the tracks?

Thanks, Gareth

If you make them inactive, settings will remain. If you remove them from the inserts, non-default settings will be gone

[Franklyn]

People,
I think this Probleme is not (!) solved.
Is it my job to test every single plug in if it works 100% fine with this very sensible AAX engine? NO !!!
I payed so much money for the PT HD 10/11/12 Software and updates.
Avid, please do your job. I have 100s of Plug ins of renowned manufacturers.
Waves, Soundtoys, Slate, Sonnox, McDSP, Softube, UAD.
It takes hours to check every plug in. Thats no solution.Yes,
I can confirm that some plugs work better than others,
but these plug ins works much better in every other DAW. I thought some years ago we changed the plug in format from rtas to aax to get better compatibility with plug ins. But today many plug ins works 50 or 80% "fine". I think its a Pro Tools Problem. Such a "unclear" Problem exsisted in any other previous version of Pro Tools.
Please integrate a clear AAX Plug in verification in Pro Tools that show us if a plug in work correct or not.
these CPU peaks are so frustrating.
I have a lot of Sessions where i can not work on."9173 error" all the time.
But I have to finish a album.
Terrible !
Please, please, please help us !!!
Aaaaaavid Heeeeeelloooooo !!!

[Darryl Ramm]

Originally Posted by Franklyn

People,
I think this Probleme is not (!) solved.
Is it my job to test every single plug in if it works 100% fine with this very sensible AAX engine? NO !!!
I payed so much money for the PT HD 10/11/12 Software and updates.
Avid, please do your job. I have 100s of Plug ins of renowned manufacturers.
Waves, Soundtoys, Slate, Sonnox, McDSP, Softube, UAD.
It takes hours to check every plug in. Thats no solution.Yes,
I can confirm that some plugs work better than others,
but these plug ins works much better in every other DAW. I thought some years ago we changed the plug in format from rtas to aax to get better compatibility with plug ins. But today many plug ins works 50 or 80% "fine". I think its a Pro Tools Problem. Such a "unclear" Problem exsisted in any other previous version of Pro Tools.
Please integrate a clear AAX Plug in verification in Pro Tools that show us if a plug in work correct or not.
these CPU peaks are so frustrating.
I have a lot of Sessions where i can not work on."9173 error" all the time.
But I have to finish a album.
Terrible !
Please, please, please help us !!!
Aaaaaavid Heeeeeelloooooo !!!

You can ask for Avid for anything you want. That works great if you have infinite time to wait for them to do anything. If you are trying to finish an album then posting here asking avid to do something long term is a waste of your current precious time. Right. If you want to get going/optimize your workflow then you need to test with what you have.

You need to develop a rapid as possible testing approach to your problems. Start by checking all plugins are up to date, trash prefs, etc. Systems fully optimized, try doing all other tricks folks have tried here. Getting rid of Click II, etc. You on 12.6? That better or worse than 12.4?

Then pull all plugins out and confirm you can run stable sessions at all, if so then put them back and pick obvious suspect/high risk plugins and pull them out of the session. And yes start with UAD. And if this happens on some session and not others, and Save Session In does not fix that, then you can start to triangulate what common plugins are running in those session issues, make a spreadsheet if that helps. It may well still be a very broken version of Pro Tools, but you need to work out how to do what you can do to make progress. And if you finf a flakey plugin the first place to go is that plugin vendor support.

[DJ Hellfire]

Originally Posted by Matt Hepworth

All you have to do is change the buffer to a different setting. No reboot or anything like that required. I just switch between 512 and 1024 back and forth as needed.

Originally Posted by Southsidemusic

Same weird workaround here aswell. Change buffer size to anything doesn't matter and then back again solves it for us. Have no clue why this is still happening though

Same here!