Jump to content

Recommended Posts

Hi guys 

i have got X-T10 with XF18-55mm f2.8/4

the problem i have is that when i put the Aperture on manual mode and the zoom at 18mm f2.8 and go to 55mm the aperture stays stuck at F2.8 .... in other words it acts just like pro 16-55 f2.8 lol 

Notice : my body and lens are updated.

Edited by Kader2727mosta
Link to post
Share on other sites

So, it looks like the lens isn't communicating properly with the camera. With luck it might just be a tiny bit of dirt/fluff/oil etc on the contacts. Have you tried removing the lens and very gently cleaning the contacts on both lens and camera with a soft cloth?

Link to post
Share on other sites

5 minutes ago, dfaye said:

So, it looks like the lens isn't communicating properly with the camera. With luck it might just be a tiny bit of dirt/fluff/oil etc on the contacts. Have you tried removing the lens and very gently cleaning the contacts on both lens and camera with a soft cloth?

Yeah i've cleaned it and updated it also but still same , on Automatic mode it works properly but when i switch to manuel it works as 16-55 f2.8

Edited by Kader2727mosta
Link to post
Share on other sites

As lens&body have the newest firmware installed, I think the rotary encoder telling your lens at what focal lenght it is, is either broken or unattached to the mainboard, hence not communicating. If you stop the aperture down yourself to f/8 or something, while at 55 mm, this will probably show as 18 mm f/8.

Anyway, your lens needs to be serviced.

Link to post
Share on other sites

12 hours ago, quincy said:

As lens&body have the newest firmware installed, I think the rotary encoder telling your lens at what focal lenght it is, is either broken or unattached to the mainboard, hence not communicating. If you stop the aperture down yourself to f/8 or something, while at 55 mm, this will probably show as 18 mm f/8.

Anyway, your lens needs to be serviced.

Yeah that's true , thanks 

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