Jump to content

X-T3 with Godox X2T-F

Yonathan

By Yonathan
in Fuji X-T3 / Fuji X-T30

 Share

Recommended Posts

Yonathan Newbie

Yonathan

Posted
Posted

I have seen many posts regarding the faulty combination of the two.

To sum up the issues so far I noticed:

1. Occasional lag (orange LED) when shooting with the X2T-F attached. Supposedly to be fixed in the latest firmware V1.2, however I still experienced the same issue.

2. Flash Settings in the X-T3 defaulted to TTL always despite all my Godox Flashes are Manual-only. Tried switching to M but it always defaults back to TTL mode. And the mode switches back and forth occasionally on its own. This results in a slight delay when pressing the shutter button.

Very frustating indeed! Has anyone has these problems too?

Link to post
Share on other sites
  • 1 year later...
larsdaniel Rookie

larsdaniel

Posted
Posted

It is a frustrating problem that placing a Godox flash or trigger on a Fuji camera will not allow the camera to be in anything but TTL mode. As far as I know it is the same for all Fuji cameras, and all Godox triggers except for X1T that reportedly has a firmware that fixes the problem.

This thread is a good read: https://www.dpreview.com/forums/post/62565196

Also, please write Godox an email. They need to fix it.

Link to post
Share on other sites
larsdaniel Rookie

larsdaniel

Posted
Posted (edited)

IMPORTANT UPDATE

Regarding the issue that a Fuji camera will always be in TTL mode if a Godox product is in the hot-shoe:

I got a sad response from Godox, but at least we know now that this issue will not be fixed. From this point on I can not regard Fujifilm and Godox to be actually compatible. (Many users will off course never feel this is a problem, but for shooting very timing specific action (think skateboarding or dancing) a delay to the shutter (because camera is always in TTL) is no joke.)

Here is the message from Godox:

Quote

 

Dear Lars
Good day!
 
Thanks for contacting Godox.
I relayed your feedback to our techs and they replied that this issue could not be resolved.
Sorry for the inconvenience caused.

 

 

 

 

Edited by larsdaniel
Link to post
Share on other sites
  • 1 year later...

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