Attila Bakos

The example I showed earlier was possible because the video has a few seconds of unprocessed S-Log2/S-Gamut footage. The closeup at 5:05 is already processed, and it doesn't look like his S-Log2 grade, so it's possible that he used some other picture profile there.

I believe it's user error, and a common one unfortunately, even among people who actually teach log grading. He shot many clips in S-Log2/S-Gamut, and forgot to convert color space during color correction. This a screenshot from his video: Here it is corrected with the color space transform plugin in Resolve, I only added a bit of contrast: Now if I skip color space transformation and only apply contrast and saturation, see what happens: And finally this is the uploaders grade: So it's pretty clear what's happening here, it's not the camera's fault.

It's possible that you're correct, I can't check it now.

The camera eats the batteries one by one, the one in the body comes first, then it switches to the ones in the grip. When this switch happens, recording stops. The camera won't turn off, you just have to press record again. It's easy to forget, and because the screen is on, it's easy to remain under the impression that your recording is on. Then comes the surprise, and blood pressure rises to 200 in like 1 second.

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.

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

Veszprém, Hungary.

That's not that easy unfortunately. I created my own method and software to do these conversions. I take about 15000 reference points from each profile to build the conversion LUTs. So basicly I need to have the body for a few days, I can't give away my method and tools.

Hello, that's nice to know Und ich kann ein bisschen Deutsch sprechen

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

No, couldn't pull the trigger yet, I don't want to step back in AF smoothness and 1080p60 quality (I don't really care about 120 fps).

Unfortunately not a lot of people speak about the problem in 1080p60 because it's not that obvious, I wonder if it will be fixed at all. Seeing the new upgrades I kinda wish I hadn't sold my X-T2.

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.

And how exactly is that related to the problem we have with 120p slowmo?

Where? I only see antialiasing support for image scaling.

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.

Haha thanks, but it's a pain for me too, it would be so much easier if there was an anti-aliasing plugin for Resolve or Premiere. I couldn't find any, but I noticed that the avisynth community has some very skilled developers, and it's all free.

I was experimenting with a few anti-aliasing scripts in avisynth to see if I could clean up moiré & aliasing in X-H1 120p footage. It's not perfect but it makes the footage more usable. Download a comparison from here: DOWNLOAD On the left you see footage recorded in 120p F-Log (provided by Fenchel & Janisch), with my Classic Chrome LUT + a bit of contrast applied. On the right you see the same color correction with additional anti-aliasing, temporal noise reduction and post sharpening. Check the top of the bridge, less aliasing there. Also, the background buildings show less moiré. With more optimization the results can be even better. The only downside of using avisynth is, well, avisynth itself. It's geeky stuff, not suited for everyone.

You can loose short takes as well, if you forget that you started recording with low battery level on the currently used battery.

Keep in mind that it can't switch batteries when recording, which means recording will stop when a battery runs dry, so you have to plan accordingly.

@BTM_Pix I noticed this in many X-H1 IBIS videos, I believe the only solution is to hold it as steady as you can (ninja walking, no running) or use an additional gimbal, otherwise you will have these sudden corrections when the IBIS has no more room to hold the image in a fixed position. It's still better than IBIS on full frame.

That dual ISO mode ML implemented is not the same as having two native ISOs. The first one is basicly a kind of bracketing, the second one is two different circuits dedicated to a lower and a higher ISO, before gain is applied. These two native ISOs have about the same noise levels, which is obviously not the case with ML's dual ISO.

Thanks, that would be much appreciated! @frontfocus I had the same feeling so asked the guy specificly about the high speed setting, and he said it was switched off at the first shot.

@frontfocus Thanks for the test! I'm happy for the results but it's also confusing, that video earlier showed a massive difference in 1080p60 mode. I just checked it again, the movement is about the same, but the X-T2 looks noticably cleaner. There must be a difference in settings, or maybe his unit is flawed, I don't know. I don't really care about 120p, but as I'm switching from the X-T2, I want to be sure that I get at least the same 60p quality. Too bad I can't rent this camera where I live.