[FFmpeg-devel] FFMPEG RTSP parameters support
Stas Oskin
stas.oskin
Sun Nov 14 17:15:02 CET 2010
Hi.
It's very normal, e.g. for session IDs or so.
>
Indeed.
>
> There is no solution. You can't give parameters a=1 in the URL if the
> server doesn't support that. The ?tcp is a hack and should become a
> commandline option (using AVClass/AVOptions) instead of an appendage
> to the URI, but nobody has done that so far.
>
Perhaps we can expand the rtsp.c for that, as another option to AVContext?
> >
> > - rtsp://1.2.3.4/stream.sdp?a=1/trackID=1
> > - rtsp://1.2.3.4/stream.sdp/trackID=1?a=1
> > - rtsp://1.2.3.4/stream.sdp/trackID=1
> >
> > The first one is what we do now (as far as I know), I guess one of the
> > other ones is what this server requires. Can you find any standard
> > document saying that this way of handling it (whichever the server wants)
> > really is the one mandated by some standard, too? Otherwise we might
> > encounter some other server wanting the parameters formatted in some
> other
> > way at some point.
>
> The second one is what we use right now if we want custom options, and
> the third is what it should be if that was the original URI in e.g.
> the playlist.
>
>
About 2nd one, is this supported from command line?
I get "460 Only Aggregate Option Allowed" when trying the following form:
ffmpeg -i "rtsp://192.168.0.150/loadtest.sdp/trackID=1?a=1"
or
ffmpeg -i "rtsp://192.168.0.150/loadtest.sdp/trackID=1?a=1&tcp"
Regards.
More information about the ffmpeg-devel
mailing list