[FFmpeg-devel] [PATCH] Use the actual RTSP peer IP for RTP sessions

[Michael Niedermayer]

On Tue, Mar 09, 2010 at 05:49:25PM +0200, Martin Storsj? wrote:
> On Tue, 9 Mar 2010, Luca Abeni wrote:
> 
> > Michael Niedermayer wrote:
> > [...]
> > > > Also i should refer you to the list of minimal requirements for an
> > > > key-value list option system ive posted a while ago.
> > > > (dont remember subj of that thread)
> > > 
> > > and the most likely way this would/should be implemented is through
> > > adding an AVOption array to the private context and thus allowing the user
> > > app to set the parameters in there
> > 
> > Yes, this looks like a much better solution.
> > Martin, what do you think?
> 
> I'm not sure I totally follow you on how this should be implemented. 
> Should we add an AVOption array to AVFormatContext, for passing custom 
> muxer-specific options to the muxer (or SDP generator in this case)?

I assume you know how AVOptions are used to set things in AVFormatContext
the idea is to do the same with AVFormatContext->priv_data


> 
> This part (making the control name non-hardcoded) isn't any big priority 
> for me at the moment, but syncing the NTP start time is. Does the same 
> thing apply for that too, that I should pass it through AVOptions in some 
> way, instead of through metadata as initially tried?

the question is if NTP start time is metadata or a muxer parameter

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20100309/a4c44774/attachment.pgp>