Avid Behaving Badly #23: Exporting 4k 23.97 files that have been converted to 1080p 23.976 fails after about 6 minutes

"What the fuck does that title even mean," you're probably wondering.

Well, I'll tell you: It means Avid is fucking stupid. Not that this fact should surprise any of my long-time readers.

Let me lay out the scenario. I'm on Avid 8.6.somthing. My production team shot on a brand new Sony Fancycam 9000. They shot in 4k. The "24P" setting on this camera is actually, apparently "23.97." Where did the 0.006 go? No one fucking knows. Maybe they though that because 29.97 was a thing, 23.xx should be rounded to 23.97 as well. I couldn't tell you.

What I can tell you is that when I AMA linked the source footage, transcoded it into an XDCam 35 codec (which is standard fare for my particular project needs right now), and then tried to export it, the export fucking failed. Not in a nice, polite, "here's an error message for your troubles and also so you can screenshot it and use it in your blog posts because we appreciate the value you add to the Avid community" sort of way, either. Nope, Avid just fucking sat there. For hours. Slowly ticking up the time elapsed and the time remaining.

So I had to force quit.

I'll save you the awful details of the next two full working days that I spent troubleshooting this particular bugaboo. The important take away is that I kept my cool and they'll never find the body.

Here's what I learned: Transcoding is stupid. Avid is stupid. I am stupid for using Avid. But mostly transcoding is stupid.

IF I transcode the footage and "convert to project framerate" (still 23.976, which is ostensibly identical to the source footage), then the resulting files will not export.

If I transcode the footage and "keep original framerate" (23.97, per the sony codec, but since that's a weird thing avid doesn't support, also 23.976 per avid's framerate column when viewing the final clips), then the resulting files export just fine.

Fuck You, Avid. May the STDs of a thousand murderers find solace in your tainted private areas.

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