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

[Martin Storsjö]

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)?

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?

// Martin