Pro Tools Error AAE: 9173 with EZDrummer 3

[Jeepman813]

My Pro Tools sessions keep crashing with the AAE: 9173 error.  It states that “Audio processing deadline was not met and was caused by EzDrummer 3 Plug-In”.

I have uninstalled EZDrummer 3 but not the add on packs.  It didn’t Help.

I have changed every setting in the Pro Tools Playback engine.  It didn’t help.

I have deleted my plug-In preference and rebuilt it.  It didn’t help.

I have been through all of the Pro Tools trouble guides and hardware requirements.  No changes seem to help.

I have a Dell notebook i9 processor 64 gigs of ram 2.4gig 8 core processor.  I am using the Focusrite Scarlett 4i4 for my audio interface.

Does anyone have any words of wisdom.

EZdrummer version: 3.0.6
Operating system: Windows 10

Topic

[Brad]

Hi there,

Sorry to hear you are having problems with PT and EZD3. What version of Pro Tools are you running? Has the Focusrite Driver been updated to current?

I know you said you changed all the settings in playback engine, but would you mind if we take a revisit it can sometimes be a setting there.

• Would you mind setting the H/W Buffer to 256. ( I know a little high but just for investigation)
• Make sure you have Video Engine deselected.
• Make sure you have Ignore Errors Durring Playback/Record selected.

Also would you mind deleting the click track in the session if there is one.

 

EZdrummer version: 3.0.6
Operating system: Windows 10

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Jeepman813]

Brad,

Hello.

I changed the Playback settings as you described.  I even increase the HW Buffer size to a larger number. The Video Engine is off and the Ignore Errors has been selected.

I also uninstalled the Focusrite Software and drivers.  Reinstall them.

I removed the Click track.

I rebooted my computer after all the changes and tried again.

I still get the same error.

I also tried loading the ASIOAll and removed the Focusrite all together.  It still errored out.

Any other thought or ideas for me to try?

I am using Pro Tools Studio Version 12.

I used EZDrummer 2 with no issues.  I used the EZDrummer 3 sucessfully.  But now errors.

Jeff

[Brad]

Jeepman813 wrote:

Brad,

Hello.

I changed the Playback settings as you described.  I even increase the HW Buffer size to a larger number. The Video Engine is off and the Ignore Errors has been selected.

I also uninstalled the Focusrite Software and drivers.  Reinstall them.

I removed the Click track.

I rebooted my computer after all the changes and tried again.

I still get the same error.

I also tried loading the ASIOAll and removed the Focusrite all together.  It still errored out.

Any other thought or ideas for me to try?

I am using Pro Tools Studio Version 12.

I used EZDrummer 2 with no issues.  I used the EZDrummer 3 sucessfully.  But now errors.

Jeff

Good morning (here on the west coast)

So a few other things to go over.

• Is this happening on a specific session or even a new session with just EZD?
• Could you try (as an experiment) using the internal sound card?
• It was AISO4ALL driver you installed in addition to Focusrite, yes?

EZdrummer version: 3.0.6
Operating system: macOS Ventura (13)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Jeepman813]

Brad,

Good morning.  Lunch time here on east coast.

I did try on multiple session and even creating a new one.  Same error.

I also tried the internal card, and I got the same error.

I also tried using the ASIOALL with the Focusrite.  Same error.

I removed EZDrummer 2 and EZDrummer 3.  The played the track.  It errored out on EZBass.  I remove EZDrummer2, EXDrummer3, and EZBass as a plugin on tracks and it plays without issue.

I am in the process of removing ALL Toontrack products and the expansion packs.  Then I will reboot.  Load one at a time until I figure out which one cause the issue.

I have been monitoring through Windows and inside of Pro Tools system usage.  CPU and Memory are barely being used.

I am at a loss.  I figure I would try uninstalling everything and try again.

Your thoughts.  I appreciate your help.

Jeff

[Brad]

Jeepman813 wrote:

Brad,

Good morning.  Lunch time here on east coast.

I did try on multiple session and even creating a new one.  Same error.

I also tried the internal card, and I got the same error.

I also tried using the ASIOALL with the Focusrite.  Same error.

I removed EZDrummer 2 and EZDrummer 3.  The played the track.  It errored out on EZBass.  I remove EZDrummer2, EXDrummer3, and EZBass as a plugin on tracks and it plays without issue.

I am in the process of removing ALL Toontrack products and the expansion packs.  Then I will reboot.  Load one at a time until I figure out which one cause the issue.

I have been monitoring through Windows and inside of Pro Tools system usage.  CPU and Memory are barely being used.

I am at a loss.  I figure I would try uninstalling everything and try again.

Your thoughts.  I appreciate your help.

Jeff

Exactly what I was going to suggest next. Just move them out of the AAX plug-ins folder.

You don’t need to remove libraries.

Reboot

Add them back one at a time.

Actually Avid’s guidance is to remove all plugins, in my case that would take a long time and a lot more wine than I have at home.😆

So let’s just start with Toontrack plug-ins

cheers

Brad

EZdrummer version: 3.0.6
Operating system: macOS Ventura (13)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• This post was modified 2 years, 3 months ago by Brad.

[Brad]

Do you have AudioSender plug-in as well? Has it been updated?

EZdrummer version: 3.0.6
Operating system: Windows 10

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Brad]

Hey Jeff,

I had a thought (usually arrives after a 3rd espresso).

Have you looked at the CPU affinity settings?

https://avid.secure.force.com/pkb/articles/en_US/Knowledge/Optimising-Processor-Affinity-Windows?retURL=%2Fpkb%2Farticles%2Fen_US%2FTroubleshooting%2FOptimising-Processor-Affinity-Windows&popup=true

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Jeepman813]

Brad,

It has been a busy afternoon.

I uninstalled ALL Toontrack software.

FYI:  Yes I use the AudioSender.  I uninstalled it also.

I reinstalled just EZDrummer 3 and EZBass with no addon packs.

I also switch over to my Helix Floor as my Audio Interface to eliminate the Focusrite 4i4.

Everything was working but I wasn’t play a drum track.

I loaded the add on Pack ALT Rock EZX.

Then I play a track with drums that called to the ALT Rock EZX kit.

It crashed fast.

I exited out of Pro Tools and rebooted.  This time I increase the cache.

I was able to play the song a few times.  Then I plugged my guitar it to play along with the track.  It crashed.

I have attached a log file from Pro Tools.  Not sure if this is the right one or not.  It is a big file.  About 90 percent through the file (line number 1153) you can see where I get the error message.  I hope this helps in solving the mystery.

I will keep on testing to see what I can discover.  At this point I don’t think it is the Focusrite Scarlett 4i4 since it crashed with a different audio device.

I do have another question.  Different topic.  I started with EZDrummer 2.  I upgraded to EZDrummer 3.  Does EXDrummer 3 have all the drum kits and drum groves from Drummer 2?  Do I need to load or keep EZDrummer 2?

Again, I appreciate all of your help.

Jeff

 

[Brad]

Jeepman813 wrote:

Brad,

It has been a busy afternoon.

I uninstalled ALL Toontrack software.

FYI:  Yes I use the AudioSender.  I uninstalled it also.

I reinstalled just EZDrummer 3 and EZBass with no addon packs.

I also switch over to my Helix Floor as my Audio Interface to eliminate the Focusrite 4i4.

Everything was working but I wasn’t play a drum track.

I loaded the add on Pack ALT Rock EZX.

Then I play a track with drums that called to the ALT Rock EZX kit.

It crashed fast.

I exited out of Pro Tools and rebooted.  This time I increase the cache.

I was able to play the song a few times.  Then I plugged my guitar it to play along with the track.  It crashed.

I have attached a log file from Pro Tools.  Not sure if this is the right one or not.  It is a big file.  About 90 percent through the file (line number 1153) you can see where I get the error message.  I hope this helps in solving the mystery.

I will keep on testing to see what I can discover.  At this point I don’t think it is the Focusrite Scarlett 4i4 since it crashed with a different audio device.

I do have another question.  Different topic.  I started with EZDrummer 2.  I upgraded to EZDrummer 3.  Does EXDrummer 3 have all the drum kits and drum groves from Drummer 2?  Do I need to load or keep EZDrummer 2?

Again, I appreciate all of your help.

Jeff

 

Hi there,

To answer your question; you don’t need EZDrummer 2 if you have EZDrummer 3 as it will be able to access all the EZXs and MIDI add ons, however, if you have EZDrummer 2 inserted on a session, Pro Tools will complain.

Have you disabled hyperthreading on your PC? If not, could you try disabling it?

Thanks for posting the application dump. I did find where the crash is being triggered. Unfortunately I am unable to determine what yet.

 

1153.311485,03b38,000d: Plugin com.toontrack.EZdrummer3 exceeded the buffer duration 23219 us – plugin processing duration 25103 

1153.336259,03b38,000d: Plugin com.toontrack.EZdrummer3 exceeded the buffer duration 23219 us – plugin processing duration 24705 

1153.348576,02620,0e10: CFicMariaTDMDeck::ErrorStop – err: -9173

1153.373485,02620,000f: CDAEErrorHandler::DAEErrorStopProc – err – -9173

1153.388688,013a8,000f: FicWaitingForTriggeredStop – runningTime = 0 mPlayStopTrigger = 5882868 isWaitingForStop = NO

1153.388695,013a8,000f: about to call PostStopProcessing 1

1153.388710,013a8,000f: stopLocalTime = 663549

