Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy “Searching for movie data in file….”

  • “Searching for movie data in file….”

    Posted by Anne Holst on January 23, 2009 at 4:33 pm

    Hi there,

    I’ve copied all my media files (including render files, project files etc.) from one to another external hard drive (basically copied the whole drive).

    After reconnecting all the media, some files has gone corrupt.

    When starting up FCP, opening 1 specific project and 2 sequences in that project, a long string of windows pop up with: “Searching for movie data in file-FIN-00000021” and “Searching for movie data in file IV’s.mov”. So it is both Capture scratch files and Render files. When I open the clips is mentions (Like “IV’s”), they play perfectly.

    I’ve tried to delete my preferences with no luck. Any suggestions?

    Thanks!

    Anne.

    Lucy Moon replied 14 years, 1 month ago 11 Members · 14 Replies
  • 14 Replies
  • David Bogie

    January 23, 2009 at 4:56 pm

    q[Anne Holst] “After reconnecting all the media, some files has gone corrupt. “

    They’re not corrupt, they just don’t exist. These are reference movies that you exported and then brought back into your program. But the items the reference files point to are gone, probably render files that were replaced with updates or deleted because FCP assumed they were obsolete.

    bogiesan

  • Shane Ross

    January 23, 2009 at 4:56 pm

    What that error means is that you are missing render files. You have QTRefrence movies that are referencing render files, and cannot work without those render files.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Anne Holst

    January 23, 2009 at 5:23 pm

    Thank you both!

    So I have deleted the sequences that were affected and deleted my FCP preferences, but the problem still occur when opening up FCP. Have you any suggestions on how to overcome this problem?

    Thanks,
    Anne.

  • Shane Ross

    January 23, 2009 at 5:31 pm

    It isn’t a sequence that is causing this…it is a reference movie. When you export a QT movie and make it NOT self contained, it basically makes a reference movie that points to media and render files. THAT is what is causing this…a reference movie.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Bret Williams

    January 23, 2009 at 6:03 pm

    You’ll have to also delete the clips from the bin. AND don’t export and import unless you know exactly what’s going on. Nested seqs were designed to accomplish the same thing without having this issue and retaing tc info. But there are times when an export import is easier. Just don’t do ref movies.

  • Rob Frenette

    May 7, 2009 at 12:39 am

    has anyone had this problem when dealing with red one footage?

    Every time i open up my project it goes through a half hour of “searching for movie data in file xxxxxx.R3D

    So I’m assuming this has nothing to do with render files. It seems like FCP is losing track of my R3D proxy files????

  • Shane Ross

    May 8, 2009 at 9:39 pm

    [Rob Frenette] “So I’m assuming this has nothing to do with render files. It seems like FCP is losing track of my R3D proxy files????”

    Actually, it sounds like it lost track of your MASTER files. The proxies are the files that reference the master footage, and the .R3D is a master file extension

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Nathan Mobley

    January 8, 2010 at 3:48 pm

    I have had the ref movie problem before, but this morning FCP is looking for data from a ref movie that isn’t in the project I am working on. And just to check that I didn’t miss the file in the bin, I closed all projects, quit FCP and relaunced and it is still searching for the files even though it only opens “untitled project”. Any ideas what I can do to fix this?

  • Kristopher Schooler

    June 3, 2010 at 8:47 pm

    I am having the same issue and it is super annoying. It makes FCP load up slower than usual. I would love to find out how to end this.

    I personally do not like to work with reference movies because something always seems to go missing. I helped a buddy with a project that was using them, and now that the project is done and gone, FCP is still trying to find the reference clips when it loads.

  • Ryan Poirier

    June 4, 2010 at 6:13 pm

    I’ve had this exact same problem. A project I was no longer working on was previously loaded via a networked HDD. When I wasn’t connected to that drive I’d get a similar message saying FCP 7.0.2 was searing for a render file for a project I haven’t worked on in weeks, and was not loaded in FCP’s project bins. From a user standpoint there was absolutely no reason FCP should be looking for these files and I couldn’t figure out why it still wanted them.

    Eventually I decided to clean house, Found all my autosave, waveform cache, & thumbnail files and trashed nearly everything save for some recent autosaves. It all added up to a few gigs worth of space just from those files.

    Relaunch FCP. Everything back to normal.

    My guess is one of the waveform or thumbnail files were referencing to the networked drive. Why FCP was still trying to load these cache files I’m not sure. Perhaps it’s default action is to load all files located in these folders. Similar to loading a plugins folder. If it’s there, it’ll try to read it.

    A little spring cleaning can go a long way to keep an efficiently running ship! I’ve noticed FCP launches more snappy now, even compared to before that error message ;~)

    All the more reason to clean out old files. As cruft builds up, you start to loose performance. But it’s usually so slow you don’t even notice it happening. Until FCP has heart attack.

    -®yan P.

Page 1 of 2

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