Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Hardware > Pro Tools HDX & HD Native Systems (Mac)

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 07-19-2022, 12:21 AM
LukeHoward LukeHoward is offline
Member
 
Join Date: Mar 2001
Location: Melbourne
Posts: 1,233
Default Error finalising ADM WAV

Getting a frustrating error bouncing an ADM WAV which unscientifically appears to depend on routing and number of plugins. Appears with Hybrid Engine disabled and enabled. I'm on 2022.6 with HDX, MTRX clocked by Sync X, DAPS is connected via a separate MADI interface.

Generally it errors out finalising the ADM WAV and the logs are filled up with the following error. After the error occurs Pro Tools needs to be restarted. Bouncing non-ADM WAVs is fine. I eventually worked around it by simplifying the routing in my session, moving some prefader sends on some tracks to outputs (they previously had no output assigned, perhaps this confused something).

Edit: this workaround didn't always work, it appeared in simple sessions with almost all plugins disabled. It appears that there were many changes to the ADM bounce code in 2022.6 and this may be a regression.

Code:
2759.482711,51a03,0e0f: CMN_TRACEASSERT err == 0 /Users/autobld/gitlabci/PT/release/2022/r2/ProTools/AAE/Source/HostTDMDeck/CHostXDevice.cpp line 1875

2759.701733,101803,0b09: SLnk_UMEClock::UpdateRunningTime got a 0 running time!
2759.952474,101803,0b09: SLnk_UMEClock::UpdateRunningTime got a 0 running time!
2760.006766,51a03,0e10: FicOSErr: DAE Error being generated: -9004
Stacktrace:
	0x112eb98fa : FicOSErr(int) + 362 (AAE @ 0x112d9d000)
	0x112e591aa : CHostXDevice::ErrorCallback(int) + 266 (AAE @ 0x112d9d000)
	0x112e5aad6 : CHostXDevice::AudioCB_WorkLoop(CHostXDevice::CCallbackInfo&) + 198 (AAE @ 0x112d9d000)
	0x112e54dc3 : CHostXDevice::DoAudioProcessing() + 339 (AAE @ 0x112d9d000)
	0x112e59d27 : CHostXDevice::AudioCallback(IODriverAudioPB*) + 295 (AAE @ 0x112d9d000)
	0x112f10f8d : CBerlinIODevice::AudioCallback() + 637 (AAE @ 0x112d9d000)
	0x112f0fa94 : CBerlinIODevice::HandleAudioInterrupt(EDhmIsochEngine_InterruptMask) + 132 (AAE @ 0x112d9d000)
	0x112f0f779 : CBerlinIODevice::HandleInterrupt(EDhmIsochEngine_InterruptMask, unsigned int) + 697 (AAE @ 0x112d9d000)
	0x103f03ba3 : CDhmBerlinIsochEngine::IOBerlinDriverPrimIntHandler(void*, DSPRecord*, unsigned int, unsigned int) + 19 (DSI @ 0x103d5e000)
	0x103dac507 : InternalInterruptHandler(void*, unsigned int, unsigned int, unsigned int, unsigned int) + 23 (DSI @ 0x103d5e000)
	0x1015f9162 : CModule_Hardware_Imp::InvokeInterruptHandlers(unsigned int, unsigned int, unsigned int, unsigned int) + 108 (DigiPlatformSupport @ 0x1015f0000)
	0x1015f996b : CModule_Hardware_Imp::ThreadMethod(IPSThread*) + 391 (DigiPlatformSupport @ 0x1015f0000)
	0x1015faebb : CTask_Imp::MacOSXMasterThreadProc(void*) + 95 (DigiPlatformSupport @ 0x1015f0000)
	0x7ff81aa3c4e1 : _pthread_start + 125 (libsystem_pthread.dylib @ 0x7ff81aa36000)
	0x7ff81aa37f6b : thread_start + 15 (libsystem_pthread.dylib @ 0x7ff81aa36000)
