5.11 crashing on startup - * RESOLVED *

deepcgi · Post by **deepcgi** » Fri Nov 24, 2006 4:30 pm

5.11 gives me an "application Digital Performer quit unexpectedly. I've got the most recent versions of Altiverb 5, Atmosphere, Ivory, BFD, and Amplitube 2. They all worked fine in 5.1. Any ideas?

mctmct · Post by **mctmct** » Fri Nov 24, 2006 4:34 pm

I get the same thing. Tried fixing disc permissions and it still crashes. Worked before updating.... Running Mach5, Symphonic Inst, MX4 and Battery2

Frodo · Post by **Frodo** » Fri Nov 24, 2006 5:06 pm

Folks--

CPU's? RAM? OSX version? More info would help.

Clearly it's working well on a lot of machines, judging from users' posts.

Both of you have a variety of non-MOTU plugins. First start by trashing your DP Preferences. Check for improvements. If the problem stops, read no further.

For as painful as it may sound, uninstall all of your third-party plugins, trash your Audio Unit Info Cache to see if you can get DP to load without crashing. Then, re-install one third-party plugin at a time to find the culprit.

Don't forget to go the extra mile with DiskWarrior, TechTools, or similar. Files do get damaged. Directory forks get bent. Levels of disc and file repair may be required which exceed the capabilities of what repairing permissions does.

One thing that really helps keep directory forks in line is to keep your desktop clean. Why this is the case, I can't tell-- but I've taken the advice from someone who is wiser than I and have reduced instances of directory problems by about 70%.

Also, OSX is an odd cookie at times. The UNIX code under the hood can be quite stubborn. Despite claims that the user no longer has to restart the computer after every install, there are many instances where shutting down the computer entirely for a few minutes is the only way to dump stubborn UNIX references to older versions of apps which have been updated. That is-- Shut Down and Reboot the computer as opposed to doing a mere Restart. Let the computer write new and clean references to app updates.

In that context, uninstall older versions of DP whose code and wayward files may be interfering with the latest version. Get rid of old aliases and create new ones if needed. Such dust bunnies and spider webs accumulate quickly on our systems, and while they *ought not* cause a problem, the best assurance is to eliminate them entirely.

Do you have any expired plugin demos taking up useless space? Get rid of them. DP is a little snobby about these things-- it may identify an expired demo as a glitch and self-destruct when it doesn't know how to reconcile a stream of third-party firewall securty code.

My point is, give DP and OSX the least baggage to sort. At least you will eliminate a hoard of possible causes for the unexpected quits. Chances are greater than not that you'll actually fix the problem with a bit of consciencious HD housekeeping. Worst case scenario is that you can send the list of issues and solutions attempted to MOTU and the third-party customer support so that they are aware that their software is bumping heads. They may pass the buck on the issue, they may also not recognize the issue as an attested one, but they could no longer declare ignorance once any problems or common solutions which have failed.

It's been said-- if you want to find the needle in the haystack, you gotta burn the haystack.

The fastest way to get to the bottom of it? Check your Crash Reports!! There will be threads in the report that will list the specific file which instigated the crash. Takes a lot of the guesswork out of it.

deepcgi · Post by **deepcgi** » Fri Nov 24, 2006 5:32 pm

G5 Quad. 4.5 Gig of Ram. 10.4.8. Fixed disk permissions. tossed preferences directory. Still won't start up

Frodo · Post by **Frodo** » Fri Nov 24, 2006 5:37 pm

deepcgi wrote:G5 Quad. 4.5 Gig of Ram. 10.4.8. Fixed disk permissions. tossed preferences directory. Still won't start up

The next step is to try uninstalling the plugins. If no startup, then uninstall and reinstall DP itself.

Did you find a Crash Report?

deepcgi · Post by **deepcgi** » Fri Nov 24, 2006 11:32 pm

FYI. I reinstalled 5.0 and it worked. Re-upgraded to 5.11 and it still doesn't startup. I guess plug-ins are next, but I doubt that is the problem, when the only plugin he mentioned that wasn't MOTU was Battery. It did kick out an error report, which I sent to MOTU.

