Launching Mixing Board crashes DP

[JohnG]

Hi all,

I had to relocate my studio recently in a hurry and am unfortunately working with a different configuration. Everything is going through AVB to my MOTU interfaces (112D and 1248 -- firmware is latest).

I'm getting crashes, especially when launching the Mixing Board [shift_M]

I've been using DP since the early 1990s and never had this level of instability. Crash logs suggest it could be graphics related, as it keeps mentioning Metal API. I'm pasting in brief synopsis of what ChatGPU generated from the crash log:

[from Chat GPU ]Possible Fixes:

1. Update Digital Performer and Vienna Ensemble Pro. Ensure you’re using the latest stable versions of both applications.
[DP is latest, VE Pro is latest, using OSX Sequoia 15.3]

2. Check Plugin Compatibility. If you recently installed or updated a plugin (especially ones using GPU acceleration), try disabling it.
[using a “Hardware Insert plug-in” to use an external hardware tc electronics reverb]

3. Adjust Audio Buffer & Sample Rate Settings Lower the buffer size and ensure your sample rate is consistent across all audio interfaces and applications.
[buffer is at 512; sample rate is 48]

4. Run in Safe Mode Try launching Digital Performer in Safe Mode (holding Shift while launching) to disable third-party plugins.
[Only 3d Party plugins are pretty tame and seasoned; Native Instruments, u-he, Blackhole]

5. Check System Memory Usage Open Activity Monitor and look for high RAM or CPU usage from Digital Performer, Vienna Ensemble Pro, or any plugins.
["Idle" CPU stays over 70% during playback. When DP is parked, it's 75%
["Idle" Ram use is 132; physical memory is 192]

6. Verify GPU Stability Since Metal API errors appear in the crash log, consider: Updating macOS & GPU drivers Disabling GPU acceleration in Digital Performer (if available)
[I don't know how to do this -- was wondering if there is a "most stable" "Theme" (under DP's Settings)

In reading the crash logs, I’m guessing something is conflicting with Metal API. which causes the crush.

[HCMarkus]

No specific solutions, but wondering if you've tried stripping down to base DP using Safe Mode without the external FX...

Try DP without VE Pro?

You're on an M2 Mac Pro, right? Interfaces are connected to computer via Ethernet, Thunderbolt or USB?

I guess I'm just suggesting taking things to a minimum, as close to your prior properly working setup as possible, then building back one element at a time.

[JohnG]

Hi HC

those are all good ideas. I tried opening the DP session with everything else off, after a cold boot. No VE Pro, email -- nothing else running at all. Tried safe mode (disables 3d party plugins). I don't even generate a crash log now, which makes tracking this down even harder.

Interface is connected to the computer via thunderbolt. Second interface is connected to first interface via CAT 6 Ethernet.

thank you

[mikehalloran]

Holding the Shift key is not how to open DP in Safe Mode.

Click the DP icon/. dpdoc file as if to launch normally, and immediately hold the Alt/Option key when you see the DP splash screen. In the Plug-In Set Selection window that appears, select “Safe”. This will launch DP with only MOTU plug-ins enabled.

[JohnG]

Holding the Shift key is not how to open DP in Safe Mode.

yes, sorry to mis-type.

Nevertheless, I am having unprecedented instability. I'm going to start taking bits out of the signal path one at a time and see if things improve.

Kind regards,

John

[mikehalloran]

Clear your Users cache.

/Users/[username]/Library/Preferences/com.motu.MotuAudioSystem/

Find any cache files in that folder and delete them.

Relaunch DP. All installed plug-ins will be rescanned and only the cache files you need will be rebuilt. This will take awhile but it will happen only once.

When I did this last year, I found AudioDesk caches going back to 1999. It's a good idea to do this once a year or so.

[JohnG]

Clear your Users cache.

/Users/[username]/Library/Preferences/com.motu.MotuAudioSystem/

Find any cache files in that folder and delete them.

Relaunch DP. All installed plug-ins will be rescanned and only the cache files you need will be rebuilt. This will take awhile but it will happen only once.

When I did this last year, I found AudioDesk caches going back to 1999. It's a good idea to do this once a year or so.

Hi Mike,

Thank you for your idea, which I followed. After rebuilding, the cache file is a different size. The only one there was: "Audio Unit Info Cache 64-bit." Took a while to rebuild but the new one is smaller, so probably cleared out some rubbish.

Out of curiosity, did you specifically suggest that to address a crash with the Mixing Board, or was it more along the lines of "general maintenance?" I'm in the middle of a TV show so this has been murder. Because of space and other things in my new location, I had to move from old school optical interfaces to an AVB network using a 1248 and a 112D. Theoretically sound, but a brave new world.

Any other ideas like that are very welcome. I've also gone through some of the recommendations here for a "crash free" DP.

One other question -- I had to use Finder's "Go_optionkey" to get to a library location with . Under my user name [the little house image with my name next to it] there is no Library at all, which surprised me. Recently updated to Sequoia in a desperate bid for stability, so maybe that changed the location. I've been using this program since it was "Performer" and can't remember ever having cleared that cache.

[HCMarkus]

John, have your tried using Consolidated Windows? Just an idea, maybe it will help...

[JohnG]

John, have your tried using Consolidated Windows? Just an idea, maybe it will help...

that's an interesting idea -- I am hoping that Mike's cache-clearing will help but I can maybe try that next.

[mikehalloran]

Clearing the users cache has cleared a lot of crashing issues for many users, myself included..

[JohnG]

Clearing the users cache has cleared a lot of crashing issues for many users, myself included..

Thanks Mike.