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

On Thu, Jun 07, 2018 at 11:23:40AM +0200, Paul B Mahol wrote: > On 6/6/18, Nicolas George wrote: > > Michael Niedermayer (2018-06-04): > >> 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

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

On 6/6/18, Nicolas George wrote: > Michael Niedermayer (2018-06-04): >> 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 >>

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

Michael Niedermayer (2018-06-04): > 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 In terms of design, the big

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

On Sun, Jun 03, 2018 at 07:43:24PM +0200, Paul B Mahol wrote: > On 6/2/18, Paul B Mahol wrote: > > On 5/2/18, Paul B Mahol wrote: > >> On 9/11/16, Paul B Mahol wrote: > >>> On 9/10/16, Nicolas George wrote: > Le quartidi 24 fructidor, an CCXXIV, Paul B Mahol a ecrit : > > So everybody

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

On 6/2/18, Paul B Mahol wrote: > On 5/2/18, Paul B Mahol wrote: >> On 9/11/16, Paul B Mahol wrote: >>> On 9/10/16, Nicolas George 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

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

On 5/2/18, Paul B Mahol wrote: > On 9/11/16, Paul B Mahol wrote: >> On 9/10/16, Nicolas George 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 >>>

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

On 9/11/16, Paul B Mahol wrote: > On 9/10/16, Nicolas George 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 >>

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

On 9/10/16, Nicolas George 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

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

Le quartidi 24 fructidor, an CCXXIV, Paul B Mahol a écrit : > 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

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

On 9/4/16, Michael Niedermayer wrote: > On Sun, Sep 04, 2016 at 10:16:57PM +0200, Nicolas George wrote: >> Le nonidi 19 fructidor, an CCXXIV, Paul B Mahol a ecrit : >> > And what would that cleaner implementation do? >> >> There is a rather simple implementation of format

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

On Sun, Sep 04, 2016 at 10:16:57PM +0200, Nicolas George wrote: > Le nonidi 19 fructidor, an CCXXIV, Paul B Mahol a écrit : > > And what would that cleaner implementation do? > > There is a rather simple implementation of format change in lavfi: have on > each input a boolean flag

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

On 9/4/16, Nicolas George wrote: > Which is why I would like to be authorized to ignore this kind of hiccups. > Format change does not currently work, this particular case used to work > only by chance. Can I break it and repair it later? I agree, format change in filtergraph,

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

Le nonidi 19 fructidor, an CCXXIV, Paul B Mahol a écrit : > And what would that cleaner implementation do? There is a rather simple implementation of format change in lavfi: have on each input a boolean flag "can_deal_with_format_change". If a frame with a different format arrives on a filter

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

On 9/4/16, Nicolas George wrote: > Le quintidi 15 fructidor, an CCXXIV, Michael Niedermayer a ecrit : >> ./ffmpeg -i tickets//679/oversized_pgs_subtitles.mkv -filter_complex >> '[0:s:1]scale=848x480,[0:v]overlay=shortest=1' test.avi >> fails assertion: >> Assertion progress

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

Le quintidi 15 fructidor, an CCXXIV, Michael Niedermayer a écrit : > ./ffmpeg -i tickets//679/oversized_pgs_subtitles.mkv -filter_complex > '[0:s:1]scale=848x480,[0:v]overlay=shortest=1' test.avi > fails assertion: > Assertion progress failed at libavfilter/avfilter.c:1391 > >

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

On Wed, Aug 31, 2016 at 02:20:27PM +0200, Paul B Mahol wrote: > On 8/31/16, Michael Niedermayer wrote: > > On Wed, Aug 31, 2016 at 10:18:31AM +0200, Paul B Mahol wrote: > >> On 8/30/16, Nicolas George wrote: > >> > Le quartidi 14 fructidor, an CCXXIV,

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

On 8/31/16, Nicolas George 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

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

Le quintidi 15 fructidor, an CCXXIV, Paul B Mahol a écrit : > 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,

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

Le quintidi 15 fructidor, an CCXXIV, Michael Niedermayer a écrit : > ./ffmpeg -i tickets//679/oversized_pgs_subtitles.mkv -filter_complex > '[0:s:1]scale=848x480,[0:v]overlay=shortest=1' test.avi > fails assertion: > Assertion progress failed at libavfilter/avfilter.c:1391 > >

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

On 8/31/16, Michael Niedermayer wrote: > On Wed, Aug 31, 2016 at 10:18:31AM +0200, Paul B Mahol wrote: >> On 8/30/16, Nicolas George wrote: >> > Le quartidi 14 fructidor, an CCXXIV, Paul B Mahol a ecrit : >> >> the filter frame multithreading would just

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

