[FFmpeg-devel] Evolution of lavfi's design and API

[Michael Niedermayer]

On Sun, Jun 03, 2018 at 07:43:24PM +0200, Paul B Mahol wrote:
> On 6/2/18, Paul B Mahol <onemda at gmail.com> wrote:
> > On 5/2/18, Paul B Mahol <onemda at gmail.com> wrote:
> >> On 9/11/16, Paul B Mahol <onemda at gmail.com> wrote:
> >>> On 9/10/16, Nicolas George <george at nsup.org> wrote:
> >>>> Le quartidi 24 fructidor, an CCXXIV, Paul B Mahol a ecrit :
> >>>>> So everybody agrees, we should proceed.
> >>>>
> >>>> I am proceeding, but as you can see in the patch, there is still a fair
> >>>> amount of work to be done. Still, people can help if they want to speed
> >>>> things up, especially since a significant part of the work is design
> >>>> decisions that I can not do alone and will need to be discussed.
> >>>>
> >>>> What needs to be done (using this mail as a notepad, but including the
> >>>> tasks
> >>>> where help is required):
> >>>>
> >>>> - Finish documenting the scheduling and make sure the implementation
> >>>> matches
> >>>>   the documentation.
> >>>>
> >>>> - Discuss if "private_fields.h" is acceptable or decide another
> >>>> solution.
> >>>>
> >>>> - Clearly identify and isolate the parts of the scheduling that are
> >>>> needed
> >>>>   only for request_frame()/request_frame() compatibility.
> >>>>
> >>>> - Decide exactly what parts of the scheduling are the responsibility of
> >>>>   filters (possibly in the compatibility activate function) and what
> >>>> parts
> >>>>   are handled by the framework.
> >>>>
> >>>> - Think ahead about threading and use wrapper to access fields that
> >>>> will
> >>>>   require locking or synchronization.
> >>>>
> >>>> - Think about features whose need I realized while trying to get it
> >>>> working:
> >>>>   distinguish productive / processing activation, synchronize several
> >>>> filter
> >>>>   graphs.
> >>>>
> >>>> Please feel free to ask details about any of these points: not only
> >>>> would
> >>>> getting interest help me stay motivated, but discussing implementation
> >>>> details and explaining the design would help me having a clear idea of
> >>>> the
> >>>> whole system.
> >>>
> >>> For start removal of recursiveness is mostly I'm interested in.
> >>> What needs to be done for that, can I help somehow?
> >>>
> >>
> >> Hi,
> >>
> >> So what's remain to be done to have frame threading in lavfi?
> >>
> >
> > Ping
> >
> 
> Ping

If noone, who has time to reply knows the awnser then you probably have to
find it out from the code and any unfinished patchsets

sending nicolas a private mail may also be more vissible to him than the ML
in case he is busy

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

He who knows, does not speak. He who speaks, does not know.

Lao Tzu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20180604/1dedc0e3/attachment.sig>