Jump to content

Recommended Posts

Hello everyone, i just bought a used X-H1 with a rather weird kind of damage.

“Sometimes”, horizontal bars that look like old tv interference appear on the screen, evf, RAW and jpeg images. Other times, the image gets “mosaiced”: colors of individual pixels can be seen as if not demosaicing correctly. both examples (a video and a RAW photo that have only been downscaled for easier sharing) attached.

The camera is in good condition overall, all I know from the past owner (who bought it used) is:
It has been consistently used with W126 batteries, NOT W126S (and still is, since i don’t have W126S, but i did test it with a W126S and nothing changed)
The damage seems to have appeared out of nowhere (could be a lie tho)
It used to have a battery grip, and the bottom rubber cover for the contacts has been lost, so the contacts have been exposed.

The camera works flawlessly when not showing these defects. Sometimes, it may randomly show the lines for a few seconds, and then stop. Or, it may display the mosaiced image for a minute or two, and then just stop.I have found that the only thing that seems to trigger and also fix the defects are light taps on the bottom of camera body, rather reliably. I also found that if i use continuous stabilization the artifacts seem to arrive more often but also last less, perhaps because the sensor is moving around so much.
I haven’t found anything on google that seems to fit my problem.
I think it may just be a slightly misconnected flex cable, that’s why the light taps work.
I would attempt a repair since i’m pretty good at electronics, but i wouldn’t want to open the camera without a clue about what i’ll be looking for. So if anyone could get me any pointer, i’d greatly appreciate it.

And just to clear this out, i knew about the damage when i bought the camera, so i'm not gonna return it and i think sending it out for repair will cost more than what it's worth spending on this camera. 

Thank you guys!

Here are the examples

https://imgur.com/a/0xlvK0p

Link to post
Share on other sites

5 hours ago, Wikij said:

I think it may just be a slightly misconnected flex cable, that’s why the light taps work

I agree. Could be a broken cable or a bad soldering point, too. But by trying to repair it yourself you might destroy the camera. 

Link to post
Share on other sites

3 hours ago, Olaf W. said:

I agree. Could be a broken cable or a bad soldering point, too. But by trying to repair it yourself you might destroy the camera. 

You are right, in fact I think I'll keep it like this until it becomes unbearable (or it eventually fixes itself, though unlikely) and then risk it with a fix.

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