Beiträge von scarbrtj

https://drive.google.com/open?id=1Iy559…iws9l1s2y3idmzA

I get about ~7db louder mix (in playback) with Vouk encodes.

you can try yourself, encode at dialnorm -31 or -1. I play back in MPC64 or bitstream to my receiver. Whatever dialnorm value you set in Voukoder it doesn't change the playback volume strangely. So it must be some other bit of metadata.

would it have anything to do with dialnorm or bsid( whatever that is)

The original is on left and the vouk encode on right. The original is dialnorm -27dB and vouk is -31dB. The original bsid is 16 and vouk encode is 8.

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

would you believe me that playing back the file made in vouk, it is much louder?
But when bringing the same file back into premiere the peaks and waveforms look exactly the same and the playback within premiere of the encoded file is NOT louder?
I know this sounds goofy but it's true.

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

I have found the sound "over loudened" in all outputs I have tried e.g. EAC3 and DTS too. And TrueHD too.

Def not clipping (ie all audio sources themselves at <0dB max peaks).

Vouk:

Output is def over-normalized in Voukoder. I can supply A/B comparisons if nec, but have you not also noticed this. Take in AC3 source file, re-encode as AC3 or EAC3 or DTS or TrueHD and we have noticably louder output in Voukoder encoded files. Not sure why that would be. However if you use SurCode in Premiere, which I would consider a standard, I notice it uses different channel levels for its outputs for AC3 and EAC3. Can you check on this and see if you agree with me.

ok will try that. can say the "usual" HDR workflow we have mentioned made Voukoder output a really weird looking output, and I know this was a P3D65 colorspace file. Although interestingly if you try to MediaInfo the file, you can not get a confirmation of that.

All...
If I have a P3D65 colorspace file... and want to output in that space of course... correct workflow to use NVENC for that? TIA.

Vouk... I would not know exactly, and maybe what I should have said is 8 channel audio or multichannel in general? You can setup multichannel audio beyond 5.1 in Premiere. I have never done it! But I know at least in theory it's possible, and that would be cool if we had that option for Voukoder. Mapping tracks to correct channels for conforming output... IDK.

https://community.adobe.com/t5/premiere-pr…on/td-p/9836832
https://tmpgenc.pegasys-inc.com/en/product/tppm4/00113.html

Would it be possible to implement a 7.1 audio export for EAC3, TrueHD.

Zitat von morphinapg

Premiere's editing workflow is rec709. Even when you edit HDR natively, it saves that in a floating point rec709 pixel format, which Premiere's native encoder converts back to PQ/BT2020 when you select HDR encoding (floating point ensures no color or highlight loss on conversion). When using any other encoder, you're getting that rec709 output, clipped to the first 100 nits. Hence why I needed to create the effect preset to "pre-format" the pixel data as PQ/BT2020. The problem is, Premiere thinks it's seeing rec709, so yes, you absolutely must use rec709 output for my effects preset to work. If you select anything else, Premiere will think it needs to convert the colorspace, modifying those pre-formatted values I so carefully calculated.

As for a Voukoder preset, the HDR process requires the premiere effects preset I uploaded earlier (or for your input video to be HDR without PQ/2020 flags) so it wouldn't be so simple as someone picking a preset in Voukoder. Their video needs to be sending the right color data to begin with or it will look completely wrong. That's why I wrote the guide I did. If they are sending the right color data to vukoder, then there is one preset you could create I suppose:

For just generic HDR support, simply using setparams with:

Will allow HEVC, VP9, H264, and ProRes (if not more) to output in some form of HDR (compatibility would depend on devices of course). HEVC is obviously preferred, so I would default to that with 10bit 4:2:0. You could create presets for both NVENC and x265, and for x265 I'd also enable "HDR Options" and "UHD Blu-ray conform" for the most ideal encoding efficiency. I personally use CRF13 with x265 with HDR content. I haven't experimented enough with NVENC to know what the equivalent would be there.

For a more "perfectly compliant" HDR10 encode, the user would also need to include the actual metadata that describes the brightness of the content and mastering display, as I describe in my guide. As far as I know, that's only doable on x265 for now. But it becomes a much more complicated process if you don't already have numbers prepared for that. The guide explains that process involving a tool I created to measure the light output of individual frames. So I don't think it would be particularly useful to create a voukoder preset with predefined metadata. That should be something the user is inputting themselves.

