Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Captured files – video only – kinda’ time sensitive

  • Captured files – video only – kinda’ time sensitive

    Posted by Jeff Markgraf on January 26, 2010 at 3:10 am

    Hello Cows.

    Odd problem that cropped up a while back and is about to cause a major headache.

    I’m capturing DV files and getting a “-v” added to the file name on disk. (For example: “test-v.mov” when the clipis logged and loaded as “test”) They play fine in the project, but there’s no audio when played via Quicktime or when imported into a different project.

    Details:
    FCP 5.1.4 on MacBook Pro (Intel, first generation, so several years old). 2 Gig RAM
    1 LaCie 1Terabyte (striped RAID 0) via eSata.
    1 Blackstar Pro 400 Gig (from Melrose Mac), also via eSata.
    Capture device varies from consumer camera to JVC BR-DV3000 deck.

    This is a relatively new problem, and I’m about to start loading lots of tapes to an archive drive for a client. Obviously, no audio except within the original project is a problem.

    Any ideas? Did a search, couldn’t find this problem.

    Rafael Amador replied 16 years, 7 months ago 5 Members · 7 Replies
  • 7 Replies
  • Rob Grauert

    January 26, 2010 at 3:20 am

    hmm…I could be wrong, but I think that means your hard drive is not formatted correctly. Check Disk Utility and make sure it’s formatted for Mac OS Extended

    Robert J. Grauert, Jr.
    http://www.robgrauert.com
    command-r.tumblr.com

  • Jeff Markgraf

    January 26, 2010 at 3:25 am

    Sorry – forgot that part. Both drives are Mac OSX Extended. 1 is journaled, the other is not. I think the 2 Gig split files show up as -1, -2, etc.

  • Shane Ross

    January 26, 2010 at 3:37 am

    Then you have a file size limit set in the System Preferences. Unchecked that.

    Shane

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

  • Jeff Markgraf

    January 26, 2010 at 3:39 am

    Well…trashing the prefs seems to have fixed the problem. So I guess the immediate panic is over. But I would like to know what people think about this behavior. Anyone else had this happen? Any thoughts on just what went wrong?

  • Jeff Markgraf

    January 26, 2010 at 3:41 am

    Hi Shane. That was one of the first things I checked. I did some tests and it happened on each 3-5 second test capture I did, whether “capture now” or log & capture. See below, though, where trashing the prefs seems to have fixed the problem.

  • Jeremy Garchow

    January 26, 2010 at 4:10 am

    You fed Gizmo after midnight. No other way to explain it.

  • Rafael Amador

    January 26, 2010 at 5:01 am

    These AV files always show when the system, for any reason, is unable to write directly the files on the HD.
    The system write in a temporal memory and these AV are the remaining of the process.
    That’s what I think. No legal proves about.
    rafael

    http://www.nagavideo.com

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