- 22 Nov, 2016 2 commits
-
-
Miroslav Slugeň authored
User selectable surfaces are not working correctly, if you set number of surfaces on cmdline, it will always use minimum 32 or 48 depends on selected resolution, but in nvenc it is not necessary to use so many surfaces. So from now you can define as low as 1 surface and nvenc will still work, it will ofcourse lower GPU memory usage by 95% and async_delay to zero That was the easy part, now littlebit more... Next part of this patch is to always prefer rc_lookahead to be more important for number of surfaces, than user defined surfaces value. Maximum rc_lookahead from nvidia documentation is 32, but could increase in future generations so there is no limit for this yet. Value async_depth is still accepted and prefered over rc_lookahead. There were also bug when you request more than rc_lookahead > 31, it will always set maximum 31, because surface numbers recalculation was after setting lookahead, which is now fixed. Results: If you set -rc_lookahead 32 and -bf 3 it will now use only 40 surfaces and lower GPU memory usage by 20%, also it will now increase PSNR by 0.012dB Two more comments: 1. from my internal test, i don't understand addition of 4 more surfaces when lookahead is calculated, i didn't used this and everything works as with those 4 more extra surfaces, does anybody know what is going on there? I looks like it was used for B frames which are calculated separately, because B frames maximum is 4. 2. rc_lookahead is defined default to -1, but in test condition if (ctx->rc_lookahead) which sets lookahead it will be always true, i don't know if this is intended behavior, so in default behavior is lookahead always on! This is default condition when rc_lokkahead is -1 (not defined on cmdline), whis is maybe something that is not intended: ctx->encode_config.rcParams.enableLookahead = 1; ctx->encode_config.rcParams.lookaheadDepth = 0; ctx->encode_config.rcParams.disableIadapt = 0; ctx->encode_config.rcParams.disableBadapt = 0; Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Timo Rothenpieler authored
-
- 05 Nov, 2016 1 commit
-
-
Matt Oliver authored
Signed-off-by: Matt Oliver <protogonoi@gmail.com>
-
- 19 Oct, 2016 1 commit
-
-
Sven C. Dack authored
Adds a check to see if the hardware supports temporal aq. Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
- 12 Oct, 2016 1 commit
-
-
Timo Rothenpieler authored
-
- 28 Sep, 2016 3 commits
-
-
Yogender Gupta authored
Merged from libav commit by Yogender Gupta: https://git.libav.org/?p=libav.git;a=commitdiff;h=70de2ea4261f860457a04e3d0c58c5543f403325
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
Based on libav commits by Luca Barbato and Yogender Gupta: https://git.libav.org/?p=libav.git;a=commit;h=352741b5ead1543d775ccf6040f33023e4491186 https://git.libav.org/?p=libav.git;a=commit;h=e02e2515b24bfc37ede6ca1744696230be55e50b
-
- 24 Sep, 2016 1 commit
-
-
James Almer authored
Should fix compilation with mingw32 Reviewed-by: Timo Rothenpieler <timo@rothenpieler.org> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 08 Sep, 2016 1 commit
-
-
Timo Rothenpieler authored
-
- 07 Sep, 2016 3 commits
-
-
Sven C. Dack authored
nvenc still encodes as yuv, but does the conversion internally which brings some performance gains. Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
- 28 Aug, 2016 7 commits
-
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Oliver Collyer authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Oliver Collyer authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
- 06 Jun, 2016 1 commit
-
-
Timo Rothenpieler authored
-
- 04 Jun, 2016 1 commit
-
-
Timo Rothenpieler authored
It's not expected to be set on video packets and causes issues in ffmpeg.c.
-
- 31 May, 2016 17 commits
-
-
Timo Rothenpieler authored
Directly adapted from libav
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
-
Timo Rothenpieler authored
The CONSTQP enum value is 0, so this check failed for it.
-
Andrey Turkin authored
Otherwise timestamps/pending FIFOs would go out of sync if nvEncodePicture ever fails. Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Use explicit nvenc capability checks instead to determine usable devices instead of SM versions. Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
Andrey Turkin authored
Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
-
- 25 May, 2016 1 commit
-
-
Timo Rothenpieler authored
-