[FFmpeg-devel] [PATCH 1/3] libavformat: add "capture:" protocol

wm4 nfxjfg at googlemail.com
Mon Apr 3 13:42:20 EEST 2017


On Mon, 3 Apr 2017 18:20:35 +0800
Steven Liu <lingjiujianke at gmail.com> wrote:

> 2017-04-03 18:12 GMT+08:00 wm4 <nfxjfg at googlemail.com>:
> 
> > On Mon, 3 Apr 2017 11:25:39 +0200
> > Michael Niedermayer <michael at niedermayer.cc> wrote:
> >  
> > > On Mon, Apr 03, 2017 at 07:10:42PM +1000, Timothy Lee wrote:  
> > > > On 04/03/2017 06:35 PM, Nicolas George wrote:  
> > > > >Hi. Thanks for the patch.
> > > > >
> > > > >Le quartidi 14 germinal, an CCXXV, Timothy Lee a écrit :  
> > > > >>Capture is an input stream capture protocol that dumps the input  
> > stream to a  
> > > > >>file.  The default name of the output file is "capture.dat", but it  
> > can be  
> > > > >>changed using the "capture_file" option.
> > > > >>
> > > > >>capture.c borrows heavily from cache.c.  
> > > > >Can you explain more precisely how and why? Borrowing code often means
> > > > >features could be merged or should be more clearly separated,  
> > depending  
> > > > >on cases.  
> > > >
> > > > Hi Nicolas,
> > > >
> > > > Thanks for your quick reply.  Regarding the almost direct copy of
> > > > code from cache.c, I previously submitted a patch on 31 March that
> > > > adds a "cache_file" option to the cache protocol.  It was intended
> > > > to allow a specifically named cache file to serve as a dump of the
> > > > input stream.
> > > >
> > > > Michael Niedermayer explained that his intention was to maintain a
> > > > caching system that was more consistent with how a browser's cache
> > > > works, and my changes to the cache protocol was not appropriate.  
> > >
> > > both can be done in cache.
> > > the primary way of caching in cache.c should be automatic though
> > > and not require the user to manually set it up per url  
> >
> > I don't think disk cache management should be in the scope of FFmpeg.
> >  
> Perhaps i misunderstand something, dose he want add CDN(Content Delivery
> Network) Cache function into FFmpeg?

No, this is about caching on the client side. Timothy Lee wants a
simple option that would write the cache contents to disk, while
Michael Niedermayer wants it to work like in a browser, with automatic
deletion of old files etc. (if I understood him right). I think that's
a bit too much for libavformat.


More information about the ffmpeg-devel mailing list