Jump to content

Recommended Posts

Hello,

I have been using the new Fujifilm GFX 100s II firmware 1.01 for a few days now and have noticed strange behavior in saving some RAW files (I have attached examples). I would like to point out that I am an experienced photographer with 35 years of experience, and this is the first time in my career that I have seen such behavior (I previously used a digital Canon EOS 5DS R). 
The perspective has been recorded strangely in the attached photos.
Link to RAW (RAF) photos:


Please check and comment.

In addition, the same camera has problems downloading photos saved on the camera card to the computer via the FUJIFILM X Acquire v. 1.29.0.1 application in the Windows 10 Professional environment.

After correctly connecting the camera to the computer via the original USB cable included with the camera (according to the camera instructions), the application does not allow downloading photos. The only thing the FUJIFILM X Acquire application allows you to do is save and restore the GFX 100S II camera settings.
I have tried all possible camera settings.
I would like to point out that the camera is visible through Windows 10 Pro in the USB settings and allows you to download photos, but only through the "Windows Photos" application.
Additionally, the FUJIFILM X RAW STUDIO v. 1.24.0 application works correctly.

Please help.

Regards
Ralf
Link to post
Share on other sites

1 hour ago, Greybeard said:

Thats bizarre - its not just RAW though is it - at least one of the jpgs are also showing strange behaviour.

You might try turning off IBIS although that is clutching at straws.

Sure. A camera that has 102 MP without IBIS? That's more of a trash can camera, not one to use, especially without a tripod.

Link to post
Share on other sites

11 hours ago, RR_photo said:

Sure. A camera that has 102 MP without IBIS? That's more of a trash can camera, not one to use, especially without a tripod.

Agreed - although in looking for a solution I would go through the functions that could result in movement - especially image #147 - which could be due to electronic shutter but it looks as though the camera would have been rotated while the image was taken

Link to post
Share on other sites

On 8/12/2024 at 4:12 PM, RR_photo said:

Hello,

I have been using the new Fujifilm GFX 100s II firmware 1.01 for a few days now and have noticed strange behavior in saving some RAW files (I have attached examples).

You are using a camera with pretty big sensor and a lot of MP. This sensor have a big readout time so you need to hold the camera still and shoot static scenes to use the electronic shutter, otherwise you will get a rollingshatter effect (just this effect in your pictures).

Try to switch to mechanical shutter to be sure that this effect will not be repeated at a crucial moment.

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