Jump to content

Recommended Posts

As confirmed previously, I was able to update the firmware from the Beta to this latest version with no issues. Although I still suspect it was an early leak of the final version. Comparing the byte size of each file shows them as identical. Maybe the changes were minimal if it was indeed a release candidate or beta.

Link to post
Share on other sites

I'm using http://onlinemd5.com and getting the following:

 

MD5 Checksum

------------------

 

Beta release - "4E12F4EB43AD6AD1F215FE189B9CBED7"

Fuji release   - "F7AD4C2FB4CFCF18CEEB3B6ADDEC3840"

 

SHA-256 Checksum

-----------------------

 

Beta release - "199CC47270CAF456909972398403B0DECA0D2B0831FF43DB1E2CC5E77F77F29A"

Fuji release   - "330EA550094D48D292E73359454A78D7D5B4924E8290DD4F654F6BC1D9C57615"

 

Cheers!

Rolly

Link to post
Share on other sites

Hi,

I need help...last time it worked, but this time sadly not...

I formatted the card in the camera, copied the downloaded fw update file on the sd but when i try to install it it says no fw found on card...

I checked again the sd and it was there...tried a few times, but always the same message...

Anyone an idea what im doing wrong?

Link to post
Share on other sites

As confirmed previously, I was able to update the firmware from the Beta to this latest version with no issues. Although I still suspect it was an early leak of the final version. Comparing the byte size of each file shows them as identical. Maybe the changes were minimal if it was indeed a release candidate or beta.

The size in bytes is the same, but the file is in deed different as others have commented. It seems like all strings are encrypted, but not the code and the data, but there is probably an embedded check sum to avoid installing tampered files...

 

;-D Hans

Link to post
Share on other sites

Testing after an almost sleepless night ;)

 

 

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!

Link to post
Share on other sites

I became very sceptical about FW4 after first impressions of beta version users and fuji guys video. Someone has written that 56 has the same speed. Thus I've descided that the only meaningful improvement for me will be EC in manual.

 

Well I was wrong. New zone AF with AF-C makes 56/1.2 an autofocus lens. I am finally able to shoot my son no it only when he's sitting still. Moreover thanks to this new tracking ability the viewfinder functionality has increased. Why? I'm now able to shoot in CL and AF-C with high percentage of correct focus. (Spot AF is still useless with AF-C.) And only in this mode the viewfinder shows video image between two frames. Additionally I love that AF spots are dispayed in CH drive. This helps a lot.

 

I the end new AF capabilities are amazing!

Link to post
Share on other sites

All is set, the 60mm, the slowest of my lenses , has received a boost and works much better that it did before. Transition between macro and infinite is not instantaneous ( how could it be?!?) but the macro setting no longer requires to be enabled ( well, it is no longer there!) for the camera to be performing in macro mode (a general improvement with all lenses but one which particularly affects the 60).

 

When operating within any given range  ( macro, medium distance and infinity) things are very much faster than they were before although a little lag still persists with subject lacking contrast ( especially white ones). The face and eye detection seem to be operating rather well on this lens too. I don’t know whether I am ever going to use this function much but it might come in handy.

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