Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Render Issue/Question?

  • Render Issue/Question?

    Posted by Steve Cohen on November 6, 2007 at 2:02 pm

    I’m rendering out a project that is pulling footage from 5 different drives on my SAN.

    I have my 6th drive set as my capture scratch disk, but for some reason Final cut is giving me an error when I go to render the project. The error is something like ” File error: the file is locked.:

    When I set my other 5 drives to write access in my Fibre Managemenrt software (FiberJet), the project will render fine.

    My issue is I don’t want to tie up those other drive with write access, when I actually just need to read from them.

    Other stations need write access to those drives for thier projects.

    Steve Cohen
    Editor
    O2 Media Inc.

    Steve Cohen replied 17 years, 11 months ago 3 Members · 4 Replies
  • 4 Replies
  • Paul Escandon

    November 6, 2007 at 3:26 pm

    Try trashing everything in your render files folder off the 6th drive that isn’t working and rendering again. See if that yields any better results.

    * * *
    Paul Escandon
    Producer | Director | Editor
    Apple Certified Trainer – Final Cut Pro
    Oremus Productions
    http://www.oremusproductions.com
    – –
    Adjunct Professor of Media
    John Paul the Great Catholic University

  • Steve Cohen

    November 6, 2007 at 4:39 pm

    Thanks Paul.

    I just finished rendering out with my other drives set to write access.

    I’m not about to trash the render files and re-render a 3 hour render just to test something out, but this has happened in the past and now I know what to try when it happens again.

    Steve Cohen
    Editor
    O2 Media Inc.

  • Jeremy Doyle

    June 6, 2008 at 3:06 pm

    Did you ever get this resolved? We are experiencing this exact problem and wondering if there is a fix.

  • Steve Cohen

    June 6, 2008 at 6:09 pm

    Sorry Jeremy; I never figured out what was casuing it.
    It just kind of fixed itself.

    Wish I could be more help.

    Steve Cohen
    Editor
    O2 Media Inc.

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