Avid Behaving Badly #7: Failure to Draw Audio Data on Track 24

This one is just asinine.  For no reason that I can think of, Avid simply won't draw audio data (waveform or energy plot) on Audio Track 24.  Tracks 1 through 23 work perfectly well, but track 24 is total bullshit.

Anyway, simple workaround:  Use a different audio track.

Protip:  You can add a specific audio track by hitting Command + Option + U (and a specific video track with Command + Option + Y).  Now you know, and knowing is half the battle.  The other half of the battle is killing people.

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

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