Re: trying mp_image -> get/release_buffer migration...

On Tue, May 27, 2003 at 10:07:17PM +0200, Arpi wrote:
> main differences from g1/mpi style:
> - no more specialized schemes like IP and IPB, and more than 3 buffers
>   supported... (mpi is limited to 3)
> - no 'one frame decoding == one get_image call' restirction. it's possible
>   to allocate 3 buffers at init (or at first farme decoding) and then use
>   them all them and then release them at uninit. or a filter (likeinv.
>   telecine) may delay video by many frames, by allocating for example 5 of
>   them. and so on, there is no limit. it will solve some problems we
>   currently have. and it also make sit easier to implement filter
>   merging/branching (multiple vo drivers, mixing 2 videos etc) _later_.
>   also a buffer (image) may be returned multiple times by process_image().
> - buffer structs aren't cloned/copied while transfering from one filter to
>   another, like mpi. although i'm not sure it's required / is a good idea.
> 
> comments?

I'm a bit confused how all this works with DR into video memory, since
a given buffer can only be "used" once, and the filter/codec drawing
into it MUST release it along with displaying it in order to prevent
shearing. Is this already covered, or do you have a plan in mind?

Rich