Jump to content

Recommended Posts

Hope somebody can help me here...!

In short terms: A few weeks ago I sent my X-T3 to the Fuji repair service here in Mexico, the front command dial was no longer working. Last Friday I received a camera back.

My problem now: The camera I received back shows in the EXIF data a different serial number than the camera I sent to the repair center. The serial number on the tag on the back of the screen still shows the serial number of the camera I sent to the repair center.

I also recognized that the shutter count is totally different, the camera I received back shows a significant lower shutter count number.

Calling Fujifilm USA they explained to me that the change in the serial number shown in the EXIF data may be caused by a change of the cameras main board and the following new initialization of the camera. But they told me I need to get the information what really happened from the repair center here in Mexico.

The Fujifilm repair center here in Mexico at this time refuses, despite I asked them several times, to tell me in writing what they did with the camera, especially concerning the different serial number!

My questions now:

- What can cause this different serial number shown in the EXIF data?

- Would you accept that your camera shows different serial numbers on the tag (physically) and in the EXIF data?

Any hint and advice very welcome!

Herbert

Link to post
Share on other sites

  • 5 weeks later...

If it functions OK and is still covered by a repair warranty then don't worry about it.

BTW - the "internal serial number" in the EXIF data is not the camera's actual serial number as depicted on the external badge.  😉

Link to post
Share on other sites

I know this is quite an old post but I would take the information from Fujifilm USA - its quite likely that a change of main board caused the change in serial number reported by the EXIF (and your local repair centre just didn't bother to change the label). I'm not sure it would be something that would bother me too much so long as the camera work OK.

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