1153.388712,013a8,000f: stopGlobalTime = 663549

1153.888714,013a8,000d: CHostXDevice::SetTriggeredStop() runningTimeStopSample=18446744073709551615, entryTime=0 (diff=0)

1153.891725,013a8,000f: timeSincePlayStarted = 0

1153.891732,013a8,000f: mActualPlayStartSample = 0

1153.891733,013a8,000f: theStopSample = 663549

1153.892199,013a8,000f: CProToolsMachine::DoRecordCleanUp inStopElapsedTime = 663549

1153.892209,013a8,001b: CSync::PTStateUpdateCallback – last state – eMachineState_Play, new state – eMachineState_Play

1153.892615,013a8,001b: CMachine::SetRecordEnable inRecordEnable = NO, mRecordEnable = YES

1153.892622,013a8,001b: CSync::PTStateUpdateCallback – last state – eMachineState_Play, new state – eMachineState_Play

1153.892627,013a8,000f: FicActualPunchInEx tempStartRecSamp = 0 tempStopRecSamp = 663549

1153.893234,013a8,0d02: Performing TCommand: Record

1153.904816,013a8,0d02: TProToolsDoc::SetCurrentSelection

1153.904823,013a8,000f: TProToolsDoc::SetCurrentSelection – start = 0 end = 0

1153.904893,013a8,0b09: SLnk_Manager::SetCurrentSelection: in:0 out:0

1153.914482,013a8,001d: SetStackSymbolicationDuringPlayback: stopped syms=1 save=0

1153.914497,013a8,001b: CSync::PTStateUpdateCallback – last state – eMachineState_Play, new state – eMachineState_Stop

1153.918954,013a8,0d02: TProToolsDoc::DoStopCleanUp

1153.919239,013a8,000f: CSync::GetStopSample = 663549

1153.919244,013a8,001b: TProToolsDoc::GetStopSample = 663549

1153.919305,013a8,0d02: TProToolsDoc::SetCurrentSelection

1153.919308,013a8,000f: TProToolsDoc::SetCurrentSelection – start = 0 end = 0

1153.919323,013a8,0b09: SLnk_Manager::SetCurrentSelection: in:0 out:0

1153.920629,013a8,000f: TTransportSyncView::StateUpdateCallback – inLastState – eMachineState_Play, inNewState – eMachineState_Stop, inOnline – false

1153.920647,013a8,000f: TTransportSyncView::StateUpdateCallback – inLastState – eMachineState_Play, inNewState – eMachineState_Stop, inOnline – false

1153.962755,013a8,0d02: Performing TCommand: class CHandleErrorStopCommand

1153.962859,013a8,000f: CDAEErrorHandler::HandleErrorStop – mErrorStopOSErr – -9173

1153.962896,013a8,0b09: SLnk_MachineMgr::SendDialogOnScreen: 253239304, error msg = Pro Tools ran out of CPU power. Try de-activating or removing Native plug-ins.  (AAE -9173)

1153.962906,013a8,0b09: SLnk_MachineMgr::UpdateDialogOnScreen: eSLnk_DialogType_DAEError, IP = 255.255.255.255 0

1153.962948,013a8,001b: CProToolsMachine::Stop

1153.962951,013a8,000f: CProToolsMachine::Stop – display error – false, requestedStopLocation = 0

1153.962954,013a8,000f: CProToolsMachine::Stop beginning mCurrentTimelinePosition = 663549, mStopSample = 663549

1153.962977,013a8,0e10: ReportDAEError – iDAEError – -9173

1153.963041,013a8,0b09: SLnk_MachineMgr::SendDialogOnScreen: 253239304, error msg = Audio processing deadline was not met. This may have been caused by the following plugin:

Plug-in: EZdrummer 3 (3.0.6.35660)

Track: Drums

Insert: A

Try inactivating the plug-in or increasing the HW buffer size.

(AAE -9173)

1153.963045,013a8,0b09: SLnk_MachineMgr::UpdateDialogOnScreen: eSLnk_DialogType_DAEError, IP = 255.255.255.255 0

1153.963075,013a8,001b: CSync::Stop

1153.963077,013a8,000f: CSync::Stop

1153.963080,013a8,0b09: SLnk_Manager::StopOK

1153.963084,013a8,001b: CSync::Stop – skipping WaitForStateTransitionToPlay

1153.963086,013a8,001b: CSync::Stop mPaused set to false

1153.963088,013a8,000f: CSync::ComputePlayStopRunningTimeTrigger

1153.963094,013a8,000f: satelliteStopDelay = 0

1153.963096,013a8,000f: totalStopDelay = 3072

1153.963155,013a8,000f: requestedStopRunningTime = 3072

1153.963158,013a8,000f: CSync::ComputePlayStopTimeLineLocation: inRunningTime = 3072

