I struggled with this since the release of M5 ver 1.12 (which never worked until I moved to Tiger). M5 1.8 was great, then 1.12 started the intolerable load times (if it loaded at all!) I complained loudly to MOTU, and finally went thru sales to get an answer. I'll post the MOTU emails below FYI, but here's what fixed it.
When I moved to Tiger, DP 4.52 crashed and would not work at all (even after reading the last word of page 531 of the manual
. Eventually, I tracked the DP problem down to a bad CD ROM from MOTU and when I downloaded the update from the MOTU site, it loaded fine and ran well. So I thought, "what the heck, I'll give M5 1.12 another chance" and M5 1.12 also was fixed. So the problem would seem to be related to the Mac OS
But the problem you mentioned, Jim, is old hat to me. Fortunately, it somehow magically got fixed. Seems the reverse happened to you, so below is the MOTU solutions that were suggested (but did not work). Notice they acknowledge that the problem HAS been reported before. BTW, the problem seemed worse in old files and most new files in M5 seemed to be pretty good for the most part
---------
Jan 25, 2005
MIchael,
Here's the response I received from Jon in MOTU tech:
We've had this reported a couple of times, but we've never been able to reproduce this. One thing I would suggest is to try creating a new user with admin privileges. It's possible there might be something within his user profile that is causing some type of conflict with the samples being loaded into RAM. Beyond that, he may also want to try pulling out some RAM, trying different combinations of sticks to see if there may be an issue with his RAM.
--------------
(Note: M5 started to freeze my entire system).
Nov 20, 2004
Hello Michael,
If you go to your Activity Monitor in the Utilities folder, does it tell you what is using the RAM/Processor? Does anything look out of whack here when running the latest Mach Five? Do you see any RAM being "held onto" by the program even after you quit that looks abnormal? Do you see any functions that it lists that look very suspect, such as a process that is using 80 percent CPU or something of the sort? Are you ever using the Disk Streaming functions in Mach Five? If so, what disc are you trying to stream from? Have you tried different disks? Have you tried running the Mach Five Sounds off a different disk, in general?
Thanks for writing,
Nathan
MOTU Tech
---
Nov 16, 2004
Hello Michael,
When you say the system is sluggish, how do you mean? In terms of files, for Mach Five, there is only the Mach Five bundle in your plug ins folder, the Mach Five folder in the Library > Application Support folder and the preference files in your Users > your name > Library > Preferences folder. Once you remove these, Mach Five is gone. Do you have other peripherals/hardware attached to this machine?
Thanks for writing,
Nathan
MOTU Tech
----
July 8, 2004
Hello,
Thank you for the update. I apologize for not responding sooner.
Try removing the iLok Drivers and install the latest version from PACE's website. Does this affect the performance on your machine?
Thanks for writing,
Nathan
MOTU Tech
-----
June 28, 2004
Hello Michael,
Thank you for your email.
We take any issues such as these quite seriously, so please help us in understanding these issues. Are you loading old projects with Mach Five? Do you have problems when loading Mach Five into a brand new project? Do you have the latest version of your recording software? What kind of computer are you running on? DP can never be force quit from the dock, unless it has just been started. As soon as it loads, you must use Command - Option - Escape to force quit.
Thanks for writing,
Nathan
MOTU Tech
---
My original complaint:
The 'streaming' update not only slows performance of MachFive to a crawl when loading, but takes over the entire system (Mac OS X 10.3.4) so that you can't force quit from the dock! You can force quit by using the CMD>OPT>ESC keys. I lost access to everything on my Mac (running programs, Finder, etc.) while MachFive was 'loading.' Let me be more specific... loading the bank of sound was fast as always, but selecting an instrument takes WAY too long.
Loading even a small sample takes a very long time. A large sample probably will be unusably long to load, especially on the fly. It just ain't gonna happen. Also, the program shows all 16 channels as "working" during a load patch.
MOTU has not offered a link to download the earlier version (1.08) so if you want to go back, you have to have saved the earlier version to disk. Fortunately, I did and simply ran the installer and all is well again. But I won't be using 1.12 any time soon...
----
(end note August 15, 2005)
I'm on a Quciksiler 2001, Sonnet 1.4 processor (I suspect this may have been part of the problem), with 1.25GB of RAM. The problem was in Panther (all versions). It went away with Tiger (all versions - although i haven't tried it since today's Security Update... better go check!)
MM
<small>[ August 15, 2005, 02:15 PM: Message edited by: MIDI Life Crisis ]</small>
