Strange Crash when in Record on PT8, anyone?

[Stompinmsc]

So for months I have been having Protools crashes only when I am recording. Usually 1 track being recorded (Dialogue sessions). When I am mixing or doing sound design (no recording) my rig is literally 100% stable and never crashes. I go weeks with no crashes. The morning I start a dialogue session the computer averages a crash every hour. So weird. And it is not just while in record but if the track is armed and Protools is just sitting there waiting to go into record, the PT might randomly crash. Yesterday had 3 crashes in 2 hours of a VO record, then was mixing the entire day after that with ZERO crashes.

Anyone have any idea what is going on? Thanks guys!

Rob

[formfunction]

Originally Posted by Stompinmsc

So for months I have been having Protools crashes only when I am recording. Usually 1 track being recorded (Dialogue sessions). When I am mixing or doing sound design (no recording) my rig is literally 100% stable and never crashes. I go weeks with no crashes. The morning I start a dialogue session the computer averages a crash every hour. So weird. And it is not just while in record but if the track is armed and Protools is just sitting there waiting to go into record, the PT might randomly crash. Yesterday had 3 crashes in 2 hours of a VO record, then was mixing the entire day after that with ZERO crashes.

Anyone have any idea what is going on? Thanks guys!

Rob

Tell us what troubleshooting you have already done,,, would save some time for everyone. ff

[Stompinmsc]

Aside from the usual trash prefs and painstakingly upgrading the 1000's of plugins to latest versions, that is about it. Something weird is definitely going on. For the most part when I am not recording, my system is pretty much flawless. I am running HD6 pci on a magma, mac 2.26 8 core, 24GB RAM with 10.6.4 latest cs version of 8.1 but this issue has always been there through every version of PT8. It's like something doesn 't like being accessed when in record mode. I was hoping someone might be familiar with what is going on.

[Stompinmsc]

Hmm, ok so looking through my crash log I came across this.

Thread 53 crashed with X86 Thread State (32-bit):
eax: 0x0000003c ebx: 0x971ee0d9 ecx: 0xb193e44c edx: 0x971ee28e
edi: 0x00000080 esi: 0xb193e4a8 ebp: 0xb193e488 esp: 0xb193e44c
ss: 0x0000001f efl: 0x00000247 eip: 0x971ee28e cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x2bf0a000


Then I looked at Thread 53:

Thread 53 Crashed:
0 libSystem.B.dylib 0x971ee28e __semwait_signal_nocancel + 10
1 libSystem.B.dylib 0x971ee172 nanosleep$NOCANCEL$UNIX2003 + 166
2 libSystem.B.dylib 0x9726903a usleep$NOCANCEL$UNIX2003 + 61
3 libSystem.B.dylib 0x9728a6f0 abort + 105
4 libstdc++.6.dylib 0x9004efda __gnu_cxx::__verbose_terminate_handler() + 433
5 libstdc++.6.dylib 0x9004d17a __cxxabiv1::__terminate(void (*)()) + 10
6 libstdc++.6.dylib 0x9004d1ba __cxxabiv1::__unexpected(void (*)()) + 0
7 libstdc++.6.dylib 0x9004d24b __cxa_throw + 0
8 ...esAudio.WaveShell-DAE.7.1.1 0x28c8f0f8 CGenericWavesDSP::ReadExec(long, long, long, long, long*) + 864
9 ...esAudio.WaveShell-DAE.7.1.1 0x28c93d09 Execute(BUFFER_HEADER*) + 187
10 ...esAudio.WaveShell-DAE.7.1.1 0x28c934ce TDMExecutionCallBack(long, long, void*, void*, void*) + 344
11 com.WavesAudio.Dorrough.7.1.0 0x3539bbf1 cDorroughMeter_ALGT<1l>::ReadTicksCycArray(TickPac kedT<unsigned long>*) + 147
12 com.WavesAudio.Dorrough.7.1.0 0x353a0a89 cDorroughMeter_ALGT<1l>:orroughReadAndUpdateLEDs 3(unsigned long) + 115
13 com.WavesAudio.Dorrough.7.1.0 0x353a0dd2 cDorroughMeter_ALGT<1l>::UpdateDisplaySelf(unsigne d long) + 72
14 com.WavesAudio.WavesLib.7.1.1 0x3506bdf2 cALGORITHM::UpdateDisplay(unsigned long) + 56
15 com.WavesAudio.WavesLib.7.1.1 0x3506d462 cALGORITHM:oIdle(short) + 92
16 com.WavesAudio.Dorrough.7.1.0 0x353a2a19 WP_DoIdle + 145
17 ...esAudio.WaveShell-DAE.7.1.1 0x28d25211 WCPluginGraphic::_DoGraphicIdle() + 121
18 ...esAudio.WaveShell-DAE.7.1.1 0x28d256f1 WCPluginGraphicWithThread::WCIdleCommand::execute( ) + 193
19 ...esAudio.WaveShell-DAE.7.1.1 0x28d6386e WCGraphicThread::Execute() + 122
20 ...esAudio.WaveShell-DAE.7.1.1 0x28d638c8 WCGraphicThread::threadMain(void*) + 62
21 libSystem.B.dylib 0x971ae81d _pthread_start + 345
22 libSystem.B.dylib 0x971ae6a2 thread_start + 34

Perhaps having/viewing the Waves Dorrough TDM meter active on the record channel is the issue? Strangely enough it did cross my mind yesterday. The next session I will disable the plugin while in record mode. I'll give that a shot.

Rob

[diamondschwin]

Potentially, I always have issues with Waves Dorrough not correctly following the display preference you have set in the plug in, so it seems to be bugged to a certain degree.

[formfunction]

Originally Posted by Stompinmsc

Perhaps having/viewing the Waves Dorrough TDM meter active on the record channel is the issue? Strangely enough it did cross my mind yesterday. The next session I will disable the plugin while in record mode. I'll give that a shot.

Rob

If that does not work, make sure that you REMOVEE the WAVESHELL from the plugins folder taking all your waves plugs out of the equation unfortunately. ff