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 34

  • General Error 34

    Posted by Heidi Perkins on August 13, 2012 at 10:41 pm

    General Error 34…I have read all the postings regarding this error…I have no in and out points selected…I have disk space…BUT EVERYTIME I LAUNCH MY PROJECT I GET THE “GENERAL ERROR 34” MESSAGE…I have made a new sequence and pasted my edit–still get the message. When I log to digitize I get no reel name or in & out points…so when I do a batch digitize it just searches for the tc. I also opened a completely different project and get the same General Error 34 message.

    Please help!!

    Thanks,
    Heidi

    Heidi Perkins replied 13 years, 9 months ago 2 Members · 2 Replies
  • 2 Replies
  • Anna Ingenthron

    August 18, 2012 at 12:15 am

    I’m going to suggest a few different things, as this error can indicate basically anything.

    -What is most likely is you have a corrupt file somewhere in your project. One way of checking is stringing out all your materials in a sequence and trying to render. The clip that won’t render is corrupt. You will need to get rid of it and bring it back into the project. I suggest converting from raw again if it’s video or re-exporting an aif from QT7 if it’s audio. In some way, you need to refresh the file before bringing it back in.

    -Quit FCP and delete all of the files in “Render Files.” (If you don’t want to re-render your sequences, try the other options first.) Be sure to empty your trash before re-opening FCP.

    -Quit FCP and trash your preferences. This is a great catch-all for FCP errors. Your preferences can be found here: [Your system username]>Library>Preferences>com.apple.FinalCutPro.plist Empty your trash and reopen FCP.

    -Restarting your whole system often helps with these mysterious errors as well. FCP will bug out if the computer or program has been up and running too long.

  • Heidi Perkins

    August 22, 2012 at 5:56 pm

    Thanks!! It turns out it was one corrupt file. A shot that was only 10 seconds.

    Heidi

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