Hi,

On Mon, Feb 27, 2012 at 1:12 PM, Felipe Contreras
<[email protected]> wrote:
> On Mon, Feb 27, 2012 at 10:46 PM, Felipe Contreras
> <[email protected]> wrote:
>> Compared to vaapi and vdpau, this code is much simpler; frames in, frames 
>> out,
>> and not many parameters are required. It's also worth remembering that this
>> interface is asynchronous; buffers are processed in a delayed way, and 
>> polling
>> is required in order to see if the DSP has finished processing them.
>
> So, I'm going to list the issues I have encounter to make this
> performs as well as it can:
>
> 1) Agree on an I420 packed format
>
> GStreamer, the DSP codecs, and I guess others ignore strides and
> planes, so it would be extremely useful to check if the client (e.g.
> GStreamer gst-av) requires this format, to avoid line by line, or even
> plane by plane copying.
>
> 2) Client buffers
>
> It would be nice if the client could tell libav to use certain buffer
> (e.g. framebuffer), so that the DSP can write the output directly
> there, and avoid memcopies altogether. I recall somebody mentioning a
> facility for that already existing, but I don't remember which it is.

AVCodecContext->get_buffer()?

Ronald
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to