|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#21
|
||||
|
||||
Re: -9173 Error HELP
__________________
Help Us Help You ______________________________________ Chris Pro Tools 2024.3 Focusrite LS56 Focusrite Pro40 (3) Slate Digital VRS8 Analogue Tonebuss 24 Channel UAD-2 OCTO Core Accelerator UAD Volt 2 macOS 10.15.7 32 GB DDR4 RAM 4.01GHz Quad-Core Intel Core I7 NVIDIA GeForce GT 740 2 GB |
#22
|
|||
|
|||
Re: -9173 Error HELP - solved my overloads here also more DSP tests
Just installed the latest UAD apollo Tbolt mac driver and am having the best performance overall that I have had with PT since i first used it at V12.4.. I am on 2018.3
Still a no go at 32 samples but 64 samples with 32 tracks all armed for recording, with ew VMR's with three modules on each one, can now literally be done.. There are still some Vi's that I can not play a single note with at 64 samples but as usual 128 fixes all. I too was using the mac's own internal core audio till i finally took the apollo twin out of my studio and put it on the laptop, as I have another A8 on the way to hook up with my current A8, with my 2 adat expanders of 8 channels each, that will give me the exact maximum 32 inputs for pro tools through apollo for now. Anyway putting the tbolt twin on my 2015 built, 2014 model macbook pro, works SO much better than the internal sound.. SO.. my first recommendation to the OP is to get a decent T Bolt interface and basically run at 128 buffers which is perfectly safe all day, or 256 if you go to 88 or 96khz. The thing is, the apollo TBolt's output (the only one that matters for VI's), is only 3.4 milliseconds at 128 buffer.. that's better than many usb interfaces at 256. It works great.. It's even usable at 128 with my virus TI now (doubles the latency if used via USB audio so basically exactly 7.8 ms which is still playable for a VI). But even so, i can put the project at 64 if i really want to, just when i am recording some virus midi.. as long as the virus is the only armed VI of course at that low a buffer. Then I can just put it back to 128. I did some more DSP tests today with Apollo.. Pro tools Vs Cubase Vs Logic. I used steinberg retrologue synth, FM EP patch, 4 note chord progressions for 8 bars and a single melody on top of the chords in the same midi clip.. Pro tools was able to get 32 of them playing back at 128 buffer, record ARMED.. every VI track was armed, that's right. Taking them off monitoring and pro tools shuffling them on the playback buffer only got like 3 or 4 extra tracks. That's how well 128 buffer works with a good thunderbolt interface. Honestly, at 128, i haven't had a single drop out all day. The kicker is at 64 samples, i was able to also play back all 32 Vi's, and remember retrologue is not a native AAX, so unlike the cubase VST3 and Logic AU versions, i have to put it in a wrapper like blue cat patchwork which IS extra overhead, no matter how tiny. But at 64 samples i could only have 8 of them record armed. Still, pro tools was literally at 99% and occasionally the performance meter would go red but it did NOT drop out and i left the 8 bars looping for 10 minutes! I was really impressed. Cubase at 64 buffer can play back the 32 Retrologues using the same midi file, but can only arm one or two of them, and if you move the mouse around or the screen view, none at all - clicks and pops. At 128 buffer it matched Pro tools but unlike pro tools it did have occasional clicks and pops.. 28 was the number that never caused issue at 128 buffer. Logic was 24 instances playback or 12 armed (logic can only use half the available logical cores for live tracks, so out of 8 here it will only use four.. So even if you have 64 tracks armed for record, it will only use half your processors for those armed tracks.. Cubase and PT and Reaper use all of them). Yet, and this is the big one.. At Logic i could put the UAD at 32 buffer at 88K. The output latency is, get ready for it, 0.7ms. I am literally playing VI's at 0.7ms. And all the Vi's i can NOT play at 32 or 64 samples in protools at even 44K, i can play in Logic in realtime at 88K at *32 samples*. Same machine. That says everything about Avid's need to further optimise the low latency engine. Cubase falls exactly half way, if logic can do it at 32 cubase can usually do it at 64.. etc... Anyway, with the apollo, my macbook performs better than my 3.4ghz i7 imac (2600k basically), and i have turbo boost disabled on the macbook so it's always at 2.8ghz.. The imac is not far behind in track count, and is always at 3.7ghz, no need to disable turbo as the temps never get out of control like the macbook. ---------------------------------------------------------------------------------------------------------------------------------------- Anyway, for those TLDR the above In short, get a thunderbolt interface with good drivers for your imac which will also work on your macbook. I highly recommend a UAD twin duo. Or quad if your budget can stretch that far. it really did solve almost all overload problems on my macbook. Also i have to say, there are just some effects and Vi's that simply still denormal, and intel processors are the most susceptible. I have seen it with even the korg gadget stuff.. i am literally playing away and pro tools says 4% usage, then after i stop playing my midi keyboard, and there is silence, after 2 seconds it jumps to 100% and drops out all the audio. So it really could be a combination of things and since it is happening on both the OP's systems, it is not his macs.. can't be.
__________________
- Intel 14900K/NzXt Kraken Elite/64GB Kingston DDR5 6000 mhz (32x2)/ Asus Pro Art Z790/Asus 4090/Win 11 Pro 23H2/UAD Apollo 8 x2 w TBolt 3 card u/g/UAD Twin X. |
#23
|
|||
|
|||
Re: -9173 Error HELP
I'd contact support if I were you. Let them figure it out.
C
__________________
PT 2021.10 HDX 16x24 -Mac Pro 12 Cores 48 GB RAM OS 10.13.6 - API 16 channel - AMS Neve 16 channel, AMS-Neve-SSL -Pres/Processing, Bock Audio, BLUE Bottle, Neumann, Josephson -Mics, Bogner, Kemper- Guitar, Chandler Zener-Curve Bender Outboard/Master. UAudio, Waves, Plugin Alliance etc. |
#24
|
|||
|
|||
Re: -9173 Error HELP
I’m late to the party on this one, but I’m getting the same error message on a Mac Pro 5,1 mid 2012 12 core/2x3.06 ghz - 32 gig of Ram
This occurs with the buffer is set @ 512 running only Easy Drummer 2 midi samples with no audio files and no plug-ins in use. System usage CPU meter is 8% and OS system monitor CPU is less than 4%. Any advise would be appreciated. |
#25
|
|||
|
|||
Re: -9173 Error HELP
I’m late to the party on this one, but I’m getting the same error message on a Mac Pro 5,1 mid 2012 12 core/2x3.06 ghz - 32 gig of Ram
This occurs with the buffer is set @ 512 running only Easy Drummer 2 midi samples with no audio files and no plug-ins in use. System usage CPU meter is 8% and OS system monitor CPU is less than 4%. Any advise would be appreciated. |
#26
|
|||
|
|||
Re: -9173 Error HELP
similar issue here.
I'm on mac mini late 2012, quad i7 full ram. OS X el Capitan 10.11.6 Pro Tools 2018.4 Never seen this issue in the past years (pt 12.x on same machine running OS X 10.10 working on very crowded sessions with uncountable tracks and plugins. Now EVERYTIME I open a session (even with very few tracks and less that less plugins) I get this error. The very strange thing is that the issue seems to be connected with MIDI and instruments tracks but ONLY on the first run. After I close the error window and play again the session from the same point everything it's ok. No more error until I open another session (or close and reopen the same) and, as before, after the first attempt to play an instrument track (which gives me the usual error), it works fine... and so on and on. This happens even with a very light instrument like the simple mini grand piano plugin which comes with pro tools itself. Doesn't matter if the session is almost empty... the first run of an instrument track produce the -9173 error... Session are 96k 24bit (always worked this way even when I didn't get this error in the past). Don't know if it's a problem related to el Capitan or the new pro tools (since it changed name in 20xx.x) or what else. It looks like the system needs to set "something" related to the track it's about to play, and after it "knows" this track it can play it with no problem at all.... like it has to set a sort of "something" that allow it to play that track until the session is open, But this magic thing disappear when I close the session and needs to be "find out" again the next first run of the same session. Hope someone has a clue about this strange error. Thanks for the help and your time. Cheers. Marco
__________________
Mac Mini late 2012 - 2,3 GHz Intel Core i7 quad core, 16 GB 1600 MHz DDR3, - Pro Tools 2018-4 up to 2022-6 / OSX el Capitan 10.11.6 up to Mojave 10.14.6 |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AAE error -9173 | nikydvt | Pro Tools 12 | 11 | 01-14-2017 04:05 PM |
AAE error -9173 on PT 12.4 | marcnyc | Pro Tools 12 | 2 | 06-24-2016 03:27 PM |
-9173 error in PT 12 | ArKay99 | Pro Tools 12 | 10 | 06-11-2016 01:41 AM |
PT 11 Clearly Not An AAE 9173 Error | rgconrad1 | Pro Tools 11 | 3 | 09-29-2014 11:56 PM |