Jump to content

Recommended Posts

Hello guys, I've a question and I really appreciate if you could help me.

I've a Fuji XT4 and i normally use Eterna film simulation in the lowest ISO possible. The question is, now I have a project and i wanna shoot in F-Log, i know you can't go below 640 ISO because supposedly is Fuji native ISO. But i did some tests and Flog at 640 ISO and has a lot more noise compared with Eterna at 160 ISO.

I've tested with -4 NR and 0 NR and still, the FLog has a lot more noise compared with eterna or every other simu. at 160 ISO.

What i'm doing wrong?

Note: You can only see that difference when the video is running, i've tried in Premiere, DaVinci and even did an export and transfer it to iphone and yes, is noticeable.

Thank you

Link to post
Share on other sites

  • 1 year later...

Flog2 requires some noise reduction.  Zebras need to be set to 85.  Expose clip to 1/3 stop less than when zebras appear.  I use Davinci Resolve Studio Noise Reduction.  Temporal noise reduction set to the following: Frames = 5, Motion Estimation Type = Faster, Motion Range = Medium, Luma/Chroma = 5 is great starting point and usually works well.  You can refine the amount of noise reduction by looking at the waveform.  Adjust Luma/Chroma up and down until waveform does not change.

To the fairest,

Eris

Edited by Don Barar
Link to post
Share on other sites

Hello,
I've sold my fuji xt4 and bought the XH2S and i've been learning how to use Flog 2 properly.
Yes Flog 2 has a lot of noise involved, so make sure before recording something if you need that amount of dynamic range in your videos. If not, Flog 640 has plenty of DR.
If you expose FLOG 2 incorrectly the shadows and blacks will suffer, A LOT!
What i think makes people confused is thinking that you must expose LOG profiles as the other "normal" color profiles, meaning, it's always better to underexpose than over expose. Wrong. When using LOG profiles it's always better to over expose. A little bit like film.
Use your light meter and expose everything at least 1 stop over (i find 1.5 being the sweet spot). I don't use zebras, but dont expect miracles when you have a hi contrast scenes, even the best cameras will suffer.

About the noise that's really subjective, if you want a super corporate clean look yeah maybe you need to use NR, but the noise in FLOG 2 is really beautiful not that kind of color noise you find in other cameras. I never use NR in artistic projects, again, i find the noise in Flog very filmic. But to summarize, over expose FLOG 2 always!

And P.S. i do agree that Fuji could lower the base iso for FLOG2

Edited by P_eterna11
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

  • Posts

    • A fungus in the forest.

      Welcome, dear visitor! As registered member you'd see an image here…

      Simply register for free here – We are always happy to welcome new members!

      (p.s. Open Topic.)  
    • The backslashes you are referring are just symbols denoting path.  Once you import into these LUTS into Davinci Resolve those backslashes are removed by default and you only see is the true file name which has no backslashes.  Convince yourself of this by opening the LUT folder from the Davinci Resolve Project Settings.  Do you see any backslashes in those LUT names? Of course not.  The only name you see is the one that has the underscores and the periods. These LUTS work as designed without having to change any path names.  However, they need to be set up properly through CSTs and by what is supported in Davinci Resolve.  Hence, the FLog2C film simulation LUTS cannot be used because Davinci Resolve does not support Fuji Gamut color space and the FLog2C gamut. Alternatively, Davinci Resolve does support Flog2 film simulation LUTS because the color space for FLog2 is Rec 2020 and there is an FLog2 gamut. If all you are doing is changing the path names then you are not getting the correct results.
    • I found the reddit topic i refere to :  https://www.reddit.com/r/davinciresolve/comments/1pc3f1e/cant_apply_new_fujifilm_gfx_55_lut/ "Update for y'all, It's just like what @ExpBalSat said, it's because of the backslashes in the names break them. I changed the file name and it works now. "   For me it was the solution. Realy annoying if it doesn’t work for you 😕  
    • Here is the solution to using the Eterna 55 file simulation LUTs in Davinci Resolve.   In general, do not use the FLog2C to film simulation LUTs as they are not supported by Davinci Resolve for two reasons: 1) Davinci Resolve does not support Fuji Gamut Color Space and 2) Davinci Resolve does not support FLog2C gamma.  Instead, use Flog2 which is supported by Davinci Resolve.  Here is an example.  Let's say that you want to use Classic Chrome simulation.  Do the following: Complete your color grade and use a CST to get to Rec 709. Add a node.  Use a CST to convert from Rec 709 to FLog2.  Output Color space is Rec 2020 and Outout Gamut is FLog2. Add a node.  Apply the FLog2 to Classic Chrome LUT Create a combination node from node in steps 2 and 3. Apply a Key to the combination node and adjust the Key Output Gain to get the amount of the combination node that you want applied. So that you do not have to do this over and over again, generate a LUT for the combination node.  Remember to turn off all other nodes before generating the LUT. Hope this helps others. Don  
    • Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...