Crashes, MOTU audio system quits.

[cubehead]

I am getting more crashes than I ever did on my G4 dual 533. I am wondering if a ram upgrade would help. This is slightly frustrating because 1.5 gig of ram should be plenty. A typical session is 24-30 audio tracks, 8 MIDI tracks, 8-10 UAD plug-ins, 3-5 Autotune plug-ins, one mach 5 track, 2 Waves L2 plug-ins and a few DP plug-ins. A fair ammount of automation but nothing to intense. I run all my audio off of it's own internal 7200 drive which is brand new. If a ram upgrade is necessary is there a brand that is better than the others? Thanks, I would appreciate any suggestions.

[qo]

Hi cubehead,

Posting the crashlog would give us a better chance of figuring out what the problem is. Post that (or post multiple if they are all different), and we can go from there. If you don't know where the crashlog is, lemme know and I'll describe how to display it. You should only need to post the header and the crashed thread info, but post the whole thing if you're not sure.

regards,

qo

[cubehead]

How should I go about finding the past crashed messages. Should I just wait for it to happen again? Thanks for the help.

Chris

[qo]

Hi Chris,

1. Launch /Applications/Utilities/Console

2. You'll see an icon in Console's GUI (upper left) that's labeled "Logs." Click that.

3. In the left-hand pane, you'll see a number of items. You want the one that's labeled:

~/Library/Logs

4. Click its disclosure triangle to open its sub-items.

5. One of the sub-items will be CrashReporter, click its disclosure triangle to open it

6. You should see an item called "Digital Performer.crash.log" Click this to display the log in the right-hand pane.

7. The most recent crash will be at the bottom of this log (you'll probably see multiple crashes in this log since you haven't ever cleared it).

You can copy/paste this the same way as any other mac text stuff.

regards,

qo

[jimwunderlich]

I had a file crash...any idea what this means?:

**********

Host Name: G4.local
Date/Time: 2005-12-26 15:25:37 -0800
OS Version: 10.3.9 (Build 7W98)
Report Version: 2

Command: Digital Performer
Path: /Applications/MOTU DP4.6 Folder/Digital Performer 4.61/Contents/MacOS/Digital Performer
Version: 4.61 (4.61)
PID: 613
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000016

Thread 0 Crashed:
0 AllUtilitiesLib.dylib 0x11004510 DP000000000000f + 0x14
1 <<00000000>> 0x00000589 0 + 0x589
2 PerfEngine.dylib 0x12e6fc6c DP00000000000000000000000000112 + 0x24
3 com.motu.DigitalPerformer 0x002e7a5c 0x1000 + 0x2e6a5c
4 com.motu.DigitalPerformer 0x002ea454 0x1000 + 0x2e9454
5 com.motu.DigitalPerformer 0x0062f454 0x1000 + 0x62e454
6 com.motu.DigitalPerformer 0x0062d018 0x1000 + 0x62c018
7 com.motu.DigitalPerformer 0x00639e0c 0x1000 + 0x638e0c
8 com.motu.DigitalPerformer 0x00639b58 0x1000 + 0x638b58
9 com.motu.DigitalPerformer 0x0063d078 0x1000 + 0x63c078
10 com.motu.DigitalPerformer 0x0063f8e8 0x1000 + 0x63e8e8
11 com.motu.DigitalPerformer 0x0064a1c4 0x1000 + 0x6491c4
12 com.motu.DigitalPerformer 0x006464fc 0x1000 + 0x6454fc
13 com.motu.DigitalPerformer 0x00022b44 0x1000 + 0x21b44
14 com.motu.DigitalPerformer 0x00022ce0 0x1000 + 0x21ce0
15 com.motu.DigitalPerformer 0x00022e04 0x1000 + 0x21e04
16 com.motu.DigitalPerformer 0x00268dfc 0x1000 + 0x267dfc
17 com.motu.DigitalPerformer 0x00269080 0x1000 + 0x268080
18 com.motu.DigitalPerformer 0x00268098 0x1000 + 0x267098
19 com.motu.DigitalPerformer 0x0010dbb8 0x1000 + 0x10cbb8
20 com.motu.DigitalPerformer 0x0010c3d0 0x1000 + 0x10b3d0
21 com.motu.DigitalPerformer 0x0010c6c8 0x1000 + 0x10b6c8
22 com.motu.DigitalPerformer 0x004289e8 0x1000 + 0x4279e8
23 com.motu.DigitalPerformer 0x00428584 0x1000 + 0x427584
24 com.motu.DigitalPerformer 0x00623054 0x1000 + 0x622054
25 com.motu.DigitalPerformer 0x00009460 0x1000 + 0x8460
26 com.motu.DigitalPerformer 0x00009a68 0x1000 + 0x8a68
27 com.motu.DigitalPerformer 0x00005400 0x1000 + 0x4400
28 com.motu.DigitalPerformer 0x00004db4 0x1000 + 0x3db4
29 com.motu.DigitalPerformer 0x00004be4 0x1000 + 0x3be4

