Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy ” is missing

  • Bob Flood

    January 22, 2010 at 10:16 pm

    Wow. this post just showed up as a different subject AND by chris borjis! hey lindeblooms wot up widdat!

    Charlie et al

    in the time i took to write my reply, three people answered.

    thats great!

    as for the various theorys why this happens? who knows. I have seen it since we first bought FCP, version 5.0. their seems to be no ryme or reason, no matter what its named, where it is, what its made of, the **** program database just loses track of the file names!

    With version 7 you can rename the clip based on file name, or file based on clip name. Maybe once you reconnect the clips, if you remane the file based on clip name it will stick better.

    Hey Apple!!!! FIx THis!!!

    “I like video because its so fast!”

    Bob Flood
    Greer & Associates, Inc.

    “I like video because its so fast!”

    Bob Flood
    Greer & Associates, Inc.

  • Jeremy Garchow

    January 22, 2010 at 10:23 pm

    [Charlie Key] “It’s that simple? Holy crap!”

    No, it’s not, unfortunately. As Bob says, there’s no rhyme or reason, but I have seen illegal characters cause these issues. It just doesn’t always happen like that.

    Jeremy

  • Jeremy Garchow

    January 22, 2010 at 10:24 pm

    [Paralee Whitmire] “@Jeremy, how do I search out the files individually when it doesn’t tell me what file is offline?”

    There’s nothing offline in your browser? What about your timeline, there’s no clip name in the timeline?

    I should add you click the locate button and force connect it. You have to do this one clip at a time.

  • Paralee Whitmire

    January 22, 2010 at 10:24 pm

    Thanks for all the super fast responses everyone. I have given up on a fast fix and decided just to click the file in timeline, then file, reconnect. It’s so annoying!

    At least now I know that it could be because I originally created the file on a different computer. I probably deleted some super important file in the move to the new computer.

  • Charlie Key

    January 22, 2010 at 10:25 pm

    “Wow. this post just showed up as a different subject AND by chris borjis! hey lindeblooms wot up widdat!”

    There is something sinister about this bug, it even follows us to the forums. It knows where we live!

  • Andy Mees

    January 23, 2010 at 1:58 am

    a useful tool to have in your bag at times like this may be the COW’s feisty friend Bouke Vahl of VideoToolshed’s FCPReconnect
    https://www.videotoolshed.com/?page=products&pID=41

    am not 100% sure it would resolve this particular issue but perhaps Bouke will comment

  • Matt Lyon

    January 23, 2010 at 5:45 pm

    Kinda late to the party here:

    I’ve also seen this happen in many projects over the years, possibly even going back to FCP 4 (but my memory is hazy). Like everyone else, I can’t narrow the issue down to any kind of repeatable situation. It’s happened with internal drives, external drives, still images, DV media, etc.
    Unmounting an external drive accidentally while a project is open has definitely been the culprit in one case. And I think that sharing projects between computers makes it more likely to happen.

    Of all the problems with FCP, I’d say this one keeps me the most paranoid! Good workflow can minimize the issue: have clip names match files names ALWAYS (but in reality not always possible, I know)… this makes reconnecting much easier. Using very conservative naming conventions helps too. Letters, numbers and underscores only if possible! (not even white spaces).

    Thinking back to the last couple times this happened to me, I realize both cases involved sharing work across different machines (that DID NOT share the same storage). Maybe this is significant? What have other people’s experiences been?

    Matt Lyon
    Editor
    Toronto

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy