MOTUnation.com

Nope. I check summed the file and even MOTU weighed in at one point. Same file. Different date on the web page is all.

At a loss then as to what's up. I guess I can try re-installing all the updates now that 10.9.5 is my current system. It just drains my hard drive storage space down a little each time I re-install, and I can't figure that out either. I thought it was suppose to just write over itself. I've literally gone down 6GB from all the experimenting I've done this weekend.

Then DELETE it all and THEN install. No reason it should increase the drive usage. It should just replace what's there.

any recommendations as to what to use to fully delete it? Or where to go to fully delete everything?

Can Mach5 be installed with just the Installation file? No disk needed? Can't remember. My new system doesn't have an optical drive.

Is there an uninstall option? I don't recall.

Not that I've seen. Anyone else know where to look?

When DP crashes, how can I see the entire crash log?

Tech at MOTU suggested the following:

<<<
This problem could be caused by a bad prefs file. Let's try removing them. Quit Digital Performer. Click the ‘Go’ drop down menu from Finder while holding option and select the library. Go to the Preferences folder. Drag the ‘com.motu.DigitalPerformer’ and 'com.motu.MotuAudioSystem' folders to the desktop. Also in the Preferences folder, delete the following:

com.motu.MachFive3.AU.plist
com.motu.MachFive3.plist
com.motu.MachFive3.SA.plist
com.motu.MachFiveSA.plist
MachFive3

Now, run DP. DP will rescan your plug-ins. Let me know whether this helps or not. If it doesn't, will MF3 launch in standalone mode?
>>>

I went through the steps four different times, and each time MachFive3 would cause the crash (according to the crash report). Yes, MachFive3 will open in standalone mode just fine. Yes, some projects do open just fine with MachFive3. But, then there are a select few that totally crash upon load. Could it be a patch hang-up?

I'm at a loss here. Anyone?

UltimateOutsider wrote:Yep, and CSM 1.5 is still throwing this error:

I am having the same problem, anybody run across a solution yet? The UVI sound banks I tested, such as CSM 1.5, don't loop the samples. The original CSM works fine and the banks also work in the UVI workstation.

Thanks,

Todd