Skip to content
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

add surface hint for recon/reference/raw #344

Closed
wants to merge 1 commit into from

Conversation

XinfengZhang
Copy link
Contributor

Signed-off-by: Carl Zhang [email protected]

@XinfengZhang XinfengZhang requested a review from dvrogozh October 15, 2019 07:17
@XinfengZhang
Copy link
Contributor Author

@fulinjie @dvrogozh please help to review

va/va.h Outdated Show resolved Hide resolved
va/va.h Outdated Show resolved Hide resolved
va/va.h Outdated Show resolved Hide resolved
@XinfengZhang XinfengZhang force-pushed the hint branch 2 times, most recently from 73bfa02 to 3de8b05 Compare October 16, 2019 05:35
va/va.h Outdated Show resolved Hide resolved
this surface hint is used to require usage hint
for some codec , to optimize the memory footprint
reconstruct surface is use another format
for example, if input surface is AYUV for encode, it 444 format,
backend driver maybe just use YUV to be reference, A is ignored
to safe memory. in this scenario, application should not confuse
the raw input surface and reconstruct/reference surface.

Signed-off-by: Carl Zhang <[email protected]>
@HeJunyan
Copy link
Contributor

Information is enough.
I want to have a try before it merge, it that ready in iHD driver now?

@fulinjie
Copy link
Contributor

fulinjie commented Mar 8, 2020

Here is some comments from the community:
http://ffmpeg.org/pipermail/ffmpeg-devel/2020-March/258119.html

The basic question is why not handling it transparently (and not to introduce extra attribute).
Hi @XinfengZhang, would you please help to elaborate whether its' possible?

@XinfengZhang
Copy link
Contributor Author

to make it transparent, it will bring a lot of effort, 1. need to record the real format information inside driver. 2. do not create real surface until it is was used, it is difficult to implement it, we we call vaCreateSurfaces, we even don't know the context, config...

@XinfengZhang
Copy link
Contributor Author

close it for intel/media-driver#915

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants