-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Got incorrect bitstream in encoding VP9 8K #1847
Comments
After disable scalability as below, this issue is not reproduced. diff --git a/media_driver/agnostic/common/codec/hal/codechal_hw.h b/media_driver/agnostic/common/codec/hal/codechal_hw.h This issue is caused by enabling scalability for 8K VP9 encoding. |
@Shao-Feng May I know which platform you are working on? |
On RPL, Gen12 |
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]>
This issue only can be reproduced with kernel 6.1.80. |
thanks shao feng for experiment! |
Enabled and run encoding with 2 VDBox |
Auto Created VSMGWL-75955 for further analysis. |
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]>
Pls check the release note, RPL starts fron kernel 6.2. ADL-N/RPL-S/RPL-P: starting from kernel 6.2 |
Thanks for checking it. Probably this issue is caused by the GuC of SRIOV VF. Close this one. I will check on local |
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Signed-off-by: Lina Sun <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Tracked-On: OAM-128364 Signed-off-by: Lina Sun <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Tracked-On: OAM-128364 Signed-off-by: Lina Sun <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Tracked-On: OAM-128364 Signed-off-by: Lina Sun <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Tracked-On: OAM-128364 Signed-off-by: Lina Sun <[email protected]>
In VP9 8K encoding case, scalability is enabled. and make encoding incorrect. Issue is reported to upstream on intel/media-driver#1847 Tracked-On: OAM-123073 Signed-off-by: Shaofeng Tang <[email protected]> (cherry picked from commit a059ab2) Tracked-On: OAM-128364 Signed-off-by: Lina Sun <[email protected]>
Which component impacted?
Encode
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
On Android,
with media-driver intel-media-24.1.5, and intel-gmmlib-22.3.18
Running oneVPL example "hello-encode" with the change projectceladon/libvpl#16
for encoding VP9 7680x4320 video. The bitstream is incorrect.
The input is generated with ffmpeg cmd below
ffmpeg -v verbose -f lavfi -i testsrc=size=7680x4320:rate=1 -pix_fmt yuv420p -vframes 5 -y test.yuv
On Ubuntu with the media-driver and gmmlib, this issue can not be reproduced.
The Codec dump on Android and Ubuntu is below
T1829561088_ubuntu_8k.zip
T1389417720_android_8K.zip
What's the usage scenario when you are seeing the problem?
Video Conference
What impacted?
Fail to encode VP9 video in 8K.
No problem to encode VP9 video in 4K
and no problem to encode H264 and H265 video
Debug Information
No response
Do you want to contribute a patch to fix the issue?
None
The text was updated successfully, but these errors were encountered: