On Sun, Sep 21, 2014 at 09:47:54PM +0200, wm4 wrote:
> 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?

i dont know details about the application/lib using this, this patch
was just the result of some investigation into why this other patch
was needed:
"[FFmpeg-devel] [PATCH 1/2] mux: make sure that the AV_PKT_DATA_H263_MB_INFO 
side data is received by the H.263/RTP packetizer (rfc2190)"


> Shouldn't nut be able to handle all
> these potentially ffmpeg-specific things?

maybe

the idea though was that a 5 line patch would avoid some application
redesign work. And it may very well be usefull in various other
scenarios.

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I am the wisest man alive, for I know one thing, and that is that I know
nothing. -- Socrates

Attachment: signature.asc
Description: Digital signature

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to