Attila Bakos

14 minutes ago, webrunner5 said:

Wow AF is terrible! And people complain about the GH5. Holly crap.

Since the X-T2 looks better here, it must some pre-production firmware issue. It's also worth noting that the X-T2 focused as fast as the A6300 in Max Yuryev's comparison, it only lacked the smoothness of the Sony.

We don't know the exact settings but AF on the X-H1 leaves some to be desired.  Also notice the focusing smoothness of the A6300 compared to the Fujis.

1 hour ago, Axel said:

My opinion: terrible! Way over the top (you can judge even in SDR that the colors are ridiculously oversaturated, most of the time). This kind of HDR grading borders on assault. 

I don't have a HDR display, but you're right, some of the shots are waaay oversaturated even on SDR. People still like it nevertheless.

I would use masks/keys and Resolve's deband filter for this kind of stuff.
Just one frame: before | after
I did not finetune the key so there is some detail loss here and there, I also modified the sky's color a bit. This is way faster than grain + denoiser.

16 minutes ago, Matthew Hartman said:

Neat Video is THE defacto industry noise reduction plugin worth every cent they charge for it. I would rather purchase Neat Video than buy another LED light. 

My process is to first run an instance of Neat Video, than grade the footage, then add a very subtle instance of noise to further help with dithering. In most applications, I don't need the noise instance to help smooth out banding and artifacts because Neat Video takes care of most, if not all of it. The noise layer is mostly psychological for me because that's how I took care of business before Neat Video came along. I seriously doubt a manufacture could script a NR algorithm in-cam on the fly with the power the NV delivers. 

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

I'm sorry if this was already posted, but you can clearly see the problems with the new 100/120 fps mode:

If you don't have straight lines and you're shooting with narrow DOF, then it can be fine, but other than that...

1 minute ago, cantsin said:

Recorded with an external recorder, I guess? (So 8bit 4:2:2 ProRes without transcoding?)

Yes, the frames are directly exported from Resolve. I believe banding would be much less visible in 10bit. The pink patch might not be related to 8bit though, but to some problem with the F-Log implementation in the X-T2. The red channel is very noisy and from the footage I've seen so far they fixed this problem with the upcoming X-H1.

My samples are from ProRes 422. 492Mb/s at 2160p25.

Yeah, and btw it can be used in more difficult situations as well. Again, F-Log, very strong grade, banding and nasty pink patch:

:

Now there are the rooftop edges, branches, whatnot, and you don't want them to be affected. In Resolve I was able to do a very precise selection with the HSL selection tool. Just make sure you use zero or very minimal softening. Then I applied grain and then noise reduction. You have to play with the grain and noise reduction amount until it looks the best. At this step the pink patch was already better, but I changed it's hue to match the rest of the sky, then applied some midtone detail in the same mask, and arrived at this:

Like it was shot in 10 bit

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.

F-Log out of the box is not that pleasing (not to everyone at least), it has a green tint when compared to the in-camera profiles. I used the X-T2 + BM Video Assist 4K to create LUTs for F-Log that emulate the film simulations of the camera (at -2 shadows, -2 highlights, -4 color). I don't know how my LUTs will work with the X-H1, but I've found one of the sources that was used in the Slashcam test, and applied my LUTs to it. Although I can't tell you how accurate they are, I can see that we'll have some room to grade before the footage breaks.

Original F-Log frame

F-Log + Provia LUT

F-Log + Velvia LUT

F-Log + Astia LUT

F-Log + Classic Chrome LUT

F-Log + Pro Neg Hi LUT

F-Log + Pro Neg Std LUT

Since I emulate the flattest in-camera settings, you need to apply some contrast and maybe saturation.

X-H1 F-Log test:

1 minute ago, Matthew Hartman said:

I can't wait to see the soon to be announced Samsung S9+ record 120 in UHD HEVC. In good light, it could actually be usable in certain situations. 

Don't want to hijack this thread, but holy shit, 120 in UHD HEVC, is this for real? The S8 maxes out at 30.

1 hour ago, bigfried said:

https://www.youtube.com/watch?v=SnV-fo8Wuk0

Is it me or is there a heck of a lot of moire throughpout this clip, and considerring this is a pro produced marketing hype they must have minimised it.

hair at 0.23

bag at 0.28

camera lens at 0.38

