Avid Behaving Badly #21: Matte Key GFX leave after images

I've upgraded to Avid 8.5.6 over the last few years, and you may have noticed that the number of posts I put in my blog has dropped dramatically. That's good. It means Avid is scared that they might start losing market share to Adobe Premiere, or DaVinci Resolve, or Sony Vegas (okay, definitely NOT Sony Vegas). They've started improving workflow, fixing bugs, and even - seriously - demystifying some of the many many error messages that appear while you work. It's great! It's almost enough to make you think that Avid doesn't truly hate your goddamn guts anymore.

And then shit like this happens:


That is not at all what my graphic is supposed to look like during playback. What it's supposed to look like is this:


Isn't that lovely?

So why the fuck isn't it playing back correctly?

Let's talk about how complicated this graphic is: It isn't. At all. Complicated. It's simple enough to ride the short bus and get a free candy and a pat on the head from the local grocer while he gives sympathetic looks to this graphic's parents.

This is an imported still image for the background, and an imported matte key for the text. That's it. There are no other effects involved in any way. 

The text's top and bottom lines fly on from the left, and the middle line flies on from the right. So what you're seeing in the broken graphic is every single frame of the text drawn on top of each other. That is NOT supposed to happen. These ghost images or after images ruin the graphics.

Compounding this issue is the fact that it does not happen when avid is in draft mode (green/yellow) mode. But it DOES happen in full (green) mode and it happens in any export. Fucking great, right? So the odds are you're editing in draft mode and don't see any problems, export, and discover your graphics are completely fucked, like the year 2020 run through a food processor, boiled, simmered for 2 hours, reduced down to a thick, vile tar, and then injected directly into your veins.

Fortunately, after much trial and error, I was able to fix this stupid fucking nonsense. The problem, as it turns out, is not the graphic at all. It's the background. I don't know why Avid has decided that media created from still images is bullshit that breaks everything, but apparently that's a new feature they added without documentation. So to fix this, you have to match into your background image, right click the source monitor, and create a freeze frame of it. 

Yes, you heard that correctly. I want you to create a freeze frame of your still image. I understand how insanely stupid that sounds. Welcome to Avid, where everything is stupid. Fucking. Everything.

Overcut your still image media with your new freeze frame of a still image media and viola, the ghosting graphics vanish.

On the off chance that any of you work at a BDSM sex dungeon, the next time one of your clients asks you to humiliate them, instead of pissing on them, slapping them, and calling them names, just dress them up like an Avid employee and show them this bug. You're going to have to call the Guiness people to tell them about the tip you get after that.

For crying out loud, Avid, I'm embarrassed for you on this one.

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