dp closing down after loading project

For seeking technical help with Digital Performer and/or plug-ins on MacOS.

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.
Post Reply
User avatar
scott dansby
Posts: 78
Joined: Tue May 31, 2005 10:01 pm
Primary DAW OS: MacOS
Location: Brooklyn, NY

dp closing down after loading project

Post by scott dansby »

I am having trouble loading a project that has been saved. Last night I opened it and everything worked fine, but today the project loads up but doesn't let me do anything before shutting down. Other projects are loading. This is the only one that is not loading. Very, very frustrating. What should I do?
studiodog
Posts: 428
Joined: Sat Oct 23, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by studiodog »

Always start with the usual suspects,

Restart, repair permissions, restart and see what happens.
No luck, then trash your DP prefs.
azusa749a
Posts: 607
Joined: Wed Oct 20, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by azusa749a »

Try changing the name or open a new project and load the trouble one.
studiodog
Posts: 428
Joined: Sat Oct 23, 2004 10:01 pm
Primary DAW OS: Unspecified

Post by studiodog »

azusa749a wrote:Try changing the name or open a new project and load the trouble one.
My DP brain saw what Scott D. typed and just assumed he meant he was "Loading" the file as Azusa recommended.

This is good advice from Azusa, create a new file and select "load" from the main DP menu. Loading a file into a fresh new one will solve lots of problems.

Never tried the "changing the name" thing though. Does that help problem files?
TheHopiWay
Posts: 551
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: N.W. Washington

Post by TheHopiWay »

This may be a long shot but I recently had the same situation and while permissions repair and restart didn't help (though it never hurts) running disc first aid corrected something and the problem never reoccurred.
mattfort
Posts: 337
Joined: Wed Sep 07, 2005 1:02 pm
Primary DAW OS: Unspecified

Post by mattfort »

Try this...

Create a new project.

Load all soundbites, chunks etc...

Close the project

Open the old "corrupt" project

I've done this on several projects that wouldn't open as well as projects that were giving me a "-199" error....
2.66 Mac Pro, 10.6.5, 16 G RAM, DP 7.22, 6 SATA internal drives (2 RAIDS & 2 singles), Ozone 4, 2 UAD 2 Quad card with most of the plugs, Waves Diamond(V7), V- Series (V6) & SSL4000(V7), PLAY 1.25, EMI TG12413, URS CSPro, Autotune Evo, Scarbee KGB, EWQLSO Platinum Pro XP, Drumagog, BFD2, NI Komplete 7, Breverb, Ivory w/ Italian Grand, USB Plugsound Pro & Synths Anth, Ampeg SVX, Amplitube3 (And Fender), Altiverb, Melodyne, MOTU 24 I/O with Black Lion Mod.
nixon72
Posts: 23
Joined: Sat Oct 16, 2004 10:01 pm
Primary DAW OS: MacOS
Location: Detroit

Post by nixon72 »

Are there any VIs or plugins installed in the project. These are the culprit 99% of the time. Especially Sampletank or SonikSynth2.

Remove these components to open this project if this is the case. There are known issues w/ DP4.6 and Sampletank 2 XL and SonikSynth2. Seems to be only the XL versions though...hmmm...
Dual 2.0, OS 10.4.3, DP4.52, MOTU 828 MKII, IK Plugs, Plugsound, Mach 5, Waves 5.0.
Post Reply