PT 9 Crashes All The Time When Working with VI's

[edadema]

Process: Pro Tools [201]
Path: /Applications/Digidesign/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 9.0 (9.0f121)
Code Type: X86 (Native)
Parent Process: launchd [141]

Date/Time: 2010-12-02 03:00:18.437 -0800
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000a352002f
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.digidesign.framework.DAE 0x03ecadd5 FicSetInputDelaySamples + 10
1 ...gidesign.framework.ProTools 0x00f68190 MFortressHWBPEntryPoint_exit_mfort6317_ + 6215459
2 ...gidesign.framework.ProTools 0x00f5d679 MFortressHWBPEntryPoint_exit_mfort6317_ + 6171660
3 ...gidesign.framework.ProTools 0x00f5e545 MFortressHWBPEntryPoint_exit_mfort6317_ + 6175448
4 ...gidesign.framework.ProTools 0x013d8419 MFortressHWBPEntryPoint_exit_mfort6317_ + 10869164
5 ...gidesign.framework.ProTools 0x013d89a7 MFortressHWBPEntryPoint_exit_mfort6317_ + 10870586
6 ...gidesign.framework.ProTools 0x015f24b5 MFortressHWBPEntryPoint_exit_mfort6317_ + 13072968
7 ...gidesign.framework.ProTools 0x00e6c784 MFortressHWBPEntryPoint_exit_mfort6317_ + 5184791
8 ...gidesign.framework.ProTools 0x00e90335 MFortressHWBPEntryPoint_exit_mfort6317_ + 5331144
9 ...gidesign.framework.ProTools 0x00ed7a68 MFortressHWBPEntryPoint_exit_mfort6317_ + 5623803
10 ...gidesign.framework.ProTools 0x01c326b8 MFortressHWBPEntryPoint_exit_mfort6317_ + 19627083
11 ...gidesign.framework.ProTools 0x01967d59 MFortressHWBPEntryPoint_exit_mfort6317_ + 16700140

[edadema]

Process: Pro Tools [185]
Path: /Applications/Digidesign/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 9.0 (9.0f121)
Code Type: X86 (Native)
Parent Process: launchd [139]

