Mac Error -111 (WhichZone failed (applied to free block))

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 after relaunch.  Take a screenshot of your title beforehand if it's complicated; that way you have a visual reference of what you're trying to reproduce.

Okay, the workaround for the title tool window not closing:  You can click on the desktop to make the Finder active, then click back on Avid, and you should now be able to close the title window (if you tell Avid to save, you'll get the same errors, so you have to choose to discard your title.  The good news is that, once the title window closes, you can save your bins normally and exit Avid without force-quitting.

Relaunch Avid and you should be able to make and save your title successfully.

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

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