On Sun, 28 Sep 2014 10:40:18 +0200 Reimar Döffinger <reimar.doeffin...@gmx.de> wrote:
> On Sun, Sep 28, 2014 at 10:15:51AM +0200, wm4 wrote: > > On Sun, 21 Sep 2014 10:17:16 +0100 > > Reimar Döffinger <reimar.doeffin...@gmx.de> wrote: > > In general, this avio_read_seek() thing seems to be a somewhat > > misguided attempt to coerce high level streaming protocols into the low > > level byte-oriented "protocol" layer. Apparently it's only used by > > rtmp, which does scary thing like remuxing the received data to flv, > > just to bypass the protocol/demuxer separation. Newer protocol > > implementations like HLS don't do this anymore, and just put everything > > into the demuxer. > > And instead don't allow for any kind of proper caching. > Not exactly my definition of a better design. > Either way the read_seek is there, and until such time someone removes > it I am not inclined to consider it a good idea to keep it broken! PS: besides, you could implement a generic caching muxer, which automatically reads packets from a slave demuxer, and writes them as byte stream. So basically similar to what rtmp does, but generic and useable with any demuxer. This way you could e.g. use a byte cache for HLS. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
