HDR color space irregularities

    Okay it's cool to see Premiere has changed their output options there for HDR. Sorry about being inaccurate about that. Haven't tested that in a while. When I tested it, it was just a single checkbox for HDR and that was it.

    However, your source isn't anywhere near that dark. The source values are flat out wrong. Like I said, MaxCLL in your source is probably close to something like 2000. MaxFALL I wouldn't be able to tell you without taking a lot more measurements.

    Zitat von Vouk

    I was mistaken. It's the codec context I need to supply these values to. Still, they are unspecified by default and i guess we need to be able to set them somehow without any filters.

    I see two cases:

    1. leave it at unspecified when no filters are used. If someone wants they can set these manually in x265 and maybe other codecs that have those options. This is how I use 2.3, I believe.

    2. They can use filters to specify them if they need to be specified

    Zitat von scarbrtj

    FWIW here's the HDR info from the source at the moment of source capture

    https://i.imgur.com/Yhck95q.png

    Okay, so either that is a measurement of a single frame, or Premiere absolutely is transforming your RGB values, making highlights brighter (and shadows darker)

    If the whole source gives you that metadata, you should use it in premiere. But Premiere is still setting the output inaccurately it seems.

    Zitat von morphinapg

    Okay, so either that is a measurement of a single frame, or Premiere absolutely is transforming your RGB values, making highlights brighter (and shadows darker)

    If the whole source gives you that metadata, you should use it in premiere. But Premiere is still setting the output inaccurately it seems.

    I am using an HDFury Diva (https://www.hdfury.com/product/4k-diva-18gbps/) to generate that info so I would *guess* it's not individual frame but the HDR metadata as transmitted by the source itself for the entire stream. That is, this info pops up the split second an HDR stream starts, and that info doesn't change for the entire time I capture.

    Well I think we can all agree ingesting and encoding HDR is pretty complicated to get right.

    Zitat von scarbrtj

    I am using an HDFury Diva (https://www.hdfury.com/product/4k-diva-18gbps/) to generate that info so I would *guess* it's not individual frame but the HDR metadata as transmitted by the source itself for the entire stream. That is, this info pops up the split second an HDR stream starts, and that info doesn't change for the entire time I capture.

    Well I think we can all agree ingesting and encoding HDR is pretty complicated to get right.

    Okay I know the HDFury gets it right. Premiere is definitely expanding from limited to full range then, which causes the nit values to display and measure incorrectly. It might still look close enough in many places, but it's not a totally accurate reproduction. My process should result in something much more accurate.

    And with the setparams filter in the future, that process should be applicable to NVENC HEVC as well.

    Zitat von Vouk

    2.3rc2 allows you setting different color space values using the "setparams" filter.

    Hope that helps.

    https://github.com/Vouk/voukoder/releases/tag/2.3rc2

    I tested it and it works. I can't fully test 10bit HEVC with NVENC because my GPU doesn't support 10bit encoding with NVENC (GTX970) but with 8bit selected, all of the correct color space flags get passed correctly. I've updated the HDR guide to add this bit of detail.

    So we can still only select bt709 color space here:
    https://i.imgur.com/RrXUZaB.png

    And that's what I chose. I am using NVENC HEVC. Here setting param's thusly
    https://i.imgur.com/cnsQBzD.png
    https://drive.google.com/file/d/1t5zjJe…iew?usp=sharing
    We get encode equally as bad as before. Looks like s**t.

    And setting param's like this
    https://i.imgur.com/CPIOb2o.png
    https://drive.google.com/file/d/14333ed…iew?usp=sharing
    We get an encode that actually looks very reasonable... if you play back on an SDR monitor. This is, so far, the best Vouk has done w/HDR source and an HDR encode. HOWEVER, if you play back this file on an HDR TV, evidently there is no metadata and the TV will not "engage" HDR mode and doesn't see this as a trie HDR10 file. And thus the playback shows quite overblown highlights and some weird coloring, although not quite as bad or as pronounced as in all previous versions of Vouk.

    2.3rc2 HDR still essentially broken even with setparams. But I think you are almost there. Now you just need to get the HDR metadata in there somehow so that an HDR monitor or TV will "know" it's truly dealing with HDR. In 2.2, when outputting with HEVC NVENC, although the files looked bad the TV would know it was HDR. Again as I previously shared:
    https://drive.google.com/file/d/1zy6b8i…iew?usp=sharing

    The mediainfo looks quite similar between 2.2 and 2.3rc2 outputs, so you have obviously changed something since 2.2 which now no longer enables an HDR TV to "see" HDR.

    (Obviously with the caveat can do this HDR encoding guide thing, but that is too difficult when Premiere can output good HDR footage as is. I will however try the HDR encoding guide next. But I still obviously would love to get HDR just to work with Voukoder alone without adding Premiere Lumetri stuff etc. Almost there I think!)

    Also would still note 2.3rc2 encoding NVENC HEVC slower than 2.2. 2.2 CPU use would be ~50% and use single GPU at 50%. Now I get this with releases since 2.2:
    https://i.imgur.com/KWy93LR.png

    Zitat von morphinapg

    scarbrtj are you using the plugin preset I included in my guide? Without that, it won't look right. You need that for correct unclipped HDR output

    Now my "problem" I would like to see solved (before going down the encoding guide road, Lumetri etc) is in 2.2, HDR10 metadata was included with HEVC NVENC and TV would engage HDR mode. Now, it will not with 2.3rc2. Would like to see that added back somehow.

    Regarding HEVC NVENC... To put another way, 2.2 made true HDR10 files that looked really bad. 2.3rc2 makes files that are not true HDR10 from a 4KHDR TV standpoint but look a lot less bad than they ever have.

    Zitat von scarbrtj

    Now my "problem" I would like to see solved (before going down the encoding guide road, Lumetri etc) is in 2.2, HDR10 metadata was included with HEVC NVENC and TV would engage HDR mode. Now, it will not with 2.3rc2. Would like to see that added back somehow.

    Regarding HEVC NVENC... To put another way, 2.2 made true HDR10 files that looked really bad. 2.3rc2 makes files that are not true HDR10 from a 4KHDR TV standpoint but look a lot less bad than they ever have.

    Again are you using the plugin preset from the guide? It's the only way to get the colors to be pre-processed correctly to look right on HDR output. Otherwise you'll get way blown out highlights and oversaturated colors.

    Again, for the TV thing you may need to try both MP4 and MKV, and if neither work, you can try remuxing. I've had that issue before too, it's not the video encode, it's with the way ffmpeg handles the container it seems. Sometimes it works, sometimes it doesn't. Also, files that won't work on one device may still work on others. I've had files not display on my TV but work fine on my 4K Blu-ray player.

    It's possible the container issue may be related to the fact that the encodes are flagged as variable frame rate, and need to be flagged as constant frame rate. Extracting the stream and remuxing can solve this. Also, manually selecting the frame rate in mkvtoolnix may solve this as well.

    EDIT: Nevermind this appears to be fixed in the latest build

    Einmal editiert, zuletzt von morphinapg (5. Dezember 2019 um 22:50)

    Zitat von scarbrtj

    I mean, it plays them fine, they just don't engage the HDR mode on the TV like all my other HDR files do. And this is a new (bad) behavior since 2.2.

    When I say it plays them fine, I mean it triggers the HDR mode. My encodes from earlier betas were having that problem (which remuxing solved), but RC2 works fine for me.

    If you're having an issue getting the TV to recognize it as HDR, this was my process whenever I encountered that in older builds:

    First, extract the streams using gMKVExtractGUI:

    https://sourceforge.net/projects/gmkvextractgui/

    Then mux them back together. My choice was to use the MP4 Muxer gui in MeGUI:

    https://sourceforge.net/projects/megui/

    Open MeGUI, if it asks to update, do so, then go to tools -> Muxer -> MP4 Muxer, and from there, import your extracted video and audio tracks.

  • Vouk 6. Dezember 2019 um 08:34

    Hat das Label In Bearbeitung hinzugefügt.