Jump to content

Lots of underexposed pictures with X-H2S since firmware 3.0

Breath81
 Share

Recommended Posts

Breath81 Newbie

Breath81

Posted
Posted

Hi all!

Today I tested the camera, in continuous autofocus mode using the back button to focus, with only the 100-400 lens, only the 70-300 lens, and with the 70-300 lens + 1.4 teleconverter. In all 3 cases, I found the same problem: many photos came out underexposed! From this test, it is clear that the problem is not with the lenses. After that, with the 100-400 lens mounted, in manual mode with automatic ISO selection, and in continuous focus mode, I repeated the following tests in sequence, always pointing to the same spot. I clicked the shutter button halfway multiple times (with the shutter AF, AF-C ON option in the menu) and the exposure meter always gave me an ISO value of 400. Then, I switched AF-C OFF (so pressing the shutter button will not focus anymore) and pressed the shutter button halfway multiple times, still getting ISO values of 400. Finally, I held down the back button (so the autofocus is active and continuous) and pressing the shutter button halfway multiple times the exposure meter gave me values of 160! So, the algorithm somehow makes a mistake in setting ISO when pressing the shutter button halfway, while the back button (or autofocus) is constantly active! Has anyone else noticed this? This is just a terrible situation for people doing wildlife photography (which is one of the reasons this cam exists!). 

 

Thanks!

Link to post
Share on other sites
  • 3 weeks later...
intercontinental Rookie

intercontinental

Posted
Posted

Hi, i experienced similar issues with exposure during panning. I tried different meterings and sort out that i have to useing compensation but it not always work. For exapmle when i panned plane during landing  - shots at the beiginign point of series were  underexposed but at the end of series exposure was correct (sun was behind me all the time) I have 50-140/f2.8 and 16-55/f2.8. Fuji recently updated firmware of that lenses related to chosing correct exposure but i didn't have time to test it yet.

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