View Single Post
Old 1st July 2020, 23:44   #29558  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Quote:
Originally Posted by cartman0208 View Post
I don't see a lot of memory growth, even on the 32bit version ... starts at 750MB and finishes with 850MB used by nvencc.exe

What I also noticed ... no matter what preset or rate factor ... the processing speed stays the same for a given resolution ... 4K is always around 75fps for me

Graphics driver was updated yesterday (451.48), but I'm not on Win10 May 2020 update yet, if that helps.


Code:
--------------------------------------------------------------------------------
U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.hevc
--------------------------------------------------------------------------------
NVEncC (x86) 5.08 (r1585) by rigaya, Jul  1 2020 14:48:28 (VC 1900/Win/avx2)
OS Version     Windows 10 x64 (18363)
CPU            Intel Core i7-6800K @ 3.40GHz [TB: 3.80GHz] (6C/12T)
GPU            #0: GeForce GTX 1660 Ti (1536 cores, 1770 MHz)[2147483.64]
NVENC / CUDA   NVENC API 9.1, CUDA 11.0, schedule mode: auto
Input Buffers  CUDA, 16 frames
Input Info     avcuvid: H.265/HEVC, 3840x2160, 24000/1001 fps
Vpp Filters    copyDtoD
Output Info    H.265/HEVC main10 @ Level 5.1
               3840x2160p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control   CQP  I:25  P:25  B:25
Lookahead      off
GOP length     240 frames
B frames       3 frames [ref mode: disabled]
Ref frames     3 frames, MultiRef L0:auto L1:auto
AQ             on
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(999.999975 0.000100)
MaxCLL/MaxFALL 1000/0
Others         mv:auto repeat-headers

encoded 175440 frames, 76.88 fps, 7280.96 kbps, 6351.12 MB
encode time 0:38:02, CPU: 9.8%, GPU: 7.4%, VE: 99.2%, VD: 20.6%
frame type IDR    731
frame type I      731,  total size    70.98 MB
frame type P    43860,  total size  2313.22 MB
frame type B   130849,  total size  3966.92 MB
Edit: 1080p runs at 175fps stable with above settings, no big memory increase either...
Part of that might be because you are using GOPs of 240 frames. That's 10 times larger than what it would need to be for a UHD-BD encode. The --repeat-headers would not be activated as often and would probably not hit the routine that causes the memory leak as often. Try adding --gop-len 24 and see what happens.

[Edit] Yeah. I just set the GOP length to 240 frames and it is barely growing at all... but, of course, that encode would fail to meet the UHD-BD standard. I would assume that it would also mean that as you attempt to fast forward, each picture step would jump 10 seconds instead of 1. The table used for these actions only logs IDR positions.

Quote:
Originally Posted by gonca View Post
Finished a remux and it seems to work FF, REW and CHP skips
I just went back and looked at your post again as well... and you are also using the default 240 frame GOP. That's probably why you're not seeing the issue as well. You are only having to insert the SPS/VPS/PPS once every 10 seconds instead of once per second. The headers are only inserted on the IDR frame that begins a GOP.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net

Last edited by jdobbs; 2nd July 2020 at 00:12.
jdobbs is offline   Reply With Quote