Avid Behaving Badly #10: Avid won't Quit

This is possibly the most ironic of the errors that I've encountered while using Avid.  Imagine, if you will, a program that crashes two out of every three times that you use it.  The only program on the Mac (at least that I'm aware of) that is so poorly coded as to literally require you to reset your PRAM on a regular basis just in order to keep it running.  Imagine that this program is so frustrating to use, so annoyingly buggy, that you just want to quit.

But you can't.

I hit Command-Q and I get the Mac "bonk" sound.  Avid doesn't quit.  Go to the File menu and choose "Quit."  Bonk.

What the fuck, Avid?  Of all the times that you could just crash me to the desktop, instead, you refuse to exit.  You dirty, sneaky, underhanded asshole.

Near as I can tell, this is a bug that only happens in Avid 5, which is good, because no one on Earth should ever go near that flaming piece of garbage.  It's the Final Cut X of Avids.  I'm just sayin'.

There's an easy workaround, but it doesn't allay the fact that this is just a terribly frustrating annoyance of a bug:  Close your project window, taking you back to the "choose a project" launch window.  From there, click the Quit button.  Stupid, stupid, stupid.

I hate you Avid.  So much.

Comments

  1. RicemanNovember 7, 2013 at 8:00 PM

    AVID sure has its moments of offering up some frustration - as do all editing applications. Why dont you upgrade to 7? Version 5.5 is ancient at this point...no wonder it crashes. One of the things I love about MC, and I am on v7.something, is that it DOESN'T crash like FCPX and FCP7 does/did.

    ReplyDelete
  2. JuddNovember 8, 2013 at 9:34 AM

    Hi Riceman! Thanks for the comment!

    If it was up to me, I'd upgrade to 7.x in a heartbeat, but I work for a company, and they rent from a rental house, and between the company being scared to change anything mid-season (or even between seasons) and the rental house only offering tech support for "established" versions of Avid... Yeah. At my old company (posts before September, 2013), we were on Avid 4.0.5.16.

    It's a major problem with the larger TV post production houses; once you find something that works, you're loathe to upgrade because it would mean you've got to re-learn what all of the issues are as well as how to solve them. By all accounts Avid 7 is the most solid version they've put out in a while, but until I work for a company that's new enough to use it, I doubt I'll get to post much about it here.

    ReplyDelete
  3. +++The Videophonic Workshop+++September 10, 2015 at 12:22 AM

    This comment has been removed by a blog administrator.

    ReplyDelete

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

CM_LABEL_NOT_FOUND: tt:3, lnum:3

Image
Well this was a fucked up error. The actual message was:   Timecode not found for clip, 'CLIPNAME' and when you click MORE, you get  CM_LABEL_NOT_FOUND:  tt:3, lnum:3 , which was supposed to convey some sort of information. The internet was no use, because it apparently only cares about CM_LABEL_NOT_FOUND:  tty:3, lnum: 4 , which is something completely fucking different. Let me back up:  I got this error by trying to multigroup some clips.  The group was properly constructed and everything, all subbed out, all the AuxTCs were in place and correct.  Error. So... what doesn't have timecode?  Well, all the tapes were totally normal.  The iso audio was a bitch to deal with because my sound guy doesn't understand how to make polyphonic .WAV files.. let's start there. Okay, so we imported the sound files using Avid's autodetect polyphonic wave groups feature, and it worked, but all three iso clips that resulted had bas...
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