Don Barar

I have also have an XF 150-600 that I use for wildlife videography--mostly birds. That lens has vignetting from 400 mm - 600 mm when shot at the largest aperture. In general, I do not notice the vignetting with little sky involved. However, If I have a bird against a bald sky (frequent occurrence in Arizona) I can have wild vignetting that bounces all over the place. The only solution is to stop down to f/11 which corrects the issue. For video, the X-H2S does have peripheral correction. However, it does not seem to work at 400 mm and above. I have tried with peripheral correction on and off. Makes no difference--it just does not work. I did some research on long telephoto zoom lens and vignetting. Regardless of company (Sony FE 200-600, Nikon 180-600, Canon 200-800), all suffer from vignetting at their longest focal lengths and wide open--it is function of the design. The solution on all of these lens is to stop down by 1 stop where it virtually disappears. Based on reports, the amount of vignetting for the XF 150-600 is on the low end from all of the reports that I have read--but then again I would expect it to be lower because this is an APS-C camera. Hope this helps others, Don

Hi All, We are halfway through November. Where is this new firmware that is supposed in FujiFilm’s words “nail-it” on video autofocus? To the fairest, Eris

I have a similar issue with my X-H2S (Firmware 7.0) and my RS2 (RS2 does not formerly support the X-H2S). However, most of time when I select record on the RS2, the camera records for a short period of time and then stops. A second press of record on the RS2 will result in the camera staying in record. The behavior is odd because X-H2S firmware 1.1 there was no issue when pressing record on the RS2. Somewhere around X-H2S release of firmware 3.0 this became an issue. I do not believe this to be an issue with your gimbal. This is a Fujifilm firmware issue! Good luck getting this resolved by Fujifilm. But I really doubt you will get very far. Fujifilm firmware development is absolute train wreck. Look at what is going on with autofocus. In two years, they have gone from an autofocus that worked reasonably well, to an autofocus that many complained about, to one that works better but still is not as good as the original. To the fairest, Eris

Flog2 requires some noise reduction. Zebras need to be set to 85. Expose clip to 1/3 stop less than when zebras appear. I use Davinci Resolve Studio Noise Reduction. Temporal noise reduction set to the following: Frames = 5, Motion Estimation Type = Faster, Motion Range = Medium, Luma/Chroma = 5 is great starting point and usually works well. You can refine the amount of noise reduction by looking at the waveform. Adjust Luma/Chroma up and down until waveform does not change. To the fairest, Eris

Paul: You leave your Sync E plugged into your X-H2S? Really? That's exactly what I do. Why? Because it is the only way to accomplish time code sync between the camera and any off camera sound recording device. But this thread was about Jam Sync. Fuji chose the Atomos system. So any other time code system does not work. Why not release a firmware update that allows jam syncing with multiple systems? Eris

Thank you Fujifilm?????? I am using the TentacleSync system. Why can't I jamsync with any time code generator? Why does it have to be just the Atomos system. Another bone headed Fujifilm limitation. Just like their crap autofocus!

There are other bugs as well. I frequently mount my X-H2S on an RS2 with RavenEye. When I select record on the RS2, the camera records initially, but then stops. I then have to push the record button again to initiate recording. My understanding is that the same thing happens with the RS3/RavenEye. The original firmware that came with the camera when I purchased in August 2022 did not do this. But somewhere in 2023 and the release of firmware version 3.xxxxx this problem cropped up. It is very annoying. But at least there is work around. Don Barar

I am using a X-H2S with my DJI RS2. What happens is this. Select record button. Record starts for about 2 seconds then stops. Select record again and the camera will continue to record. Happens almost every time, except when I initially start the camera, then it will stay recording with the first selection of record. Interesting that the RS3's have a similar issue and this has not been resolved. Since this was not an issue with my X-T3, I have to assume this is a FujiFilm firmware issue with the X-H2 series cameras. But I doubt this will ever get fixed by FujiFilm. Don Barar

The only way I can find to make the 240P somewhat acceptable is to be in bright conditions and get the ISO as low as possible. Do not use Flog 2! Minimum ISO is 1250 is too high for 240P. Flog with a minimum ISO of 640 is OK. You even might want to consider Eterna at the lowest ISO possible. It is my impression that FujiFilm laid an egg with the stacked sensor if your goal was to shoot 240P.

HI Serghios, Wow. We are numbers are growing by leaps and bounds. Doubling or tripleing our user base in just under a year. I am only using the RS2/X-H2S (firmware 5.01) for video through RavenEye on my iOS device operating under version 16.x. I have no issue getting the X-H2S to start recording. Though, I may have to push record more than once before the record mode stay latched in. Are you attempting to take photographs? Are you using Android or iOS? Don

You are most welcome. Don

HI Rufo, I have changed procedures. I now use the colors space transform (CST) as my first node. The CST is set up as follows: - Apply the CST effect to the first node. - Color Space is Rec 2020 - Input gamma is FLog - Output color space is Rec 709 - Output gamma is Gamma 2.4 All other nodes to grade the clip proceed the node that contains the color space transform. Hope this helps. Don

You might want to consider the following: 1) Use optimized media. These are ProRes files that can be generated inside FCP, or 2) Use proxies. Incidentally, I too had difficulty editing 4K H.265 All I 4:2:2 10 bit recorded at 360 mbps with FCP. Playback was choppy, as you have pointed out, so proxies or optimized media were required. To improve performance I purchased a MBP16 M1 Max, 32 core GPU, and 64 GB of RAM. I no longer have to take time to generate optimized media. Also, I switched to Davinci Resolve Studio. I think it is a better editing experience than FCP. Hope this helps. Don

Hi Oliver,Thank you for writing.X-H2S firmware 2.1 was the best. It did not require two selections of record to get the camera to record for more than a few moments--one selection was enough. Version 3.00 and 3.01 has broken this and now requires selecting record twice as did firmware version 2.0.Be careful what you wish for on DJI upgrading the firmware so that it allows of the X-H2S on the RS2. In looking at DJI’s compatibility chart of the X-H2S with RS3 it does not do very much except start/stop record. At least with the RS2’s current firmware, from the Ronin App I can also adjust the X-H2S' shutter speed, aperture, an ISO through RavenEye.Don

Hi Rufo: With X-H2S I find I do not have to over expose fLog by more than 1/2 stop. I expect the X-T4 to be similar. I follow this procedure to color grade in Davinci Resolve: First node has FLog only. Insert a node before the node that contains FLog. Here I do my main color grading. You want to do main color grading before the conversion to FLog as the changes you make will be linear. If required, insert another before the node before the color grading node. This node will contain any noise reduction. If you want to sharpen, insert a node after the node that contains FLog. I find a sharpening of 0.47 to more than enough. Any more and the image may begin to break down. This should be enough to get you started. If you want more, watch some of the YouTube contributors. Don