Avid Behaving Badly #2: Re-Creating Title Media

This bug annoys the crap out of me. So, because I work in Reality TV, I have to edit in low res.  It's just not financially possible to keep all 2000+ tapes of any given series online in full 1080i HD (even at DNx145).  So when we edit in low-res, we also make titles in low-res.  We use 10:1m for our low-res editing, in case anyone is interested.  When you re-create those low-res titles in HD, an interesting thing happens: Any titles that used kerning are re-created incorrectly.  This is Super Awesome.

Now, when I say re-create the titles, I mean the easy method of marking in to out over the whole sequence, going up to the Clip menu, and choosing the "Re-Create Title Media" option.  That's the one the creates bad titles where kerning is involved (as far as I can tell, only when moving from SD to HD projects).

The solution is also Super Awesome.  You have to manually select each affected title in the Effect Editor, click the "edit title" button in the effect editor window, and then re-save the title (no need to actually change anything).  Doing this for 100+ titles per show will make you want to stab your eyes out with a pair of bananas.  Trust me, you can find a way to make that fruit work.

Thanks Avid, now I'm fucking blind.

Comments

  1. john:PNovember 14, 2012 at 2:43 PM

    Possible work around: I always work in HD, since I don't have anything that will end up SD for final product.

    I switch the format tab to SD for importing / digitizing media, then right back to HD for editing. The titles are rendered in HD, and will look the same when you online.

    NERDS!

    ReplyDelete
  2. JuddNovember 14, 2012 at 9:39 PM

    Hi John! Thanks for the comment!

    Here are my Angry Avid Thoughts (I need an "A" word for "thoughts"):

    While that would solve the title recreation problem, it then causes another issue: All of your titles are beautiful HD, but the rest of your media is crappy 10:1m, which is jarring to the eye.

    Also, god forbid you have timecode burn-in or a graphic overlay for bug placement or something, but those effects can't be lower res than the media below them... now you're rendering 44 minutes of HD timecode burn because of one three second long HD title.

    I guess if your timetable allows for HD renders instead of SD 10:1m ones, and whomever you're delivering to doesn't mind the look, and you have a spacious render drive for all of that HD media, then I'm totally jealous of you.

    Unfortunately, my workflow, timetable, and storage limitations all combine to force me to do all of my offline work in 10:1m, so I'm stuck waiting for Avid to fix their god-forsaken bugs.

    ReplyDelete

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

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

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