Date/Time: 2010-12-02 16:05:21.522 -0800
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000003b98
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0x00670073 g_dwILiLokTokens + 315395
1 Massive.dpm 0x4a74409c NI::GP:eviceNotificationHelper:nVolumeChanged( NI::GP:eviceNotificationListener::eState, short const&) + 220
2 Massive.dpm 0x4a7309db NI::GP:eviceNotification:nVolumeChanged(NI::GP :eviceNotificationListener::eState, short const&) + 139
3 Massive.dpm 0x4a730b1e NI::GP:eviceNotification::eventHandlerProc(Opaqu eEventHandlerCallRef*, OpaqueEventRef*, void*) + 158
4 com.apple.HIToolbox 0x91829f2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
5 com.apple.HIToolbox 0x918291f6 SendEventToEventTargetInternal(OpaqueEventRef*,

[edadema]

Process: Pro Tools [381]
Path: /Applications/Digidesign/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 9.0 (9.0f121)
Code Type: X86 (Native)
Parent Process: launchd [136]

Date/Time: 2010-12-02 19:57:00.925 -0800
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000009
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 Reaktor5.dpm 0xd0a0f8c3 NI::GP::VolumeManager:nVolumeChange(NI::GP::eVol umeChange, NI::GP::VolumeInfo const&) + 1011
1 Reaktor5.dpm 0xd0a0fd16 NI::GP:eviceNotificationHelper:nVolumeChanged( NI::GP:eviceNotificationListener::eState, short const&) + 214
2 Reaktor5.dpm 0xd09ef54b NI::GP:eviceNotification:nVolumeChanged(NI::GP :eviceNotificationListener::eState, short const&) + 139
3 Reaktor5.dpm 0xd0a2b02e NI::GP:eviceNotification::eventHandlerProc(Opaqu eEventHandlerCallRef*, OpaqueEventRef*, void*) + 158
4 com.apple.HIToolbox 0x91829f2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
5 com.apple.HIToolbox 0x918291f6 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
6 com.apple.HIToolbox 0x91896441 CallNextEventHandler + 95
7 Kontakt 4.Synth.vst 0x61d78350 NI::GP:eviceNotification::eventHandlerProc

[edadema]

You can look at the time and Date stamp. There is more but I don't want to make this 20 pages. It is the same session but it seems like it is all the NI plugs. Do they share the same engine or something.
They work flawless in Logic. Why can't they work in pro tools? They never have. It must be Pro Tools not sharing there code.

Pro Tools is the industry standard right? but when you go to the NAMM Show all the Plug In Companies show there products on Logic or Abelton. Is that just a coincidence or can NOBODY there VI's to work in Pro Tools!!!!!!

This last post is because of a low memory warning this time it didn't crash. Just a restart. I can't believe 8 VI's will bring PT 9 down

[brianjanthony]

dont know if this was covered... not a ton of time here but maybe it will help. make sure the NI stuff (esp Kontakt4 or 3.5) is NOT NOT NOT NOT running in multiple processor mode (there's a checkbox in the K prefs for enabling multiprocessor mode. And in Kontakt, enable the memory server. I hammer a ton of large samples into it and it causes no probs. And most of the time its drums and such, so they are playing the whole song. But make sure that multi processor is turned off and memory server is on. that would be a start. if you've done that, then hmmmmm. don't know. i use K4, B4, and Komplete stuff ok in 9. The only thing I know will crash it is if I am playing a VI heavy song and try to load a large sample while transport is running... that becomes a prob sometimes. hope this helps....

[edadema]

Thanks I will uncheck that. I very rarely use kontakt 4 but I did the other day
Thanks for the tip
Ed

[edadema]

Another Crash I am done for the night. Avid charges us more than ever and it works worse than ever here is one more crash report

Process: Pro Tools [181]
Path: /Applications/Digidesign/Pro Tools/Pro Tools.app/Contents/MacOS/Pro Tools
Identifier: com.digidesign.ProTools
Version: 9.0 (9.0f121)
Code Type: X86 (Native)
Parent Process: launchd [140]

Date/Time: 2010-12-03 21:08:43.608 -0800
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Interval Since Last Report: 66124 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 43312 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: E1DFA3AD-FB32-4778-8690-DF84AF86FA3F

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x00000000000045fc
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0xdac31f5d 0 + 3670220637

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x93eab982 kevent + 10
1 libSystem.B.dylib 0x93eac09c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x93eab559 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x93eab2fe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x93eaad81 _pthread_wqthread + 390
5 libSystem.B.dylib 0x93eaabc6 start_wqthread + 30

[edadema]

Let me get this straight. If the problem are the Third Party Plug ins then why doesn't Pro Tools Have a plug in verifier like Logic.
When you install a new Plug in and when you launch Logic it will test the Plugin and either Pass Or Fail it. If it Fails then we don't use it, and the Company that made it will not be able play the blame game

Not a new concept. Then We know for sure no guessing! Why doesn't Pro Tools have that?????

[Phil Buckle]

Originally Posted by edadema

Let me get this straight. If the problem are the Third Party Plug ins then why doesn't Pro Tools Have a plug in verifier like Logic.
When you install a new Plug in and when you launch Logic it will test the Plugin and either Pass Or Fail it. If it Fails then we don't use it, and the Company that made it will not be able play the blame game

Not a new concept. Then We know for sure no guessing! Why doesn't Pro Tools have that?????

The problem is NOT 3rd party plugs.
The problem is 3rd party plugs in PTools.
They sure as hell work fine in other DAWS and plenty of pros use those plugs in other DAWS day in, day out.
The problem is RTAS and Avids refusal ...........apart from lip service.......to do anything about it.

Let's wait a few more years and see if they get it together...........make it 3 years.........no 4 would be better. Ok then, let's all come back in four years and everything should be fine.
In the meantime just.........do something else

[Dism]

Just for kicks... have you tried reverting back to a qualified version of OSX?

I don't use any NI plugs personally... so I can't say I have the same problems, and cannot comment on their stability... but I have heard issues from other users.

Play 2.0.25 has been nothing but stable for me in PT9. Moreso than in 8. Since I installed PT9, I've been loading pretty well purely VI sessions just to see how hard I can push it. While I do run out of CPU, I definitely have not crashed yet.

Sorry to hear about your troubles...hopefully Avid or NI, or anyone can provide a solution/explanation.