Jump to content

Recommended Posts

I had heard prior to the recent firmware update there were issues with the 2x and the 100-400.

 

Can anyone comment on whether this is no longer the case???

 

I have just tried my 100-400 with 2x teleconverter on my XT2 with the new firmware. It works, though (as you might expect) focus is a bit slow, certainly slower than the 50-140 with 2x converter. I'm afraid I can't comment on whether or not there's a difference in performance after the new XT2 firmware, as I don't normally use the 2x converter on the 100-400 (and after this little experiment I think I'll continue to leave it off, except in exceptional circumstances).

Link to post
Share on other sites

I have just tried my 100-400 with 2x teleconverter on my XT2 with the new firmware. It works, though (as you might expect) focus is a bit slow, certainly slower than the 50-140 with 2x converter. I'm afraid I can't comment on whether or not there's a difference in performance after the new XT2 firmware, as I don't normally use the 2x converter on the 100-400 (and after this little experiment I think I'll continue to leave it off, except in exceptional circumstances).

 

I must agree, any teleconverter is going to affect Focus Speed and Image Quality.  I have the 1.4x converter that I usually keep in my pocket for those shots I just can't reach and then only for a still shot.  I may pick up the 2x someday as there are many shots just out of reach, but it is not a priority.

Link to post
Share on other sites

  • 6 years later...

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