who runs dp5.1 crash free on intel?????

cchord59 · Post by **cchord59** » Fri Oct 13, 2006 1:18 pm

With all this discussion of dp 5.1 crashing, I think we should take a poll of how many users out there are running an intel mac with dp5.1 and having no crashing problems.

I'll start.

Running dp 5.1 mac pro, 828 fw interface. no 3rd party pluggins. no other programs running with dp. Tracking to a maxtor 7200 rpm fw HD.

My life has been hell the last month, dp crashes on average about 10 times a day. today it was 15 times in 4 hours. fukking rediculous.

I want to see if the crashing is a result of something I am doing, or the computer is doing that can be fixed. I am starting to think that I just need to wait for dp to come up with an update. I've tried everything short of foamating my hd and starting from scratch.
I am weary of doing that because the computer is only 1 month old, and its been doing it from day one.

stovall · Post by **stovall** » Fri Oct 13, 2006 5:33 pm

I run 5.1 on a Mac Mini 1.66 GHz 1 GB, M-Audio Firewire Solo. I have only had a problem with my Waves Native Power Pack which was solved by getting a new authorization from Waves. I honestly don't know how to help

motuhelper · Post by **motuhelper** » Fri Oct 13, 2006 6:33 pm

What do the crashlogs say? Post the most recent so we can see why your system is crashing.

Tomas E · Post by **Tomas E** » Sat Oct 14, 2006 4:23 am

There should be a sticky about Intelmacs and DP 5.

Salvator · Post by **Salvator** » Sat Oct 14, 2006 5:48 am

For me on a brand new intel imac, no other software installed but DP it crash even while idle ...

I'd say just wait for the update !

Salvator

Phil O · Post by **Phil O** » Sat Oct 14, 2006 6:10 am

I'm on a Mac Pro 2.66GHz w/2Gig RAM. MIDI seems to be a little buggy. I have had an occasional unexpected quit when I have a Waves plugin window open.

Other than that everything seems ok. All crashes seem to be connected to Waves.

Phil

cchord59 · Post by **cchord59** » Sat Oct 14, 2006 10:04 am

motuhelper wrote:What do the crashlogs say? Post the most recent so we can see why your system is crashing.

0x95a40000 - 0x95a56fff libJapaneseConverter.dylib /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
0x95a58000 - 0x95a79fff libKoreanConverter.dylib /System/Library/CoreServices/Encodings/libKoreanConverter.dylib
0x95a86000 - 0x95a94fff libSimplifiedChineseConverter.dylib /System/Library/CoreServices/Encodings/libSimplifiedChineseConverter.dylib
0x95a9c000 - 0x95aaefff libTraditionalChineseConverter.dylib /System/Library/CoreServices/Encodings/libTraditionalChineseConverter.dylib
0x96052000 - 0x96088fff com.apple.audio.MIDI.CoreMIDI 1.5.1 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x96451000 - 0x96451fff com.apple.vecLib 3.3.1 (vecLib 3.3.1) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x96ab7000 - 0x96abcfff com.apple.agl 2.5.9 (AGL-2.5.9) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x97dac000 - 0x98896fff com.apple.QuickTimeComponents.component 7.1.3 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents
0x98aa5000 - 0x98aa7fff com.apple.QuickTimeH264.component 7.1.3 /System/Library/QuickTime/QuickTimeH264.component/Contents/MacOS/QuickTimeH264
0x98aa9000 - 0x98c51fff QuickTimeH264.scalar /System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar
0x98cc1000 - 0x98d7efff com.apple.QuickTimeMPEG4.component 7.1.3 /System/Library/QuickTime/QuickTimeMPEG4.component/Contents/MacOS/QuickTimeMPEG4

the crash log is so huge, I didn't know what part of it to post. this is the bottom bit of it.

i found it under digitalperformer.crash.log

Grigri · Post by **Grigri** » Sat Oct 14, 2006 10:11 am

Macbook dual 1,83 with 2 gig of RAM & DP5.1 here and no crash.
I had to remove all the plugins non-UB and it works fine.

Grigri

cchord59 · Post by **cchord59** » Sat Oct 14, 2006 10:20 am

So I trashed the dp crash logs temorarily, and let it crash again and I got this:

