MOTUnation.com

I'm working with DP 8.05 and I like to leave the program on when I'm composing. However it quits on me and the last time it did that, I experienced some losses due to working with older files done in earlier versions. I was able to retrieve the losses, though time consuming. I called the MOTU help line but they did not have any answers at the time. What is the fix to keep the program running? Appreciate any suggestions.

There's a MOTUNation help line?

This site is not associated with MOTU. You might try calling them.

--"There's a MOTUNation help line?"
yes it's MOTU Customer Service 617 576 3066 

--"This site is not associated with MOTU. You might try calling them."
-I called them already and they did not have a fix for me, that's why I'm contacting the list.

thanks

That is MOTU's #. Not Motunation's #.

yes thnx got that...
The issue I am asking about is to discover the fix to keep the program running.
Appreciate any suggestions.

That's going to be tough to find, as this isn't a common problem... I leave DP 8.05 running all day and it never just quits when not being used. Are you getting the option to send a crash report to MOTU when this happens?

I leave DP 8.05 running all day and it never just quits when not being used.


Are you getting the option to send a crash report to MOTU when this happens?

not that I have seen ...unless I missed something... but I doubt I would have missed a msg like that… hmmm

cdemby wrote:I'm working with DP 8.05 and I like to leave the program on when I'm composing. However it quits on me

I, too, have never experienced this. What are you doing when it "quits"? Are you running other software simultaneously? Is it actually quitting or is it crashing? A detailed rundown could help us help you.

I'm guessing it is something other than DP that is causing your problem. The quitting may be a symptom of other issues.

when my engineer comes next week we will research, diagnose and hopefully fix this issue. meanwhile I've been able to restore and save all files by restarting and zapping the p-ram three times which always helps to clear things out.
thnx to all for your suggestions.
CD

cdemby wrote:--"There's a MOTUNation help line?"
yes it's MOTU Customer Service 617 576 3066 

We're just trying to head off confusion. You'd be surprised. I used to get people telling me their username and password didn't work and they were talking about the MOTU site. That's why I added the disclaimer text to the main header of the site. It's just to avoid confusion and also why I'm going to edit your original post. Again... not trying to give you a hard time, but it's a very important distinction.

Thanks for that distinction James … it's been a while since I've posted to the site and will make note of that info… The good news is that through our original post, we found a great DP engineer nearby to assist with the new recordings. Thanks for all that you provide to the community, I'm sure everyone appreciates it! CD


We're just trying to head off confusion. You'd be surprised. I used to get people telling me their username and password didn't work and they were talking about the MOTU site. That's why I added the disclaimer text to the main header of the site. It's just to avoid confusion and also why I'm going to edit your original post. Again... not trying to give you a hard time, but it's a very important distinction.

Constance,

I just noticed that you've got 4GB RAM. I don't know what virtual instrument libraries you might be using, but if they push the limits of your RAM, that might be your problem. The solution? RAM is cheap; buy a bunch!

Shoosh

Re: DP 8.05 quits
I just noticed that you've got 4GB RAM. I don't know what virtual instrument libraries you might be using, but if they push the limits of your RAM, that might be your problem. The solution? RAM is cheap; buy a bunch!

Thnx Shooshie… All my symphonic instruments and electronic sounds and digital orchestral samples are located on external hard drives, and when I start the composing process, the sounds for any particular song are loaded into the Kurzweil K2500 keyboard. I then perform the parts on the keyboard and everything shows up in the DP file. That's how I've always done it all these years. With this as my working model for composing, I don't think that would be the issue. My engineer will be over this week and hopefully we can determine why DP is quitting on me. I've never had that problem before. And I will also be calling the MOTU Customer Service line 617 576 3066 to see what they have to say about it. Thanks to all for the help and suggestions. CD

+ 1 on what Shooshie said:
DP8 and modern VI libraries require more ram.

If you don't have the buffer set for 1024 or higher when editing and mixing, fix that. There are many reports that a buffer set too low will not use all the RAM efficiently. Low buffer for tracking; higher buffer for mixing and editing.

Hopefully, your MacPro does not have the Retina display. If so, your RAM is soldered in and cannot be upgraded. The non-Retina versions do not have this issue.

Run Repair Permissions in Apple Disk Utility if you haven't done so lately. If DP tries to load something without proper permissions, it can quit without a crash log.

If there's no crash report, there's another way to see what is happening. Open Console. When DP quits, you should see what is going on at the time. Permission issues and old software trying to load will appear in Console. Tech Support may find it useful if you can't read the log.

Sometimes these issues are fixed by re-running the Installer. Just download and reinstall. No need to remove anything first and it doesn't affect the License Manager. I've done it a few times when issues were caused by certain plugs not behaving.

I recently had your exact issue after an Izotope Ozone upgrade. Their uninstaller doesn't work in Mavericks. Console told me that an old evaluation was trying to load and DP 8 would just quit. I had to manually remove every trace of Ozone 5 I could find, reinstall 5.05b, Reinstall DP 8.05 and I have been trouble free.

Another time, Console told me that the Control Surface plugs were failing to load. Re-running the installer fixed that, too.