intel / intel/media-driver

VPP can not enable more feature dynamically

Open
#927 7 comments 0 reactions 1 assignee Claimed by @MicroYY View on GitHub
Bug P3 VP
Dominant language
C
Stars
1.2k
Forks
383
Avg merge
8d 18h
Merged PRs (30d)
4

Description

Create a VPP using
vaCreateConfig(display, VAProfileNone, VAEntrypointVideoProc, NULL, 0, &config);
and create the context using
vaCreateContext (display, config, 0, 0, 0, NULL, 0, &context);

then, let the context do simple CSC job using vaBeginPicture/vaRenderPicture/vaEndPicture call. it can successfully generate output frames.
then, using the same context, enable some filter, such as `brightness`, while do the CSC job, the VPP fails and report:

[MHW]: CRITICAL - SetVeboxSurfaces:363: Unsupported format.
[MOS]: CRITICAL - SubmitCommandBuffer:1183: Command buffer submission failed!
[VP]: CRITICAL - VeboxSendVeboxCmd:2169: MOS returned error, eStatus = 0x22
[VP]: CRITICAL - VeboxRenderMode0:3390: MOS returned error, eStatus = 0x22
[VP]: CRITICAL - Render:3598: MOS returned error, eStatus = 0x22
[VP]: CRITICAL - VpHal_RndrRenderVebox:4387: MOS returned error, eStatus = 0x22
[VP]: CRITICAL - RenderSingleStream:850: MOS returned error, eStatus = 0x22

We found that, create a vpp context and do simple jobs for first several frames(may not enable VEbox) and then enable some complicated feature(may enable VEbox) later for the same context, this bug generates.
But if we enable the complicated feature at the first time(the first frame), it's OK.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.