Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Stubborn “General Error” message at end of QuickTime output.

  • Stubborn “General Error” message at end of QuickTime output.

    Posted by Scatcat425 on October 17, 2005 at 7:57 pm

    Can anyone help me? I’m experiencing a stubborn General Error message at end of QuickTime output and don’t know what to do.

    Trouble exporting one reel (of five) to QuickTime (other 4 reels from same sequence exported okay). Each is about 20 minutes.

    Appears to write entire file, then “General Error” message. No file created. No other information given.

    Quadruple checked that all was rendered, mixed down sound, and at someone’s suggestion, I even tried removing all photoshop graphics. Same error. Same error. Same error. Made fresh reel sequence three times. Same error.

    Any ideas? Deadlines looming and no way to get clean output, even straight to tape b/c frames dropping in playback.

    Using Final Cut 4.1.1; Quicktime 7.0.1; 1GHz G4 powerbook (1.25 GB RAM); external firewire hard drives.

    Thanks for any help in advance!
    Anne

    Michael Peele replied 20 years, 6 months ago 4 Members · 4 Replies
  • 4 Replies
  • Arty Gold

    October 17, 2005 at 10:44 pm

    hi anne…
    not an expert here…but i do know of this problem.

    with my stuff when i get that message it usually means that i ran out of space…actual hard drive space…
    try saving the quicktime to another drive

  • Jerry Alto

    October 17, 2005 at 10:51 pm

    Ann- Had a similar situation on a 28 min QT movie. We finally figured out that it was a corrupt rendered graphic. To find the problem file we broke the segment into about three equal parts on new timelines and exported in three chunks and narrowed it down from there. Tedious but we found the culprit. Ours was bailing from the export (General Error 34) at the same point every time (about 1/4th of the way thru the export). And guess what, the bad file was 1/4th of the way through the timeline. My guess is that your problem file is right at the end or close to it. Hopefully an easy fix.
    Hope this helps.
    Jerry

  • Scatcat425

    October 17, 2005 at 11:58 pm

    Jerry –

    Thanx SO MUCH for the suggestion — seems to have been a corrupted slow-motion render file. Splitting up the reel into smaller and smaller sections helped isolate the problem — and was not as time consuming as I feared. After fixing, the reel exported fine.

    Yay.

    A.

  • Michael Peele

    October 18, 2005 at 1:58 am

    I find that general errors of this sort can often be solved by trashing all relevant renders using render manager.
    mike peele

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