Bus Thread Error #3: When Importing a Still Image

I don't know why I post all of the bus thread pictures; they all look exactly the same.  But whatever, here you go:

Pretty sweet.

This particular bus thread error was when attempting to import a still image for use as a graphic.  The file is a .PNG, and Avid hates it.  Importing the image into Photoshop and exporting a flat .PSD also failed.  so did a .TIFF.  And a .JPG.  And every other format we could think of.  Testing all of these formats was fucking awesome, because every fail results in this crash, and necessitates a relaunch of Avid.  Hooray for two minutes of sitting around with my thumb in my ass.

So what gives?  I can import other files, so it's not the act of importing.  I can import those files to the same drive I'm trying to import this particular file to, so it's not the drive.

Okay, what's going on with this graphic?  It's 720p, has transparency, is full-raster 16:9, and - oh.  What the fuck?  Why is the color space RGB instead of 601 or 701?  Goddamn graphics department doesn't know their color space has to be different for television.  Did I mention this is the network's graphics department?  Awesome.  Remind me to tell you about the time they gave us graphics that weren't title safe, and then rejected our color-corrected master tapes of said episode because - seriously - the graphics weren't title safe.  But I digress.

The color space still shouldn't fuck up Avid.  But lo - when I change it to 601 in photoshop and re-save the graphic, it imports just fine.  As it turns out, something about this particular version of Avid (4.0.5.14), 720p stills with transparency, and RGB color space just makes the world end.  So stupid.

Anyway, an easy fix - though admittedly exasperating to test.

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