Jump to content

White Balance and Exposure shift with X-T2 and AD200

Carlos Mendes
 Share

Recommended Posts

Carlos Mendes Rookie

Carlos Mendes

Posted
Posted (edited)
Hi there, I've just bought a Godox AD200 with an XPro F trigger, and I'm looking for some help to understand why I get a color and exposure shift while using TTL vs. using it on manual mode, using the same settings.

 

I'm attaching an example to explain the current behavior:

- The image on the top has been taken with TTL

- The image on the bottom has been taken in manual mode.  I've used the TTL-Convert-Manual (TCM) function to convert the first shot TTL settings to manual mode. 

 

I would expect the images to be the same since, in theory, I'm using the same settings. 

 

But there's a big color difference and also about a half a stop difference regarding exposure.

 

Color temperature:

- There's a difference of 700k from what I can see on Lightroom (the TTL image reports 5900 on the  Temp slider while the manual image reports 5200 on the Temp slider)

- There is also a minimal difference in the Tint slider (10 for the TTL image vs. 15 for the manual image)

 

Exposure:

- To get the image taken in manual mode to look the same regarding exposure, I have to increase the exposure by about +0,45   

 

Some additional info:

- I'm using Auto White Balance

- Shutter speed 200. Aperture 8. I've taken a test shot, and there's no ambient light affecting the images

- I'm using the AD200 without any modifier pointed to the ceiling to bounce the light

- The histogram on the left is from the top image (TTL). The histogram on the right is from the bottom image (manual)

- I'm using a Fuji X-T2 with the Godox XPro F trigger

 

Here's a link to the RAW images in case you want to compare them:


 

 

 

Are these differences between TTL mode and Manual mode expected, even using the same settings?  

 

Thanks in advance

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!

Edited by Carlos Mendes
Link to post
Share on other sites
  • 1 year later...
MarioM Newbie

MarioM

Posted
Posted (edited)

Hi, Carlos. I found your older thread, because I made the same experience. 

 

X-T2, 2x AD 2oo in brolly boxes, X-Pro2 as trigger and a huge color shift when using TCM. In TTL, I got clean colors, converted to manual, I got a massive blueish colorcast. And again, AWB, and I guess, that could be the reason. Didn't had time on the shoot to switch to 5600 K as WB. But I will test it asap. 

 

Mario

Edited by MarioM
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
 Share
Go to topic listing

  • Similar Content

  • Posts

    • jerryy
      Fungus

      By jerryy · Posted

      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.)  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      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.
    • PoorAlchemist
      LUT doesn't works on resolve

      By PoorAlchemist · Posted

      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 😕  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      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  
    • crazyfields
      Please save me from insanity 23mm f2 vs F1.4r

      By crazyfields · Posted

      Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...