Creative COW SIGN IN :: SPONSORS :: ABOUT US :: CONTACT US
APPLE FINAL CUT PRO: HomeFinal Cut ForumFinal Cut TutorialsFinal Cut ServerBasics ForumTrainingPodcastFAQ

General Error (34)

Cow Forums : Apple Final Cut Pro

<< PREVIOUS THREAD   •   VIEW ALL THREADS   •   PRINT   •   NEXT THREAD >>
General Error (34)
by Alex Elkins on Jul 22, 2009 at 12:02:22 pm

Hi All,

I'm repeatedly getting a 'General Error (34)' warning whenever I open up a particular project.

Research shows me that General Error (34) indicates a serious disk error. My media is stored on a fibre channel RAID 5 (8 disks), with almost 1TB free. Project files are stored on an internal RAID 1 (2 disks). Mac HD is just for the system and apps, plenty of space free on it. I also have an e-SATA RAID 5 attached (5 disks), although it's not used for this particular project.
I did the usual - delete render files, repair permissions, trash preferences, turn off for 3 minutes etc but was still getting the error.

I then bought DiskWarrior and ran a repair of all of the disks. It looks like a great bit of software, but alas, it hasn't helped for this.

Does anyone have any suggestions? Similar threads seem to come up every few months, but all of the solutions posted haven't worked for me.

Thanks,
Alex Elkins

Respond to this post   •   Return to posts index

Re: General Error (34)
by Dino Vince on Jul 22, 2009 at 2:14:20 pm

Does the General Error come up when trying to open the project, or does the project open? I've gotten these errors occassionally over the years, sometimes from corrupted media files, sometimes from errors in formatting drives. If you can open the project, try saviing it again using a different name. That's worked for me a few times.

Good luck!

Respond to this post   •   Return to posts index

Re: General Error (34)
by Alex Elkins on Jul 22, 2009 at 2:28:36 pm

Thanks for the response, Dino.

Unfortunately saving a copy of the project under a different name didn't work.
The thing is, I can open the project and edit away quite happily. Bizarrely the only detrimental effect I've noticed is that I'm not able to use the 'Make Freeze Frame' command. There are worse things I can think of not being able to do in an edit, but I'm just concerned that the problem may run deep into corruption of files that eventually could cause bigger issues.

Thanks for taking the time,
Alex Elkins

Respond to this post   •   Return to posts index

<< PREVIOUS THREAD   •   VIEW ALL THREADS   •   PRINT   •   NEXT THREAD >>


FORUMSTUTORIALSMAGAZINETRAININGVIDEOS - REELSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

© CreativeCOW.net All rights are reserved.

[Top]