Moderator: James Steele
Yes but only the makers of de-frag software claimed it was really important after SATA in 2002. Apple and others could show that it made no real difference—even if it made sense.So it used to be important to have all the data from a project together on the hard drive so it wouldn't be so hard to read because of the physical movement of the reader beam.
Technically, it's impossible nowadays. The firmware of SSDs and TRIM + garbage collection in the OS are designed to keep it from happening. Since there's no mechanical arm, well, you know . . .But now you say that with SSD's, this is not necessary anymore.
Yes, almost certainly this is the case. As I stated in the post above, working as a Mac Technologist we remove Mackeeper as policy.David Polich wrote:MacKeeper is 100% Malware, I'm convinced.
If the problem was with DP 8 or 9, then you would expect most, if not all users to see CPU spike and audio dropouts with projects of this size. CPU rarely goes much above 40% on my old iMac with projects up to twice that size, with a number of VI tracks, and plugins. Logic would dictate the problem is something more specific concerning specific systems and setups, rather than the thing we all have in common -- using DP.Gerk wrote: I've come to the conclusion that DP9 is just a resource hog. And in terms of using UAD-2 stuff to help out -- it doesn't. I have project with reasonably low track counts (like 12-14 tracks, no VIs at all) that use nothing but UAD plugins and I still see my CPU meter spike out constantly. And I DO get audio dropouts at times. I had similar issues with DP8 (but nowhere near as bad in terms of CPU usage).
The problems _IS_ with DP 9 -- not with something else, it's DP 9 that's showing me these "fake" spikes -- and I call them fake because nothing outside of DP is seeing any kind of usage like that, but I see what you're saying, that something else may be contributing to the issue. Not sure what it would be though. At some point I suppose I should take this up directly with support -- but to be honest my time is valuable to me and I didn't intend on paying to be a beta tester. With the issues DP9 has on my rig it's pretty much unusable. At this point I would rather just cut my losses and move along to using something else until they spend their own time and $$ (well mine that I already gave them) to get their corner cases sorted out.bayswater wrote:If the problem was with DP 8 or 9, then you would expect most, if not all users to see CPU spike and audio dropouts with projects of this size. CPU rarely goes much above 40% on my old iMac with projects up to twice that size, with a number of VI tracks, and plugins. Logic would dictate the problem is something more specific concerning specific systems and setups, rather than the thing we all have in common -- using DP.Gerk wrote: I've come to the conclusion that DP9 is just a resource hog. And in terms of using UAD-2 stuff to help out -- it doesn't. I have project with reasonably low track counts (like 12-14 tracks, no VIs at all) that use nothing but UAD plugins and I still see my CPU meter spike out constantly. And I DO get audio dropouts at times. I had similar issues with DP8 (but nowhere near as bad in terms of CPU usage).
