C300: Final Cut Pro X Log Processing Fail?

[mizzar]

Hi there,

Today when editing some footage in Final Cut Pro shot by my C300 Mark II, the image seemed very different than when I shot it. Everything looked way over exposed, but I recalled checking the waveform constantly. After poking around a bit, I found this support article (dated 04/17/17):

https://support.apple.com/kb/PH12685?locale=en_US

It explained how to view change the LUT applied to your log footage. After disabling a Canon Log 3 LUT that had been automatically applied, everything looked as expected! Yay!

Now, I don't want to have to do this for every clip, so how can I disable this auto-log-LUT "feature"? It kills my dynamic range and won't let me pull it back when grading in FCPX!

How long as this been a thing? I haven't been editing much of the stuff I've shot myself because most of the gigs I shoot these days are passed off to another editor. I know I updated FCPX not too long ago and I hope this LUT application wasn't introduced at that point, and if it was, I hope it can be disabled!

Here are some pictures to demonstrate the issue:

http://imgur.com/a/OghZh



Notice how the corrected Log image looks natural and retains all highlight detail whereas the "corrected" Auto LUT photo clips the highlights no matter how much I bring down the levels.

 

[cpreston]

I noticed this, too. Like you said, I wouldn't mind the LUT other than the fact that it permanently clips the whites and darks. Just stupid. Hopefully they update/fix this in the next version.

 

[Jon Roemer]

This has been a thing for C-log 3 only since the most recent FCPX update (10.3.3). It's been a thing for C-log since 10.3.1 I think.

Apple lists this new way of doing things as a "feature" so if you and anyone else gets a chance be sure to use the FCP X feedback form to let Apple know that things shouldn't work this way!

Apple Final Cut Pro Feedback Form

I was hoping they'd fix it but instead they expanded it to include not only C-log but C-log 2 and C-log 3.

 

[mizzar]

This has been a thing for C-log 3 only since the most recent FCPX update (10.3.3). It's been a thing for C-log since 10.3.1 I think.

Apple lists this new way of doing things as a "feature" so if you and anyone else gets a chance be sure to use the FCP X feedback form to let Apple know that things shouldn't work this way!

Apple Final Cut Pro Feedback Form

I was hoping they'd fix it but instead they expanded it to include not only C-log but C-log 2 and C-log 3.

That is really bad news! Anyone who is bothered by the inability to choose whether or not this LUT is applied upon import, please reach out to Apple using the link above!

 

[Jon Roemer]

I have contacted them twice about this.

It's also not just a Canon thing. It affects Arri, Sony, and Panasonic cameras, too.

 

[mizzar]

I have contacted them twice about this.

It's also not just a Canon thing. It affects Arri, Sony, and Panasonic cameras, too.

If they can't react to customer feedback more nimbly, I'll need to start warming up to Adobe or the new Resolve...

 

[Noel Evans]

This should be an option on import. That said the quick work around I use is to import everything, select all clips, click the (i) information tab in the upper right side bar and then simply alter the log processing. It will update all clips.

 

[Noel Evans]

I noticed this, too. Like you said, I wouldn't mind the LUT other than the fact that it permanently clips the whites and darks. Just stupid. Hopefully they update/fix this in the next version.

The issue with the LUT is that it doesn't have any clue about what your intention was when you shot the clip. Unless you're using the LUT on your monitor to see how it will look, it most likely will be off. This is exactly why I monitor with a LUT applied when I shoot, weather its a standard rec.709 LUT for general shooting, os something Ive created specifically for the shoot Im doing.

Apple lists this new way of doing things as a "feature" so if you and anyone else gets a chance be sure to use the FCP X feedback form to let Apple know that things shouldn't work this way!

Did.

 

[markfpv]

This should be an option on import. That said the quick work around I use is to import everything, select all clips, click the (i) information tab in the upper right side bar and then simply alter the log processing. It will update all clips.

Noel is right - it's simple enough to select all the clips and alter the log processing but I also agree that it should be an option to check or uncheck on import.

 

[Jon Roemer]

Noel is right - it's simple enough to select all the clips and alter the log processing but I also agree that it should be an option to check or uncheck on import.

I didn't realize that you could select all the clips at once and turn it off. Great to know.

It should be an option in the preferences, not hidden in an info palette, and the default should be off.

 

[markfpv]

agreed

 

[indiawilds]

Last year december I was stumped by this update. All my clog footage looked way overexposed. It looked like as if a newbie has done the exposure. Then after some struggle I found it. You can select all your clips and turn this off. Pretty simple.

 

[mizzar]

Last year december I was stumped by this update. All my clog footage looked way overexposed. It looked like as if a newbie has done the exposure. Then after some struggle I found it. You can select all your clips and turn this off. Pretty simple.

Hah yeah I had the EXACT same reaction!

I agree it isn't too tough to correct but it's ridiculous that a professional tool has implemented something automatic that most professional users need to remember to undo. Let's fix this Apple.