Jump to content

Recommended Posts

I am having problems with my XT3 regarding blown highlights. If I set the camera so that the histogram is reasonably far over to the left with no evidence of clipping on the right of the histogram I still get blown highlights in the RAW file that cannot be recovered. I use Natural Live View for the LCD/viewfinder. 

An additional issue is that the Highlights Alert is not working. Even with the image on the LCD screen clearly blown out there are none of the blinking black warnings that I have seen on various YouTube tutorials. This problem is the same whether I have Live View on or off. 

I'm hoping that there are some obvious settings that I am getting wrong, but can't think what they might be.

Can anyone help please?

Link to post
Share on other sites

Starting with the second problem first, go to the shooting menu:

SET UP menu > SCREEN SET UP > DISP. CUSTOM SETTING, then scroll down to LIVE VIEW HIGHLIGHT ALERT and make sure this is selected (has a checkmark) save and exit the menu.

Try focusing on a lamp or some other brightly lit object that you know will be blown out if you took the photo, crank the aperture wide open and slow the shutter speed way down so that it really will be a very high key image. Okay, the blinkies should be going wild, except in your case they might not.

Push the DISP/BACK button a few times. The display (lcd or evf) should change each time you do this, one time it will be a screen full of information with a small image tucked away in a corner, one time it will be only the image with no information and no blinkies, and one time it will be the image with some information and the blinkies will be there. The screen customization options you choose play a big part in these screen offerings. Having Live View or not, that does not matter.

 One of the display options is called the Exposure Indicator. Turn this one on and pay attention to it as well as the histogram, when it starts pushing past 2, you are getting a lot of white in your image -- okay if you really are shooting high key, but otherwise this means you are starting to blow out the image.

The histogram is a good tool, but using it takes practice, especially if you are using the composite one instead of the separate RGB histograms as they take up a lot of space. Sometimes the blown areas will show up only on the far right right side and they might seem like part of the border instead of being a little to the left where they would be more noticeable.

Also, using the DR200 or DR400 settings, these underexpose the highlights (while boosting the low end a bit) might help get the shot in some situations.

Edited by jerryy
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...