dp 5.1 crashes on launch @#%$%$!!!!
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.
dp 5.1 crashes on launch @#%$%$!!!!
whats up with dp 5.1??....lots of my files are crashing right after all the plugs are scanned...i just added an APOGEE ensemble to replace my 828...i have a feelin that has something to with it.....verrry frustrating here......are alot of people here experiencing DP5.1 delemma????curious....thank you very much!
DP 4.6 Mac G5 dual 2 gig 6 GB Ram 10.3.8 OS ,Motu 828,Waves 4 Diamond,Altiverb, Antares Auto-Tune,AkaiS-5000,TubeTeck Recording Channel,TC Wizard, Edirol MIDI 8X8 USB
Have you talked to Apogee about UB and DP 5.x compatiblity issues? The first thing you'll need to confirm is that they have gotten Ensemble to work well with 5.1 and your model of computer (or similar), and to understand what systems they've used for testing. You will also want to know if they've discovered any known incompatibilities.
If you are not using your 828, you might want to remove any 828-related drivers.
(The following suggestions are not in any particular order, but are a summary of workarounds collected from various sources.)
Remove all default templates which may be predisposed to look for the 828 instead of the Apogee, and to make sure that DP's default setting is for the Apogee. Making new default templates may be necessary.
Check your audio Bundles-- rebuild your Bundles for your old files by removing any connections which appear in the Bundles window and replace them with new Bundles settings. Save your new Bundles settings so that the same settings can be imported into other projects. This will save you the hassle of having to recreate the same Bundle setting repeatedly.
Make sure your Ensemble interface is selected in Hardware Settings (before you try to open an old file). Use a new file and fly in some audio just to get it to work.
You may need to rebuild your entire project. Use Built-In audio to avoid audio driver conflicts. Open your old projects and select ALL-- and then copy all. Open a new template which matches your old project and paste the audio and MIDI data into project. You can save your new project file in the same location as your old one so that the Audio Folder can be easily located.
Shut down (not "restart") your computer, if necessary, to flush any old UNIX references of its own hubris.
Other users might likely have additional suggestions, but this is all I've gathered to date related to the 5.1 crash on boot.
If you are not using your 828, you might want to remove any 828-related drivers.
(The following suggestions are not in any particular order, but are a summary of workarounds collected from various sources.)
Remove all default templates which may be predisposed to look for the 828 instead of the Apogee, and to make sure that DP's default setting is for the Apogee. Making new default templates may be necessary.
Check your audio Bundles-- rebuild your Bundles for your old files by removing any connections which appear in the Bundles window and replace them with new Bundles settings. Save your new Bundles settings so that the same settings can be imported into other projects. This will save you the hassle of having to recreate the same Bundle setting repeatedly.
Make sure your Ensemble interface is selected in Hardware Settings (before you try to open an old file). Use a new file and fly in some audio just to get it to work.
You may need to rebuild your entire project. Use Built-In audio to avoid audio driver conflicts. Open your old projects and select ALL-- and then copy all. Open a new template which matches your old project and paste the audio and MIDI data into project. You can save your new project file in the same location as your old one so that the Audio Folder can be easily located.
Shut down (not "restart") your computer, if necessary, to flush any old UNIX references of its own hubris.
Other users might likely have additional suggestions, but this is all I've gathered to date related to the 5.1 crash on boot.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
oh .........when i do get a file open and hit the harware settings button it also crashes..........
frodo...thank you for the suggestions...i wil try to apply your wisdom...aloha!
frodo...thank you for the suggestions...i wil try to apply your wisdom...aloha!
DP 4.6 Mac G5 dual 2 gig 6 GB Ram 10.3.8 OS ,Motu 828,Waves 4 Diamond,Altiverb, Antares Auto-Tune,AkaiS-5000,TubeTeck Recording Channel,TC Wizard, Edirol MIDI 8X8 USB
Up late, are you? Hmm. Sounds serious.
Okay-- skip the process of opening your old projects for now.
Can you get an Empty project working properly? If that doesn't work, then the troubleshooting will have to take a different direction...
But one thing at a time.

