Quote:
Originally Posted by MacStef
I see the wisdom inn what you say...Hindsight, right?
|
Yup, hindsight...she's a big ol' mean (w)itch, ain't she?!?
I think at this point because of your deadline you might do best to make a backup of your project file and any other project-related files on your system drive onto a jump drive or other removable media. Then go to a local computer store, pick up a new drive for the computer, take out the old drive or put the new one in a second drive bay if you have it, do a bare-bones install of the OS you were using previous to the unfortunate QT upgrade, & Final Cut HD and any of the apps like Photoshop or whatever you will need to finish just this project and get through this project. This should take you far less than two days, and you don't run the risk of the limp-along work around being only a symptom of a larger issue that won't rear it's ugly head until you get even further into crunch time. Make sure you stop with the updates before you go too far. Only go as far as it was when it last worked for you.
If I'm reading your specs right, you need a 7200RPM 3.5-inch Ultra ATA/100 Hard Disk Drive. Fry's or Micro Center would definitely carry it. Best Buy might.
It seems to me that this may be the lesser of two evils for your current situation.
Now for the copious information that won't help you now, but might help you next time: The general wisdom is to never update/upgrade
anything when you are in the middle of a project unless you are having problems and the update is reportedly supposed to fix the specific problems you are having. Even then, each editor should evaluate the risk of the system going wonky versus the problem being solved and decide if it's an acceptable risk. I don't trust anything the internet tells me unless I can verify it, even if it comes from Apple.
Even at their best, any software company can't test under all circumstances, system configurations and old versions of the software for incompatibilites and conflicts. (I think they all could do better in looking for actual bugs, though.)
I usually update my laptop first and test it out before I update my tower, which is my bread-and-butter machine. I also check here, the FCP forum at lafcpug.org, macintouch.com and the Apple website forums for known issues before I install major stuff. It's all so much more complicated than back in the OS9 days. To me, it's not surprising we see more issues, but I think Apple in particular could do a lot better than they have been in the last year or so. I have been doing complete installs on new drives for the past few years, keeping the old drive as a backup if I have problems and need to quickly revert to a system that I know is stable so I can get my work done. It's pretty cheap insurance, what with the drop in the cost of hard drives.
The hitch for you is that FCP 4.5 simply doesn't understand the version of QuickTime that's now installed. It's too advanced for the App. FCP 4.5 is several iterations back, and just does not have the oomph nor the sophistication to keep up with the new QuickTime. Apple isn't going to fix it. I'm sorry. Your version of FCP is simply too old. They are not going to backwards-engineer QuickTime to make a three-year-old product compatible. Three years is aeons in computer-time.
As much as we'd all love our old software to remain compatible until we're done using it, it would severely jack up the price on everything if the software companies kept going back and back and back to test old versions for compatibility. And as much as I cringe every time I have to whip out the credit card because I work for myself and it all comes out of my own pocket, I know from personal experience that keeping current is a lot less expensive in the long run than trying to get mis-matched components to work properly. Well, I mean current within reason. I'm still running FCP 5.1.4 on OS 10.4.11. I won't be upgrading to Final Cut Studio 2 until my clients also start upgrading.
I know this doesn't help you now, but for future reference....
debe