[Ffmpeg-devel] Embedded preview vhook/voutfb.so /dev/fb

Ivo ivop
Sun Apr 1 12:23:55 CEST 2007


On Sunday 01 April 2007 11:56, Michael Niedermayer wrote:
> On Sun, Apr 01, 2007 at 11:31:06AM +0900, Bobby Bingham wrote:
> > I also want to ask about the motivation for treating full frames and
> > slices differently in libmpcodecs.  Obviously slices have the benefit
> > of being small and fitting in cache - but is there any reason for
> > having separate APIs for both of them (put_image() vs draw_slice())? 
> > At first glance, it seems to me that if a filter requires full frames,
> > it could still be passed in the form of a single, frame-sized slice. 
> > That would have the benefit that filters that support both frames and
> > slices could implement just draw_slice() instead of implementing the
> > same operations again in put_image().
> well i dont know, maybe theres no reason or need for draw_slice +
> put_image

I think a filter could flag whether it needs full frames or supports slices. 
In the former case, the filter layer (or an inserted filter in between) 
could collect all incoming slices, assemble them together and feed them as 
a single slice of frame width*frame height to the next filter.


More information about the ffmpeg-devel mailing list