Host Name: ryan-worsleys-computer-2
Date/Time: 2006-10-14 10:09:03.095 -0700
OS Version: 10.4.8 (Build 8L2127)
Report Version: 4

Command: Digital Performer
Path: /Applications/MOTU DP5 Folder/Digital Performer 5.1.app/Contents/MacOS/Digital Performer
Parent: WindowServer [64]

Version: 5.1 (5.1)

PID: 2040
Thread: Unknown

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

Backtrace not available

Unknown thread crashed with X86 Thread State (32-bit):
eax: 0x1dcb6010 ebx: 0x01e8afa7 ecx: 0x03fbb8f0 edx: 0x03fbb8f0
edi: 0x03fbb8f0 esi: 0x03fbb8f0 ebp: 0xb0507f08 esp: 0xb0507d50
ss: 0x0000001f efl: 0x00010206 eip: 0x01e8b831 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:

can someone tell me what this means?

Timeline · Post by **Timeline** » Sat Oct 14, 2006 12:08 pm

Looks like a ram or mother board error.

Send it to apple.

Mr_Clifford · Post by **Mr_Clifford** » Sat Oct 14, 2006 6:58 pm

DP 5.1 is working fine on my MacBook Pro (dualcore 2Ghz). Although I haven't pushed it real hard as my main rig is on my desktop G4. Also I use it with absolutely no extra hardware (built-in audio & network MIDI only - hardly a 'professional' setup) and the only 3rd party software on it is BFD.

I still haven't been able to get all the VI's to come up though (all I get is polysynth) - although I've saved Master Frodo's suggestions and haven't tried them yet. I understand this is because DP still thinks my VI's are non-UB and doesn't load them.

bjornln · Post by **bjornln** » Fri Oct 20, 2006 7:38 am

cchord59 wrote:
motuhelper wrote:What do the crashlogs say? Post the most recent so we can see why your system is crashing.
0x95a40000 - 0x95a56fff libJapaneseConverter.dylib /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
0x95a58000 - 0x95a79fff libKoreanConverter.dylib /System/Library/CoreServices/Encodings/libKoreanConverter.dylib
0x95a86000 - 0x95a94fff libSimplifiedChineseConverter.dylib /System/Library/CoreServices/Encodings/libSimplifiedChineseConverter.dylib
0x95a9c000 - 0x95aaefff libTraditionalChineseConverter.dylib /System/Library/CoreServices/Encodings/libTraditionalChineseConverter.dylib
0x96052000 - 0x96088fff com.apple.audio.MIDI.CoreMIDI 1.5.1 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x96451000 - 0x96451fff com.apple.vecLib 3.3.1 (vecLib 3.3.1) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x96ab7000 - 0x96abcfff com.apple.agl 2.5.9 (AGL-2.5.9) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x97dac000 - 0x98896fff com.apple.QuickTimeComponents.component 7.1.3 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents
0x98aa5000 - 0x98aa7fff com.apple.QuickTimeH264.component 7.1.3 /System/Library/QuickTime/QuickTimeH264.component/Contents/MacOS/QuickTimeH264
0x98aa9000 - 0x98c51fff QuickTimeH264.scalar /System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar
0x98cc1000 - 0x98d7efff com.apple.QuickTimeMPEG4.component 7.1.3 /System/Library/QuickTime/QuickTimeMPEG4.component/Contents/MacOS/QuickTimeMPEG4

the crash log is so huge, I didn't know what part of it to post. this is the bottom bit of it.

i found it under digitalperformer.crash.log

Try to activate ALL fonts. Just by reading the first few lines of the crash log, I got a vague memory about this happening when people have "Optimzed" their system by de-activating all non-english stuff..... If you have removed them. Do a clean install.....

/B

spainspivak · Post by **spainspivak** » Sat Oct 21, 2006 12:29 am

I think I only crashed about 20 times today. 17 were when I had stopped the playback.

XYZ · Post by **XYZ** » Sat Oct 21, 2006 8:05 am

No problems for me, but I have a fairly simple system. DP, UAD1e, Waves [AU], Ozone/Trash.

Aramis · Post by **Aramis** » Sat Oct 21, 2006 8:26 am

Hello all !
I cannot keep silent here .....May I suggest that you put more precise informations about what is your hardware setup and software setup for everyone to understand what is going on ....
It could be a lot more usefull ....and constructive ....
Aramis