Frodo · Post by **Frodo** » Fri Nov 24, 2006 11:42 pm

deepcgi wrote:FYI. I reinstalled 5.0 and it worked. Re-upgraded to 5.11 and it still doesn't startup. I guess plug-ins are next, but I doubt that is the problem, when the only plugin he mentioned that wasn't MOTU was Battery. It did kick out an error report, which I sent to MOTU.

Hmm. Good thing your contacted MOTU. This is a serious problem. Curious-- did you try to download a fresh copy of 5.11? Sometimes things can get corrupted during download.

The quandary here is the same that MOTU goes through all the time-- they can't always reproduce the problem, but perhaps they could provide a list of causes as to why DP wouldn't boot.

I'm really sorry that you have to go through this. It's so frustrating when you can't even get out of the gate. Do keep us posted on what you find. Such solutions help everyone-- and if nothing else, it's simply encouraging to hear that someone conquered a nagging issue.

Cheers, D.
Frodo

deepcgi · Post by **deepcgi** » Sat Nov 25, 2006 12:02 am

Question. Why does this update require a system restart. 5.01 from the original CD-ROM doesn't, and neither does the 5.1 update.

Obviously something heavy going on in this update.

deepcgi · Post by **deepcgi** » Sat Nov 25, 2006 12:47 am

another FYI...

Once the 5.11 update is installed, v5.1 will no longer startup, either. If I uninstall the 5.11 update, 5.1 works perfectly again. Still don't understand the reboot.

chrispick · Post by **chrispick** » Sat Nov 25, 2006 12:55 am

deepcgi wrote:another FYI...

Once the 5.11 update is installed, v5.1 will no longer startup, either. If I uninstall the 5.11 update, 5.1 works perfectly again. Still don't understand the reboot.

Maybe a permissions problem then?

Or your 5.11 download is screwed up.

Just a couple of guesses.

Frodo · Post by **Frodo** » Sat Nov 25, 2006 2:55 am

deepcgi wrote:another FYI...

Once the 5.11 update is installed, v5.1 will no longer startup, either. If I uninstall the 5.11 update, 5.1 works perfectly again. Still don't understand the reboot.

Something unusual is happening on your system. It's not a common problem that is being solved with the most common solutions. Why 5.1 will no longer startup unless 5.11 is uninstalled is a mystery.

Question is-- does 5.11 start up if you uninstall 5.1?

Try this-- if you have both 5.11 and 5.1, control click the app icon and choose Show Package Contents for each one.

You can highlight all the files in the package contents finder window and they will paste themselves here on the forum. Please include the file dates for each as well. I'll check for anomalies, if you want.

Some aspect of 5.1 is not being overwritten and is in conflict with 5.11. Now, that *is* a familiar issue with MOTU software upgrades. Installers have failed in the past.

I'd mentioned it earlier and Col. Chrispick did as well-- download a fresh copy of the 5.11 installer if you haven't already done so.

corbo-billy · Post by **corbo-billy** » Sat Nov 25, 2006 3:58 am

Hello _

I have the same problem that deepcgi and I foolow the tutorial of Frodo: I have extract the expired plgin demos.
It's perhaps the solution _

Frodo · Post by **Frodo** » Sat Nov 25, 2006 4:39 am

corbo-billy wrote:Hello _

I have the same problem that deepcgi and I foolow the tutorial of Frodo: I have extract the expired plgin demos.
It's perhaps the solution _

corbo-billy--

Is it working for you?

corbo-billy · Post by **corbo-billy** » Sat Nov 25, 2006 5:28 am

One moment, please; I am testing a little file with the new version of Kontakt2 and all I.V. of D.P _

Thanks and I release my test (sorry for the language) _

corbo-billy · Post by **corbo-billy** » Sat Nov 25, 2006 6:04 am

OK, let's go _ My sequence is still and D.P. work fine after yesterday an uninstall and reinstall from the CD of D.P. 5.01 and a new update in version 5.11 with new Preferences and eject for the plug-ins demo expired _