Hi,
I'm also quite curious about this. The Media SDK for servers seems to
ship with a closed implementation of vaapi. libva's main contributors
seems to be Intel employed. Is there any relationship between the two
(other than providing the same api, and presumably sharing some code)
Is it the s
Hi Alexey,
It's straight forward,
Setup multiple VAEncSliceParameterBufferH264, the fields are
/** \brief Starting MB address for this slice. */
unsigned intmacroblock_address;
/** \brief Number of macroblocks in this slice. */
unsigned intnum_macroblocks;
As you say, y
Hi,
On 05/29/2014 06:18 AM, Zhao, Yakui wrote:
> On Wed, 2014-05-28 at 04:34 -0600, Torbjorn tyridal wrote:
>> if I run two of the above in parallel, each goes along at 230fps, 18%
>> cpu (top). ie a total of 460 fps/36% cpu
>> If I then add a third instance the frame rate
I have the following case on a haswell 4770R (gigabyte brix)
A libva based encoder reads raw 1920x1088 nv12 frames from file on
ramfs. Encoding set to 10 slices, fixed qp (26). cpu governor set to
performance.
if I run two of the above in parallel, each goes along at 230fps, 18%
cpu (top). ie a
Hi,
>> I have a scheme where the decoder ack's received frames - With
>> this information I could resync without an IDR by carefully
>> selecting the reference frame(s).
> Will you please describe your idea in detail?
>> long term references would typically be employed as well, but it
>> seems r
Hi,
Is it possible to select which reference frames to consider when encoding a
frame with libva (Intel, haswell)?
I have a scheme where the decoder ack's received frames - With this
information I could resync without an IDR by carefully selecting the
reference frame(s).
long term references wo
