Avid Behaving Badly #20: LUTs break Multigroup Functionality in Avid 8.8.x and Avid 2018.x

Are you working on the newest, "top of the line," "best," Avid? Do you have multigroups? Are your multigroups completely fucking broken such that you can't select which camera is active in your quad or nine splits, and if you just cut the whole damn thing into your sequence, matching back into it actually takes you to a subgroup rather than the main group? If so, the problem isn't you. It's motherfucking Avid.

More specifically, Avid is crawling its way into the future of tapeless workflow and vast arrays of digital codecs in exactly the same way that a two year old might cling to every available surface in order to avoid being unceremoniously deposited into a crib. Seriously, Avid, why are you fighting the future? Why do you hate progress? Why can't you make LUTs work in any sort of reasonable way?

Wait... LUTs? Color Look Up Tables? Why the fuck are those even being mentioned in a rant about how bad Avid is at future proofing their product?

Well, it has to do with those broke-ass multigroups, and I can't tell you why. What I can tell, with absolute certainty, is that the problem is LUTs. Okay, I can tell you why: Avid's programmers don't give two fucks about you or your workflow and they want you to stab yourself in the eyes as soon as possible, preferably today. Don't do it! I've got a solution for you and, if I do say so, it's really goddamn elegant:

Don't delete that broken group. We're going to fix it with magic. Seriously. Avid has taken us back to the goddamn dark ages where people still believe supernatural spirits control their computers. Or something.

Anyway, go into your group work bin. Select all of your subclips. Right click those fuckers and choose "Source settings..." Find the section for LUTs. It should say something like "Slog 2" (because jesus christ modern workflow is a fucking slog, isn't it. Well named, Sony). Maybe it says "<multiple selections>" or something to that effect. That's fine. Whatever. Delete that shit. No matter what it says, delete it. No LUTs for you!

Save your bin and check out that group. Bam! It fucking works. Because Avid is bullshit and can't figure out goddamn new-fangled nonsense like color look up tables. You're welcome.

Comments

  1. AceMcCollAugust 7, 2018 at 3:16 PM

    Having this exact problem but unfortunately this solution is not working :/
    Specifically, the sequence is matching back to the audio sub-groups. Any solutions for that? Thanks in advance!

    ReplyDelete
    Replies
    1. JuddJanuary 30, 2019 at 10:35 AM

      And you cleared all LUTs from your source subclips while both the bin with the final multigroup and your edited sequence were open? That is odd. Sorry I don't know what could be causing that if the fix here didn't work.

      Delete
  2. UnknownOctober 21, 2018 at 3:06 AM

    Hello! I did find your blog just now, but every day extreme working with fucking buggy sluggish Avid MC (PC) on TV news production I thought to create something like your blog using Elizabeth Olsen`s words: "pizdets suka blyad nahui" (https://www.youtube.com/watch?v=3OtA0JxInkQ) (I am russian). Now I`m your follower.

    ReplyDelete

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

CM_LABEL_NOT_FOUND: tt:3, lnum:3

Image
Well this was a fucked up error. The actual message was:   Timecode not found for clip, 'CLIPNAME' and when you click MORE, you get  CM_LABEL_NOT_FOUND:  tt:3, lnum:3 , which was supposed to convey some sort of information. The internet was no use, because it apparently only cares about CM_LABEL_NOT_FOUND:  tty:3, lnum: 4 , which is something completely fucking different. Let me back up:  I got this error by trying to multigroup some clips.  The group was properly constructed and everything, all subbed out, all the AuxTCs were in place and correct.  Error. So... what doesn't have timecode?  Well, all the tapes were totally normal.  The iso audio was a bitch to deal with because my sound guy doesn't understand how to make polyphonic .WAV files.. let's start there. Okay, so we imported the sound files using Avid's autodetect polyphonic wave groups feature, and it worked, but all three iso clips that resulted had bas...
Read more