Glacial launch-times after crashes [RESOLVED - AGAIN]

[mikehalloran]

Yes, the one I posted earlier has stopped working. According to Apple Support, this is the latest version:

Reset Launch Services

1. Open Terminal and run these commands:

2. /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed -lint -r -f -v -dump -domain local -domain system -domain user -domain network
<Enter or Return key>
3. killall Dock
<Enter or Return key>
4. sudo mdutil -E /
<Enter or Return key> (enter Admin password when prompted, then <Enter or Return key>)

5. Restart your Mac

[dix]

Thank you, Mike!

Unfortunately, this had no effect on my launch times Ran the sequence twice, and even booted into Safe Mode (and then restarted), and I'm still getting long launch times after crashes. ...force quitting DP causes the same problem so at least it's easy to test.

Other things I've tried, that didn't help:
-Trashing DP's prefs, and com.motu.DigitalPerformer.plist
-Starting DP with plugins disabled
-Starting DP with MAS disabled

I'll try James' suggestion of updating Monterey first chance I get (thanks for that btw James).

Any other ideas are welcome and appreciated. Thank you!

[James Steele]

I'll try James' suggestion of updating Monterey first chance I get (thanks for that btw James).

I suggested that to HC Markus. I have no idea if it will help your issue, but it might be worth a shot.

Just, of course, be careful not to update to Ventura. There will be a little blue "More..." link under the box where it shows the Ventura update and if you click that it will show you the Monterrey update. Latest is 12.6.2.

[mikehalloran]

What is going on in the Activity Monitor? You should have the window open and, if something turns red, drill down ASAP. That's how I found the Corel problem. Unfortunately, it didn't help with CodeMeter—that was found accidentally.

[dix]

What is going on in the Activity Monitor? You should have the window open and, if something turns red, drill down ASAP. That's how I found the Corel problem. Unfortunately, it didn't help with CodeMeter—that was found accidentally.

Nothing remarkable that I can see, Mike. Nothing turns red. Not even a "Not Responding" next to DP while it's launching. It looks like DP is using slightly more CPU during the long starts than a it does if I'm starting normally.

[dix]

Well, it looks like simply reinstalling DP fixed this. I did do the full recommended uninstall procedure that MOTU suggests, which involves removing all prefs etc., but ended up restoring them all, so I didn't lose any of my preferences.

Just reinstalling without the uninstall steps might have worked too, but I didn't try that. For ez ref for anyone else having this issue, MOTU's recommended un/reinstall procedure is:

- Quit DP

- Open a Finder window, go to Applications and move all versions DP to the Trash. Make sure to remove any alias from the Dock as well.

- Go to Macintosh HD > Library > Application Support > MOTU > move the Digital Performer folder to the Desktop.

- Go to Macintosh HD > Library > Audio > Plugins > move the MAS folder to the Trash

- In the Finder window, navigate to the 'Go' menu at the top of the menu bar. Hold the Option key and navigate to Library (which will reveal itself when you hold Option).

- Go to Preferences folder and move the "com.motu.DigitalPerformer" and "com.motu.MotuAudioSystem" folder to the Desktop

- Empty the Trash

- Restart your computer

- Once you're back up go to motu.com/download and download the latest version of DP (for Mac).

- Run the installer and open the program.