Troubleshooting with Activity Monitor

Recently Activity Monitor has been instrumental in troubleshooting problems for me. Activity Monitor is part of the Mac OS and lives in the Utilities folder, which is in the Apps folder. It gives you read-outs on things going on with the computer, including what the CPU and RAM are doing.

Here are a couple of good descriptions of the RAM display in Activity Monitor:
Final Cut Studio - System Memory Usage--Larry Jordan's Tip of the Day
Mac OS X: Reading system memory usage in Activity Monitor--Apple Support

The two pages actually give somewhat contradictory advice. Larry Jordan says that if your wired and active memory is regularly half of total memory then you could benefit from a RAM upgrade. While Apple says that even if you only have 10MB of free memory you don't necessarily need more RAM.

I've been noticing some bad examples of slow FCP that I blame on memory issues. So I think it's important to keep track of your RAM issues. Here some tips to keep your RAM usage streamlined and efficient:
- If you don't plan to switch back to an app, quit it and don't leave it open
- Avoid running multiple apps at once, especially programs that can suck up memory, like FCP, DVD Studio Pro, After Effects, and Photoshop
- Only keep open FCP projects open that you need, same things with sequences
- Restart your computer at least once a day and if your system seems really slow then restart it
- Web browser and webpages can use a surprising amount of RAM--avoid browsing with lots of windows/tabs
Now all of these RAM saving tips can reduce your efficiency in working. So it's a tradeoff. If your system zips along fine, then don't worry about it. But if you notice that your system starts the day zippy and ends up later trudging along, then try to follow some of or all of these tips.

I also uncovered a problem recently with Mosaic where the Mosaic project file had become huge even though there didn't seem to be that many clips or edits in the project. The size of the project file can give you an idea about how much memory an FCP project will take up in your RAM and how many resources the computer will use to work with the project. I'm not really sure why the Mosaic project file got so large--over 300MB. But I think it hurt that the editors were just adding stuff into the same project file day after day--even if they were deleting old clips and sequences regularly. I think the Mosaic project seems to have retained data from old clips and/or timelines that had been deleted and didn't appear in the project view. So I created a new project and just copied the timeline and clips that were visible in the project window--the new project was something-like one-tenth of the size, and the system got much quicker. I also read recently that clips that are really long are more taxing on the computer than more shorter clips that have the same amount of media.

Another things that Activity Monitor does is measure CPU usage. This was helpful recently when I was having problems with the single processor G5 computer. An intern was having problems capturing DV footage from a DV deck. I had set up an unusual firewire cabling setup, so first I tried changing that--no luck. Then I brought in a different deck. No matter what I did, I was still getting dropped frames and funky audio dropouts. I noticed that the intern had Firefox running, which I didn't think was I big deal--she was checking her Gmail. Then I opened up the Activity Monitor and I saw that Firefox was quite active. It's CPU usage was hopping all around, peaking at up to 15% of the computer's CPU usage. And it wasn't even like she was actively browsing--that's was up to 15% of the CPU just to keep up with Gmail. Well I quit Firefox and the computer started capturing fine and did about 5 hours of capture with no problems.

Now I'm lucky to have a four-core G5, and I regularly have multiple webpages, email client, and even iTunes running all while I capture from DV. But for a single-processor G5 the demands of running FCP, capturing DV, and having Gmail open were too much. So it is important to know your computer. Also remember that laying off is at least as demanding on your system as capture and almost always much more. You are almost always playing back multiple clips at once (remember all your audio tracks) and your system is probably trying to apply some real-time effects to the video and/or audio. So be even more conservative about what your computer is doing when you lay off to tape.

BTW, I recommend Larry Jordan's Tip of the Day. I don't want to visit his website everyday, so I subscribed to the RSS feed and check out the tips when I have time.