FCP married to wrong Drive

T

thunderMex

Member
I have a new MacPro and the Final Cut Suite including Final Cut 7.

A month ago when the system was delivered I had to start editing without an eSata connection to my 6 TB external hard drive unit because the eSata input was apparently defective. The drive was connected with Firewire 800 for the time being until the new unit arrived with a working eSata cable socket.

The 6TB -- 4 X 1.5 TB drives-- were not partitioned, simply made one drive called "Video".

Today the technician showed up with the exact replacement external hard drive from Sonnet and made an exact copy of all the files from my existing "Video" to its new mirror also named "Video".

I went into FCP system settings and re-set it to work with the new eSata connected "Video". I also used Media Manager to save a Copy without compression of all the used media files in my existing open project into newly named folder on my new eSata external hard drive also named "Video". Supposedly I had two identical "Video" drives otherwise.

But now my projects all seem married to the previous "Video" Volume where they were originally saved. If I start up FCP without the previous "Video" mounted I cannot open up my most recent Autosaves of projects or the deliberately named .fcp files. FCP, which is installed on my internal system drive, tries to load up the last project and I have to keep force quitting it because it gets about 32 to 36% status on the loading files and then can go no farther. It will sit with the spinning beach ball forever.

When it does run because I keep my previous "Video" external drive open through the Firewire 800 connection I see that I "sucessfully" re-set FCP to use the new "Video" as the place for capture and scratch and render files. But FCP even when I have the original hard drive unit unmounted can not read project .fcp files -- unable to load the media, apparently.

The only difference with the new mirrored RAID is that it uses S.M.A.R.T. , which was disabled on the Video volume running on Firewire 800.

Tomorrow they want to send a courier to pick up the original volume but I cannot get FCP to work with the eSata duplicate Volume.

Any tips out there?

If I CAN open up a copy of the project .fcp from a couple of days ago it will not load the timeline!

If I shut down the new eSata "Video" so that it does not mount and return to starting up my MacPro with the previous "Video" unit connected by Firewire 800 I can get back all my projects and timelines and media.

Thanks for any relevant help.
 
I don't know if I fully understand your problem, but maybe it would help to rename the new drive to something other than 'video', and then reconnect the media when prompted. Then save the fcp file when everything is connected.
 
my idea

my idea

My idea was that cloning the new hard drive with a faster eSata connection with the same volume name and exact same files and file structure would enable me to simply start up FCP and continue working on some projects that had been saved some time ago. I was hoping FCP would not know the difference when it was re-started.

I didn't want to have Final Cut unable to load up projects and media that had been saved in previous timeline and project files mapped to a volume with another name.

The two Sonnet external hard drive Volumes are exactly the same. But the eSata did not work on the orignal order so Firewire 800 was the connection method available until the replacement arrived with eSata functional.
 
Has anyone heard of a .fcp text editor? Some of my .fcp files are a few million megs in size. I know that the old ones have directory references to media files and things that would load up if they were directly edited to point the older FCP files to updated references and saved again. But as it is I have too many that cannot be opened in FCP itself all of a sudden simply because they point to a different volume.
 
I see what you were trying to do but I don't think it was necessary, you could have copied those media files to you new drive and simply reconnected your media without an issue. You probably still can if you trash your preferences and name the new drive something different. You can then open your old project and you will get a prompt telling you your media is offline, then you click the locate button and point it to your new drive. Final cut will find everything and re-link it. I have done this many times and it works well as long as you copied all of your media to the new drive.
 
Thanks Ram, but now I see I have a bigger issue. The whole RAID drive is corrupted.

Every media file...jpegs, mov's, blah, blah, woof woof...Corrupted.

The file names are there. The visual thumbnail icons show what the media looks like, but I have half a terabyte of corrupted files.

For some reason copying or moving the disk from the perfectly fine RAID unit running through Firewire 800 onto the new Destination Volume connected by eSata is creating a corrupted version of the first hard drive.

It has been a month since receiving this setup...and the Fusion D400QR5 with 4 1.5 TB hard drives has yet to be successfully installed with a working eSata connection.
 
You must log in or register to reply here.
Back
Top