etc etc

I believe that's the new 120p mode, it looks very bad. I saw the same thing in all the 120p X-H1 videos I could find. There is a reason they left this out from the X-T2 which has the same processor. They kinda had to include it in the X-H1, but it's seems there's a price to it.

4 hours ago, Andrew Reid said:

Blown away by the codec...

This shot had some serious underexposure going on.

At least 3 stops head-room in the highlights.

Brought the shadows up in Premiere and remapped to 16-235 (Fast Color Corrector)

There's almost zero signs of compression in the shadows!! Which came up from invisible.

The first image shows an image encoded with data levels interpreted as video range. It will look more contrasty than it really is. Premiere does that with the NX1's files, that's why you have to do the remapping. So your "before" image should be the one after the fast color corrector, this way it's a bit misleading as correcting a bad interpretation is not part of the recovery.

18 minutes ago, Inazuma said:

@jonpaiswhere did you hear that you can change the focus rings to linear?

This is from the dpreview first impressions artice: "A linear response option for focus-by-wire lenses is something we've long been calling for, but Fujifilm is the first manufacturer to listen"

I also saw in in some youtube video, can't remember which one, but the feature is really there.

I'm not sure if this was mentioned before, but there is a very annoying bug with the X-T2, and it is still present in the X-H1. If you use the grip and one of the batteries dies, recording will stop. This means you have to guess how many minutes you have left in the battery that is currently used, and plan accordingly. If you think the remaining time is not enough, you have to pull that battery from the grip. This is a pain in the ass really.

I'm sure not many people shoot F-Log with the X-T2. I do, and in many cases the footage is unusable because of the noise in the red channel. Sometimes it's really bad, like the implementation is broken somehow. Now I downloaded some X-H1 F-Log footage from the photographyblog.com, and it seems that they solved this issue. This is big news for a few people, me included

I use the Video Assist 4K to record F-Log from the X-T2, and I really hope Fuji upgraded the implementation in the X-H1. The red channel is a mess, even the slightest grade can create pinkish blotches. And this is something you can't remove with noise reduction. I've worked with 8bit C-Log and 8bit S-Log2, and to my eyes they are cleaner. So yeah, 8bit can be enough, but it's certainly not enough for F-Log, not with the current implementation. It also has a very obvious green tint, so you have to deal with that too.

2 hours ago, Eno said:

@Andrew Reid: "A first for a Fuji camera, F-LOG with Rec.2020 colour"

Rec. 2020 defines a bit depth of either 10-bits per sample or 12-bits per sample, have I missed the 10 bit output somewhere in the specs?

It records in the color space defined by Rec.2020, just like the X-T2 (with external recorder). The X-T2 is 8bit only, and I'm afraid the same is true for the X-H1, which is very unfortunate.

37 minutes ago, DBounce said:

I have to admit, when I shot that footage and bought it into post I thought nothing short of raw could recover those blown out whites. I really didn’t think the data was there. But apparently HLG is pretty data rich.

Just asking, is there a chance that you interpreted HLG as video range in your NLE? My understanding is that it's full range, and it might look clipped when interpreted as video range, even though it is not.

I wish they added 4K60, but yeah, probably not gonna happen. I also wish for 10bit, internally or externally. I'm shooting F-Log with the X-T2 and with 8bit it leaves some to be desired. And I'm not sure if it's just my X-T2 or a general issue, but the camera gets hot relatively fast when you use HDMI out. And thermal noise appears after a few minutes at ISO 6400 and above, which you won't see when you only record internally. Oh and it would be great to have waveforms or rgb parade in video mode. And adjustable zebras.

Well, in theory you could build a Cordova/Phonegap app where the index.html inside the app does nothing but a window.location.href redirection (as long as the target URL is whitelisted in the app). Then it would be the same as your app, and it could be compiled for other platforms too. I haven't tested it but I don't see why it wouldn't work.

Cordova/Phonegap is not made for redirecting to a web URL, it packages your entire web application into the app, and it runs it in a webview. It gives you access to hardware functions though specific javascript calls, and compiles to multiple platforms without too much effort. I'm not sure if this would work out for you, it all depends on the HTML5 support of the webview engines on each platform. Just something I though you might want to take a look at.

Wouldn't it work in a webview? Then you could compile it with Cordova/Phonegap to multiple platforms.