Thread 1:
0 libSystem.B.dylib 0x90012808 clock_sleep_trap + 0x8
1 libSystem.B.dylib 0x9000d9f8 nanosleep + 0x78
2 libSystem.B.dylib 0x90012528 usleep + 0x48
3 MSL_Perf.dylib 0x137254f4 DP000000000000000000000000000000000000000186 + 0x6c
4 MSL_Perf.dylib 0x13725928 DP000000000000000000000018f + 0x20
5 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 2:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 PerfFoundation.dylib 0x11f52da0 DP00000000000000000000002d5 + 0x78
3 PerfFoundation.dylib 0x11f52d14 DP0000000000000000000000000000000374 + 0x14
4 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 3:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 com.apple.audio.MIDI.CoreMIDI 0x81ebdc9c _ZN15XServerMachPort14ReceiveMessageERiPvS0_ + 0x54
3 com.apple.audio.MIDI.CoreMIDI 0x81eb0d58 _ZN16MIDIInPortThread3RunEv + 0x13c
4 com.apple.audio.MIDI.CoreMIDI 0x81eb4e50 _ZN7XThread9RunHelperEPv + 0x3c
5 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 4:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 com.apple.CoreFoundation 0x901c15e8 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x901c5d74 CFRunLoopRunSpecific + 0x148
4 com.apple.audio.CoreAudio 0x96c034b8 _ZN10HALRunLoop9OwnThreadEPv + 0x104
5 com.apple.audio.CoreAudio 0x96c032ec _ZN9CAPThread5EntryEPS_ + 0x30
6 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 5:
0 libSystem.B.dylib 0x900078b8 mach_msg_trap + 0x8
1 libSystem.B.dylib 0x90007438 mach_msg + 0x38
2 MotuAudioSystem 0x1198b01c DP00000000000000000000004a + 0x80
3 MotuAudioSystem 0x1198af84 DP000000000000000000000000000000081 + 0x2c
4 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 6:
0 libSystem.B.dylib 0x900147e8 semaphore_wait_trap + 0x8
1 MotuAudioSystem 0x11984dd4 DP000000000000000000003f + 0x14
2 MotuAudioSystem 0x1197cf24 DP00000000000000000000000000000000000000072 + 0x180
3 MotuAudioSystem 0x1197ebac DP00000000000000000000000000060 + 0x164
4 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 7:
0 libSystem.B.dylib 0x90018e78 semaphore_timedwait_signal_trap + 0x8
1 libSystem.B.dylib 0x9000ea14 _pthread_cond_wait + 0x268
2 com.apple.audio.CoreAudio 0x96c05ef8 _ZN7CAGuard7WaitForEy + 0xdc
3 com.apple.audio.CoreAudio 0x96c05df8 _ZN7CAGuard9WaitUntilEy + 0x130
4 com.apple.audio.CoreAudio 0x96c20cec _ZN10HPIOThread8WorkLoopEv + 0x358
5 com.apple.audio.CoreAudio 0x96c21894 _ZN10HPIOThread11ThreadEntryEPS_ + 0x1c
6 com.apple.audio.CoreAudio 0x96c032ec _ZN9CAPThread5EntryEPS_ + 0x30
7 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

Thread 8:
0 PerfEngine.dylib 0x13059b1c DP00000000000000019a + 0x8
1 PerfEngine.dylib 0x13059ff8 DP000000000000000000000000000351 + 0x15c
2 libSystem.B.dylib 0x90024990 _pthread_body + 0x28

PPC Thread State:
srr0: 0x11004510 srr1: 0x0200f030 vrsave: 0x00000000
cr: 0x24000222 xer: 0x00000004 lr: 0x12e6fc6c ctr: 0x110044fc
r0: 0x12e6fc6c r1: 0xbfffd8b0 r2: 0x00000000 r3: 0xbfffd9a0
r4: 0x00000016 r5: 0x00000010 r6: 0x02d56008 r7: 0x00000001
r8: 0x0000001f r9: 0xa00016b4 r10: 0x00001cb8 r11: 0x1322545c
r12: 0x110044fc r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000589 r19: 0x00000001
r20: 0x132294a8 r21: 0x00000000 r22: 0x02ce496c r23: 0x00000001
r24: 0x00000001 r25: 0x00000001 r26: 0x0c5f14bc r27: 0x0c569dba
r28: 0x00000001 r29: 0x0c5f14bc r30: 0x02ce4dec r31: 0x00000016

