Segmentation Fault #1: When Quitting

Me:  Command-Q.
Avid:  Go fuck yourself.

I guess the end result was the same though; the program did close.

Comments

Post a Comment

Popular posts from this blog

Avid Behaving Badly #28: Avid 2023.12 Batch Import just refreshes the old Media Somehow and it's Fucking Stupid

Avid 2023.12 is the first moderately functional Avid since 2018, in my opinion. Titler+ is still hot flaming garbage, but the rest of the NLE mostly works. It only seems to crash when quitting the program, so, like, task failed successfully, I guess, and editing is pretty smooth. You can even import .mov files with transparency again! HOWEVER, there is one MAJOR  caveat to this, and that's that the Batch Import functionality is sometimes completely off its fucking rocker. I'll walk you through what I consider to be a perfectly normal workflow: - I make a graphic. It's gorgeous. Goddamn I'm good at graphics. Holy shit this thing is the goddamn Platonic Ideal of what a graphic should be. - I import it into Avid. Since I'm on Avid 2023.12, and not, say, 2019-2023.AnythingElse, this works. - My producer sends me a note to change the graphic even though she hasn't even seen it yet. Fine. I move the old graphic out of today's renders folder, drag it into the garde...
Read more

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

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 y...
Read more