[FFmpeg-devel] rtmp support and librtmp

[aviad rozenhek]

On Sun, Sep 26, 2010 at 23:59, Michael Niedermayer <michaelni at gmx.at> wrote:

>  On Mon, Sep 27, 2010 at 12:16:52AM +0200, aviad rozenhek wrote:
> > On Sun, Jun 6, 2010 at 10:36, Howard Chu <hyc at highlandsun.com> wrote:
> >
> > > aviad rozenhek wrote:
> > >
> > >> On Thu, Jun 3, 2010 at 15:06, trueice<trueice at gmail.com>  wrote:
> > >>
> > >>  On Wed, Jun 2, 2010 at 9:42 PM, aviad rozenhek<aviadr1 at gmail.com>
> > >>>  wrote:
> > >>>
> > >>>>
> > >>>>> it says the stream is not found
> > >>>>>
> > >>>>
> > >>>>  try:
> > >>> ./ffplay "rtmp://myserver/live/mystream live=1"
> > >>>
> > >>>
> > >>>  it works!
> > >> however embedded spaces are indeed annoying.
> > >>
> > >
> > > Feel free to write a better solution. Take as much time as you like.
> > >
> > >
> > How about this general purpose method of passing parameters to protocols?
> >
> > instead of:
> > udp://localhost?pkt_size=1316&localport=1234
> > [where ?pkt_size=1316&localport=1234 are actually parameters to udp
> > protocol] use
> > udp?pkt_size=1316&localport=1234://localhost
> >
> > and in the same manner, instead of
> > "rtmp://localhost/live/mystream live=1 buffer=100"
> > [where live=1 buffer=100 are actually parameters to rtmp protocol instead
> of
> > part of url] use
> > rtmp?live=1&buffer=100://localhost/live/mystream
> >
> > this achieves a couple of things
> > 1) it is clear which parameters are part of the real url, and which are
> > ffmpeg-specific flags
> > 2) it reuses familiar syntax with the ? & notation
> > 3) since & and ? are not legal in protocol names, this shouldnt break
> > anything
>
> i like the idea
>
I'll try to get a patch ready next week