Failed to Save Bin

This is one of the few errors that actually - and correctly - describes the problem that caused the error (in this specific case):

Failed to save bin, BIN_NAME, to
PATH_NAME
Changes will not be saved.
The volume is full.

Sweet, my drive is full.  Well, I'll just click OK, clear some space off the drive, and then save again.

Hrm.  Fairly insistent little bugger, isn't he?

I'll double check.  Okay, yeah, well Avid, there's definitely 63.9 GB free on this volume now.  Maybe you should refresh or something.  Oh, wait, you don't do that anymore.  Thanks... dick.


Oh yeah, remember how I said "In this specific case" up above?  You can also get this same error message due to a bug in Import settings.  Basically, when your import settings are set to a full or read-only drive, Avid will try to import to that drive, even if you specify a different drive to import to in the import dialogue box that appears when selecting "Import..." from the drop down File menu. Even though it tries to import to the drive in the Import settings, Avid will tell you that your other drive is full.  Good times.

The lesson here is to always specify which drive to import to in the Import settings window, and never believe that any choice you make in the pop up dialogue box when actually importing something will have any effect on your import.

Because assuming that Avid doesn't work in the way that it says it does is the only way to make Avid work at all.

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