Attila Bakos

The problem with the grip is that the body can't switch batteries while recording. This is rarely mentioned even though it can be a real pain in the ass. Imagine you have 5 mins left in the battery inside the body and two fully charged batteries in the grip. You will still be limited to 5 mins of continuous recording, as the recording stops when the currently used battery dies. So you have to keep an eye on that, and in this case remove the battery if you plan a shot longer than 5 mins.

That is an excellent review shared by @jindrich. Interesting to see the behavior of the IBIS in the "Laguna Beach" video.
I've just packed up the X-H1 I recently purchased and sent it back to Adorama. It really is an excellent camera and so many improvements over the X-T2 for a true hybrid shooter. These were my issues:
I also experienced too much jerkiness with the IBIS. In "Laguna Beach" you can see some of the hops and jerks now and then, even within their chosen edit. Even with smooth, slow pans, I would have a fair bit of this. I spoke with a Fuji tech yesterday and "Dan" informed me that is was likely an issue of "buffer on the sensor" and that was all he could say. There are time too when the IBIS produces an effect akin to a warp stabilizer in post that I loathe.
I also picked up a Fringer Pro adapter and much prefer the quality of the stabilization I get in my Canon 17-55/2.8. I am using this with both my X-T2 and tried it with the X-H1, both IBIS off and lens stabilization on and IBIS on and lens stabilization off as well as both on. For me, relying on the lens stabilization in the Canon produced the best look consistently.
I would love to use my fast, small Fuji primes, obviously, but this 1st gen. just IBIS just isn't there yet for me.
The other issue I had was the increased aliasing in the X-H1's 1080p/60 vs. the X-T2. It's there.
So with the Fringer adapter, the upcoming firmware, and examples like what @Vladimir posted, I've got a lot of mileage to pull from my X-T2 still. Feeling good about that. Excited about that shutter mechanism coming to the X-T3 or an X-H2 with better IBIS and aliasing control.
Oh, lastly, I think the new grip is not universally better. It is better than an X-T2 w/o the battery grip, which I shoot with, but felt just a bit more than what I wanted. Subjective, is all.

It seems those blinking pixels mentioned in this thread will be fixed with the new 1.01 firmware, which is already downloadable:
Resolves an issue where blinking pixels may appear at bottom edge of the camera setting and with certain lenses, especially during XAVC S 4K (PAL 25p) recording Resolves a rare issue where the touch panel cannot be operated Improves overall stability of the camera

It seems those blinking pixels mentioned in this thread will be fixed with the new 1.01 firmware, which is already downloadable:
Resolves an issue where blinking pixels may appear at bottom edge of the camera setting and with certain lenses, especially during XAVC S 4K (PAL 25p) recording Resolves a rare issue where the touch panel cannot be operated Improves overall stability of the camera

That's actually my site I believe I could easily create a flatter Eterna LUT, but I don't have the X-H1, and I don't know anyone in my area (Hungary, Europe) who has one.
(If you try my LUTs, make sure to switch the clip to video levels.)

Yes it all started with a comparison I made, where I tried to do anti-aliasing on a heavily aliased X-H1 120p footage. I did it in avisynth since Resolve has nothing that can help here. The feature you recommended does nothing when you post your 1080p120 footage to an 1080p timeline. It only helps when your footage's resolution does not match timeline resolution, that whole section in the project settings page is for scaling only.

Yeah many people do it like this, as having a bit of noise reduction in the first node can also lead to cleaner keys.

For the banding removal mentioned earlier, when you have massive banding, it can be useful to add grain and then apply temporal noise reduction. I applied a very strong grade to one of my X-T2 F-Log clips here, to show some nasty banding (view in full size):

Then I created a mask for the sky in Resolve, applied some heavy grain and then some heavy temporal noise reduction in Resolve's denoiser, and voilá. Obviously this will only work if you can mask out the problematic area and if there's no real detail there.

I'm not sure it's a good idea to judge motion cadence by looking at videos that were most likely shot with very high shutter speeds.

Yes I tried it on this footage but avisynth fixed aliasing much better. For noise it's king though.

Yes I tried it on this footage but avisynth fixed aliasing much better. For noise it's king though.

My cat disagrees.

I recently finished this project. If you like the results, download the LUTs for free on colorizer.net.
 

4K 16bit uncompressed RAW at 25 fps needs 422 MB/s. That's megabytes, not megabits. Based on the information we've been given so far the body can handle that, but you can't write that to the SD card, the fastest UHS-II cards can write up to 250-260MB/s continuosly. So you either compress RAW, or lower the number of bits.

Long but informative review:
 

Great lateral thinking by the guy who came up with the workaround but I'm now wondering if the best fix for these issues is to set my own calendar into the future and buy the mark IV version of it.

Long but informative review:
 

Long but informative review:
 

Yeah, the A7III is a steal :D

Yeah, the A7III is a steal :D

Yep. Works particularly well with teh SLR Magic Rangefinder, or so I hear.

Yeah, the A7III is a steal :D

So in order to have working AF, don't use DR400 (or 200), don't use F-Log, and don't use a fixed ISO. And even then the transition is not smooth at all.
 

Oh that's not my video, I don't have an X-H1 (yet?).

Yes, even at DR100, it looks herky-jerky. Is that somehow usable? There's a difference between saying that it's less bad at DR100, and saying that CAF for video is actually usable.
Also, I find it disturbing that folks seem to be almost preemptively anticipating problems as inevitable; that they'll later be fixed in firmware as part of Fuji's world-class Kaizen.
My understanding is that Kaizen (the Deming cycle, Toyota Production System, call-it-what-you-will) was meant to discover and prevent flaws like this from being pushed into market in the first place; not to fix errors that were sloppily discovered only after the release.
A more accurate term for what Blackmagic, Sony, and now Fuji and others are doing is the well-known strategy of "Release it Now; Fix it Later."
For $1800, I expected more. (And a headphone jack.)