Avid Behaving Badly #9: Autosequences

Dear Avid,

Thank you for taking the time to read this letter.  I know that you're very busy fucking up someone else's job, career, and possibly life, and so I truly appreciate you stepping away from whatever catastrophe of television horror you were in the process of creating to listen to my humble question.

Why doesn't autosequencing work?

If timecode is a thing, and sorting by timecode is a thing, then why the fuck, when I sort my clips by goddamn timecode, do you sometimes just give me an autosequence of them that is fifteen fucking days long?!?  And then, when your shitty little single-processor-using compu-brain goes and makes a fifteen day long autosequence for no fucking reason, why do you even bother to alert me that the playlength toggle needs to be turned on?  I mean, if you know it needs to be turned on, why don't you just go ahead and turn the damn thing on already??

But I digress.

They say that the definition of insanity is repeating the same actions and expecting different results.  Autosequencing, then, is proof that you, Avid, are driving me fucking insane, because the way to fix a bad autosequence is to delete the bad sequence and then autosequence the exact same clips in the exact same order as before.

Like, hypothetically, if I have one clip that starts at TC 08;12;36;14, one that starts at 12;44;40;02, and one that starts at 23;11;14;00, why in the fucking pig-footed hells would you think that the last clip should go 32 HOURS before the first clip in the autosequence?  Oh, you don't think that this time?  That's good news.  I guess everything is totally fine and we can all go home now.  Dick.

Warm regards,
Judd

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