On Wed, Aug 31, 2016 at 10:18:31AM +0200, Paul B Mahol wrote: > On 8/30/16, Nicolas George wrote: > > Le quartidi 14 fructidor, an CCXXIV, Paul B Mahol a ecrit : > >> the filter frame multithreading would just internally, in filter context > >> cache frames, once enough frames

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

On 8/30/16, Nicolas George wrote: > Le quartidi 14 fructidor, an CCXXIV, Paul B Mahol a ecrit : >> the filter frame multithreading would just internally, in filter context >> cache frames, once enough frames are in cache - call workers and be done, >> repeat. At eof call workers

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

On Tue, Aug 30, 2016 at 09:08:18PM +0200, Nicolas George wrote: > Le quartidi 14 fructidor, an CCXXIV, Paul B Mahol a écrit : > > the filter frame multithreading would just internally, in filter context > > cache frames, once enough frames are in cache - call workers and be done, > > repeat. At

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

Le quartidi 14 fructidor, an CCXXIV, Paul B Mahol a écrit : > the filter frame multithreading would just internally, in filter context > cache frames, once enough frames are in cache - call workers and be done, > repeat. At eof call workers on remaining frames in cache. I have no idea how much

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

On Tuesday, August 30, 2016, Nicolas George wrote: > Le duodi 12 fructidor, an CCXXIV, Paul B Mahol a écrit : > > Nicolas, what is status of this? > > > > I'm currently interested in frame multithreading in lavfi. > > I am currently locked on a patch series to replace the

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

Le duodi 12 fructidor, an CCXXIV, Paul B Mahol a écrit : > Nicolas, what is status of this? > > I'm currently interested in frame multithreading in lavfi. I am currently locked on a patch series to replace the recursive calls to filter_frames() with a FIFO on each link. I think this is an

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

Hi, On Thu, Oct 30, 2014 at 1:59 PM, Michael Niedermayer wrote: > On Thu, Oct 30, 2014 at 11:50:46AM +0100, Stefano Sabatini wrote: > > Sorry for the slow reply. > > > > On date Wednesday 2014-10-22 23:45:42 +0200, Nicolas George encoded: > > > [ CCing Anton, as most that is

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

Sorry for the slow reply. On date Wednesday 2014-10-22 23:45:42 +0200, Nicolas George encoded: [ CCing Anton, as most that is written here also apply to libav too, and this would be a good occasion to try a cross-fork cooperation; if that is not wanted, please let us know so we can drop the

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

On Thu, Oct 30, 2014 at 11:50:46AM +0100, Stefano Sabatini wrote: Sorry for the slow reply. On date Wednesday 2014-10-22 23:45:42 +0200, Nicolas George encoded: [ CCing Anton, as most that is written here also apply to libav too, and this would be a good occasion to try a cross-fork

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

Le duodi 2 brumaire, an CCXXIII, Clement Boesch a écrit : I'd be curious to hear about how VapourSynth friends handle that problem, because AFAIK it's only one way. It's likely they don't have to deal with the same problems we have though (the usage is more limited, no audio typically);

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

Le duodi 2 brumaire, an CCXXIII, Clement Boesch a écrit : More still standing problems while we are at it: 1.7. Metadata Metadata are not available at graph level, or at least filter level, only at frame level. We also need to define how they can be injected and fetched

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

On Fri, 24 Oct 2014 13:07:22 +0200 Nicolas George geo...@nsup.org wrote: Le duodi 2 brumaire, an CCXXIII, Clement Boesch a écrit : I'd be curious to hear about how VapourSynth friends handle that problem, because AFAIK it's only one way. It's likely they don't have to deal with the same

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

On Fri, Oct 24, 2014 at 04:22:23PM +0200, Nicolas George wrote: Le duodi 2 brumaire, an CCXXIII, Clement Boesch a écrit : [...] As for the actual implementation, I suppose that a filter that supports seeking would be required to advertise so on its output: I can seek back to pts=42, and a

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

On Wed, Oct 22, 2014 at 11:45:42PM +0200, Nicolas George wrote: [ CCing Anton, as most that is written here also apply to libav too, and this would be a good occasion to try a cross-fork cooperation; if that is not wanted, please let us know so we can drop the cc. ] 1. Problems with the

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

On Wed, 22 Oct 2014 23:45:42 +0200 Nicolas George geo...@nsup.org wrote: [ CCing Anton, as most that is written here also apply to libav too, and this would be a good occasion to try a cross-fork cooperation; if that is not wanted, please let us know so we can drop the cc. ] 1. Problems