Reason for deprecation of NV_ENC_PARAMS_RC_2_PASS_FRAMESIZE_CAP mode?

Gaming and Visualization Technologies Video Processing & Optical Flow
1

Can someone from nvidia please explain why NV_ENC_PARAMS_RC_2_PASS_FRAMESIZE_CAP was deprecated?

In older documentation, NV_ENC_PARAMS_RC_2_PASS_FRAMESIZE_CAP was suggested in scenarios where low latency and staying below a certain bitrate/framesize is desired. Now that FRAMESIZE_CAP is deprecated, what is the correct rc mode to use now, given the same frame size + latency constraints?

2

I do see that the release notes for 7.1 say “The names of the rate control modes have been
modified to reflect quality and performance.”, but I’m looking for a bit more specific information. Was functionality changed, or were the names simply changed to new names? Is there still an equivalent to NV_ENC_PARAMS_RC_2_PASS_FRAMESIZE_CAP, which keeps the framesizes more consistent? What is that equivalent? etc.

Thanks.

3

NV_ENC_PARAMS_RC_2_PASS_FRAMESIZE_CAP is equivalent to NV_ENC_PARAMS_RC_CBR_HQ.

The functionality is the same, with some additional quality enhancements and better bitrate conformance.