Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Firewire Drive Limits

  • Firewire Drive Limits

    Posted by Nate Stephens on December 11, 2007 at 9:48 pm

    I have a 149.75GB FCP movie file that I am trying to back up to a fire wire drive. The FW drive was daisy chained and plugged direct. Tried different drives/manufacturer, etc..New drives. It seems the FCP file on my Medea array transfers the file to the FW drive up to 130.31GB then just sits there, telling you that 12 or 14 more minutes is needed. The drives are not running but the blue bar on the copy window is vibrating but the GB numbers are not moving either. It just site there for hours. Anybody know what is the problem or what is happening. When I use Force Quit to stop the copy process it locks up the Mac, forcing a reboot. I have checked the file and it plays great in FCP..

    Mac 10.4.9 / Dual 1ghz /1.5 sdram / FCP 5.1.4

    Nate Stephens replied 18 years, 7 months ago 2 Members · 2 Replies
  • 2 Replies
  • David Roth weiss

    December 12, 2007 at 5:54 am

    Try running Disk Warrior on that drive. It sounds as though something in the header info on that drive is bot jiving with the OS.

    David Roth Weiss
    Director/Editor
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Business & Marketing, and Indie Film & Documentary forums.

  • Nate Stephens

    December 12, 2007 at 3:43 pm

    David, That is exactly what I did. I had one red light on my Medea Array so I did the Medea Config Dirve routine. Then opened Disk Warrior, did the graph, which looked terrible, ran the repair/replace, rebooted did the graph again and it looks great.

    Last night I opened the FCP movie in FCP, put it into a timeline and left it to export out a new movie to the Fire wire drive. This morning, I checked on it and it hanged up at 85% done.

    I appreciate your reply and thoughts. I thought it might have been due to the version of OS or FCP that I am using or the 169GB size of the file.

    Maybe I should just consider it a cosmic message that this client will be back with more work and does not want to lose her “space” on my array.

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