I would like to know what is exaclty the range of QPI, QPP, QPB for RateControl CQP?
I assumed it was [0,51] but the h264 encoder init function returns Invalid parameter if I set QBI = QPP = QPB = 0.
QP value range is 0-51. And there should be no issues setting the value to 0.
I performed a quick check here on my side and it works fine.
If you are still encountering issues, please provide a Media SDK trace log, so that we can better understand you complete encoder configuration to determine potential issues.
I just noticed this bug only occurs on the h264 SW encoder, the QSV works well.
Do you test the SW encoder?
I did a quick test using SW path. it works fine using QPI = QPP = QPB = 0.
Are you SW library from Media SDK 2013?
It is Media SDK 2013.
I will try to give you some extra informations. How do we enable the Intel Media SDK log?
In the Media SDK tools folder you will find the "mediasdk_tracer" tracer tool. To capture a log just launch the tool and start capturing before running your workload. When done, click Stop and retrieve the log.
This is the 2 files I generated with your logging tool:
- the file analyzerSW.log is the log file generated when I set QP=0 with the h264 SW encoder. In this file you can see the error return by the Init function.
- the file analyzerQSV.log is the log file generated with same parameter but with the h264 QSV encoder
I hope this helps, let me know if you need something else.
unfortunately your log files did not get attached to your post.
Could you please try to upload the log files again?
Sorry I have some proxy problem to upload.
It should work this time.
thanks for the logs. From what I can see, it looks like the reason for the issue is that QPI = QPP = QPB = 0 is not allowed for target usage = 7 (speed).
If you set target usage to a value from 1-6, it works.
I will check with codec expert and get back to you on why this is the case.
Hi again Karine,
Many thanks for reporting the issue.
This specific configuration was confirmed to be a bug in the Media SDK SW DLL. Fix will be introduced in future release of the Media SDK.
Thanks, I will patch it on my current implementation.