Jump to content

Attila Bakos

Members
  • Posts

    513
  • Joined

  • Last visited

Posts posted by Attila Bakos

  1. 16 minutes ago, androidlad said:

    From LUTCalc data.

    HLG was not designed to be an acquisition format, the curve is extremely non-linear and hard to grade manually.

    I think HLG does offer a bit more shadow detail due to its efficient use of all available bits, compared to F-Log's more compressed tonal range (elevated black level). 

    I'm really starting to like HLG more, mostly because the new colorimetry, it's more clean and neutral.

    But in LUTCalc you can choose between NHK / BBC reference white scaling, and the BBC one gives you 38% IRE for 18% grey, which I believe is closer to what's happening in the X-T3 when you let the camera figure out middle grey. I filmed a lastolite middle grey background filling the entire frame and I could only see about 10% IRE difference between F-Log and HLG.

  2. 18 hours ago, androidlad said:

    BT.2100 HLG maps 18% grey at 22% IRE

    Where do you get the 22% from? I couldn't find it in the specs.

    I also did my tests with the X-T3 when the update arrived. I used ETTR and placed highlights at the exact same level near clipping, then pushed shadows to the same level in post. Overall noise level was identical, and to my surprise I could get a little more detail out from the shadows of HLG even though they appeared more crushed. The difference is very little though, I wouldn't base my choice on it. I've chosen to stay with F-Log, because I learned to work with it in the past and I find it easier now.

  3. 54 minutes ago, thephoenix said:

    Sure It has nothing to do with fuji af. Would probably need to use It manual  but It has stabilization and 2.8 

    Might answer my needs for handheld  

    Not sure if it matters to you, but the body corrects for CA, vignetting, and distortion when you use the Fuji lens. You won't have that with the 17-50.

  4. 4 minutes ago, Emanuel said:

    Not Ninja V, but with Inferno (Z7 running firmware 1.0) :

    https://www.dropbox.com/s/kgtgezwqaayinb2/Z7 N Log 4k.mov?dl=0

    courtesy by Jeff Curtner

    Thanks, I already have that one :) That seems to be the only one available on the net. Something else would be great then :)

    @DBounce On a second thought, I would be happy if you could share a short footage shot with the lens cap on.

  5. 38 minutes ago, androidlad said:

    On the regular 5in Video Assist, there's a "HDMI Range" setting that allows you to specify the range of input signal. It's very simple for Atomos to implement this, instead of treating all input signal as video range.

    ProRes can contain either full or video range data, it just need to be specified in the metadata header.

    Well, the 4K version doesn't have that. And I graded X-T2 F-Log files coming from the BM Video Assist 4K, one of the Atomos recorders, and the Convergent Design Odyssey 7Q+, they were all video range. It's really not a problem of Atomos, altough I imagine it would be fairly easy to implement what BM did on the smaller Video Assist.
    I'm not sure if Prores has flags for full or video levels. I've never seen a full range Prores 422 for example. I'm on Windows so I could only try ffmpeg, but the Prores implementation ignored my level scaling parameters.

  6. 20 hours ago, androidlad said:

    It's a known unresolved issue for many years, Atomos applies a forced data range to video range scale regardless of the actual range of the source, clipping highlights and crushing blacks, making the images look more contrasty. Fortunately the range can be mapped back in post, as demonstrated in previous posts.

    Are you really sure that it's an issue with Atomos? My X-T2 recorded in-camera F-Log as data range, but when I used it with the Blackmagic Video Assist 4K, it recorded in video range, levels went up to 109% IRE. It's also worth noting that Prores is assumed to be video levels, except for Prores4444 RGB. As long as the data is there just mapped differently, I wouldn't worry. In Resolve it's just a few clicks to map it back to data levels, in other NLE's or on the recorder itself you can use a LUT for that. I can create such a LUT if anyone's interested.

  7. 3 minutes ago, androidlad said:

    X-T3's F-log introduced some small but obvious changes in its colorimetry. X-T2's LUTs aren't fully compatible.

    I know, that's why I'm creating new ones. BTW you're Luke Mason right? Why did you create a new account?

  8. 5 hours ago, thebrothersthre3 said:

    Yes! I am excited for HLG. Also looking forward to using film simulation luts to monitor log. I wonder if they will have more luts for vlog other then eterna(classic chrome maybe?)

    I will have :) Check the ones available for the X-T2 at http://colorizer.net. You can also try them for the X-T3's F-Log. Just make sure to switch footage to use video levels. 

  9. 9 hours ago, androidlad said:

    I think it only records fine because the camera has a large buffer (for 30fps stills shooting).

    Noticed a strange phenomenon today, when using the touchscreen to pull focus in video during recording, in AF-S mode, a touch would only half focus on the subject (focusing starts slowly and stops midway). In AF-C mode it works wonderfully though, locks dead on almost every time. But AF-C focuses everywhere the focus box goes and does not offer much control vs. AF-S.

    Anyone experiencing the same?

    @Cameramoto

    @Attila Bakos

    Yes, I have the same problem, didn't find a solution yet.

×
×
  • Create New...