Jump to content

Recommended Posts

Hey all,

 

New here.

 

So, I have a used X-T10 that I just bought. I was looking to update the firmware, but I think I already have the latest (body: 1.21,  lens 3.12).

 

What's got me confused, however, is that the body firmware page says that the lens should be updated as well, but the link for it takes me right to the body firmware update (I have no way, therefore, to verify if 3.12 is the latest). So my question is, are there two firmwares for this camera or just one? Does the main body firmware update the lens as well?

 

Thanks,

 

Starkman

Link to post
Share on other sites

As you'd originally thought, bodies and lenses have different firmware and need to be updated separately. To be on the safe side, make sure the body is up-to-date before updating the lens. It should work the other way around, but there have been a couple of unpleasant incidents with certain camera/firmware/lens combinations when the camera wasn't updated first.

 

Here's the page with all of the updates. Scroll down past the cameras to get to the lenses:
http://www.fujifilm.com/support/digital_cameras/software/fw_table.html

 

As you said, the latest X-T10 firmware is 1.21, which you already have. You didn't say which lens you have, but the only lens with firmware at 3.12 or above is the 18-55, and its current firmware is 3.21.

 

So all you'd need to do is update the lens. Unless you typo'd the version number, and you've really got 3.21 already.

 

Note: Fujifilm's firmware update process will only apply newer updates. It will simply ignore update files for the version that's already installed, and for earlier versions. So there's no way to accidentally (or intentionally) set things back to an earlier version.

Link to post
Share on other sites

To continue here...

 

I downloaded the new firmware for the lens, but I can't get it copied over to the camere; the Paste option isn't available, only View, Sort By, Group By, etc.

 

The card's been formatted (Scandisk SDHC, 32GB) and I can see the card in Windows, but I just can't copy the firmware to it.

 

It can't be, can it, that I have to have a card reader? I sure hope not!

 

Any ideas?

 

Thanks.

Link to post
Share on other sites

I built my own system, and it's a good system, but no card reader came on the box. Further, didn't have to worry about this with my Nikon D3200, if I recall correctly. Either way, I got a card reader - $18.89 at Walmart, which was a wrong price; the online price is half that! Three trips to Walmart today...hip, hip...hurrah!

 

Thanks again.

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