Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Deleted renders

  • Deleted renders

    Posted by Jason Levy on March 26, 2009 at 4:11 pm

    We have been having a strange problem with renders getting deleted.

    It’s happened around five times now and each time on a different project.. the editor opens the project and we get the beachball right away for 2 or three minutes. Then.. bang. Back in action but most of the renders are gone. And not just unlinked. Actually deleted off the disk. Bit of a drag as

    Working in ProRes at 720/60

    Kona card. All software, OS etc as fresh as possible up to today. Quad core intel mac with 8 gigs of memory. Sata raid drive.

    Anyone else ever get this? It’s a mystery.

    Jason

    Chris Borjis replied 17 years, 1 month ago 3 Members · 6 Replies
  • 6 Replies
  • Chris Borjis

    March 26, 2009 at 4:15 pm

    Are you running FCP 6.01?

    It has this problem.

  • Jason Levy

    March 26, 2009 at 4:47 pm

    6.0.5

    So you have had that happen to you?

    jason

  • Mark Maness

    March 26, 2009 at 6:29 pm

    [jason levy] “So you have had that happen to you? “

    Yes… Every now and then it will happen mysteriously. Sometimes, its not even an entire render file, just a part of it.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Chris Borjis

    March 26, 2009 at 7:45 pm

    it was fixed in 6.03

  • Mark Maness

    March 26, 2009 at 8:35 pm

    Not exactly….

    Still happens sometimes in 6.05, but now, it seems that instead of losing lots of render files, its only a few and parts of render files. It happens on all three system at our facility.

    _______________________________

    Wayne Carey
    Schazam Productions
    https://web.mac.com/schazamproductions
    schazamproductions@mac.com

  • Chris Borjis

    March 26, 2009 at 9:52 pm

    so it was fixed in 6.03 then broken again in 6.05

    I’ve not seen this problem with 6.03 at all.

    but I do remember what a pain it was with 6.01

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