[vlc-devel] [PATCH 1/5] [RFC] core: allow use different pool sources for different types

[Steve Lhomme]

On Wed, Mar 29, 2017 at 8:10 PM, Rémi Denis-Courmont <remi at remlab.net> wrote:
> Le keskiviikkona 29. maaliskuuta 2017, 17.45.24 EEST Steve Lhomme a écrit :
>> I see vdp_output_surface_create() and vdp_video_surface_create() which
>> produce different types of surfaces. Given the display module doesn't
>> know of VdpVideoSurface, I assume it creates the whole pool size
>> requested by the core (let's say 30 4K pictures) and then each module
>> creates its own surface (!) to deal with processing and copies to the
>> vout pool at some point.
>
> Of course not.

My bad, I assumed VDPAU could do direct rendering. But it seems
vd->info.is_slow is false so there's no direct rendering. In that case
the display pool has just 3 pictures and the rest is allocated as CPU
surface. Since it's an opaque type the core allocates no memory. The
various VDPAU must fill the picture_sys_t as they go along.

So this has nothing to do with the direct rendering with filters I'm
trying to solve here.

>> >> No, in the case on zero, the filter pool is not used. It's still
>> >> distinct.
>> >
>> > The number of filters is not constant. At the time when the picture is
>> > allocated by the decoder, you don´t know if/how it will be filtered.
>>
>> In the case of filtering direct rendering is disabled.
>
> No, there is no such implication in the VLC video output works.

http://git.videolan.org/?p=vlc.git;a=blob;f=src/video_output/vout_wrapper.c;h=310f50cdc6e08b1f96bdb5f70f7ea44c41656abd;hb=HEAD#l125
http://git.videolan.org/?p=vlc.git;a=blob;f=src/video_output/vout_wrapper.c;h=310f50cdc6e08b1f96bdb5f70f7ea44c41656abd;hb=HEAD#l203

> --
> 雷米‧德尼-库尔蒙
> https://www.remlab.net/
>
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel