[Libva] Directly encoding a surface after decoding
ykzhao
yakui.zhao at intel.com
Sun Jan 27 18:35:57 PST 2013
On Fri, 2013-01-25 at 01:59 -0700, Timo Rothenpieler wrote:
> Indeed, the library which contains the initialisation code was reloaded
> between the calls which caused the initialization-routine to be run
> twice, but not my checks if it's the same Display.
> Sorry for the mess, it seems to work fine now.
> Now just a bit of polishing and a lot of testing, and maybe there'll be
> a vaapi transcoding version of vlc soon.
Thanks for so quick response. It is good news that it can work fine
after reworking the initialization routine.
And we are looking forward to the new version VLC with the support of
vaapi transcoding.
Best regards
Yakui
>
> > Hi,
> > From the tracelog it seems that both the decoding and encoding call
> > the function of vaInitialize, which will initialize the different
> > display context for decoding and encoding. In such case the surface ID
> > can't be shared correctly between decoding/encoding.
> > Will you please also call the vaInitialize only once for
> > decoding/encoding and then see whether it is helpful?
> >
> > Best regards.
> > Yakui
>
> _______________________________________________
> Libva mailing list
> Libva at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libva
More information about the Libva
mailing list