Jump to content

Recommended Posts

I already have the 90mm F2 and uses it to shoot wildlife/portraiture, very satisfied with the IQ, sharp in focus and creamy bokeh out of focus. During a trail I constantly need to switch between the 10-24 mm and 90mm lens. 

I'm considering adding one lens. 56mm is highly praised for portraiture shooting and its samples are stunning. But would the 56mm kind of redundant when I already have 90mm even though it's faster at F 1.2? 

 

Link to post
Share on other sites

I have both, and only rarely use the 56 since I got the 90 three years ago.   But I do not shoot many portraits, mostly landscapes, nature, flowers, cats, and headshots.  I also have the 18-55, and paired with the 90 it is perfect for my hikes.

Edited by merlin
Link to post
Share on other sites

I have the 56mm and love it, but when people ask me about buying one, I always try to throw the 55-200mm out there as a second option to consider for a smaller budget. While the 56mm is my first choice for portraits, the 55-200mm has decent bokeh when shot wide open, is fairly versatile for longer focal lengths, and you can find a good used copy of it for under $500. 

Link to post
Share on other sites

4 hours ago, Nero said:

The 23mm f/1.4 is one of my top 2 lenses, but it does overlap with your 10-24mm. If you're thinking you'd like another prime lens and you don't want it to be redundant, I'd say look at the 35mm.

i already have 35mm. here is what i thought. i would take a wide for senery (10-24) and a tele for wild life (90) in my trip. 

23mm 1.4 is large. though it can create some magic that 10-24 cannot, most probably i will not carry both in travel. 10-24 is more essential for landscape.

16mm 1.4 can shoot some interesting photos due to its fast aperture. maybe i can pick it instead of 10-24mm in a travel because 16mm is more versatile.

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