Jump to content

Recommended Posts

Hi, I'd like to share a trouble that I have on my X100T. I do a lot of panoramic shots through stitching method and for this, I lock focus & exposure for a given series. My trouble is that this doesn't lock the white balance - I'm on auto white balance - and this makes the whole process a pain as I currently shoot in JPEG - Classic Chrome. I know how to work around it (shoot in RAW instead of JPEG, or at least force the white balance), I don't look to solve the problem, more to discuss it.

 

I tend to think of it as a bug: lock exposure should lock the white balance in my view, this is clearly linked and forcing one should force the other. As such, I'd like to know how to report it so that it gets solved in a firmware update (or at least that you can choose to lock the AWB along the exposure or not)

 

 

 

 

 

Link to post
Share on other sites

 

I tend to think of it as a bug: lock exposure should lock the white balance in my view, this is clearly linked and forcing one should force the other. As such, I'd like to know how to report it so that it gets solved in a firmware update (or at least that you can choose to lock the AWB along the exposure or not)

 

One might consider adding another menu option to the AE-L configuration that allows a user to use AE-L to lock exposure and WB in concert. I'd oppose any "fix" that forces a WB lock, I'd consider this as a bug. But as an option, why not? Still, very few users will need it, and I haven't heard from a second person who actually wants this feature. Obviously, 99% of panorama shooters either use the Panorama function, shoot RAW or simply set a custom WB (or use a WB preset) before they start a JPEG series (using a grey card, for example).

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...