Log in

View Full Version : YV12 input hevc encoding also no hdr flag


lazyjss
4th February 2021, 01:39
Staxrip question
When i select the h265 Nvidia encoder the input color space is always yv12.
I am new to this and if someone would be kind enough to let me know if this is ok for my use.
It appears to signify 4:2:0 in what i can find online.
I am encoding my blu rays and my uhd blurays with a turing nvidia card into h265 hevc.
From what I can tell everything appears ok on the finished product.
AVS automatic changed to ffvideosource once i load my media.

Should i be on the look out for anything particular on my media when using this input yv12?

Also I have updated staxrip and there is no longer a hdr flag in the h265 nvidia selections, is this an issue?

Thank you for any wisdom shared

Blue_MiSfit
4th February 2021, 02:55
YV12 is planar 8 bit 4:2:0 but I saw you mention HDR. This would typically require at least 10 bits.

lazyjss
4th February 2021, 17:18
i do not have the logs here at work with me, but in the output files
shows yv12 10bit>p010
can yv12 be 10 bit at all?
not sure how to read this, is it a conversion?

stax76
4th February 2021, 17:45
YV12 fcc is 8 bit: YUV420P8

P010 fcc is 10 bit: YUV420P10

benwaggoner
4th February 2021, 20:04
i do not have the logs here at work with me, but in the output files
shows yv12 10bit>p010
can yv12 be 10 bit at all?
not sure how to read this, is it a conversion?
And as a mnemonic, yv12 comes from there being 12 bits per pixel; 8-bit luma and 2 bits each for Cb and Cr (one chroma sample per 4 pixels in 4:2:0).

lazyjss
6th February 2021, 05:24
thank you for the help, here is an excerpt from the log file

NVEncC (x64) 5.25 (r1777) by rigaya, Jan 10 2021 12:50:12 (VC 1928/Win/avx2)
OS Version Windows 10 x64 (19042)
CPU AMD Ryzen 7 2700X Eight-Core Processor (8C/16T)
GPU #0: GeForce RTX 3060 Ti (4864 cores, 1800 MHz)[2147483.64]
NVENC / CUDA NVENC API 11.0, CUDA 11.2, schedule mode: auto
Input Buffers CUDA, 16 frames
Input Info AviSynth+ 3.7.0 r3382(yv12(10bit))->p010 [AVX2], 3840x2160, 24000/1001 fps
Vpp Filters copyHtoD
Output Info H.265/HEVC main10 @ Level 5.1
3840x2160p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control CQP I:17 P:17 B:17
Lookahead off
GOP length 240 frames
B frames 3 frames [ref mode: disabled]
Ref frames 3 frames, MultiRef L0:auto L1:auto
AQ off
CU max / min auto / auto
VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,chromaloc:topleft
MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
WP(0.312700 0.329000) L(1000.000000 0.005000)
Others mv:auto aud repeat-headers
encoded 195319 frames, 23.69 fps, 15520.18 kbps, 15072.11 MB
encode time 2:17:26, CPU: 15.9, GPU: 41.4, VE: 56.4
frame type IDR 814
frame type I 814, total size 149.88 MB
frame type P 48830, total size 5025.43 MB
frame type B 145675, total size 9896.80 MB

Start: 4:55:22 AM
End: 7:12:51 AM
Duration: 02:17:29

The (yv12(10bit)) is what was confusing me as I was under the impression that yv12 was 8 bit only.
Yet it appears to be a 10 bit input to 10 bit out, is this correct?

AS I know little of the source filters I have been unsure on which one to select so it has been left on automatic.

MeteorRain
6th February 2021, 09:15
yv12(10bit)

Here YV12 is used as a synonym as YUV420, so YV12-10 is the same as YUV420P10, which is P010.

lazyjss
6th February 2021, 19:48
Thank you for the help

benwaggoner
7th February 2021, 23:35
yv12(10bit)

Here YV12 is used as a synonym as YUV420, so YV12-10 is the same as YUV420P10, which is P010.
And "YV12-10" is downright perverse nomenclature! It should not be used.