Jump to content

Recommended Posts

I have the XH1 and Xpro2. I love both. I am considering a second body to go with the XH1 and wondered about the XT3. Is it an upgrade in terms of image quality? If you have both what wold you say are the improvements with the XT3? I may decide that the differences in ergonomics are too difficult for me to use both alternately. What have you found?

I was considering the XT4 but the flippy screen has put me off.
 

Best, John

Link to post
Share on other sites

On 2/19/2021 at 4:26 PM, John Kemp said:

I have the XH1 and Xpro2. I love both. I am considering a second body to go with the XH1 and wondered about the XT3. Is it an upgrade in terms of image quality? If you have both what wold you say are the improvements with the XT3? I may decide that the differences in ergonomics are too difficult for me to use both alternately. What have you found?

I was considering the XT4 but the flippy screen has put me off.
 

Best, John

Hi, Although there's a different sensor/processor in the X-T3 compared to the X-H1 (26MP vs. 24MP) the difference in image quality is virtually invisible. Theoretically the low light performance (noise level) of the 26MP sensor should be better due to 8% less amplification but that is hardly noticeable in practice. The lower amplification is offset by the smaller pixel size (26mio vs. 24mio on the same surface). Generally, the lower the pixel count, the better the low light performance.

I've had both cameras, used them professionally, but I kept preferring the X-H1 due to it's better grip and IBIS. Even printed at poster size, there was no real visible advantage for the 26MP sensor. Just some perception in edge cases in really low light. The real difference between the two sensors is in AF speed and video bit rates. Due to its shorter circuits (BSI-principle) and faster processor the X-T3 has snappier AF and can handle higher video bit rates. 

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