[rtmpdump] Escape encoding
nhjm449 at gmail.com
Sat Oct 20 07:35:46 CEST 2012
The \xx escaping only works for librtmp URL parameters (ex. 'rtmp://
However, rtmpdump *will* properly urldecode (ie. %xx) the playpath (but not
rtmpdump -r "rtmp://
--live -o foo.flv
On Fri, Oct 19, 2012 at 6:10 PM, Steven Penny <svnpenn at gmail.com> wrote:
> This site
> provides a challenge for me. The parsed playpath end with a Carriage
> Line Feed. This was discussed on the forums.
> A few solutions were offered up, including
> - remove CRLF and prepend "mp4:" to playpath
> - remove CRLF and append ".mp4" to playpath
> - pass a literal Carriage return using Bash and $'\r'
> KSV has noted that these solutions are nonstandard and might not be future
> proof. I noticed in the MAN this paragraph
> > Special characters in values may need to be escaped to prevent
> > misinterpretation by the option parser. The escape encoding uses a
> > followed by two hexadecimal digits representing the ASCII value of the
> > character. E.g., spaces must be escaped as \20 and backslashes must be
> > as \5c.
> This looks promising, but after trying to append "\0d\0a" or just "\0d", it
> appears "not to work".
> rtmpdump mailing list
> rtmpdump at mplayerhq.hu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rtmpdump