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 vaSyncBuffer #408
Add vaSyncBuffer #408
Conversation
a9e21c1
to
3dab5de
Compare
3dab5de
to
28cd4cc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@dvrogozh , @xhaihao , @XinfengZhang , @dmitry-gurulev , @wyc55069407, Please give your input: do we need VA_TIMEOUT_INFINITE here? |
same comments as in #407 |
de5443f
to
e3fb35a
Compare
hi @dmitryermilov , LGTM, but it is new , which maybe will lead to different call sequence with before, could you help to add sample into libva-utils? |
Hi @XinfengZhang , yes, I can do it. Unfortunately libva-utils has only simple encode tools. I can replace vaSyncSurface with vaSyncBuffer e.g. in avcenc. But I have to say that, IMO, it won't be very descriptive for readers since the most benefits will be in 1->N cases. avcenc doesn't support it. I can do it after 1-2 weeks due to other commitments. libva and libva-utils are different repo's, I'd propose to merge current PR now (it's blocking other tasks). Is it okay for you? |
e3fb35a
to
5a0c289
Compare
Added notes about different ways for synchronization. Signed-off-by: Dmitry Ermilov <dmitry.ermilov@intel.com>
Signed-off-by: Dmitry Ermilov dmitry.ermilov@intel.com