Attila Bakos

6 hours ago, bsalisbury said:

Do you mean Davinci Resolve Studio. The 10 bit files don't play in the (my) free version which is not unexpected.

Oh yes I'm using the Studio version.

Just did a very non scientific power bank test with the X-T3. I fully charged the battery inside the camera with the factory charger, and I wanted to see how much time it takes until 1 unit on the camera display's battery level indicator is lost when using 4K60 recording (and boost mode turned on) with a power bank attached:

Anker 20000 PD: 25 mins until heat warning, I decided to stop the test there, indicator still showed full battery
Asus ZenPower 10050 (no PD on this one, just a regular power bank): 17 mins
No power bank attached: 13 mins

It seems it's a good idea to get a power bank with PD support. Actually this is what Fuji recommends as well.

Just now, bsalisbury said:

My apologies for what might be a noob question but my searches have not found the answer to the question whether Davinci Resolve Studio supports the 10 bit files coming from the Fujifilm X-T3. I can transcode these files successfully but hope I can just edit the 10 bit files on my timeline. I currently use the free version of DR but will upgrade if it works. Thanks for any help on this.

I only tried 10bit 4K25 files from my X-T3, but they play just fine in Resolve.

9 minutes ago, androidlad said:

What do you mean no need to multiply by 1.5? I thought all lenses are marked by 35mm focal length. So 18-55 would have FF equivalent FOV of 28-85?

True. Check here: http://www.fujifilm.com/news/n180215_02.html

In the 35mm format equivalent, MKX18-55mm covers a focal distance from 27mm to 84mm and MKX50-135mm covers a focal distance from 76mm to 206mm.

If you don't like the 4GB file splitting and don't mind a bit of work, download ffmpeg, put ffmpeg.exe and your mov files you want to concatenate into a folder, and create a bat file (in windows) in that same folder with the following two lines:

(for %%i in (*.mov) do @echo file '%%i') > mylist.txt
ffmpeg -f concat -i mylist.txt -c copy output.mov

Running this will concatenate all the mov files in that folder without re-encoding into a file named output.mov. Keep in mind that on an average HDD this can take at least 1 minute/4GB.

Just noticed that you can take a picture for custom WB in video mode as well. I'm not sure if the X-T2/X-H1 has this feature. I sold my X-T2 in January this year and back then I had to switch over to photo mode to set a custom WB.

2 hours ago, no_connection said:

It does show the auto iris being very ugly, and autofocus hunting and being very ugly. The slider shot looks so bad.

There is nothing about auto iris in that video, it's about auto iso. And if you disregard that slider shot, there is nothing ugly about auto iso. The slider shot is distracting because of AF problems. Maarten Heilbron did a better auto iso test which I linked a few posts before.

This one is specifically about auto ISO:

Is this true for the 16mm as well? It's newer than the 23 or the 35 1.4, it was actually introduced after the 16-55 2.8.

For auto ISO demonstration check this review from 31:10:

31 minutes ago, Mark Romero 2 said:

 

Wish there was some sort of consensus on this. I just asked Deane and Andrew on that video on their youtube channel and they said they were 100% sure that Auto ISO is not smooth.

They are wrong, it is smooth, I have the camera. Auto iris is the one that's stepped.

Nice Lenore figure, I love her too

Zhiyun just replied that they don't support Fuji, it won't work. 

3 minutes ago, androidlad said:

Did you set the stabliser setting in the app to Panasonic? Did you connect the microUSB to the tilt motor? Did you power on the gimbal first before the camera?

Yes, I did all of that.

Does someone have the Zhiyun Crane and the X-T3? The remote jack is on the right side on the X-T3, so the Panasonic cable included with the gimbal is just the right size, however it can't start video recording, or take images. You could of course say that it's meant to be used with Panasonic, but a friend of mine has a Moza AirCross and it works flawlessly with the X-T3 using the included Panasonic cable. I already asked Zhiyun, but maybe some of you can help.

23 minutes ago, androidlad said:

Another example showing the discrepancy between internal log recording and Ninja V recording, pretty drastic!

Maybe drastic is not the right word, that's a standard data levels vs video levels difference. If you put an original S-Log3 file into Resolve and set it to video levels manually, it will look exactly the same as the Ninja V file, which is automatically interpreted as video range.

Nice DR straight out of cam:

I used the X-T2 with a Video Assist 4K not long after it was released, and I'm not sure if firmware updates changed things, but this is how it worked: the in camera recordings were indeed full range, but HDMI was remapped to video range, so nothing was really lost, but precision (220 luminance levels instead of 256). F-Log over HDMI was a different beast, it went up to 109% RGB, so even though it looked like it clipped highlights, it did not, and in Resolve I could easily recover that part of the image.

7 minutes ago, androidlad said:

I believe the movie AF-C settings only take effect during recording, not in liveview standby.

Thanks! I used live view as I don't have a card with me at the moment, so that must be the case.

3 minutes ago, DBounce said:

Yes, I believe this is the case. They should add an option to switch it on when connected to an external recorder.

Back then when I used an external recorder with the X-T2, I HAD to press record on the X-T2 too, otherwise the HDMI signal quality was worse, so I'm kinda used to doing that

Can somebody pls check if AF speed under movie settings makes a difference? I'm using the 16mm 1.4 at the moment, and focus changes pretty fast, no matter what AF speed setting I use. It doesn't seem to make any difference if it's -5 or 5, am I missing something?

3 minutes ago, jonpais said:

Which lens were you testing?

The 16mm f1.4

My X-T3 just arrived, and the first thing I checked was that Auto ISO problem. Well, Auto ISO works perfectly fine, transitions seem smooth to me. Auto shutter is also fine. Auto aperture however looks exactly like on the examples people reported as being an Auto ISO problem. I believe they left the camera on auto aperture. Will do more testing later.

4 minutes ago, MattH said:

It will slow the footage down by 2.4 times instead of 2 times, but I don't see how it will be less smooth.  We aren't shooting interlaced.

I don't see that either. 10sec at 50fps is 500 frames. 10 sec at 60fps is 600 frames. If the project is 25 fps, the first one will be 500/25=20 sec long, the second will be 600/25=24 sec long, and they will be equally smooth. There is no skipping if you use up all the frames.

An informative comparison, it's interesting to see how much better H.265 holds up when the shadows are pushed:

Nice 4K60 shots with the 35 F2: