Jump to content

Recommended Posts

Hi all,

 

i recently bought the Mitakon 35mm f0.95 and was very excited about it.

But unfortunately in comparison with the fuji 35mm 1.4 i found that the Mitakon doesn't gather more light than the Fuji.

With the same settings (manual) both lenses wide open had about the same exposure. Both set at 1.4 the Mitakon was exposed about one stop darker.

I also found that sharpness, microcontrast and colors were better with the Fuji Lens.

So the only advantage for the Mitakon was the slightly better DoF.

 

Anyone alse has the Mitakon and can verify my experience?

Link to post
Share on other sites

Check out the reviews of the Mitakon 35 f0.95 on the BHPhoto product page:

https://www.bhphotovideo.com/c/product/1226781-REG/mitakon_zhongyi_mtk35m95m2fx_speedmaster_35mm_f_0_95_mark.html

 

Especially read 'Not really f/0.95' and then 'I stand corrected'.

 

I previously gave this lens a 2 star review due to its price and apparent lack of exposure benefit. While it's true that the lens appears maybe .2-.3 stops brighter than the Fuji 35mm f1.4 (on an X-T2), I have come to realize that's not because of any deficiencies on the part of this lens. It has come to my attention that Fuji (and apparently many manufacturers) artificially increase the sensor gain when shooting at large apertures--even in RAW. This is due to diminishing returns when using large aperture lenses in combination with digital sensors. Something to do with pixel pitch and the angle of light coming through the lens.

In any case, what this means is that the camera does not artificially increase the exposure of images captured by the Mitakon since the lens has no chip in it to tell the camera aperture information. This means that images from the Mitakon show approximately 1-stop less grain than images from large aperture Fuji lenses. If your skeptical it's easy to test: Shoot a test frame at f1.4 with a Fuji lens. Then slightly disengage the lens until the camera registers f0 because it can't communicate with the lens. And take the test image again. You'll see an image ~1-stop darker.

Link to post
Share on other sites

@Mervyn: that's very interesting, i'll check that.

 

@drandyperry: the lens is already optically worse than the fuji and has has only manual focus. That sould be enough to make the prize difference. I expect a lens that is sold as 0,95 to perform at least close to that.

Link to post
Share on other sites

@Mervyn: that's very interesting, i'll check that.

 

@drandyperry: the lens is already optically worse than the fuji and has has only manual focus. That sould be enough to make the prize difference. I expect a lens that is sold as 0,95 to perform at least close to that.

F stops are not the same as t stops. Look at the fuji 56mm apd, that has both f and the stops marked on the barrel.

 

You shouldn't expect any lens to get the same t and f stops. Very few achieve this.

 

Sent from my ONEPLUS A3003 using Tapatalk

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