--------------------------------------------------------------------------------
J:\tmp\source_1_2024-03-21@11_53_56_9710_01.av1
--------------------------------------------------------------------------------
NVEncC (x64) 7.46 (r2779) by rigaya, Mar 13 2024 12:17:47 (VC 1929/Win)
OS Version Windows 11 x64 (22631) [UTF-8]
CPU AMD Ryzen 9 7950X 16-Core Processor [5.77GHz] (16C/32T)
GPU #0: NVIDIA GeForce RTX 4080 (9728 cores, 2505 MHz)[PCIe4x16][551.86]
NVENC / CUDA NVENC API 12.1, CUDA 12.4, schedule mode: sync
Input Buffers CUDA, 20 frames
Input Info y4m(yv12(10bit))->p010 [AVX2], 640x352, 24000/1001 fps
Vpp Filters copyHtoD
Output Info AV1 main 10bit @ Level auto
640x352p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control VBR
Multipass none
Bitrate 0 kbps (Max: 0 kbps)
Target Quality 23.00
QP Offset cb:0 cr:0
VBV buf size auto
Split Enc Mode auto
Lookahead off
GOP length 240 frames
B frames 3 frames [ref mode: middle]
Ref frames 7 frames, MultiRef L0:auto L1:auto
AQ on (spatial, temporal, strength 5)
Part size max auto / min auto
Tile num columns auto / rows auto
TemporalLayers max 1
Refs forward auto, backward auto
VUI matrix:bt709,range:limited
Others mv:Q-pel
encoded 429 frames, 1722.89 fps, 610.02 kbps, 1.30 MB
encode time 0:00:00, CPULoad: 2.4%
frame type IDR 2
frame type I 2, total size 0.02 MB
frame type P 107, total size 0.00 MB
frame type B 320, total size 1.28 MB
After some testing, the problem seems to be the resolution!
Taking the file that worked fine as input and resizing it to 1000x542, I get the same problem:
calling:
I see:
NVEnC then stops without an error and a 0-byte file is created.
using another file:
the output is created without a problem:
After some testing, the problem seems to be the resolution! Taking the file that worked fine as input and resizing it to 1000x542, I get the same problem:
only a 0-byte is created
Using different encoders av1/h264/h265 I get the same issue.
Taking the file which caused the problem and using avhw:
encoding works fine.
=> It seems like there is some problem with the y4m parsing depending on the resolution.
Cu Selur
Ps.: attached the source.mp4: https://github.com/rigaya/NVEnc/assets/843640/05646b43-1c09-4ec7-9bab-8cc6eff73862