Hey Guys:) I had an external hard drive fail on me, sent it off to a disk recovery place, and a few thousand dollars later, I have a new disk that thinks a ton of Final Cut pro capture scratch files are plain text files. When I try to open them up, the computer opens them as Qucktime files and they play fine but when I try to transfer them into a FCP clip bin, I get "File Error: Unknown File." Is there any work flow ya'll know that I could use to get all these clips back into FCP?

Have you tried converting to another codec?

Well, when it's opened in Quicktime, I can hit save as and then it gives me only two options that I can see one is to save it as a reference file, the other is to save it as a self contained movie. I've done that for a few files but if I do that for all the files won't that double the hard drive space I need?

Well, when it's opened in Quicktime, I can hit save as and then it gives me only two options that I can see one is to save it as a reference file, the other is to save it as a self contained movie. I've done that for a few files but if I do that for all the files won't that double the hard drive space I need?So what if it does? Do you want to recover these files or not? Having just spent thousands on data recovery wasting a bit of storage space would not concern me one jot.

If it works do it!

Cheers

Nigel

Save them as Reference Movies. They don't add any significant size to your original movies.

Years ago I had a similar problem where AfterEffects would create a MOV file that couldn't be opened in Final Cut Pro without opening it and saving it in Quicktime Pro. My theory was the Quicktime added the necessary data that FCP needed to play the file correctly.

Hopefully you don't have too many MOV files as it could take a long time to re-save hundreds of files.

A Quicktime Reference File is not a self-contained movie file but is a file with links to the actual source footage that is accessed on the fly when the this reference file is played in the Quicktime player. Given Betsy's recent data loss & subsequent recovery I would want real copies of everything that I could get even if it did involve extra disk space & redundancy.

Betsy,

The other issue here is that these recovered files have their resource-forks broken. This is OSX metadata that tells the system what program/s are used to open and modify the files.

It may be a simple matter of manually resetting the resources; do a "Get Info" on any of those recovered files that FCP normally would open. Then in the "Open With" setting select FCP from the list. Make sure you hit the "Change All..." button below. Then try to re-ingest those files into FCP.

Also, make sure the extension at the end of these files is ".mov", not ".txt" or something else that would tell OSX to use a different program other than QT or FCP. One of the issues with deep-file recovery is that the software used to recover the files homogenizes all the data into common file-type values. This usually allows for a greater amount of recovered and uncorrupted data; the downside is exactly this type of behavior, where resource forks and other metadata is wiped out.

This would also be a good time to review your archiving and backup strategies to prevent this happening in the future.

Let us know if this works.