well so demux/mux not working
Vouk... can you confirm that HDR metadata is still being added to the h265 stream. It obv was in 2.2, and seems it might be, or is, for some users.... but I can't replicate that 2.2 behavior in 2.3 now. Do you think anything changed. The main difference I see is no longer being able to select BT2020CL or BT2020NCL in the main media export Premiere window.
My TV is playing the files just fine unmodified (LG OLED 2016)
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.
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.
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
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.
FWIW here's the HDR info from the source at the moment of source capture
https://i.imgur.com/Yhck95q.png
I did supply a link to source above
I noticed in the source file these values:
https://i.imgur.com/ucIzPGD.png
So I will set Premiere output to these values and see if the CLL "calms down", just as a test. Encoding it now....
https://i.imgur.com/2oxPqD4.png
"EDIT: Confirmed the metadata is not accurate, I quickly saw frames that had CLL above 1800 nits."
Did you download the source file, and does it show similar or dissimilar CLL
(yes I forgot ranges for HDR 
The metadata does seem to accompany Premiere output (did you download the file).
When I output/encode HDR in Voukoder (rc beta8 shows this behavior; 2.2 at least did cause TV to enter HDR mode) and try to play on HDR TV, the TV doesn't know it's HDR/does not convert into HDR mode.
When I output/encode with Premiere alone, the TV enters HDR mode and the colors/highlights/shadows etc look exactly the same as the source file.
Premiere does take longer to encode than x265; but right now as stands Voukoder+x265 is kludgey.
EDIT: Also, I *believe* that if the source file in premiere is 16-235, when Premiere outputs 0-255 it doesn't map 16 to 0 and 235 to 255, so full range output is fine in that circumstance. I *believe* this is why my outputs in Premiere look correct on a TV without clipping etc... because thus far all my sources are 16-235.
I saw the encoding guide, but this just makes Voukoder a more tedious option than Premiere alone which will handle h265 BT2020 10bit encodes just fine with proper color and SMPTE (Premiere native h265 Main10 bt2020 output: https://drive.google.com/file/…q41Pxu21/view?usp=sharing); Premiere alone will be software encoding just like x265 with Voukoder. And yeah, it takes like about 14 minutes for me to encode just 3 minutes of video this way.
For now it is better to rely on Premiere alone for h265 BT2020 Main10 encodes.
However, when you use NVENC in Voukoder, 4K h265 encodes at a rate of about 1:1, i.e. it takes just 3 minutes to encodes 3 minutes of video. A much better option if that will ever work! As an aside, Cyberlink software handles GPU accelerated HDR encodes very well. So we "know" NVENC will work....
You can't select these BT2020 etc options with HEVC NVENC. Do you not get faster h265 encode though with NVENC vs x265? Or the same, more or less?
Some notes. rc beta8 encodes h265 about twice as slow as 2.2 for me. With 2.2 it used one NVIDIA 1080 @about 35%. Now it uses both my 1080s at about 8-12% each.
Sample rc beta8 output:
https://drive.google.com/file/d/1Vd0pz-…iew?usp=sharing
On playback on 4K TV, the TV does not recognize it as HDR. Also, the whites are now "zebra-ed" on the TV which is a really weird effect. (You will almost certainly not "see" this unless you attempt to playback on HDR 4K TV.) Playback on an SDR monitor looks normal. Please note Voukoder gave me no choice but to choose bt709 colorspace as bt2020 is now gone as an option with update.
What I think we have here is just really a lot of problems with Voukoder and HDR and BT2020.
OK. Connector. Got it. Updated to rc beta 8. Now the BT2020 option is gone as an output space (which of course won't work for HDR10 and a BT2020 source file, correct?). What now?
[Blockierte Grafik: https://i.imgur.com/84KjILT.png]
well hold your horses. I installed release candidate. it does not show up in premiere; i thought new versions uninstalled old ones. so I uninstalled 2.2 and uninstalled release candidate. and re-installed release candidiate. still doesn't show up. will look through forum how to get this to install. is it because i updated premiere recently??
I can confirm with the update that the colors and highlights and etc are still way off. I believe you will be able to see on your own monitor the issues even with HDR->SDR converting. (However, on a 4K HDR TV it looks even worse although as I mentioned the TV "sees" the HDR10 metadata.) I am providing link to premiere output, voukoder output, and Mp4 source file (trimmed for size). Note how premiere output and the source file "look" the same. Voukoder output quite "off" (look st the icebergs; around 1:30-2:00 min in, all the highlight detail is off and overblown). I use MadVR for HDR->SDR.
vouk-16.235.bt2020.ncl.mkv:
https://drive.google.com/file/d/1zy6b8i…iew?usp=sharing
Premiere native h265 Main10 bt2020 output:
https://drive.google.com/file/d/16OW8BN…iew?usp=sharing
source mp4 file (trimmed):
https://drive.google.com/file/d/10G7-0E…iew?usp=sharing
thanks for reply. let me try new version. I am still on 2.2 I just realized. I will report back after updating to latest RC version.
I have an h265 mp4 HDR Main10 movie file. I am editing in Premiere Pro 2020 version. When I export with Voukoder, regardless levels (0-255 vs 16-235) or constant luminance or NCL, and I am exporting with 10-bit turned on in the Bt2020 color space, when playing back these files on an HDR TV the whites are WAY blown out. It's rather horrible. If I export with Premiere's builtin h265 exporter using Main10 settings, the video comes out looking pristine. I can provide you with the source mp4 file if necessary but it is ~50GB so will take some coordination.
My question is, have you edited true 10bit HDR BT2020 files and exported with Voukoder AND played back on an HDR TV? Vouk is passing HDR metadata to the TV (ie the TV "knows" it's getting an HDR stream e.g.).
Hope this makes sense. In short, I do not think Voukoder is exporting and handling HDR source files correctly. I am aware HDR is a work in progress in premiere, but premiere on its own handles these exports in a predictable and proper manner.
Also on another note--do you think Vouk is "over amping" or "over normalizing" Ac3 and EAC3 audio on export? It sounds very very loud when bitstreaming to receivers/TVs.
thanks in advance
