Jump to content

Recommended Posts

2 suggestions

a) if the camera is able to detect the blowout whites due to over exposure - why not implement a real time digital neutral density filter that bring down the exposure of only these areas in steps controlled by the photographer

B) have a shooting mode that enables you to set the 2 extreme points that define the required depth of field so all distances in between are in focus (i had this in a very old non digital canon)

 

Link to post
Share on other sites

a) It should be possible to read and reset the sensor multiple times during one exposure and combine the pictures in the camera. This could give RAWs with more bits and a higher dynamic range and would allow a lower base ISO. However, with ES the T2 is limited to 14 frame per second. So may be this technique could be used for shutter speed of a 1/2 second and slower. The additional time for the read out would not increase the total exposure time significantly and motion blur would not be affected. So at least in the case where people want a long exposure time at bright sun light to get the soft look of moving water this would help. Of course you could also take 4 pictures and combine them in software. But this would be more work and you can't see the result on location.

 

In same cases it would be sufficient if the exposure measurement would always measure the brightest spot and adjust the exposure to avoid blown out high lights.

 

B) I think the biggest problem is the definition of sharp. In analog times the circle of diffuson should be smaller than 1/1500 of the diagonal of the picture. But this corresponds to 3 to 6 mega pixel. So on a 24 MP camera the depth of field is much smaller than the marks on a lens from analog times would suggest. So the user had to define what is sharp enough for him.

Link to post
Share on other sites

Hopefully, this would be easy to turn off.  Sometimes you just want to blow out the background.   

 

I'd love metering like on the Nikon 810 that is setup so that you expose to the right as much as possible without blowing out highlights.  This gives you the maximum data.

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