Jump to content

Copying basic config between 2 identical Fujifilm X-T bodies

mecsw500

By mecsw500
in General Discussion

 Share

Recommended Posts

mecsw500 Apprentice

mecsw500

Posted
Posted

So I have 2 Fujifilm X-T30-II bodies. I wanted  to have them both configured to the same base setup, so this is what I did:

First, I went to the Fujifilm support website and I downloaded and installed the X-Acquire application. I am running on an iMac with an M1 processor, with the Ventura release of OS X. Then I made sure both of my X-T30-II bodies were at the same firmware revision level, I had to upgrade one of mine first.

Next I connected a USB-C to USB-C cable directly to the iMac USB-C port. The process of downloading the backup to the iMac from the camera with X-Acquire fails with an "error"  (no information as to what the error was though) if I connect the camera via a powered USB 3 hub and a USB-A to USB-C cable. It only works for me if the USB-C to USB-C cable plugs directly into the iMac itself.

On each  of the cameras I set the menu setting "Wrench / Connection Setting / Connection Mode" to "USB Raw Conv./ Backup Restore". I reset this to the "USB Card Reader" when I'm finished so iPhoto, Capture One and Google Photos all work as they normally do.

I went to the "Configuration Settings" on the X-Acquire app and un-clicked all the file jpg settings etc so no data files get transferred as I use iPhoto and Capture One for that. If you right click on the X-Acquire icon on the menu bar you will see all the options. The Backup and Restore options are grayed out if the camera is not connected BTW.

Now I connect the USB-C cable and power up the camera. After a minute or so the X-Acquire icon in the menu bar turns into color from monochrome and I backup the camera to a file on my desktop using the "Backup" option. The file is about 11k and downloads in a couple of seconds. Of course it doesn't tell you when it has finished. Then I turn off the camera and unplug the USB cable.

To copy the data to my second body, I repeat the process with the second body, but this time I choose the "Restore" option and wait about 30 seconds for it to complete. Of course, it doesn't tell you when it has finished, but it seems to only take a few seconds to restore. Once again turn off the camera and unplug the USB cable. Now I turn on and reset the "Wrench / Connection Setting / Connection Mode" to "USB Card Reader" for both bodies.

Now I have both my camera bodies configure the same. The following bit I'm not sure if you need to do it, but I configure each body to use a different name for saving files. I configured one camera to save images in XXX1 filename and the other in XXX2 file name. I did this because I wasn't quite sure how iPhoto, or Capture One, or Google Images was going to handle having two cameras saving images with the same root name for the image files. You might know how this works better than I do and I might just be overthinking this bit.

Anyway, I now have 2 bodies configured largely the same and if I add custom settings to one I'll only have to duplicate the settings on the other manually without keying in everything. I will probably drift a bit from one body to the other as I might use one body for one type of picture with the prime lenses and the other with the long reach zooms. All the entries I added for custom manual lenses on adapters copied across too which was nice. As my manual lenses were all FF Zuikos and Nikkors, I made sure I entered the focal length in Focal Length divided by 1.5.

This may or may not be useful to you and I may not have done this in the optimal manner, I don't know, but there you go. I think it would probably work mostly the same on a Windows machine, but I don't have one to try it. I have not tried this on anything other than my X-T30-II bodies and I have no idea if it would work between different types of body like an X-T30-II to and X-T30, or an X-T3.

Your mileage may vary of course.

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
 Share
Go to topic listing

  • Similar Content

  • Posts

    • jerryy
      Fungus

      By jerryy · Posted

      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.)  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      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.
    • PoorAlchemist
      LUT doesn't works on resolve

      By PoorAlchemist · Posted

      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 😕  
    • Don Barar
      LUT doesn't works on resolve

      By Don Barar · Posted

      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  
    • crazyfields
      Please save me from insanity 23mm f2 vs F1.4r

      By crazyfields · Posted

      Thanks for the insights. I think it's really hard to make a decision without having the two side by side! 
×
×
  • Create New...