Jump to content

Attila Bakos

  • Posts

  • Joined

  • Last visited

Everything posted by Attila Bakos

  1. Do you have the latest custom build from Danne? For me 3584x1730 at 14bit is continuous, as long as I don't have clipped highlights. 12bit is hard to break.
  2. Remember we discussed earlier that X-H2s 6.2K ProRes RAW has a hot pixel at the exact same location for everyone? I spent days to create an executable in C++ that removes that hot pixel from the DNG raw file created from ProRes RAW. I was just about to post it here but then I noticed that this is not a hot pixel issue at all! All pixels in the same row right from the hot pixel are shifted towards the right. See here: It starts with the hot pixel, and it goes all the way to the right edge. Or here (this is the right edge of an image, you don't see the hot pixel here, it's somewhere in the middle): Atomos says it's Fuji's fault, and as usual, Fuji couldn't care less. Atomos is also silent about the framerate bug I discovered. A new firmware was released just now and it's not fixed, it's not even listed in the known bugs. Stuff like this makes me really disillusioned.
  3. The maximum I could get out from my 5D3 is 3584 x 1730 in 14bit lossless. That's not binned, it uses a 1.6x crop. We are now at around 150MB/s maximum with card spanning, sd card overclocking and several hacks to boost performance. And some talented people are still tweaking this thing.
  4. When you test this make sure you cut the first second or so. Chroma is worse in the first few frames. Will test what you found later. The problem I described in my video is that ProRes RAW doesn't even have the DR of F-Log.
  5. Actually I'm not a colorist, I'm a developer who loves color science, but I can tell you that the loss of color is final, no chance to get it back.
  6. I needed similar in-camera and external resolutions for a fair comparison. 6.2K was the only way because in ProRes RAW you only have full-sensor 6.2K or cropped 4.8K. I don't have a CF card so I can only record ProRes HQ to the Ninja, and 6.2K is not available there, it's only available in ProRes RAW mode. This is the reason for internal H.265 instead of ProRes HQ. And if you record in UHD 24p, internal H.265 has actually more bitrate than ProRes HQ (720Mbps vs 707Mbps). I tested it, H.265 actually looks better due to more efficient compression. To you other question, I did not use any LUTs during my testing, I usually work with color space transform or aces nodes.
  7. Summary of my findings so far:
  8. Yes the blacks are just cut at a certain point, F-Log has at least 1 stop advantage over ProRes RAW, F-Log2 even more. Even 5D3 ML RAW has better dynamic range in 12bit mode. Something is not right about blacks being cut like this, I have no idea why Fuji does it. The only good thing I can say about ProRes RAW on the X-H2s is the color, this is the only way out of Fuji's chroma smoothing.
  9. Well, just got reply from Atomos about the bad pixel issue in 6.2K raw: Please note that our engineering has gone over your case and replicated and tested your setup. Unfortunately, the issue lies with the camera as it is outputting the bad pixel in 6.2 k RAW. We would love to help you fix the issue but as it is on the camera end our hands are tied. Please contact the camera manufacturer to get this issue resolved. Fuji doesn't give a shit about my emails, so I wouldn't expect a fix anytime soon. This, and the framerate issue, and also the fact that Fuji's ProRes RAW has noticeably less dynamic range than F-Log, not to mention F-Log2, makes me loose faith in this company, they do a lot of things right but they always have to fuck up little things like this.
  10. I'll correct myself, it's there in the Ninja V clips as well.
  11. A small update on the X-H2s + Ninja raw recording. We tried another body and another recorder as well, and this is a general issue, not related to my unit. When you put the body to 6.2K raw mode sometimes you will get like 12 fps. It's easy to reproduce it when you switch between 23.98 and 24fps 10-20 times, at some point you will enter this low fps mode, and sometimes it stays in this mode even if you hit record. Really annoying. I also checked this another X-H2s body for that specific "bad pixel", and it's there, only in 6.2K raw mode, so this is a general issue as well. However, it was not visible when we used the Ninja V, it's related to the Ninja V Plus. I'm discussing these with Atomos already, will keep you posted. However, Fuji doesn't reply to any of my emails, so if it's their fault, I'm not sure what I can do.
  12. Ok thanks, it seems to be the same location but I'd like to make sure :)
  13. Thanks but I meant an actual still image from the recorded clip, so that I can check the exact location.
  14. Can you send me a still that shows this pixel? I wonder if the location is the same...
  15. Interesting you say that because I have a single pixel in the center of the screen as well, only in 6.2K ProRes RAW, it's not visible in 4.8K. If it's a bad pixel I'm not sure how Atomos could fix that, and why it's there in 6.2K and not in 4.8K. Even 4.8K60 is fine. Anyway, this is what I'm getting: https://drive.google.com/file/d/1m1w9o4LmO85ER9AWg3OFgQnJK1Q9cmMR/view?usp=share_link In the first half I pressed record on the Fuji, and I got like 12fps. Then I turned recording off and back on, and it was fine after that, as you can see in the second half. And this is one way to trigger it (download before watching): https://drive.google.com/file/d/1G0J2dvH2IS0mZIWlee0DZ5Rf4xvz97IK/view?usp=share_link But basically any change can trigger it, like tapping on the screen to refocus, it's totally random.
  16. Does anyone use the X-H2s with a Ninja V Plus? Some of my 6.2K 24fps clips are stuttering badly, only every second frame is different, so it's basically 12fps. It happens and goes away by random camera actions. So if it's good and you don't touch the body it stays good. But even refocusing can make it bad. The camera is in boost mode, I hit recording on the body as well, newest firmware everywhere. The cable I'm using is HDMI2.1 8K60 certified, should be more than enough. I'm out of ideas really, I hope it's a user error but I fear that it's not.
  17. To anyone who is interested in recording ProRes RAW with the X-H2s, I just got confirmation from Fuji that they convert X-Trans to Bayer in the camera, as I suspected. Because the two patterns are different, you have to calculate what's not there. So let's say at a given pixel X-Trans stores red but for Bayer we need blue. I asked Fuji if they interpolate this blue using the surrounding blue values in the X-Trans pattern or they just copy the value of a blue neighboring pixel. The latter is faster but more prone to artifacts. Unfortunately I received an one-liner that this is proprietary info. I'll know more when I test this out myself, I'll receive a Ninja V+ in the following days.
  18. I don't have the GH6 unfortunately, but I checked a ProRes HQ V-Log L sample and the chroma channels are very good. The Fuji chroma smoothing is there in all internal and external recordings, the only exception is ProRes RAW. As I mentioned earlier it's weird though. ProRes RAW can not hold X-Trans data, it's designed for Bayer. Atomos already confirmed to me that they don't modify the raw feed. I'm still waiting for Fuji's answer, but the only thing I can imagine is they demosaic X-Trans in the body, then remosaic it into Bayer and send that to the recorder. While it works it is kind of a trick, and when we compare ProRes RAW features to BRAW, one of the main things that sets them apart is that ProRes RAW is not debayered and thus more raw-like, while BRAW is partially debayered. So I'm not sure if we can talk about being not debayered as an advantage here, as the raw feed that the Ninja V records is actually already processed by the camera. And if you go into details, demosaicing is basically filling the "holes" in the R,G,B planes by interpolation methods, using the pixels that are known. See the "holes" here (it's for Bayer, but you'll get the point): Now if you remosaic the R,G,B planes to Bayer, you have to throw away about half the originally known values, as the pattern is different. You exchange them to interpolated values and send them to the Ninja as if they were the known values from the sensor. I have my doubts about the quality of this method, but I will test it when my Ninja V Plus arrives.
  19. Revised my findings, the previous comment can be deleted. (Both bodies are equally bad in 1080p.)
  20. I read some comments about the 1080p quality being worse on the X-H2s than on the X-T3/4, and I thought it's nonsense, but after a few quick tests it is worse indeed, for some reason the moiré/aliasing artifacts are more pronounced. Not sure about the reason yet, maybe the readout is different.
  21. Recently purchased the X-H2s, and you know me, the first thing I look at is chroma resolution. Just dropping this in, on the left side you see the Cr channel of an EOS R 4K C-Log 8bit 4:2:0 recording (about 420 Mbps), on the right side it's X-H2s 4K F-Log 10bit 4:2:2 (about 615Mbps): Don't get me wrong it's better than the X-T3, but this smoothing can still lead to loss of color. I really wish we could turn it off and deal with color noise in post. ProRes RAW helps but it's a mystery to me. RAW on the X-H2s has the X-Trans pattern, obviously. However, it gets magically converted into Bayer in the ProRes RAW file. I had discussions with people who are involved in ProRes RAW->DNG conversion, also did my own test with Raw convertor (resulting DNG has Bayer pattern) and it seems that the data that arrives to a Ninja V recorder is already Bayer, even though the sensor is X-Trans. I'm still trying to confirm all this but if the body demosaics the X-Trans pattern and remosaics it into Bayer, then it's kind of a hack which in some cases can lead to artifacts.
  22. Ah yes you are probably right 🙂
  23. Yes the log profiles are worse. Btw when you're testing chroma components in Fuji files, make sure to skip the first few frames, those are worse than the rest.
  24. Attila Bakos

    Panasonic GH6

    It's not the red channel that's blurred but the chroma components in the YCbCr format, that is Cb, and Cr. Both Cb and Cr are blurred the same way, but I used Cr for demonstration as it shows the issue a bit better. Btw Cr is red minus luma, so you are not that far from the truth 🙂
  25. Forgot to mention that in this test in hybrid mode the decoding was done by the iGPU and the encoding was done by the dedicated GPU (as I encoded to 4:2:0), so they can really work together.
  • Create New...