PT8: Crash when taking track out of input

[jstaczek]

PT8 seems to have a problem taking tracks out of input on some sessions. I was getting a beachball+crash pre-cs2, but in cs2 and 3 I now get frozen UI and this crash:

Process:         Pro Tools HD [237]
Path:            /Applications/Digidesign/Pro Tools/Pro Tools HD.app/Contents/MacOS/Pro Tools HD
Identifier:      com.digidesign.ProToolsHD
Version:         8.0cs3 (8.0.0f341)
Code Type:       PPC (Native)
Parent Process:  launchd [124]

Interval Since Last Report:          120 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report:  101 sec
Per-App Crashes Since Last Report:   1

Date/Time:       2009-07-20 00:21:00.792 -0700
OS Version:      Mac OS X 10.5.7 (9J61)
Report Version:  6
Anonymous UUID:  CDE839F5-5F45-4278-B36D-B5207EE11544

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c0000003
Crashed Thread:  0

Thread 0 Crashed:
0   libstdc++.6.dylib             	0x914b8560 __dynamic_cast + 60
1   ...gidesign.framework.ProTools	0x01fd5948 Cmn_TypedException<Cmn_ANSIExceptionData>::Cmn_TypedException(Cmn_TypedExceptionCode<Cmn_ANSIExceptionData> const&, Cmn_ANSIExceptionData const&, Cmn_StackDump*) + 1509484
2   ...gidesign.framework.ProTools	0x01fd5948 Cmn_TypedException<Cmn_ANSIExceptionData>::Cmn_TypedException(Cmn_TypedExceptionCode<Cmn_ANSIExceptionData> const&, Cmn_ANSIExceptionData const&, Cmn_StackDump*) + 1509484
3   ...gidesign.framework.ProTools	0x02244008 Cmn_TypedException<L10N_ExceptionData>::Cmn_TypedException(Cmn_TypedExceptionCode<L10N_ExceptionData> const&, L10N_ExceptionData const&, Cmn_StackDump*) + 1698004
4   ...gidesign.framework.ProTools	0x01fd9528 Cmn_TypedException<Cmn_ANSIExceptionData>::Cmn_TypedException(Cmn_TypedExceptionCode<Cmn_ANSIExceptionData> const&, Cmn_ANSIExceptionData const&, Cmn_StackDump*) + 1524812
5   ...gidesign.framework.ProTools	0x02334740 Cmn_TypedException<MA_OSErrData>::Cmn_TypedException(Cmn_TypedExceptionCode<MA_OSErrData> const&, MA_OSErrData const&, Cmn_StackDump*) + 104536
6   com.digidesign.framework.DFW  	0x007a5758 TEventHandler::HandleIdle(IdlePhase) + 220
7   com.digidesign.framework.DFW  	0x00787990 TApplication::Idle(IdlePhase) + 196
8   com.digidesign.framework.DFW  	0x007844d4 TApplication::PostEventListWakeupToOSEventQueue(TEvent*, long) + 324
9   com.digidesign.framework.DFW  	0x00802df0 DFW_Timers::LockedCallbackTimerProc::operator()(void*) + 84
10  com.digidesign.framework.DFW  	0x0080085c DFW_Timers::CallbackTimerManager::MasterCallback(void*) + 84
11  com.digidesign.framework.DFW  	0x007fef54 bool DFW_Event2MacOSEvent::SetDFWProperty<unsigned long, 1802334052l, 1819242087l, DFW_KeyModifiersProxy, 1096900971l>(OpaqueEventRef const*, DFW_EventRef) + 1952
12  com.digidesign.framework.DFW  	0x00817520 TC::Open() + 17056
13  com.apple.CoreFoundation      	0x957569a8 CFRunLoopRunSpecific + 2968
14  com.apple.HIToolbox           	0x93f049d4 RunCurrentEventLoopInMode + 264
15  com.apple.HIToolbox           	0x93f047f8 ReceiveNextEventCommon + 412
16  com.apple.HIToolbox           	0x93f62894 RunApplicationEventLoop + 148
17  com.digidesign.framework.DFW  	0x007f3e0c DFW_EventLoop::RunApplicationEventLoop() + 12
18  com.digidesign.framework.DFW  	0x007848c4 TApplication::Run() + 60
19  ...gidesign.framework.ProTools	0x027d4530 LaunchProTools + 1752
20  com.digidesign.ProToolsHD     	0x00009c5c 0x1000 + 35932
21  com.digidesign.ProToolsHD     	0x00003618 0x1000 + 9752
22  com.digidesign.ProToolsHD     	0x0000331c 0x1000 + 8988