Okay-- skip the process of opening your old projects for now.
Can you get an Empty project working properly? If that doesn't work, then the troubleshooting will have to take a different direction...
But one thing at a time.
6,1 MacPro, 96GB RAM, macOS Monterey 12.7.6, DP 11.33
could be file permissions.
I'd suggest repair permission on your disk and, if you have it, run DiskWarrior to repair your directory
I'd suggest repair permission on your disk and, if you have it, run DiskWarrior to repair your directory
1ghz 17" Powerbook (currently), 1gig ram, Tiger 10.4.8, DP 4.6.1, Motu 828, Edirol FA-101, Bidule, Reason, SuperCollider, synths, hardware FX, cables, plugs, plug adaptors, extension leads, dust, vacuum cleaner
- RobTalbert
- Posts: 75
- Joined: Mon Jun 27, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Gaithersburg, Maryland
Update all your drivers, etc.s
I had the exact problem over the weekend - I could not get DP5.1 to open a project with MachFive and Traveler both enabled.
I first uninstalled all my software - anything that touched DP5. I then begin reinstalling, starting with the Traveler and DP, running little tests at each step of the way. I updated the firmware in the Traveler. I figured out from this step-by-step testing process that MachFive was at least part of my problem. I installed the MachFive 1.2.3 upgrade. Reading the boards here helped me figure out that running the MachFive 1.2.3 upgrade itself wasn't sufficient -- I had to first manually remove the MachFive AU.Components and MachFive MAS.bundles file so that the MachFive 1.2.3 upgrader program would replace them.
Now I am sailing smooth [ly]... knock on wood.
I would check all your integrated music components to see if you have the latest versions of everything. Sift through the posts here to read about any of the related components you are using. [I would be suspicious of AutoTune for example.]
Good luck.
Rob Talbert
I first uninstalled all my software - anything that touched DP5. I then begin reinstalling, starting with the Traveler and DP, running little tests at each step of the way. I updated the firmware in the Traveler. I figured out from this step-by-step testing process that MachFive was at least part of my problem. I installed the MachFive 1.2.3 upgrade. Reading the boards here helped me figure out that running the MachFive 1.2.3 upgrade itself wasn't sufficient -- I had to first manually remove the MachFive AU.Components and MachFive MAS.bundles file so that the MachFive 1.2.3 upgrader program would replace them.
Now I am sailing smooth [ly]... knock on wood.
I would check all your integrated music components to see if you have the latest versions of everything. Sift through the posts here to read about any of the related components you are using. [I would be suspicious of AutoTune for example.]
Good luck.
Rob Talbert
iMac M1 with 16 GB RAM, OS X 12, DP 11, Focusrite Scarlett 18i20, Waves Plugins, Melodyne, Kontakt, BLUE Kiwi and Neuman Mics & BLUE Robbie Pre; Martin D18, Martin OM25, Cordoba, & PRS CE24 Guitars.
- daveyboy
- Posts: 873
- Joined: Sun Nov 21, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Los Angeles
- Contact:
Try this. Open DP only, no file. Go to hardware settings and make it apple only. Also, turn off audio and make MIDI only. Open file. Assuming it opens in MIDI only, go to hardware settings and turn on the correct driver. I'm having some similar issues with a few songs right now and this enables me to open them.
Dave
www.dbwproductions.com
10 core IMac w/128 gbs ram, DP11, Logic10x and PT 12, 4 room commercial studio (tuned by Bob Hodas) great for producers and composers!
www.dbwproductions.com
10 core IMac w/128 gbs ram, DP11, Logic10x and PT 12, 4 room commercial studio (tuned by Bob Hodas) great for producers and composers!
-
- Posts: 9
- Joined: Tue Nov 29, 2005 4:22 pm
- Primary DAW OS: Unspecified
-
- Posts: 447
- Joined: Wed Jan 26, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: Baltimore
-
- Posts: 16
- Joined: Wed Apr 05, 2006 4:37 pm
- Primary DAW OS: MacOS
- Location: Honolulu, Hawaii
- Contact:
What version of Altiverb are you running? Altiverb 3 will crash DP 5.1 (it works fine in DP5.01) I upgraded to Altiverb 5 and now it is fine in DP 5.1. Now I have to remember to take out any instances of Altiverb 3 in any of my sequences, write down the reverbs I had, and replace them with similar Altiverb 5 instances... Pain in da okole.
Wave shell 5.2 will cause DP 5.1 to crash. Is that part of your problem? Waves is not fully supported in DP 5.1 although some work just fine, like Renaisance Pack native... but sound shifter (and I assume Transform, etc..) are total crap in MAS.. have tried getting just the AU version to load with no luck. Anyway, maybe waves 5.2 is your problem...
Mike
Mike
3- G5 Dual 2 GHZ 6GB RAM HD 7.1 192 and 6-HD192 MOTU interfaces; all major plug ins and virtual instruments; studio and live performance