Did you do a MediaInfo (https://mediaarea.net/en/MediaInfo) of both files to compare them with each other?
In my case:
General
Complete name : C:\Users\Daniel\Desktop\test.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/mp41)
File size : 23.7 MiB
Duration : 7 s 424 ms
Overall bit rate : 26.7 Mb/s
Tagged date : UTC 2019-12-06 11:03:49
Writing application : Voukoder (Adobe Premiere)
TIM : 00:01:09:24
TSC : 60
TSZ : 1
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4.1@Main
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 7 s 417 ms
Bit rate : 26.6 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.214
Stream size : 23.6 MiB (100%)
Color range : Full
Color primaries : BT.2020
Transfer characteristics : HLG
Matrix coefficients : BT.2020 non-constant
Codec configuration box : hvcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 7 s 424 ms
Bit rate mode : Constant
Bit rate : 96.0 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 87.3 KiB (0%)
Default : Yes
Alternate group : 1As Voukoder is using FFmpeg internally, maybe it would be a good idea to create an FFmpeg command line that creates a perfect video from your point of view.
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.
Be careful with how you describe this. With the NVENC process, no "metadata" will be created. Metadata is specifically describing MaxCLL, MaxFALL, and mastering display characteristics. That unfortunately can't be included in NVENC encodes as far as I can tell. But most devices don't actually require this to display HDR video. They just fall back to a default tonemapping algorithm.
However, mediainfo confirms colorspace, transfer characteristics, and primaries flags are correctly included in the video stream. My TV recognizes these and plays them correctly without modification. Why your TV doesn't is unknown. I would imagine some difference with the container formats. Are you making sure to select 10bit in your encoder settings? (although my TV still recognizes it as HDR even with 8bit as long as those other flags are in there)
Maybe you can upload a file that worked, and then a file that doesn't, and I can see if I can find anything about them that differ.
As you can see they are essentially exactly the same except for "transfer characteristics" which was PQ in v2.2 and now, I guess with setparams filter, it becomes something else.
That's your problem. PQ is what's required for HDR10. With setparams you should set transfer characteristics to SMPTE2084, like this:
BT2020-10bit is a totally different transfer function, not what your TV expects for HDR. In your earlier post you said it looked bad, but it will look bad if you don't apply my preset to it first. Import and apply the Premiere preset, then encode with the above settings, then test it on the TV.
Lets look at the whole processing chain:
So it's more or less clear why this is not working:
I have to admit the 10bit (and higher) modes really need improvement.
But all changes need to be done in the connector, not in the voukoder itself. It is about how to get the right information from Premiere.
That's your problem. PQ is what's required for HDR10. With setparams you should set transfer characteristics to SMPTE2084, like this:
BT2020-10bit is a totally different transfer function, not what your TV expects for HDR. In your earlier post you said it looked bad, but it will look bad if you don't apply my preset to it first. Import and apply the Premiere preset, then encode with the above settings, then test it on the TV.
In 2.2, PQ is not selectable. The encode just comes out that way. In 2.3, I set the settings just like you showed for another file I previously provided a link to...
2020.2084.2020.mkv:
https://drive.google.com/file/d/1t5zjJe…iew?usp=sharing
And still no HDR-detectability by TV.
Re: HDR encoding guide, here is monitor with the Lumetri presets you provide:
https://i.imgur.com/ZjRO5fV.jpg
And here is what it is "supposed" to roughly look like:
https://i.imgur.com/QPMnHsA.jpg
And here is output file sample using BT2020/SMPTE2084/BT2020NC:
(the link is coming! will update in a minute....)
Using your guide, the output is ULTRA-dark, almost unwatchable; this is what we might guess it would be just from the monitor view in Premiere. For me for whatever reason your HDR encoding guide is the worst I have seen so far in terms of outputs. Try it on the source file I originally linked to.
- Version 2.3 changed this behaviour to:
- Format: PrPixelFormat_VUYX_4444_32f (BT601 selected)
Input: bt601
Output: unspecified (or set by setparams / colorspace)- Format: PrPixelFormat_VUYX_4444_32f_709 (all other selections)
Input: bt709
Output: unspecified (or set by setparams / colorspace)
Dumb question:
Can we not have
I expected that question.
These are the pixel formats available: https://raw.githubusercontent.com/Jam3/ae-threej…DKPixelFormat.h
So if there is not color space mentioned... what color space is it in?
Alles anzeigenIn 2.2, PQ is not selectable. The encode just comes out that way. In 2.3, I set the settings just like you showed for another file I previously provided a link to...
2020.2084.2020.mkv:
https://drive.google.com/file/d/1t5zjJe…iew?usp=sharing
And still no HDR-detectability by TV.
Re: HDR encoding guide, here is monitor with the Lumetri presets you provide:
https://i.imgur.com/ZjRO5fV.jpg
And here is what it is "supposed" to roughly look like:
https://i.imgur.com/QPMnHsA.jpgAnd here is output file sample using BT2020/SMPTE2084/BT2020NC:
(the link is coming! will update in a minute....)
Using your guide, the output is ULTRA-dark, almost unwatchable; this is what we might guess it would be just from the monitor view in Premiere. For me for whatever reason your HDR encoding guide is the worst I have seen so far in terms of outputs. Try it on the source file I originally linked to.
The monitor SHOULD look dark/incorrect. It's pre-processing the output in SMPTE2084/BT2020, which your monitor is not displaying in. If you displayed it on an HDR monitor, in HDR mode, it would look correct. Since your TV is not displaying it correctly, what are you watching it with? It's very likely your player is not processing the HDR signal, an is therefore just showing you an image similar to the premiere monitor window. What does it look like if you re-import it back into premiere without my preset applied?
I'll test your video and see what I get.
I just noticed something, you have 3 lumetri filters applied. There should only be two from the preset.
This is what my premiere monitor looks like
EDIT: Encoded, looks perfect
Maybe re-download and re-import my preset?
I just realized something from your screenshot. Are you using Premiere 2020? I created and tested my preset in 2019, and that's what I'm still using for now. It's possible 2020 is handling HDR input differently than 2019 did. For example, 2019 doesn't map black levels correctly on HDR inputs, as it expected a full range video and got limited range instead, and so my preset had to correct for that as well. So if 2020 is handling HDR input differently, I'd need to create a different preset for 2020. If you happen to have a copy of 2019 still, I'd see if it's working there.
I just realized something from your screenshot. Are you using Premiere 2020? I created and tested my preset in 2019, and that's what I'm still using for now. It's possible 2020 is handling HDR input differently than 2019 did. For example, 2019 doesn't map black levels correctly on HDR inputs, as it expected a full range video and got limited range instead, and so my preset had to correct for that as well. So if 2020 is handling HDR input differently, I'd need to create a different preset for 2020. If you happen to have a copy of 2019 still, I'd see if it's working there.
yes I am using Premiere 2020, the latest version, just upgraded a couple weeks ago. Re: the "other" Lumetri you saw which I had added, it was empty/doing nothing. Only your two were active.
Your monitor is def showing the footage w/Lumetri correction a lot brighter/visible than mine (I understand it prob would look darker; mine is just REALLY dark w/your correction). Maybe the difference is Premiere 2020??? If so... I'm worn out! I don't wanna change and downgrade lol. And as mentioned, for whatever reason, it's essentially impossible (I am too dumb) for me to get Voukoder v2.3 to give me an output my HDR TV recognizes as HDR right now.
I expected that question.
These are the pixel formats available: https://raw.githubusercontent.com/Jam3/ae-threej…DKPixelFormat.h
So if there is not color space mentioned... what color space is it in?
That would seem to be... problematic for sure.
Okay, so I'm guessing the issue is premiere changing how it handles HDR Video between versions. I'll have to create a new preset for 2020 and then everything should be good.
That would seem to be... problematic for sure.
It's not. It doesn't matter what pixel format is being sent by Premiere, it only matters that the RGB/YUV values are correct for what your encoder expects based on the flags. Hence this whole preset I've been working on. It works fine in 2019, but I need to create a new one for 2020 it seems.
I just tested in 2020 and my preset still works correctly. Not sure what's going on with your end. Try redownloading the preset as I do see the preset is named differently in your screenshots and mine. Perhaps you grabbed an older version of it before I reuploaded. I don't remember exactly what I changed before I reuploaded, but I did change something.
Nevermind, found the issue
Never mind the previous post. I found the issue and created a new preset for Premiere 2020. Use this and then try encoding to HDR.
Remember, the output window will look desaturated and darker, but that's because it is transformed into a format that your display is not set up to preview correctly. It should however be in the correct format for 2020/2084 output.
and now maybe I can get a little bit of sleep today (lol)
