Jump to content

Recommended Posts

Hello,

just reading at the manual, I found out that my Yongnuo YN560-TXII controller, is supporting "Multi Flash Frequency & Flash count". Strobo flash photography is a new technique to me, so I wanted to have a go to learn something new.
I then mounted it on top of my X-T3 and tried to do some strobo Off Camera Flash with it, paired with a YN660 speedlite, without success. When the flash gets triggered by the controller, it flashes only once.
When I press the "test" button on the speedlite it works correctly.
When I mount the speedlite directly on the camera hotshoe, the multi mode works correctly.

Is there anything I am missing or the multimode won't work through a controller (despite being available)?

Thank you.

Link to post
Share on other sites

  • 2 weeks later...

What are the flash settings in the camera? Is the YN660 set to Master or Slave?

In order to make strobo exposures, the camera needs to know to open the shutter and when to do so. It sounds like the speedlite is communicating with the camera when directly mounted, but your controller may not be. I assume you are triggering by radio transmission. Have you tried to trigger with the EF-X8? You will need to set the speedlite to Slave. This will verify the camera at least speaks "Yonguo". Perhaps the camera and trigger are in conflict at some level.     

Link to post
Share on other sites

  • 2 years later...

I have same issue on XT1. have Yn560iv on camera. 1 second exposure flash fired once. same case with Yn560Tx controller.

but on test button multi is firing perfectly. 

wondering what is missing in my camera setup. 

 

Link to post
Share on other sites

  • 10 months later...

I am having similar problems with my YN 560 mark 3 and mark 4 flashes, When set to Multi mode they fire as they should (in multi mode) when I press the test button on the gun. But when the 560 TX transmitter is set to fire the flashes I only get the one flash. The transmitter is communicating with the flashes and is in Multi mode. 

What am I (we) doing wrong??

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

    • Is the X-H2S “dynamic range improvement” a myth? Since the release of the Fujifilm X-H2S, Fuji has heavily promoted: the sensor’s internal 14-bit readout, the new F-Log2 profile, and a supposedly tangible improvement in video dynamic range compared to previous generations (X-T4, X-S20, etc.). But when you look at actual laboratory measurements, the narrative starts to fall apart. What the numbers actually show (measured data, not marketing) Based on IMATEST / SNR-style measurements: X-H2S ≈ 12.2 stops at SNR=2 ≈ 13.6 stops at SNR=1 Measured in ProRes HQ, high native ISO (1250) X-T4 ≈ 11.8 stops at SNR=2 ≈ 13.4 stops at SNR=1 Measured in H.264 / H.265, lower native ISO (800) The real-world difference is about 0.2 to 0.4 stop, depending on the threshold used. This is nowhere near a generational leap. The core question: where did the 14-bit promise go? If the X-H2S sensor is truly read internally at 14-bit, a simple question arises: Why does this extra bit depth not translate into a measurable increase in usable dynamic range? Because: the final recorded signal is still 10-bit, read noise appears to cap the signal before those extra bits can matter, SNR curves remain very close to those of the X-T4. In short: 14-bit upstream, same ceiling downstream. And what about F-Log2? F-Log2 is supposed to: extend highlight latitude, better exploit the sensor signal. Yet in practice: measured dynamic range barely increases, what we mostly see is curve redistribution, not actual expansion, shadow noise rises earlier. This raises a legitimate concern: Are we just looking at a remapping of the same dynamic range, rather than a true physical gain? Provisional conclusion (but an uncomfortable one) Based on the available data: the X-H2S “dynamic range improvement” appears largely overstated, the 14-bit readout looks more like a theoretical talking point than a measurable benefit, F-Log2 seems primarily like a grading convenience, not a sensor-level breakthrough. Open but serious question Is the internal 14-bit sensor readout and F-Log2, in practice, a damp squib with no truly palpable impact on real-world video dynamic range? If anyone has: independent measurements showing otherwise, or a demonstrable gain beyond ~0.3 stop, I’m genuinely interested. But for now, the numbers simply do not support the narrative.

      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!

    • nothing special, I thought the sky looked cool, handheld, unedited, 16-80 around F11.  Bay inland of Indian River, DE right after sunset.

      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!

    • Hello everyone, Recently, I've come across the very detailed videos from Edvard (@edvard2942 on YouTube) about Fujifilm autofocus performance. His tests highlight what he sees as a regression in AF fluidity and reliability starting from certain firmware updates, and that the best results aren't always with the latest versions. I'd love to start a discussion here to compile, based on your experiences and Edvard's tests, a kind of “best firmware list”for each body in terms of autofocus smoothness and reliability (especially in photo and video AF-C with older lenses). Here's a summary of what's already well-established from Edvard's analyses (feel free to correct or add details): • X-T3 Firmwares 3.00 / 3.30 are considered the best – smoothest AF, most natural transitions, fastest and most frequent lens motor adjustments. From firmware 4.00 onward (the one that aligned it with the X-T4), there's a clear loss of fluidity in micro-adjustments and quick distance changes. • X-T4 The AF from the initial firmware (~1.00) already uses the algorithm introduced on the X-T3 with 4.00. It's less smooth than the X-T3 on 3.xx, but generally stable. Later updates did not restore the older X-T3 smoothness. • X-H2S Very early firmware (around 1.03) is significantly better than later ones (3.xx, 5.xx, 6.xx, 7.xx), which degraded fluidity. However, even this best version remains below the X-T3 on 3.xx in terms of pure AF smoothness. I'd really like us to expand this list with other bodies (X-H2, X-T5, X-H1, X-Pro3, etc.). Which firmware gives the best AF according to you, or according to the Edvard videos you've seen? One specific question that's bugging me: Can we expect early X-T4 bodies (with factory/original firmware) to be as smooth as the X-T3 on firmware 3.xx? Or is the difference already there from launch? Thanks in advance for your feedback, any downgrade experiences, and tests with different firmwares and lenses. This could help a lot of people optimize their setup.
    • Bob is a well-known and much appreciated street performer, musician, comedian, and sometime circus performer. GFX100RF.  3200 ISO   1/60 sec.  f4.

      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!

    • If the spots are in the same place every time then its likely a dirty sensor - you can buy a sensor cleaning kit and do it yourself or take it in to get cleaned professionally.
×
×
  • Create New...