Avid Behaving Badly #14: The Leading Indicator that Avid 6.5.4 is about to Crash is that the Attic Stops Working

The title of this post is factually correct.  The thing that is supposed to save you in case of crash is the most likely thing to stop working prior to you actually crashing.  I mean: what the flying fuck, Avid?  This is the one single part of your program that absolutely fucking has to work 100% of the time!  Here's how it plays out at my office:

Producer:  "My Avid Crashed and now my work is missing."
Me:  "When was the last time you worked on this?"
Producer:  "I've been working on it all day.  I guess I crashed at 7:30 pm, so ...  7:30 pm."
Me:  "The last attic save is 1:45 pm."
All:  "Fucking Avid."

Sometimes "Producer" is even "Editor" which is a rare substitution in lost work issues, but in this case I've see it with my own damn eyes.

--

So what can we do to avoid the fact that Avid is a flaming piece of feces, fresh from the anus of Graal the World-Eater?  There's no fixing this bug through work-arounds.  Once your attic stops, you're very unlikely to notice it stopping, and you're equally unlikely to notice any other issues until you get that wonderful Bus Thread Error: 0x0 message.  All I can do is offer some Best Practices:

1)  Back your work up.  It's not enough to save your bin on the regular (even though it should be).  You should have a second backup bin that you open, copy your work into, and immediately close.  Think of it as a personally curated attic if that helps.
2)  Quit and relaunch Avid every now and again.  This seems to reset the internal "when should I fuck everything up" timer that has been a standard feature since Avid 1.
3)  Don't be a moron.  I can't believe I have to say this, but if you are aware of this issue, you should plan accordingly.  You're not a special butterfly who won't have Avid crash on you.  Avid hates you, and me, and fucking everyone.  It even hates adorable little puppies with big floppy ears.  You aren't safe, so plan ahead and back your shit up!

Comments

Post a Comment

Popular posts from this blog

How to Reset your PRAM and Delete your Site Settings

After two years, it has occurred to me that I have been remiss in my duties.  Up until now I've failed to mention the most basic troubleshooting techniques for dealing with Avid:  Resetting your PRAM and Deleting your Site Settings.  Seriously, what's wrong with my brain? Basically whenever you're getting weird errors, or multiple bus thread error crashes in a row, or "you can't write to drive X" message when pretty fucking clearly you have write permissions, the problem isn't you; it's Avid.  That's a shocker, I know, and wholly unexpected, but the fact of the matter is that Avid is the only program I've ever used that required regular resetting of your Mac's PRAM (Parameter Random Access Memory).  Avid is also one of the rare pieces of software that corrupts it's own fucking settings.  Seriously, how is that even possible, Avid?  you generate  the settings on launch, so can't you do a goddamn checksum to make sure the existing o
Read more

Exception: SYS_ERROR, OSErr: -5000

Image
Dear ISIS:  I love you.  You're great.  None of the bullshit file count limits of Unity, I can fill your drives to 100% without issue, you have automatic redundancy built into your RAID storage, your control panel is .html based and runs in my browser, and you work over ethernet instead of requiring fiberoptic cable.  You're pretty fucking swell. But there's this one thing you do sometimes that reminds me you're made by Avid.  See, it's like this:  When I create a user that has write access to a drive, and I log in as that user, I goddamn expect to be able to write to that fucking drive. Instead, Avid gives me this: What the fuck is that supposed to mean, Avid?  You're blaming the goddamn system OS for the fact that ISIS mounted my drive with incorrect permissions?  Why the christ would you do that?  Wait, wait - hang on while I get out my goddamn dictionary of What the Fuck OSErr: -5000 means. Okay, yeah, this is a write error.  It means I can't wr
Read more

File 'Avid_MediaFiles' not found.

Image
This is a great error.  It's great for a couple of reasons.  Firstly, the problem isn't that "Avid_MediaFiles' can't be found.  That's the folder on your media drive named "Avid Media Files" and it's pretty goddamn easily found by both you and Avid.  No, the real problem is that a file *inside* Avid Media Files can't be found.  Which file?  Good question.  A database file.  What this error message should really say is: File 'msmFMID.pmr' not found. OR File 'msmMMOB.mdb' not found. Or the error message could be actually helpful and say: The File 'msmFMID.pmr' which should be in path 'MediaDriveA/Avid Media Files/MXF/Ingest1' cannot be found. You know, something actually fucking helpful.  But no.  No, this message basically just says that Avid lost something, it isn't sure what, and it sure as shit isn't going to let you save any bins until you fix the problem.  Also, opening the Med
Read more