On Sun, 8 Apr 2012, Samuel Pitoiset wrote:
Hmm, this doesn't feel too nice, but I do see that we need to do the
same parsing to find the playpath. Or should the full path be used as
playpath if an app parameter is given? (How does rtmpdump/librtmp do
it?)
librtmp has an option for the application name (ie. -app) and an other
option for the stream name (ie. playpath). So, I have to make a new patch in
order to introduce the option '-playpath'.
Yes, but I meant, if I pass app as a separate parameter to librtmp but
don't pass any playpath option, does it take the full path as playpath, or
does it split the path into app/path as usual and just replace app with
the one passed on the command line?
That is, if I specify the app parameter, should I do
rtmp://server/playpath -rtmp_app the/actual/app/path
or do I have to do something like
rtmp://server/fakeapp/playpath -rtmp_app the/actual/app/path
Do you see what I mean?
That is, normally if I do something like this:
rtmp://server/app/path/playpath
This is split into app=app/path and playpath=playpath
But if I add the playpath parameter separately, should the full
app/path/playpath be parsed as app path?
Neither of them is an issue if one specifies both app and playpath as
separate parameters, but it's a slight bit of ambiguity if only one of
them is specified, and I'd like to look up how librtmp handles that case.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
