
DVman
User
Feb 10, 2006, 8:19 PM
Post #3 of 4
(709 views)
Shortcut
|
|
Re: [RatVega] Problem with smooth rendering in FCP. Complex situation.
[In reply to]
|
Can't Post
|
|
I don't know if I made myself clear. But I am not using the clone drive. I am using the system drive and that is where the problem shows. After I cloned the drive, I booted from the clone drive, saw it working, shut it down, unplugged it and stored it. And then I used my system drive. The problem happens from my system drive, not the clone drive. And about firewire drives not causing damage to circuit boards, may be you are right. But once I damaged a firewire port by plugging a camcorder incorrectly somehow into the firewire port. I had to send the computer to Apple to have it repair. So, I am still at large with this rendering issue. If you take a sufficiently geeky perspective, the possibility that the clone copy is damaged is fairly good. In today's computers, we take a lot for granted. One of those things is the goodness of a copy. If you cloned, say, 50GB from the system drive, that's about 400 billion ones and zeros. The probability of a single bit error is pretty good. If the bad bit is in a video file, you'd probably never notice a shift in the color of one pixel. No biggie. But if the error was somewhere in the FCP code or the operating system, it could subtly change something... Run Disk Warrior on your system and then on the drive with the clone copy. See what shows up. A better method might have been to do a clean install of OS X and FCP to the FW drive and then copy over the rest of the data. Yes, I know it takes longer but the probability of success is greater. Firewire issues have been known to cause malfunctions and/or damage to a firewire drive, but I've never heard of anything affecting the computer. Firewire connections are also known to occasionally abruptly go bad, causing mount and read/write problems but then the drive would probably not mount. I'm betting it's a copy thing.
(This post was edited by DVman on Feb 10, 2006, 8:33 PM)
|