A session will just suddenly get into "don't take me out of input or I'll crash" mode, and the only solution is to back up to an earlier version. After the crash, those sessions will not open--they'll just crash with same output above every time. And it's always an audio track fed by a stereo bus, by the way.

Anyone else experiencing this? Digi, I have before and after sessions if you're interested in looking at this.

Jason

[crizdee]

Hi,

Most probably session corruption! these things happen from time to time.

try creating a new session and use import session data to create a new session and see if that fixes it.

or try the troubleshooting thread...

http://duc.digidesign.com/showthread.php?t=240754

and this app for saving and trashing the prefs....

http://duc.digidesign.com/showthread.php?t=190122

[jstaczek]

Thanks for the tips.

I hope this hasn't become standard operating procedure for PT8. Never experienced crashing/corruption issues of this magnitude and frequency with versions 6.x-7.x running a commercial studio 14 hours/day. PT8 seems fragile, to say the least...

Jason

[jstaczek]

...in fact, it just infected another session. Took a track out of input and BOOM! Bye, bye Pro Tools....

Jason

[crizdee]

Originally Posted by jstaczek

...in fact, it just infected another session. Took a track out of input and BOOM! Bye, bye Pro Tools....

Jason

In which case it could be a pro tools file corrupted! you will have to uninstall pro tools (the uninstaller is in the digidesign folder in applications! use the "safe" option first and see if that fixes it) trash all the prefs. re-boot the mac, then re-install PT, first PT8 which is a complete install then cs3. this won't effect any third party plugins or auths it will only replace the fundamental pt files and shouldn't take longer than 20-30 minutes.

Chris

[DigiTechSupt]

We're going to need a bit more info to be able to help you troubleshoot - the Help Us Help You thread has details about what we need to know.

You may also want to visit the General Troubleshooting thread (below my signature), as it has many suggestions for optimizations that may fix your problem.

[jstaczek]

Turns out this is Instrument track related. Here are the steps to repro, 100%:

- Create a new session, BWAV, 24-bit, 48k
- Add a mono instrument track (default output 1-2)
- Insert Vacuum or Velvet on A
- Add a stereo audio track (default output 1-2)
- Change audio track input to stereo bus (mine's called Mix)
- Change Vacuum/Velvet output to Mix bus

NOTE: This does not crash if you insert Velvet/Vacuum on a stereo Aux instead of an Instrument track.

PT8cs3, Dual G5 2.5Ghz, 6.5G ram, OS 10.5.7, HD2 Core/Accel, 192 i/o with Analog card

Digi, please let me know if you can repro. At least I understand now why many of my sessions are crashing. I use Instrument tracks assigned to busses all the time. Not anymore...

Thanks,

Jason

[jstaczek]

An amendment.

It DOES still crash, even on an Aux. In my original test I didn't have a MIDI track routed to the input of the Velvet when it was on an Aux with bus as output. As soon as you do route a MIDI track to the input of Velvet, same crash.

So, it looks like it's not possible to route Velvet or Vacuum to a bus if that bus is also feeding the input of an audio track.

Jason

[jstaczek]

FYI, Avid support confirms that this is a bug. It occurs when bussing to stereo busses that don't have mono sub-paths defined. Adding the mono sub-paths in I/O setup as suggested fixed the problem for me. Avid support suggested always adding mono sub-paths to stereo busses and said that the bug would be fixed in an upcoming cs or point release.

Great experience with Avid support, by the way. They didn't make me reinstall OS X or Pro Tools...

Jason

[Evil Jack]

Same issue is occurring with mono busses (Stereo Inst track to mono bus):

http://duc.digidesign.com/showthread.php?t=249470