Avid Behaving Badly #25: Avid 2023.8 is a hot fucking mess

My work upgraded me to a brand new, top of the line, Apple Studio M2 Ultra this week.

And you know what that means... We also upgraded to the brand new Avid 2023.8!

Which is so much garbage it lasted exactly one day on my computer. I was crashing every 2-5 minutes. And when Avid 2023 isn't crashing, it's busy not working in any way that you would want it to.

Import no longer works at all.

Alpha channels on graphics largely aren't recognized.

That old workflow where you'd have a graphic, and import it, and then update the source and batch in the new one so you didn't have to manually replace that graphic everywhere you used it? That's out the fucking window because you can't import anymore and alpha channels largely aren't recognized. So now your only option if you want to import to use native media for graphics is a PNG sequence (fuck that; those take hella long to render and it's a mess of files to manage). 

Avid's preferred workflow is that you just link to the graphic file, leave "live link" turned on, and then replace the original file with an identically named file whenever you want to update it.

And that should work, except that isn't how anything used to work, so if you have to go back and open an old project and change something you now have to fucking manually overcut your previously imported graphics files with the new linked graphic. Fuck you very much, Avid.

Also, everything you've heard about Avid Titler + is false. Avid Titler + is actually much, MUCH worse. It's fucking AWFUL. I've seen 3 year olds with a better understanding of user interface design. It's also not actually media anymore, so you can't do all the cool things you could do with the old title tool like put effects on the primary or alpha channel to create custom or animated lettering or shading. Or replace the primary channel with video to create letters filled with video rather than solids. FUCK. YOU. AVID.

6 months ago they did say "we hear you on how bad Avid Titler + is, and we're going to fix it" But since that was FIVE YEARS AFTER TITLER PLUS FIRST DEBUTED, forgive me if I'm a wee bit sceptical.

So yeah, 2023.8 is pure liquified feces.

We back-rev'ed to 2023.3.1. Totally stable to use! Until Avid Titler + crashed me out with a kernel panic. Also 2023.3.1 is no longer available from Avid as of tomorrow. So that's a concern.

These recent versions are so bad that the only thing stopping me from ending it all is I'm not a moron who would end it all over something as dumb as Avid being the worst program to use since some sort of automated program that ends it all. But yeah, you can expect quite a few more posts in the coming days and months as I become intimately familiar with the many new and exciting ways in which Avid has failed to produce a baseline level of functional software.

Weeeeee!

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