Another Re-Linking Thread...But a Little Different

This may be helpful under the new circumstances per the crashes:

www.digitalrebellion.com

Hi Talonhead
Sounds like you somehow messed up the pathway to the proper folder/file structure. FCPX is supposed to follow the ionode ID for the files and you should be able to simply point to the volume(drive) that the file is in and FCPX should find it. That's how it is supposed to happen.
Since you moved files via the Finder, my guess is that when you either created a new drive with a different name or in moving the files, FCPX corrupted the file IDs or some of the hidden files did not get moved. Installing the new drive and then using the "Consolidate" button in the Library Pane would have been a better way to go IMHO.
Also CCC is very good about making sure all of the hidden associated files get copied, so that would have been another way to go.
So starting from the beginning, Is the new "Media" drive formatted for MacOS Journaled? If it is in a different format this could be an issue.
Do you still have the old drive with the Media on it or did you erase that drive?
Have you tried to open the project from a "Saved version"?
You might try to "Consolidate" the files anyway and see if FCPX will locate the missing files. This might work if you have the old drive mounted.
Your XML file may give you a glue to the former file structure and path, if you then recreate this pathway exactly, this may help relink the files. Coincidently, the latest FCP radio podcast with West Plate from Automatic Duck talks about XML and importance of file paths. Link … fcpradio.com/episode013.html

As to Audio files, were they always attached to the video i.e. audio from cam or were they separate files added to the project?

Hope this helps, Greg

Darren
Your screen shot showing the AU validation error may in fact point to issue. I think you corrupted some files and the AU issue is definitely related to audio. The question is whether these are current versions or are they outdated versions brought along with say Migration Assistant while upgrading OS versions. You would need to check the install date of the AU units in question.

You may need to re-install FCPX. This should reinstall any corrupted resources/files.

Since FCPX crashed, you have some additional troubleshooting aids. In the Console app (Utilities Folder) you can see Diagnostic Reports and this should point to what failed. You will also see why FCP issued Red Flags, but that is a bit complicated to find.

There are Diagnostic Reports also in the System>Library>Logs>DiagnosticReports (or in Crash Reporter)

Finally there is EtreCheck that may or may not flag a problem. etrecheck.com/#about
EtreCheck, you download the app and run it, uses UNIX commands to check the system and apps, and then provides some plain english translations to otherwise confusing system reports. Never had an issue running it, but it doesn't always find the issue either, but it is free so why not try.

I think you just corrupted files while moving via Finder. Once you get all the underlying app files and the media files in place, then I think you should be able to relink and be good to go. The saved and last saved version (current version) is the database of all the edit decisions you make backed up every 15 minutes. So you should be able to apply them once FCPX files are found/linked.

Please make back-ups now and often.

What a PITA eh

Best of Luck, Greg

VidGreg wrote: Darren
Your screen shot showing the AU validation error may in fact point to issue. I think you corrupted some files and the AU issue is definitely related to audio. The question is whether these are current versions or are they outdated versions brought along with say Migration Assistant while upgrading OS versions. You would need to check the install date of the AU units in question.

You may need to re-install FCPX. This should reinstall any corrupted resources/files.

Since FCPX crashed, you have some additional troubleshooting aids. In the Console app (Utilities Folder) you can see Diagnostic Reports and this should point to what failed. You will also see why FCP issued Red Flags, but that is a bit complicated to find.

There are Diagnostic Reports also in the System>Library>Logs>DiagnosticReports (or in Crash Reporter)

Finally there is EtreCheck that may or may not flag a problem. etrecheck.com/#about
EtreCheck, you download the app and run it, uses UNIX commands to check the system and apps, and then provides some plain english translations to otherwise confusing system reports. Never had an issue running it, but it doesn't always find the issue either, but it is free so why not try.