2760.006846,51a03,0e0f: CMN_TRACEASSERT err == 0 /Users/autobld/gitlabci/PT/release/2022/r2/ProTools/AAE/Source/HostTDMDeck/CHostXDevice.cpp line 1875
2760.006943,51a03,000d: CBerlinIODevice::ReadSDIErrors() StreamingUnderrun
2760.006946,51a03,000d: >>> ReadSDIErrors failed with error code -9093
2760.203290,101803,0b09: SLnk_UMEClock::UpdateRunningTime got a 0 running time!
2760.453586,101803,0b09: SLnk_UMEClock::UpdateRunningTime got a 0 running time!
2760.455203,51a03,0e10: FicOSErr: DAE Error being generated: -9004
Stacktrace:
	0x112eb98fa : FicOSErr(int) + 362 (AAE @ 0x112d9d000)
	0x112e591aa : CHostXDevice::ErrorCallback(int) + 266 (AAE @ 0x112d9d000)
	0x112fa12fd : CFPGA_DMA_Device::TooManyIntsRecovery() + 205 (AAE @ 0x112d9d000)
	0x112f0fb08 : CBerlinIODevice::HandleAudioInterrupt(EDhmIsochEngine_InterruptMask) + 248 (AAE @ 0x112d9d000)
	0x112f0f779 : CBerlinIODevice::HandleInterrupt(EDhmIsochEngine_InterruptMask, unsigned int) + 697 (AAE @ 0x112d9d000)
	0x103f03ba3 : CDhmBerlinIsochEngine::IOBerlinDriverPrimIntHandler(void*, DSPRecord*, unsigned int, unsigned int) + 19 (DSI @ 0x103d5e000)
	0x103dac507 : InternalInterruptHandler(void*, unsigned int, unsigned int, unsigned int, unsigned int) + 23 (DSI @ 0x103d5e000)
	0x1015f9162 : CModule_Hardware_Imp::InvokeInterruptHandlers(unsigned int, unsigned int, unsigned int, unsigned int) + 108 (DigiPlatformSupport @ 0x1015f0000)
	0x1015f996b : CModule_Hardware_Imp::ThreadMethod(IPSThread*) + 391 (DigiPlatformSupport @ 0x1015f0000)
	0x1015faebb : CTask_Imp::MacOSXMasterThreadProc(void*) + 95 (DigiPlatformSupport @ 0x1015f0000)
	0x7ff81aa3c4e1 : _pthread_start + 125 (libsystem_pthread.dylib @ 0x7ff81aa36000)
	0x7ff81aa37f6b : thread_start + 15 (libsystem_pthread.dylib @ 0x7ff81aa36000)
2760.455274,51a03,0e0f: CMN_TRACEASSERT err == 0 /Users/autobld/gitlabci/PT/release/2022/r2/ProTools/AAE/Source/HostTDMDeck/CHostXDevice.cpp line 1875
2760.704498,101803,0b09: SLnk_UMEClock::UpdateRunningTime got a 0 running time!
__________________
https://lukehoward.com/

Last edited by LukeHoward; 07-25-2022 at 10:28 PM.
Reply With Quote
  #2  
Old 07-25-2022, 09:18 PM
LukeHoward LukeHoward is offline
Member
 
Join Date: Mar 2001
Location: Melbourne
Posts: 1,233
Default Re: Error finalising ADM WAV

This appears to be a regression in 2022.6. I cannot duplicate it with 2022.4 or 2022.5.
__________________
https://lukehoward.com/

Last edited by LukeHoward; 07-25-2022 at 10:08 PM.
Reply With Quote
  #3  
Old 07-27-2022, 04:10 AM
Darryl Ramm Darryl Ramm is online now
Member
 
Join Date: Nov 2010
Location: USA
Posts: 19,510
Default Re: Error finalising ADM WAV

Luke what computer/os are you running on?
Reply With Quote
  #4  
Old 07-27-2022, 06:44 AM
LukeHoward LukeHoward is offline
Member
 
Join Date: Mar 2001
Location: Melbourne
Posts: 1,233
Default Re: Error finalising ADM WAV

Quote:
Originally Posted by Darryl Ramm View Post
Luke what computer/os are you running on?
2019 Mac Pro running macOS 12.4. Reckon it’s a PT bug though, I've logged a case with Avid and they are investigating it.
__________________
https://lukehoward.com/

Last edited by LukeHoward; 07-27-2022 at 05:52 PM.
Reply With Quote
  #5  
Old 08-14-2022, 08:11 PM
LukeHoward LukeHoward is offline
Member
 
Join Date: Mar 2001
Location: Melbourne
Posts: 1,233
Default Re: Error finalising ADM WAV

Essentially it boils down to this: no hardware inserts, everything is fine; hardware inserts on all tracks (two in my session), all fine; hardware inserts on some tracks and not others (two and one respectively in test session), issue triggered.
__________________
https://lukehoward.com/
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Transfer of Ownership Fail - Error: Error occurred while loading a Visualforce page Chevron Licensing & Accounts 10 12-19-2019 12:35 PM
Frame rate change after finalising TrentWilliams Post - Surround - Video 2 05-16-2016 11:55 AM
Pro Tools 9 Playback Error Lead to DAE Error 743 Which Lead to A CPU Overload Error EricMulhern macOS 1 11-20-2011 05:39 PM
Error type 10,address error ,illegal error, buss error ,illegal instruction KasticK Pro Tools TDM Systems (Mac) 3 05-14-2003 11:21 AM
Buss error,Address error,ilegal instruction,error type 10 KasticK Pro Tools TDM Systems (Mac) 1 02-08-2003 05:49 PM


All times are GMT -7. The time now is 01:17 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com