Digital performer nine won't open a file I just closed. It c
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Digital performer nine won't open a file I just closed. It c
Digital performer 9.51 won't open a file I just closed with several plug-ins.
This song will open in safe mode.
Song w keyscape. Trillian . Stylus
Omnisphere.
Just finished a bounce for the client.
Closed it and reopened it. Crashes!
I can open the file in safe mode w no plugs.
Where do I go from here?
I have trashed the tree preferences files as instructed.
Thanks,
Jim
Mac Pro 10.11.6
This song will open in safe mode.
Song w keyscape. Trillian . Stylus
Omnisphere.
Just finished a bounce for the client.
Closed it and reopened it. Crashes!
I can open the file in safe mode w no plugs.
Where do I go from here?
I have trashed the tree preferences files as instructed.
Thanks,
Jim
Mac Pro 10.11.6
- MIDI Life Crisis
- Posts: 26277
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Digital performer nine won't open a file I just closed.
Hmmm... sounds like one of the plugin or VI settings files may have gotten corrupted.
I'd try starting DP with the option key down and use only the safe launch (sounds like you did that already). Then I'd open the file and activate, then add each plugin one at a time via Audio preferences in DP and see if you can determine if, indeed, it is a plugin and which one is the culprit. It is also entirely possible the project file is damaged but since you can still open it w/o plugs, it's likely a plugin.
Another option is to start a new project and LOAD the sequence (chunk) to the new project. Then add your VIs and plugs (if they don't just import in).
Finally, have you trashed all the plists for the plug ins? I believe most, if not all plugins have their own plist files. If one gets screwed up and DP can't read it, it could cause a crash.
I'd try starting DP with the option key down and use only the safe launch (sounds like you did that already). Then I'd open the file and activate, then add each plugin one at a time via Audio preferences in DP and see if you can determine if, indeed, it is a plugin and which one is the culprit. It is also entirely possible the project file is damaged but since you can still open it w/o plugs, it's likely a plugin.
Another option is to start a new project and LOAD the sequence (chunk) to the new project. Then add your VIs and plugs (if they don't just import in).
Finally, have you trashed all the plists for the plug ins? I believe most, if not all plugins have their own plist files. If one gets screwed up and DP can't read it, it could cause a crash.
2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
Re: Digital performer nine won't open a file I just closed.
Thank you for your reply. I've never tried loading chunks. Is that something I can load like a MIDI file? Does it also include pointers to audio?
Thank you,
Jim
PS also since this crash and preference trash now all my plug-ins stay front of the window when I select the main track window stays covered by the plug-ins. What's the setting to always bring my selected window to the front completely?
Thank you,
Jim
PS also since this crash and preference trash now all my plug-ins stay front of the window when I select the main track window stays covered by the plug-ins. What's the setting to always bring my selected window to the front completely?
- stubbsonic
- Posts: 5152
- Joined: Fri Dec 22, 2006 12:56 pm
- Primary DAW OS: MacOS
- Contact:
Re: Digital performer nine won't open a file I just closed.
From the file menu, choose Load... rather than Open... From there you can choose a project and load individual chunks and components from that project. It allows you to do things like put a chunk into a fresh project. There are settings as you go through the dialogs about what to do with associated audio, etc.
M1 MBP; OS 15.3, FF800, DP 11.33, PC3K7, K2661, iPad6, Godin XTSA (w/ SY-1000), 2 Ibanez 5-string basses (1 fretted, 1 fretless), FX galore
http://www.jonstubbsmusic.com
http://www.jonstubbsmusic.com
- MIDI Life Crisis
- Posts: 26277
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Digital performer nine won't open a file I just closed.
It's in the DP prefs somewhere.jimf wrote:...since this crash and preference trash now all my plug-ins stay front of the window when I select the main track window stays covered by the plug-ins. What's the setting to always bring my selected window to the front completely?

2013 Mac Pro 2TB/32GB RAM
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
Instagram
Facebook
MIDI LIFE CRISIS
OSX 10.14.6; Track 16; DP 12; Finale 28
LinkTree (events & peformances)
MIDI LIFE CRISIS
- mikehalloran
- Posts: 16179
- Joined: Sun Jan 25, 2009 5:08 pm
- Primary DAW OS: MacOS
- Location: Sillie Con Valley
Re: Digital performer nine won't open a file I just closed.
Console.app should show the plugin that is failing to load.
DP 11.34; 828mkII FW, micro lite, M4, MTP/AV USB Firmware 2.0.1
2023 Mac Studio M2 8TB, 192GB RAM, OS Sequoia 15.4, USB4 8TB externals, Neumann MT48, M-Audio AIR 192|14, Mackie ProFxv3, Zoom F3 & UAC 232 32bit float recorder & interface; 2012 MBPs (x2) Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 NE Pro, Toast 20 Pro
2023 Mac Studio M2 8TB, 192GB RAM, OS Sequoia 15.4, USB4 8TB externals, Neumann MT48, M-Audio AIR 192|14, Mackie ProFxv3, Zoom F3 & UAC 232 32bit float recorder & interface; 2012 MBPs (x2) Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 NE Pro, Toast 20 Pro
Re: Digital performer nine won't open a file I just closed. It c
I was experiencing a similar issue and wanted to add a couple of observations.
My guess was that it was a plug-in (e.g., one of those plug-ins that interrupts instantiating the plug to tell you that a new version is available - cripes, I hate that).
But DP was croaking each time while loading/converting a particular Kontakt library. I changed the name of the directory just to see what would happen. DP complained about that missing library but then croaked later. The errors were of the sort when DP says, "Beats me why, but I just blew up", and provides no error message.
Per Mike Halloran's suggestion, I used Console.app to see if I could identify the issue.
Instead of finding errors on plug-ins, I found messages like this:
error 17:18:27.670181 -0500 kernel Sandbox: Digital Performe(2075) System Policy: deny(1) file-read-data /Volumes/some_volume/.Spotlight-V100
...indicating that DP couldn't read/write files and that somehow Spotlight had gotten involved.
I checked (via cmd-I) my drives and noticed that a couple were mysteriously set at "read only" for "everybody" while other drives were set at "read and write". These are sample drives and it was just a couple of them that were set this way...which seemed weird. So I set them all as "read and write" for "everybody".
I found an old thread on a seemingly not-unrelated matter:
https://apple.stackexchange.com/questio ... ds-and-usb
It's a long thread and the "punchline" is at the December 2017 entry. Specifically, I installed "CleanMyDrive 2" (free from Mac Paw which I've found to be a reliable developer). The app found some junk and cleaned the drives (man, was I sweating: even though Mac Paw is cool, I was worried that I was playing roulette with my sample drives, but everything worked out).
There's another suggestion in that thread to exclude drives from Spotlight but I didn't try that.
Bottom line, however, is that I'm back up and running though I'm still left scratching my head on this. Hope this helps someone. MacOS is ever-more locked down so I do wonder about that.
My guess was that it was a plug-in (e.g., one of those plug-ins that interrupts instantiating the plug to tell you that a new version is available - cripes, I hate that).
But DP was croaking each time while loading/converting a particular Kontakt library. I changed the name of the directory just to see what would happen. DP complained about that missing library but then croaked later. The errors were of the sort when DP says, "Beats me why, but I just blew up", and provides no error message.
Per Mike Halloran's suggestion, I used Console.app to see if I could identify the issue.
Instead of finding errors on plug-ins, I found messages like this:
error 17:18:27.670181 -0500 kernel Sandbox: Digital Performe(2075) System Policy: deny(1) file-read-data /Volumes/some_volume/.Spotlight-V100
...indicating that DP couldn't read/write files and that somehow Spotlight had gotten involved.
I checked (via cmd-I) my drives and noticed that a couple were mysteriously set at "read only" for "everybody" while other drives were set at "read and write". These are sample drives and it was just a couple of them that were set this way...which seemed weird. So I set them all as "read and write" for "everybody".
I found an old thread on a seemingly not-unrelated matter:
https://apple.stackexchange.com/questio ... ds-and-usb
It's a long thread and the "punchline" is at the December 2017 entry. Specifically, I installed "CleanMyDrive 2" (free from Mac Paw which I've found to be a reliable developer). The app found some junk and cleaned the drives (man, was I sweating: even though Mac Paw is cool, I was worried that I was playing roulette with my sample drives, but everything worked out).
There's another suggestion in that thread to exclude drives from Spotlight but I didn't try that.
Bottom line, however, is that I'm back up and running though I'm still left scratching my head on this. Hope this helps someone. MacOS is ever-more locked down so I do wonder about that.