Avid Behaving Badly #24: Importing 60 fps footage stutters during 23.976 playback

 So I work in Development now, and one of the things we do in Development is steal from other shows. Not like "concepts" or whatever, but literal footage. That's how it works. You go to the head of a network and say, "We have a brand new idea for a show that's never been on TV before!" And then they say, "Show me the teaser trailer for this thing that you literally just told me doesn't exist!" And then you say, "Were you not paying any goddamn attention? That doesn't exist!"

That's not true. What you actually say is, "Why yes, I will. Our trailer is right here, and our amazing editor, Judd, made it, with his bare hands, because he's literally the BEST."

But how did I make it? By screen capturing a bunch of other shows that had scenes or lines I wanted, and I stitch them all together in my little timeline with a bunch of music that isn't licensed because it's never going to air and no one will ever know (except I'm gonna blog about it later) and that's how the sausage is made!

Except this fucking sausage sucks ballsack, because whenever I screencap my brand new sick as fuck Macbook Pro Max, and I get a smooth as butter 60 fps capture with crystal clear picture that's so clean you could drink it, and I import that beauty into Avid, Avid shits the goddamn bed and plays back a stuttering mess of hot garbage that I wouldn't show to a blind person.

Until NOW!

Because I have discovered that while importing the footage doesn't work right, AMA linking to the footage and then transcoding it (which should be the exact same fucking process as importing, Avid) works perfectly! And the end result is a gorgeous 23.976 conversion of my 60 fps screencap that is suitable to use when demonstrating how a thing that doesn't exist will look if only you give us enough money to make it exist.

Thanks for coming to my TED talk.

Comments

  1. MateusNovember 9, 2022 at 4:57 PM

    I hate everything about this company, from the logo to the mediocre user experience. And this comes from a guy who learned to love Final Cut Pro X after years bumping my head on the wall.

    ReplyDelete
  2. annie rauwerdaJanuary 3, 2023 at 2:01 PM

    Hey Judd!!! This isn't related to the blog post, but I'm wondering if you or anyone you know anyone at Lighthearted might have copies of seasons 1-5 of Next, the MTV show! A few people online are worried that they may be lost. I can't find copies anywhere! Send me an email at annierau at umich dot edu if you can help!
    Thanks!!

    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