[Shooshie]

I had a file crash...any idea what this means?:

**********

Host Name: G4.local
Date/Time: 2005-12-26 15:25:37 -0800
OS Version: 10.3.9 (Build 7W98)
Report Version: 2

Command: Digital Performer
Path: /Applications/MOTU DP4.6 Folder/Digital Performer 4.61/Contents/MacOS/Digital Performer
Version: 4.61 (4.61)

I think that's your problem right there. DP 4.61 is not compatible with 10.3.9, if I recall correctly. Try upgrading to Tiger.

Or is it the other way around? Tiger not compatible with DP 4.5? I forget now. Either way, you had a genuine crash, and were just sh*t out of luck!

Shooshie

[mastermix]

Shooshie..

DP 4.61 is compatible with Panther -- as far back as OS X 10.3.7.

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000016

This almost always mean the application (data) is trying to
write to the read-only part of memory -- or some piece of
pernicious code that is rubbing some hardware or driver
the wrong way.

At the geek level, you will need a low level debugger like the
GNU debugger (GDB) for OS X to trace these type of errors
accurately. Plus you may need the actual DP object code to
do this. Near impossible since only MOTU developers have
access to this stuff (insert evil smile here

At a higher level:

1. Check all your plugins more carefully and make sure they
all pass the mustard. Refrain from running shady plugs and
demos with precarious origins and timeout bombs.

2. Use Apple-certified RAM. Bad or inadequate RAM
can also cause these type of crash errors.

3. Make sure you are running the latest or most compatible
drivers for all your software including DP and associated
hardware.

4. Give the upgrade to Tiger (OS X 10.4.X) some thought
as it fixes many OS X bugs found in Panther.

Kris..

[qo]

One thing to check. If you have multiple of these crashlogs, look at each of them where you see something like:

Thread 0 Crashed:


It could be any Thread number. What you want to see is if the tracebacks are the same. If so, then this points (though not 100% reliably) to a real software issue. So, you want to look at the others and see if they look like:

Code: Select all

Thread 0 Crashed: 
0 AllUtilitiesLib.dylib 0x11004510 DP000000000000f + 0x14 
1 <<00000000>> 0x00000589 0 + 0x589 
2 PerfEngine.dylib 0x12e6fc6c DP00000000000000000000000000112 + 0x24 
3 com.motu.DigitalPerformer 0x002e7a5c 0x1000 + 0x2e6a5c 
4 com.motu.DigitalPerformer 0x002ea454 0x1000 + 0x2e9454 

In the above, the functions are listed in reverse execution order. That is, AllUtilitiesLib.dylib, was the last thing to execute before the crash.

If each of the crashes are different, then that points to either bad RAM, incompatible drivers, etc, as others have already pointed out. mastermix is correct that you'd need gdb as well as DP's object files, and a core dump (and an understanding of DP's code) in order to make sense of this. But, DP is definitely implicated here (assuming you have several crashlogs that look the same).

Good suggestions have already been offered (remove plugins, trash prefs, trash the AU info cache) and I don't have anything beyond that to suggest.

[qo]

Are you using Plogue Bidule AU plugin by chance?

[jimwunderlich]

This was a simple MIDI sequencing file using:

- rack gear (from my sig)

- (1) instance of Absynth 3

- (1) stereo audio track for mixdown

A very simple file (no true plugins), yet with valuable work on it. It is the only file in my entire project library that will NOT open now...something odd happened when i was working on it (DP crash) and it hasn't opened since...^%$@#^

[jimwunderlich]

and oddly enough, this is the first time it has ever happened on my G4...a file rendered useless...an anomaly?

... and it happens on the same day my brand new dual core G5 shows up...almost like a higher power is telling me ::migrate files quickly::

[qo]

... and it happens on the same day my brand new dual core G5 shows up...almost like a higher power is telling me ::migrate files quickly::

If you haven't already, you might try using the Load command to see if you can salvage elements from the bad file into a new project. Losing work truly sucks

[jimwunderlich]

I've never used Load before (learned something new, duh)...all that happens is a new empty sequence or chunk is created.

i did create a "workaround" where i took an audio file that i had exported from my last work on the file, then sync'd it up in a new sequence and it blends fairly well. it does suck, however, that the actual MIDI data is gone...i'm just hoping that i won't have to make any alterations. thanks for all of your help & ideas. Happy New Year & Cheers!