[FFmpeg-devel] [PATCH] MMS wrapper
Dennis Fratiani Jr.
dfratiani at hotmail.com
Sat Jul 14 18:46:38 CEST 2012
> Date: Sat, 14 Jul 2012 07:34:23 +0200
> From: stefan.gehrer at gmx.de
> To: ffmpeg-devel at ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] MMS wrapper
> On 07/14/2012 01:30 AM, Don Moir wrote:
> > ----- Original Message ----- From: "Stefan Gehrer" <stefan.gehrer at gmx.de>
> > To: "FFMpeg development discussions and patches"
> > <ffmpeg-devel at mplayerhq.hu>
> > Sent: Friday, July 13, 2012 4:41 PM
> > Subject: [FFmpeg-devel] [PATCH] MMS wrapper
> >> attached patch implements a simple wrapper for handling mms:// URLs.
> >> It first tries to open using mmst protocol and on failure tries
> >> using mmsh protocol.
> >> I found some streams on tunein.com which either support only
> >> mmst or only mssh, with this patch applied both kinds can be
> >> played back with just specifying mms:// as protocol.
> >> This should fix ticket #998, the mms URL given there also works.
> >> mms://live1.wm.skynews.servecast.net/skynews_wmlz_live300k
> >> Stefan
> > Thanks
> > Would mmsh be more common then mmst and maybe should be tried first even
> > if mmst is more efficient ?
> Yes, mmsh seems to be more common. But mmst usually fails after a
> minimal communication with server (connection on port 1755 refused)
> while mmsh is likely to exchange some data on port 80 before
> realising that the request can not be fulfilled. That is why I
> did it in this order.
I submitted a ticket a long time ago, originally to the ffmpeg roundup, discussing the proper way to handle WMS streams.
You can see my ticket archive at the libav roundup here: http://roundup.libav.org/issue2484
You can also read the official M$ spec here: http://msdn.microsoft.com/en-gb/library/dd757582.aspx
I can not actually contribute to the code but I do have a lot of experience setting up and managing these types of servers.
More information about the ffmpeg-devel