1153.963160,013a8,0b09: CSync::ComputePlayStopTimeLineLocation runningTime – 3072

1153.963162,013a8,0b09: CSync::ComputePlayStopTimeLineLocation elapsedTime – 0

1153.963164,013a8,0b09: CSync::ComputePlayStopTimeLineLocation timeLineLocation – 0

1153.963166,013a8,000f: requestedStopLocation = 0

1153.963716,013a8,001b: CSync::SetState – eSynchronizerState_stopping (previous state: eSynchronizerState_play)

1153.963718,013a8,001b: mActualPlayStartTime 999999040029 – mActualPlayStartTimeSaved 999999040029

1153.963720,013a8,0b09: SLnkMM:state eSLnk_State_Stopping

1153.963739,013a8,0f09: Alert: Audio processing deadline was not met. This may have been caused by the following plugin:

Plug-in: EZdrummer 3 (3.0.6.35660)

Track: Drums

Insert: A

Try inactivating the plug-in or increasing the HW buffer size.

(AAE -9173)

1153.963799,013a8,0b09: SLnk_MachineMgr::SendDialogOnScreen: 253239304, error msg = Audio processing deadline was not met. This may have been caused by the following plugin:

Plug-in: EZdrummer 3 (3.0.6.35660)

Track: Drums

Insert: A

Try inactivating the plug-in or increasing the HW buffer size.

(AAE -9173)

EZdrummer version: 3.0.6
Operating system: Windows 10

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Jeepman813]

Brad,

Hello.

Yes, I turned off hyperthreading early on in this process.

I am considering uninstalling Pro Tools now and reinstalling to see what that gets me.

If that doesn’t work, I am considering the move to Studio One.  My Pro Tools subscription is up in April.  Does the Toontracks Plugins (EZDrummer 3 and EZBass) work with Studio One?

Let me know if you want me to try something else.

Thank you,

Jeff

[Brad]

Jeepman813 wrote:

Brad,

Hello.

Yes, I turned off hyperthreading early on in this process.

I am considering uninstalling Pro Tools now and reinstalling to see what that gets me.

If that doesn’t work, I am considering the move to Studio One.  My Pro Tools subscription is up in April.  Does the Toontracks Plugins (EZDrummer 3 and EZBass) work with Studio One?

Let me know if you want me to try something else.

Thank you,

Jeff

Always woth a try.

I use Studio One now more than I use Pro Tools. Yes EZDrummer works great, as does EZBass, EZKeys, EZMix…..

EZdrummer version: 3.0.6
Operating system: Windows 10

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[Brad]

Have you posted anything on DUC? There’s a lot folks there that use PT day to day that would have a deeper knowledge of Pro Tools than I do. I used to use it day to day, but now find the Studio One workflow more efficient for what I do, though a few mixing jobs lately have required me to start polishing up my PT skills.

Would be a good idea to post a question on DUC, detailing everything you’ve done so far.

EZdrummer version: 3.0.6
Operating system: macOS Ventura (13)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• This post was modified 2 years, 3 months ago by Brad.

[Jeepman813]

Brad,

Hey.

I have put so much effort into learning Pro Tools.  I hate to walk away but…………………………………………….

It is frustrating.

Jeff

[Brad]

Jeepman813 wrote:

Brad,

Hey.

I have put so much effort into learning Pro Tools.  I hate to walk away but…………………………………………….

It is frustrating.

Jeff

A thought…. have you tried different sample rates when creating a pro tools session.

Finally, if you can create a new session that is crashing, zip up the folder and post it here I’ll see if I can recreate the issue.

EZdrummer version: 3.0.6
Operating system: macOS Ventura (13)

Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

• This post was modified 2 years, 3 months ago by Brad.

[Aargan74]

Jeepman813 wrote:

My Pro Tools sessions keep crashing with the AAE: 9173 error.  It states that “Audio processing deadline was not met and was caused by EzDrummer 3 Plug-In”.

I have uninstalled EZDrummer 3 but not the add on packs.  It didn’t Help.

I have changed every setting in the Pro Tools Playback engine.  It didn’t help.

I have deleted my plug-In preference and rebuilt it.  It didn’t help.

I have been through all of the Pro Tools trouble guides and hardware requirements.  No changes seem to help.

I have a Dell notebook i9 processor 64 gigs of ram 2.4gig 8 core processor.  I am using the Focusrite Scarlett 4i4 for my audio interface.

Does anyone have any words of wisdom.

EZdrummer version: 3.0.6
Operating system: Windows 10

Hola!,yo también tengo un problema,Ezdrummer no me aparece en Protools 10, alguien podría decirme como solucionarlo?

EZdrummer version: 3.0.6
Operating system: macOS High Sierra (10.13)

[Author]

Replies