[FFmpeg-devel] [PATCH] Add a priv_data pointer to?AVFormatParameters

Andy Parkins andyparkins
Wed Oct 3 17:18:32 CEST 2007


On Wednesday 2007 October 03, Reimar D?ffinger wrote:

> Well, I'd says the technical reason is "what's the point"? This is only
> useful for demuxers not included in SVN, so the ffmpeg project does not
> win anything except a pointer that avoid misuse (e.g. some horrible
> out-of-band commmunication).
> For those who use it, what do they win? The save having to maintain that
> one-line patch while still having to maintain the additional demuxer
> code, which I'd call "nothing".

Fair enough.  I'm happy to let it drop.

I'd rather use ffmpeg unpatched, but I'd equally like to be able to signal 
back to other objects in a a GUI the connection state, the way I'm doing that 
at present is by wrapping the existing format and adding my own little bits 
of signal code on the path through.  The priv_data pointer in my patch is to 
let my wrapper format have some way of getting back to the creating object.  
It's the only way I can see to do this:

 GUIObject
  ->av_open_input_file(CustomFormat)
    ->CustomFormat::read_header()
       ->GUIObject->setFlag()

This doesn't seem like a crazy thing to want to do with a library like ffmpeg.

Anyway, as I say, I'm happy to let it drop.



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins at gmail.com




More information about the ffmpeg-devel mailing list