Alles anzeigen

Vouk any way to augment your setparams for HEVC NVENC to include MaxFALL and MaxCLL if user wants

Zitat von Vouk

So they way I get the pixel data from premiere is okay?

morphinapg Could you write down the settings (encoder, options, muxer, filter, etc) and a short description text so I could add this as preset? Or maybe even more than one.

From my viewpoint, yes. And if not, you're definitely on the right track.

OK, sorry been busy a few days.
Taking my original source files, using the new version of Voukoder, the new Premiere '20 presets from morphinapg... I am sorry to say...

It looks like 100% success The TV engages HDR mode. And for the first time, PRemiere & VOukoder are encoding HDR10 output that look ~exactly the same as (unedited) source files on an HDR monitor.

So good job! I knew my money was well spent

The only thing I'll say is I use MadVR for HDR->SDR on my non-HDR 4K PC monitor. Here, the Voukoder outputs are looking "greenish" compared to the source. Interestingly, though, as I said, this greenish hue seems to go away when playing back natively on HDR monitors. The original HDR source files do not show the green hue w/ HDR->SDR tone mapping.

This is just a niggling complaint, but maybe worth your while IDK.

(Also morphina, in PRemiere, your presets look very much better in the monitor in '20 version versus your '19 versions I was trying to use in '20.)

Zitat von Vouk

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.

Zitat von morphinapg

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.

Zitat von Vouk

• 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

• Format: PrPixelFormat_VUYX_4444_32f_2020 (all other selections)
  Input: bt2020
  Output: unspecified (or set by setparams / colorspace)
  
  My source is definitely BT2020
  https://i.imgur.com/ucIzPGD.png
  https://i.imgur.com/Yhck95q.png
  
  

Zitat von morphinapg

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.

hey guys thanks for looking at this. Look back at one of my original posts...

vouk-16.235.bt2020.ncl.mkv (done in 2.2):
https://drive.google.com/file/…S6JCsuWj/view?usp=sharing

Premiere native h265 Main10 bt2020 output:
https://drive.google.com/file/…q41Pxu21/view?usp=sharing

source mp4 file (trimmed):
https://drive.google.com/file/…B3oHj9CP/view?usp=sharing

It is the vouk-16.235.bt2020.ncl.mkv file, as produced by v2.2, that allows HDR on my TV (but the colors are wrong, etc).

Then here is a file (2020.2020.2020.mkv) encoded w/ 2.3:
https://drive.google.com/file/…qmJ4TJTc/view?usp=sharing
This file does not make TV go into HDR mode.

Mediainfo vouk-16.235.bt2020.ncl.mkv made w/ v2.2:

MediaInfo 2020.2020.2020.mkv mad with v.2.3:

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.

I uninstalled v2.3, and reinstalled v2.2. I made two new files...
using x265...(~14 min encode time fwiw):
https://drive.google.com/file/d/1xrxrkN…iew?usp=sharing
using NVENC...(~4 min encode time fwiw):
https://drive.google.com/file/d/1DhzaF1…iew?usp=sharing

Testing these, both make TV enter HDR mode. Which is interesting and hard to believe I know. So at least in my case, 2.2 produced HDR outputs my HDR TV recognize but 2.3 does not. And I can't make any of the 2.3-produced files "engage" HDR. It's 100% consistent working in 2.2 and 100% consistent not working in 2.3. For me. I feel like if I could get these 2.3 encodes to engage HDR on the TV I would be close to having good-looking outputs. Doing Lumetri etc in Premiere (HDR encoding guide) will not give me HDR-TV-engagement in 2.3. It will help outputs look good ultimately but won't solve this main issue for me.

Would be interesting (maybe) if you could add setparams filter to v2.2. Can this be done. I still go back to the fact that BT2020 was selectable in v2.2. (https://i.imgur.com/tvPv6kc.png). Vouk, why can this BT2020 not be selected in main media export dialog in v2.3? Why BT709 only? Why did that change from 2.2 to 2.3 versions?