Jump to content

Recommended Posts

The main difference will be due to the faster aperture. The 16-50 is at 35mm around f4.5, which is quite a bit smaller aperture than the f2 of the XC35. It will allow you to shoot images with better background separation (out-of-focus background) and that can change the look of an image completely. Of course it requires you to use the larger aperture (shoot at f2 or f2.8) and focus carefully on the subject and it will only work with subjects clearly seperated from the background. Less when you shoot landscapes.

I wouldn’t expect a big difference in image quality though. The XC lenses are very nice budget lenses and offer surprisingly good value for money. You might want to try a comparably priced second-hand XF35 f2. Next to the physical quality of a metal construction, there’s a slight improvement in IQ compared to the XC35. The dedicated aperture ring of the XF-lenses is crucial for me, but your mileage may vary...

Edited by Herco
Link to post
Share on other sites

1 hour ago, Herco said:

You might want to try a comparably priced second-hand XF35 f2. Next to the physical quality of a metal construction, there’s a slight improvement in IQ compared to the XC35.

don't know about the second hand market in the Netherlands, but in Austria a used XF35 is 50% more than a new XC35 and other than the outside shell and aperture ring, there is no difference in optics, so there won't be any difference in IQ

to answer to the OP: it depends what you shoot. a fast prime is always nice to have but if you don't use it because you prefer the zoom, then it's irrelevant how good it is

Link to post
Share on other sites

I have both lenses, and I like them both. I agree with Herco that you won't see much difference except at larger apertures. Two things I noticed using both lenses is that the XC35 focuses faster than the XC16-50, and the light weight and small size of the XC35 makes for a pleasant rig for mobile shooting. At the end of the day, I find the image quality at wider apertures is slightly better in the corners. 

I find that I shoot differently with the XC35. Without the option to zoom on the fly, I find myself using photographer knowledge, compositional creativity, and my feet instead of the zoom ring.

You probably don't need both lenses, but I don't regret buying both, and the XC35 woke up some of the old photographer in me. That said, I'm glad I kept the XC16-50 for its close-focus capability.   

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