On Sun, 21 Sep 2014 21:37:14 +0200 Michael Niedermayer <michae...@gmx.at> wrote:
> On Sun, Sep 21, 2014 at 09:23:18PM +0200, Nicolas George wrote: > > Le jour de la Récompense, an CCXXII, Michael Niedermayer a écrit : > > > This allows applications which interface through AVIOContext or > > > URLProtocol > > > to access side data. > > > > > > Based-on patch by: Thomas Volkert <si...@gmx.net> > > > Signed-off-by: Michael Niedermayer <michae...@gmx.at> > > > > Can you point to the discussion about this patch and/or explain the actual > > use case? > > user applications and libs which interface to FFmpeg or libavformat > through a URLProtocol or AVIOContext receive the AVPacket.data but > not AVPacket.side_data but the side data is often essential > > With this patch, such applications can set the flag and would > receive the complete data stream. The alternative would be for such > libs to be redesigned to interface to FFmpeg or libavformat > differently > > > [...] > So it's some kind of in-application serialization? I still don't follow. Why? Over what format? Shouldn't nut be able to handle all these potentially ffmpeg-specific things? _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
