Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy General Error rendering woes

  • General Error rendering woes

    Posted by Stacy Formby on December 17, 2007 at 4:44 pm

    Boy, do I need some advice. I’ve been having horrible problems trying to render two different projects I’m working on (Pro Res, 1920×1080). When I try to render I get a General Error after a minute or so of rendering. Sometimes, if I quit and restart, what has been previously rendered has no turned red and needs rendering. Things I’ve tried: 1) trashing prefs ad nauseum 2)sending render files to different drives 3) media managing project and then trying to render 4) running Disk Utility on drives 5) repairing permissions.

    I was having this behavior under 6.0.1, so I upgraded to 6.0.2. Same problem. I can’t export a by ref file either. Same error.

    Any suggestions??

    Paul Dickin replied 18 years, 4 months ago 3 Members · 2 Replies
  • 2 Replies
  • Hamish Lyons

    December 17, 2007 at 7:01 pm

    in times I have encountered this general error it has often come down to corrupted media. I would try rendering in sections to isolate the area, then re-inserting fresh media from source. also try cutting and pasting the whole cut into a fresh sequence. if you can isolate the issue clip and these dont work possibly re-capturing. otherwise try changing your capture scratch, even in user prefs change the real-time audio render to 12 tracks can help… if you are working on a san it can also be permission areas
    hopefully one of these might help…

  • Paul Dickin

    December 18, 2007 at 8:27 am

    Hi
    In my experience (somewhat limited. thankfully, and not with ProRes) , one cause of this is using source clips with either a dodgy frame rate, or with ‘long’ frames – which cause the frame rate not to be bang on.
    The cure in my situation has been to ‘fix’ the frame rate of the affected clips, by conforming them to a stable frame rate, them reimporting them to the project, whereupon the problem has disappeared.

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