Avid Hates You

If you're like me, well, first off... Why?  That's weird.  Stop it! Ahem. If your work set-up is like mine, you have to log on to an ISIS server before launching Avid in order to mount all of your media drives.  If you're a responsible editor who doesn't like to crash and lose all of his or her work, then at the end of the day you quit Avid, log off of ISIS, and shut down your computer.  Except, well, that's not really how the end of the day goes.  It's more like you quit Avid, log off of ISIS, select "Shut Down" from the apple menu, tell ISIS to force eject all mounted workspaces, and then your computer shuts down. For me, this is not an isolated incident.  This happens every time . In fact, ISIS failing to log off every drive happens pretty much every time I log out of ISIS, no matter which system in the office I'm using. Let's take a minute to step back and examine the ISIS Client software.  It does two things, which are to securel...

These error messages sometimes appear when attempting to save a title in the Title Tool: The first message, contains the useful information:  "Applied to free block" means that Avid has failed to allocate enough memory to save the title.  Which is dumb.  The title should already be fully stored in memory. This second message is less helpful, though I guess it does let you know that your title didn't save.  So not a total failure. in addition to your title not saving, the title tool window won't close after these messages appear and you can't deactivate it, preventing you from saving your bins (in my opinion, that's the real problem caused by this bug).  Fortunately for you, dear reader, I have a workaround for that.  Your title, however, is not going to save, and you're going to have to restart Avid in order to try again.  So yeah, the good news is that the title tool is pretty basic, so it shouldn't take you too long to recreate your title...

I don't know why I post all of the bus thread pictures; they all look exactly the same.  But whatever, here you go: Pretty sweet. This particular bus thread error was when attempting to import a still image for use as a graphic.  The file is a .PNG, and Avid hates it.  Importing the image into Photoshop and exporting a flat .PSD also failed.  so did a .TIFF.  And a .JPG.  And every other format we could think of.  Testing all of these formats was fucking awesome, because every fail results in this crash, and necessitates a relaunch of Avid.  Hooray for two minutes of sitting around with my thumb in my ass. So what gives?  I can import other files, so it's not the act of importing.  I can import those files to the same drive I'm trying to import this particular file to, so it's not the drive. Okay, what's going on with this graphic?  It's 720p, has transparency, is full-raster 16:9, and - oh.  What the fuck?  Why ...