Exception: Operation not supported on socket, filename:/Volumes/MediaDriveName/Avid MediaFiles/MXF/ComputerName.1/Creating/creating26


Clicking OK from this super helpful error message gives you the twice as helpful:
Literally twice as helpful.  Hooray.

The good news is that this is an easy fix to a dumb problem.  The problem is that your computer has dropped it's connection to the remote media drive during media creation (in this case, mine was named "TN02_CASTING_MEDIA").  My computer is named "zEDIT01_104B" which is why the media folder in the error message bears that name as well.  The title of this post has been made more generic so you can better understand where the files that you need to delete are living.

The fix to this problem is to quit avid (if it doesn't just crash out on you), dismount and re-mount your drives, delete the creating folder in the directory specified in the error message, and then start creating the media again.

So yeah, the error message is wrong, but the path is correct, so in the scope of Avid errors, this is - as stated - actually super helpful.  Even so, why the hell can't Avid tell that it has lost connection to its drives???

Ahh well, can't win 'em all.

Comments

  1. TJKNovember 29, 2015 at 12:30 AM

    Hey, so the issue may go a bit deeper - if your drive is exFAT formatted, Avid will not export that AAF. My workaround in this case was to consolidate the sequence to a different drive, and then do my AAF export. As far as I've researched, it has something to do with exFAT drive permissions, and AVID. Grrr.

    ReplyDelete
  2. UnknownNovember 30, 2015 at 2:29 AM

    Aaarrgh AVID! I usually use FCP X but I've taken a trip back into the 20th century world of Avid and have been fighting with it for months but v helpful to find this. I have 2 x 4 TB ExFAT drives full of media on a big project and have been really struggling to work out why the AAF export won't work. We wen with ExFAT because we are cross platform and it seemed a more robust solution than going with Paragon or MacDrive. I have learned my lesson. I'll try consolidating to an HFS+ drive before exporting AAF.

    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