I think you just corrupted files while moving via Finder. Once you get all the underlying app files and the media files in place, then I think you should be able to relink and be good to go. The saved and last saved version (current version) is the database of all the edit decisions you make backed up every 15 minutes. So you should be able to apply them once FCPX files are found/linked.

Please make back-ups now and often.

What a PITA eh

Best of Luck, Greg

Well Greg, to update this, I got the Info window from popping back up by deleting all "com.apple.audio" files in the Library. then re-booted. Boom...Problem solved.

Second, I did remove (not delete) the "flexolibrary" file in the Library folder. No help there.

So I'm basically left where i was before...not able re-link.

I don't have the older, original drive anymore. It got formatted (OSX Extended as with all my other drives as usual) and moved into another machine. I do backup all the time (in some machines I have backups of backups) but this situation was timed perfectly to catch me with my pants down. In blind hindsight, I should've moved the files to the new dive THEN checked in with FC to make sure it was happy (instead of making a new TM drive at the same time). As I had told Ben, should've would've could've.

Sure...there were better ways to move files, but I really didn't think it was necessary to do with a simple file moving. Finder should be alright!! But it wasn't as far as FC was concerned. Again, live and learn.

I appreciate your input folks. Greg, any more thoughts now on this?

Just for the heck of it, you could try dragging one of the stubborn files into the event browser where it's supposed to be and see what happens.

MarkNelsonMovies wrote: Just for the heck of it, you could try dragging one of the stubborn files into the event browser where it's supposed to be and see what happens.

If you basically mean re-importing into the project, I tired that early on. It works...but I lose my edits. Ouch!

Update though....this is the closest I've gotten so far. I opened up a saved version from the FC library and guess what...was able to re-link! All my ins and outs were retained as well! The saved version at this point, is just fine for me to work with.

Now, that said, I suppose all I would need to do is drag the clips into the Timeline where they are supposed to go. But the problem is, I can't get just the ins and outs of the clip I'm dragging to replace the "bad clip" in the Timeline. I've done "replace from end...start...and replace. None makes it work correctly. "Replace from start" for example, I guess means its going to replace using the start of the actual clip...not the start of the marked range of the clip (which is what I need it to do).

I feel pretty stupid, but I've never been down the road of having to "repair" a project so badly. :huh:

You definitely hit some very weird error with your finder copy. We copy entire project folders (we use externally-linked libraries only) with just a finder copy all the time, and have not had problems relinking. So theoretically, a simple finder copy should work well.

One thing you could try is create a new library and reimport all your clips. Dupe your old library (to be safe). Then, with your duped old library, make a new event and move your timeline and ONLY THAT TIMELINE into the new event. Then, with that old dupe and the new library open, drag that newly created event into the new library that has all your clips. This is actually how you copy timelines back and forth without duplicating clips (it's undocumented!), but it may work for you. Keep in mind that I've not tested this, because usually when we do this, it's because two or more editors are using dupe libraries with the same master clips in them, and it's a way of passing timelines around without duplicating the clips in the browser.

haysoos123 wrote: You definitely hit some very weird error with your finder copy. We copy entire project folders (we use externally-linked libraries only) with just a finder copy all the time, and have not had problems relinking. So theoretically, a simple finder copy should work well.

One thing you could try is create a new library and reimport all your clips. Dupe your old library (to be safe). Then, with your duped old library, make a new event and move your timeline and ONLY THAT TIMELINE into the new event. Then, with that old dupe and the new library open, drag that newly created event into the new library that has all your clips. This is actually how you copy timelines back and forth without duplicating clips (it's undocumented!), but it may work for you. Keep in mind that I've not tested this, because usually when we do this, it's because two or more editors are using dupe libraries with the same master clips in them, and it's a way of passing timelines around without duplicating the clips in the browser.

Wow...that's something I'll need to chew on for awhile. Top secret stuff to try! Thanks Haysoos.

Leave it to me to find holes in the Finder/FC. I didn't think it wold be a problem either...just didn't work. This is why I don't go to Vegas.