Jump to content

Recommended Posts

My very much loved X-Pro 2 has a serious problem for a long time but I can’t help myself, it’s too good to just sit on a shelf. 
 

Last year the display had started weird pink colors and the camera was freezing after a few seconds. First I thought the screen was the problem but when I get into the menu at once, the screen looks fine. After some seconds or when I am trying to get the the configuration part of the menu, the camera will freeze again. 
 

when I turn it off the screen stayed on for about a second. But I can’t turn it on again even after the screen finally went black. I need to remove the battery and insert it again and then I can turn it on again. But the problem is there again and again.

today I saw that there was a new firmware update 5.11 that is said to fix a freezing problem and I thought to give it a last try.

Ironically I could successfully make the firmware update with no problems. Somehow terrifying to make a firmware update when you don’t know if the camera might freeze during the process. But everything went fine.

Problem is the same as before. I tried different batteries and different lenses and without a lense. Always weird pink colors on the screen and finally freezing.

Any suggestions from the community? 
 

Or perhaps help from Fuji?

 

Link to post
Share on other sites

  • 1 month later...
First thing to try would be a factory reset.

If the camera locks up before you can select it in its menus, it is still possible clear its settings-memory (cmos?) by leaving it without battery for a while. Actually don't know for how long you would need to leave it, as I accidentally discovered this option by storing my camera for a year (wanted to have it repaired for a similar lock-up problem, which turned out to not be necessary after all ^_^).

You will know the memory was cleared when you have to re-select language and date+time when starting it again. Edited by Florian
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...