Jump to content

Recommended Posts

Found this place where you can make nice graphs:

 

http://howmuchblur.com/#compare-1.5x-56mm-f1.2-and-1.5x-90mm-f2-and-1.5x-35mm-f1.4-and-1.5x-23mm-f1.4-and-1.5x-16mm-f1.4-and-1.5x-14mm-f2.8-and-1.5x-10mm-f4-on-a-0.9m-wide-subject

 

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!

Link to post
Share on other sites

Nice.  It's interesting to see how closely the 90mm follows the 56mm's curve but never exceeds the amount of blur offered by the f/1.2.  I suspected this might be the case but there it is plotted on a graph, how handy.

 

And to me this isn't just a "pissing contest" either because I work in photographic retail and get asked this question a lot when comparing lenses across brands and formats.  Thanks again.

Link to post
Share on other sites

And the 35mm 'beats' the 90mm below <1m for some reason. Interesting indeed.

 

I have a Minolta Rokkor 85mm F1.7, and it sits right in between the 90 and 56mm.

Even beats the 56mm at above >15 meters eventually. Of course its fairly soft wide open, but that's character. :D

Link to post
Share on other sites

 

And the 35mm 'beats' the 90mm below <1m for some reason. Interesting indeed.

 

16, 23 and 35 indeed...

 

At first I was skeptical about the results, but probably the difference is due to the stop advantage of the

three over the 90mm, which at lower distances overcome the focal lenght advantage.

 

I am curious of hearing an explanation of the phenomenon by someone more practical on the argument :)

Link to post
Share on other sites

I think yours is good enough. ^_^

 

Here's one with the 35mm F2 and 27mm F2.8

 

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!

Link to post
Share on other sites

Keep in mind that the distance is the distance between subject and background, not the distance between camera and background. The graph will look different for subjects of a different size – the width of the subject can be specified. With a 35 mm lens you need to get closer to capture the same subject than with a 90 mm lens which gives a fast 35 mm lens a headstart, but as the background distance increases, the longer focal length wins out eventually. The break-even point depends on the subject size and thus the distance of the subject.

Link to post
Share on other sites

That sort of works, but it's based on very clinical/theoretical/lab subjects and conditions, which makes it biased in favour of medium input perimeters. (Until the very extremes, where nothing can deny the blurry of a 200mm f/2 or 400mm f/4.) It also doesn't seem to quite have crop factor figured out correctly.

Not bad, and great if you like DxO and all that kind of thing, but I think the point at the bottom of the page about interpreting the info should be the thing you pay most attention to. 


edit: I'm an idiot (and it's half past 2 in the morning), I left a decimal point in the crop factor box. That explains why its maths seemed off. Nevermind, seems to check out okay!

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