setQpRange error

Hi,
I ran multimedia API samples/01_video_encode/video_encode to encode H.265 stream.
When I tune QP rang I get the following error.

./video_encode ./I420 1920 1080 H265 ./tmp.h265 -MinQpI 10 -MaxQpI 50
NVMEDIA: NvMMAttributeVideoEnc_QPRange Get Parameter
VENC: NvMMLiteVideoEncSetAttribute: 4523:  NvMMAttributeVideoEnc_QPRange :Bad Parameter

tegra_multimedia_api Release version infomation is as follows

# R32 (release), REVISION: 1.0, GCID: 14531094, BOARD: t186ref, EABI: aarch64, DATE: Wed Mar 13 07:41:08 UTC 2019

Hi,
We can observe the error. Will check and update. Many thanks for reporting it.

Hi,
For information,do you have plan to upgrade to r32.2.3 or r32.3.1?

Hi DaneLLL,

Same problem for me in custom app (based on video_encode sample) with L4T R32.1.0.

NVMEDIA: NvMMAttributeVideoEnc_QPRange Get Parameter
VENC: NvMMLiteVideoEncSetAttribute: 4523:  NvMMLiteAttributeVideoEnc_QPRange: Bad Parameter
NVMEDIA: H265 : Profile : 1

Don’t remember if this problem occurs with L4T R28.3.

Do you plan to provide a patch for R32.1.0?

Thanks

Hi,
Please try attachment on r32.1.
r32_1_TEST_libtegrav4l2.zip (71.6 KB)

Hi @DaneLLL, I face this issue too. I’m running Jetpack 4.3, multimedia api 32.3.1. After replacing your .so, the setQpRange doesn’t trigger error log, but my program crashed once I Q my frame into output plane. Could you please help me?

Hi,
Please try attachment.

r32_3_1_TEST_libtegrav4l2.zip (77.1 KB)

Hi @DaneLLL, thanks for your update, it works fine!

Would there be a new official update that contain this fix? And before that update, can I use this test .so in production?

Hi,
It is fixed in next r32 release. The patch is simple, so it should be safe and stable in production.

1 Like