![]() |
[HELP] NVEnc Settings - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [HELP] NVEnc Settings (/thread-3435.html) |
NVEnc Settings - tomek398 - 13.10.2023 I've been using NVEnc to convert my video files to H.265 format for archiving purposes. I try to understand various NVEnc setting available in Hybrid. Here are my questions:
I have found following info: Quote:Weighted prediction is not supported if the encode session is configured with B frames. https://docs.nvidia.com/video-technologies/video-codec-sdk/12.1/nvenc-video-encoder-api-prog-guide/index.html I don't understand what means that "session is configured with B frames" if the context of Hybrid settings (my setting are attached) I've noticed that I can select /P-frame Settings/Weighted P-frames even is some setting for B-frames are also active. Does it mean that, when I use Weighted Prediction then B-frames are not enabled? I also don't understand second statement about Direct X 12
Any help here would be welcomed. RE: NVEnc Settings - Selur - 14.10.2023 The api can be accessed through different interfaces, since NVEncC does not use the DirectX interface can be ignored. Regarding the weighted prediction of P-frames: I checked when B-frames are enabled, NVEncC will output: weighted prediction with B frames unsupported. Cu Selur RE: NVEnc Settings - tomek398 - 14.10.2023 Thanks you for that explanation Could you please also explain me that are recommendations regarding: B-frame ref mode: each/middle Which option: each or middle is recommended? I couldn't find good explanation on internet. RE: NVEnc Settings - Selur - 14.10.2023 Quote:--bref-mode <string>source: https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--bref-mode-string (atm. Hybrid does not have 'auto' as an option) From the api, one can see what 'auto' would do: Quote:B-Frames As Referencesource: https://docs.nvidia.com/video-technologies/video-codec-sdk/12.1/nvenc-video-encoder-api-prog-guide/index.html#b-frames-as-reference So for H.264 and HEVC NVIDA by default would use 'middle' and for AV1 they would use 'each'. Personally, I use 'each' for both, but that's not really based on any tests, but on sheer lazyness. ![]() Cu Selur |