Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Media refuses to reconnect- something went awry with QT files

I posted this question a year back, and I'm just getting back to editing this project and I still haven't figured this out. I do have some new info, now, too.

I moved hundreds of gigs of footage from one drive to another.

This is my reconnect media workflow:

Select the offline files in the browser
Go to File- Reconnect Media
Select Offline Files

Files to Connect window shows the correct files
I hit Search
FCP locates the media in it's new location
I select "Choose"

And then the problem arises. The Media DOES NOT appear in the Files Located. The connect button does not light up.

I've done a lot of editing on this project already, so I need the files to reconnect properly. Any ideas?? I'm running 6.0.5

I HAVE tried the LOCATE Option- I DO find the media, but the problem is NOT that the computer cannot locate the files. It finds them just fine. It's just that for some reason once it finds them, it skips the part where it's supposed to connect them.

I just transferred all those files to NEW drive and the problem persists. However, this is what I discovered. If I try to drag the files to my browser, FCP gives me a +File Error: Unkonwn file+ message. +QT also tells me that The move could not be opened. The file is not a movie file+.

BUT when I look at the info for the files, the files are the size of QT files. For example, one of the files is 1.5 GB, and my finder calls them quicktime files. Before I start capturing all this footage over, can anyone suggest anyway to convert these files so they will work in FCP? They all at some point did work in FCP. Should I dump all these files from the new drive for good and start over?

G5, Mac OS X (10.4.11), Dual 2 Ghz PowerPC, 4.5 GB DDR SDRAM

Posted on Aug 24, 2009 6:04 AM

Reply
23 replies

Aug 26, 2009 3:21 PM in response to cameragirlnyc

You asked for an easier solution than using compressor. I'm trying to give you one. You've always captured and then used the Remove Advanced Pulldown from the Tools menu.

If you use the Capture preset that does that when you injest and it works, then you will have only one file that is 23.98, it will only be one step, and you won't have to go into another program. Some would call that easier.

Of course, if it doesn't work, then you have something more seriously wrong with FCP. Perhaps a trashing of the preferences might help.

Andy

Aug 26, 2009 6:36 PM in response to Andy Neil

So, I spent most of this morning trying to capture with the pulldown on capture using my panasonic deck, but I kept getting time code break messages. Tonight I borrowed a dvx100, which is what I shot the footage on, and am using that, and it's working much better-most of the clips are going in fine. I still don't know what to do about all Media Performance message I'm getting in regards to hundreds of clips in this 1,500 clip project, but for now...I guess I'm ignoring it. As for the hundreds of clips that FCP doesn't recognize at all, I'm keeping them on my drive for now, but will probably eventually just recapture them and throw out the old, corrupt ones.

Aug 27, 2009 1:00 AM in response to cameragirlnyc

Hi,

About the bad performance warning I earlier said:
This Performance warning is because of a codec FCP doesn't like .... So what are the 'item properties' of these clips (Codec, frame size, frame rate; give us all). Are these settings the one you thought they were? ...

If you know which files have this issue and they do not have the specs you expected then with Media Manager you can recompress them in the desired settings.
To do so select the specific clips in the Browser. Go to File > Media Manager > in there select Recompress and give the desired settings. Select the Media Destination and leave all other checkboxes unchecked/blank.

About corrupt files I earlier asked:
Did you do a check on your drives with Disk Utility or DiskWarrior or any disk-help-software? Are there any warnings? Do post them here before taking any action.

and
What way are the drives formatted? HFS+ (wrong), MAC OS Extended (good)?


Please do answer the questions in this thread. It makes us easier to help you...

Rienk

Aug 27, 2009 1:37 AM in response to Rienk

Rienk wrote:

What way are the drives formatted? HFS+ (wrong), MAC OS Extended (good)?


Please do answer the questions in this thread. It makes us easier to help you...

Rienk



HFS+ is just another way of saying Mac OS Extended.

From the apple Knowledge Base:

http://support.apple.com/kb/HT1604

Summary

This article discusses the Mac OS Extended volume hard drive format, also referred to as HFS+.

Aug 28, 2009 7:05 AM in response to Rienk

Thanks for this- I had to move to another project today, so I will try re-compressing with Media Manager tomorrow. In the meantime, I am recapturing all the clips that don't work at all, even in QT. There are also the clips that work in QT but won't be recognized by FCP, and those I won't be able to recompress with Media Manager, so I guess I'll have to use Compressor.

As for the drives- they are fine. It's not a drive problem.

Thanks!

Aug 28, 2009 7:52 AM in response to cameragirlnyc

Dollars to Doughnuts the problem was introduced when you dragged and dropped QT movies to the other drives from the desktop... it's a no no unless you've also done a sum check during the copy. It's really easy to use media manager to copy the files and it does perform this check, so they never become corrupted. Not only that, it's easy to use in that it will find the files on the source drives no matter where they are and you never miss one because it's in the wrong folder or on another drive or whatever...

I've always used MM to make the copies with and have never seen a corrupted copy result.

Jerry

Media refuses to reconnect- something went awry with QT files

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.