Sony Behaving Badly? - There is no Avid-compatible LUT for Sony's S-Cinetone Camera Settings

 If you work in a professional environment, you're probably used to production DPs insisting on always using the newest, fanciest, most whizz-bang gadgets on the market without ever checking to see if the people they're delivering footage to can actually work with what they're shooting. Usually, the result of this is a few hundred (or thousand) bucks extra cost to post for buying card readers and codecs that aren't pack-ins with Avid.

Ahh, but now there's Sony's "new" (it's a couple years old, actually) S-Cinetone camera setting. And it's a motherfucker. First, I appreciate what Sony is trying to do. They're combining color look-up-tables (LUTs) and gamma information into a single setting on their cameras in order to get their digital video to look as rich and deep as film. Kudos, you spectacular assholes.

What Sony did not do, and which they absolutely fucking should have done, is produce LUTs for editing suites that are able to work with the new S-Cinetone look. I mean, they made some LUTs. They're just not for Avid. Because fuck Avid, right? I mean, yeah, I get it, and yes, fuck Avid, but NOT LIKE THIS! You cannot tell Avid to go fuck itself by refusing to do the thing that is literally your job and hoping that Avid will pick up your own shitty slack. Because if you know anything about goddamn Avid, you know THEY WON'T.

And they didn't. Pick up Sony's slack. At all. Avid, as one should expect, did not do shit. Avid did do something though, and that something was fuck all.

Now, you can go to Sony's website and see that they have some LUTs.

https://pro.sony/en_ME/technology/professional-video-lut-look-up-table

But none of those are for S-Cinetone. Why? Because S-Cinetone isn't strictly a LUT. It's a LUT+Gamma setting. So which LUT to use???

Answer: None of those.

Or you could go to Sony's other website and see that they have color profiles made specifically for S-Cinetone:

https://sonycine.com/resources/luts/

But most of these are .art and .cube files for use in their cameras and are NOT compatible with Avid. At the verrrry bottom of the page, there are three actual LUTs, but they don't solve the problem, because it's totally unclear which of the .art and .cube files S-Cinetone actually uses, especially because S-Cinetone also lets the camera op make some adjustments on their end (and doesn't generate a pack-in LUT alongside the footage like a smart person would).

So what can you do? In Avid, the answer is nothing. It just doesn't work. Practically, you can use DaVinci Resolve (which is free, thank goodness) to load up those .art and .cube files and do some proper color-correction (conversion, really) on your S-Cinetone footage, and then export new master clips for use in Avid. Weeeeee.

Thanks, Sony. Very cool. Assholes.

Comments

  1. timelockMay 17, 2022 at 2:26 AM

    Hi, next month I have to import some terrabytes of S-Cinetone stuff into the Avid and I could not find a Lut or tutorial. So my question is if you have got a new solution in the meantime? Best for you, TM

    ReplyDelete
    Replies
    1. JuddSeptember 21, 2022 at 10:29 AM

      Hey, sorry for the late reply. No, I don't have a fix for this. Did you find a work-around?

      Delete

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

Exception: SYS_ERROR, OSErr: -5000

Image
Dear ISIS:  I love you.  You're great.  None of the bullshit file count limits of Unity, I can fill your drives to 100% without issue, you have automatic redundancy built into your RAID storage, your control panel is .html based and runs in my browser, and you work over ethernet instead of requiring fiberoptic cable.  You're pretty fucking swell. But there's this one thing you do sometimes that reminds me you're made by Avid.  See, it's like this:  When I create a user that has write access to a drive, and I log in as that user, I goddamn expect to be able to write to that fucking drive. Instead, Avid gives me this: What the fuck is that supposed to mean, Avid?  You're blaming the goddamn system OS for the fact that ISIS mounted my drive with incorrect permissions?  Why the christ would you do that?  Wait, wait - hang on while I get out my goddamn dictionary of What the Fuck OSErr: -5000 means. Okay, yeah, this is a write error.  It means I can't wr
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