Jump to content

Tethering problem with x-h1

downtime
 Share

Recommended Posts

downtime Newbie

downtime

Posted
Posted

Anyone else having issues tethering with an x-h1?

Fujifilm X-Aquire, Capture one and Exposure all work great with my X-Pro2. But I can't get my X-H1 to be recognized.

For the record, I have both cameras set with identical PC Connection mode setting of 'USB AUTO'.

The X-H1 does show up in 'X Raw Studio' and can transfer files. So I'm very confused.

I also tried different cables to see if that was the issue, with no luck.

I'm on a M1 Mac running Monterey. Tried it on an Intel Mac running Monterey and another on Big Sur.

Has anyone a solution for X-H1?

Thanks.

Link to post
Share on other sites
Herco Rising Star

Herco

Posted
Posted (edited)

I've used the X-H1 for a while for my professional work, but there were too many bugs that Fujifilm never really solved in firmware. In terms of build quality it is a great camera though. The X-Pro2 has a micro-USB2.0 connector and the X-H1 has a micro-USB3.0 connector. These 3.0 ports are more discerning when it comes to the right cable.

In case you work with an adapter try a native cable that doesn't need an adapter (also on the mac-side) and isn't too long (no more that 3m). The X-H1 is esp. sensitive to the capacity of the cable and whether it is shielded. In the end I got it working with Capture One, but I had to buy a new 3m Tethertools cable as the 4.6m was apparently too long. Now 3m is too short for me, so this on top of some other issues was for me the reason to switch to another camera. Tethertools has also a solution to boost the capacity (Tetherboost) of a USB3.0 connection, but I never tried that. I'm now on USB-C on both ends, so that solves the issue.

Edited by Herco
Link to post
Share on other sites
Herco Rising Star

Herco

Posted
Posted
1 hour ago, downtime said:

That’s a lot of great info. I’m gonna explore those options. I don’t really wanna get an XT4 at this point. (Come on X-H2!)

Thanks!

You're welcome. I still use my X-Pro2 for personal work every now and then, but I replaced the X-H1 (and the rest of the Fuji-kit) with a Z7II-based kit and I'm very satisfied with that move.

Link to post
Share on other sites
downtime Newbie

downtime

Posted
  • Author
Posted

Yes I don’t blame you. I’ll always have some Fujifilm gear. But if they don’t upgrade their gear in the next 3 months I’m going to go back to Canon for a lot of my work. I really love Fujifilm for all the right reasons but it’s faults are getting in the way of my work at this point.

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