Jump to content

Recommended Posts

The current substantial discount of $1000 for the GFX 50R might seem to indicate an update to the rangefinder-style MF camera is in the near future. For someone who is seriously contemplating purchasing a GFX 50R I wonder if this is the time to pull the trigger or wait for a new model that might be in the offing. Any rumors along those lines?

Link to post
Share on other sites

There are indeed rumors about a new version of the GFX50. Both R as well as S. The R hasn’t been as successful as Fujifilm had hoped for, hence the early price reductions. Bear in mind that the GFX was intended to capture part of the full-frame market. After  initial praise and good sales, the numbers dropped quickly. Depending on the market, the price of the R has been reduced in steps by $1500-$2000 since introduction. Professional photographers mostly prefer the S model with the ability to mount a tilting viewfinder. and a grip. Hence the prices of the S remained high for a longer period.

The 51MP sensor from Sony is a previous generation sensor compared to the 102MP Sony sensor in the GFX100. The newer sensor has phase- and contrast detection AF whereas the 51MP sensor only has contrast detection. The result is a slower AF, that’s less decisive and doesn’t perform as well in low light conditions. Another feature that is expected in the sucessor of the R and the S models, is IBIS. That works so well in the GFX100. I guess both features are regarded essential in bringing over more full-frame users to the GFX platform.

However, when you like the GFX50 this is the time for a good deal. Next to the rebates on the R and the free grip for the S, there’s still the trade-in premium for a full-frame camera. I know people who bought a beat-up 5D mark I, just to collect the extra premium. In case you haven’t used a GFX50R before, I recommend you rent one for a day or two first to see if it really fits your workflow.

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