MOTUnation.com

anyone the same? sometimes when i cut or edit single or grouped tracks dp gives me the spinning ball and quits without warning or error-descripition. i installed dp5 beside dp 4.61. 4.61 was perfect. also 5 needs much more time copying parts of tracks somewhere else.
any suggestions.
thanx, robinsky

While I like a lot of the new features in DP5, after extensive testing I have found DP 5.01 to be fairly unstable. The auto-punch-in/out is completely unusable crashes every time. In general DP5 seems very prone to crash. This has been confirmed on multiple systems and I have seen other posts regarding both these issues. Looks like I will be sticking with 4.61 for a bit.

Frodo wrote:

Kazrog wrote:I'm still having the crashes. I've done everything I know how to do. Can't go back to 4.6.1, I'm using too many 5.x features. I'm just going to have to live with the crashes until MOTU fixes them.

Kaz-- are you using both a FW hard drive and a FW audio interface perchance?

No, I've got a secondary internal SATA drive, and a MOTU 828 Mk II (Firewire) interface. This is on a dual 2.5 G5 with 1.5 gigs of RAM, and tons of disk space.

All my drives are error-free, optimized with TechTool. I use a program regularly called AppleJack that repairs permissions and does a lot of other OS X cleansing processes. Under DP 4.6.1, I never had any crashes.

I've rid my sequence of any unused soundbites, I've flushed the undo history, etc. I'm working on a project where I have a group of 8 mono tracks that I edit simultaneously. I am going to be doing some single-mono track editing today for another instrument in the project, so I'll let you know if that's more stable. I regularly toggle "Edge Edit Copy" on and off as I need it, but I've had crashes regardless of its state.

I'm running at 1024 samples/buffer and I'm keeping my CPU meter at about 25% or less most of the time. I've frozen and disabled any VIs in the sequence. I don't know what else to do at this point, I've done just about everything a sensible DP user can.

I also still am haing problems with DP 5.01. Besides what I had done last week, which is mentioned below, I have reinstalled OSX and I am still getting freezes with DP 5.01. Does anyone have any suggestions.

This is the first time any of mac audio systems behaved like a Windows XP audio system. I am disappointed. My previous post is below. Take care.

Papisax

I am running a Dual 1.25 GHZ G4, 2 GB of Ram and a 120 GB hardrive. I did not have any problems with DP 4.61. Since I have been using DP 5.01 my computer relentlessly freezes. I have to constantly power it down.

I have ran Disk Warrior, defragmented the drive, Repaired Permissions, Reinstalled DP from scratch (making sure to remove all prefernces, etc), emptied all caches. I even ran tech tool pro to check out the hardware, and everything passed all the tests.

Does anyone have any suggestions? Is anyone also having problems. I have been using DP since 3.11. This is the first time DP is not working properly on my system. Your attention to my question is greatly appreciated.

I will tell all of you this:

I saved 4.6 versons of all of my songs (I am in the middle of finishing a Latin Jazz CD which I started in 4.61), removed DP 5.01, cleaned all DP and MOTU preferences etc. and reinstalled DP 4.61. And guess what? My computer is working perfectly!

May be it is a confilct with 3rd party plug-ins, etc.. But there is a problem. I am very frustrated because I have spent over 2 weeks trying to figure this out.

I hope this post is of some use.

Papisax

No problems doing single-track editing here. The crashes happen when you start editing groups of tracks. Obviously, most of us here rely on the ability to edit groups of tracks, so this is a serious (inexcusable) bug. Anyone report this to MOTU yet?

Bumping this thread to the top... does anyone know if this bug has been reported to MOTU?

MOTU COMES THROUGH!!!

I though I was going to have to switch to Logic since DP started crashing almost everytime I edge edited or crossfaded or even hit undo.

Now in 5.1 this all seems to have been fixed! Now it's back to work.