Mac Genius: What's This Problem?

Loren Simons · September 20th, 2008, 01:45 AM

that was a close one, i was planning on doing it to my system drive tomorrow! hahaha honestly at this point, i don't know whether its the camera or the computer. I'm going to sammys tomorrow and I'm going to try uploading on their MacPro. I assume they will let me since if it works there, i'll be buying one.

Robert Lane · September 20th, 2008, 04:24 PM

Loren,

There seems to be a few things that could potentially be problems with what you're attempting.

First FCP 6.0.4 has proven to be much more stable on 10.5 than even 10.4.11; there are many API's and other code-monkey items that were optimized in FCP 6.0.2 specifically for OSX 10.5 and have proven buggy with 10.4.

Next FCP especially wants to see even amounts of RAM, even in the G5 machines. Bring that 1.5GB up to an even 2GB at least - or better yet max the RAM out to what your budget can afford; FCP 6 and especially OSX 10.5 will take advantage of all the RAM you can throw at it.

Next, you might be suffering from an ill-maintained directory. Purchase and download DiskWarrior from Alsoft, create the bootable disk and run it's routines.

Also, download and run all the automated routines in Onyx; it too will clean up old files and fix errors that can cause these issues.

Lastly, iDefrag can be used on the boot/OS drive with ease and if it's never been done would substantially improve performance. The publisher of iDefrag also has a CDMaker program which will create a bootable disk with iDefrag as the only app which will allow you to defrag your OS drive. We've been using iDefrag on our OS drives once a quarter for 3 years with zero failures/errors. HOWEVER, you must only defrag a drive that has FIRST had any directory issues fixed - that means DiskWarrior must be run first before anything else.

Before plunking down cash on a MacPro (which ultimately isn't a bad choice) try this stuff first and if you're still having issues let us know.

Loren Simons · September 20th, 2008, 06:12 PM

well the verdict is: It was the camera, i went to sammys and tried using my camera on a macpro, and than theres set up there. It worked on theirs, so it was my camera, and i sent it in for repair today. 3 weeks=(

September 20th, 2008, 01:45 AM	#16
Loren Simons Major Player Join Date: Aug 2007 Location: Los Angeles, CA Posts: 288	that was a close one, i was planning on doing it to my system drive tomorrow! hahaha honestly at this point, i don't know whether its the camera or the computer. I'm going to sammys tomorrow and I'm going to try uploading on their MacPro. I assume they will let me since if it works there, i'll be buying one. __________________ Loren Simons

September 20th, 2008, 06:12 PM	#18
Loren Simons Major Player Join Date: Aug 2007 Location: Los Angeles, CA Posts: 288	well the verdict is: It was the camera, i went to sammys and tried using my camera on a macpro, and than theres set up there. It worked on theirs, so it was my camera, and i sent it in for repair today. 3 weeks=( __________________ Loren Simons

September 20th, 2008, 04:24 PM	#17
Robert Lane Go Go Godzilla Join Date: Nov 2004 Location: Scottsdale, AZ USA Posts: 2,823 Images: 15	Loren, There seems to be a few things that could potentially be problems with what you're attempting. First FCP 6.0.4 has proven to be much more stable on 10.5 than even 10.4.11; there are many API's and other code-monkey items that were optimized in FCP 6.0.2 specifically for OSX 10.5 and have proven buggy with 10.4. Next FCP especially wants to see even amounts of RAM, even in the G5 machines. Bring that 1.5GB up to an even 2GB at least - or better yet max the RAM out to what your budget can afford; FCP 6 and especially OSX 10.5 will take advantage of all the RAM you can throw at it. Next, you might be suffering from an ill-maintained directory. Purchase and download DiskWarrior from Alsoft, create the bootable disk and run it's routines. Also, download and run all the automated routines in Onyx; it too will clean up old files and fix errors that can cause these issues. Lastly, iDefrag can be used on the boot/OS drive with ease and if it's never been done would substantially improve performance. The publisher of iDefrag also has a CDMaker program which will create a bootable disk with iDefrag as the only app which will allow you to defrag your OS drive. We've been using iDefrag on our OS drives once a quarter for 3 years with zero failures/errors. HOWEVER, you must only defrag a drive that has FIRST had any directory issues fixed - that means DiskWarrior must be run first before anything else. Before plunking down cash on a MacPro (which ultimately isn't a bad choice) try this stuff first and if you're still having issues let us know.