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

Paul B Mahol onemda at gmail.com
Wed Aug 31 23:57:18 EEST 2016

On 8/31/16, Nicolas George <george at nsup.org> wrote:
> Le quintidi 15 fructidor, an CCXXIV, Paul B Mahol a ecrit :
>> Yes, it is very simple. You just need to allocate own buffers that
>> would be needed
>> by filter. Than you just call ctx->internal->execute()...
> I am sorry, but with the current API, to have something that really works
> with threads, not just pseudo-threading that is so full of blocking that it
> is mostly sequential, it is much more complicated than that. I think.
> Please prove me wrong.

How would one use already available workers from lavfi/pthread.c ?
If somebody wrote better implementation than me and its faster I will drop mine.

>> Does this fixes buffer queue overflow for specific scenarios?
> Not by itself, but then rewriting framesync to use the link's fifo becomes
> very easy and fix all the cases that can possibly work.
> Regards,
> --
>   Nicolas George

More information about the ffmpeg-devel mailing list