Opened 20 years ago
Last modified 18 years ago
#225 new enhancement
won't play if http_proxy:// and mms:// are both specified
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | unimportant | Component: | demuxer |
Version: | unspecified | Severity: | minor |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Reproduced by developer: | no | Analyzed by developer: | no |
Description
I tryed to play a URL (damn WM streams... anyway) and did the following (The URL
are real it you want to try):
mplayer http://www.air2004.com/asx/p05010023_q8p7_bb.asx
ended with
Unable to open URL: http://www.air2004.com/asx/p05010023_q8p7_bb.asx
mplayer http_proxy://proxy:8080/http://www.air2004.com/asx/p05010023_q8p7_bb.asx
did the same
Unable to open URL:
http_proxy://proxy.fr:8080/http://www.air2004.com/asx/p05010023_q8p7_bb.asx
So I got the .asx file with wget, in it there is the URL for the WMV file :
mms://mars.via.or.jp/solidex/animate/p05010023_q8p7_bb.wmv
I tryed then this :
mplayer
http_proxy://proxy:8080/mms://mars.via.or.jp/solidex/animate/p05010023_q8p7_bb.wmv
and I got
Unable to open URL:
http_proxy://proxy:8080/mms://mars.via.or.jp/solidex/animate/p05010023_q8p7_bb.wmv
Fortunately I tryed the following
mplayer
http_proxy://proxy:8080/http://mars.via.or.jp/solidex/animate/p05010023_q8p7_bb.wmv
and it worked
The proxy may be at fault here, however couldn't it be a good idea to have some
kind of fall-back that tryes to transform the mms:// string in the URL in a
http:// and tryes to play it ? (Okay may be stupid).
I did several tryes even on the microsoft web site, worked every time so perhaps
is worth a catch.
Change History (2)
comment:1 by , 20 years ago
Summary: | won't play if http_proxy:// and mms:// are both specified → won't play if http_proxy:// and mms:// are both specified |
---|
comment:2 by , 18 years ago
Priority: | normal → unimportant |
---|---|
Severity: | normal → enhancement |
mms can not be used over a http proxy, mmshttp must be used. Making mms
fallback to mmshttp automatically might be a good idea if it isn't done already
though, so marking as enhancement.
According to Wikipedia:
Microsoft’s streaming server uses the Microsoft Media Services (MMS) protocol to
transfer unicast data. MMS can be transported via UDP or TCP. If the client
Windows Media Player cannot negotiate a good connection using MMS over UDP, it
will resort to MMS over TCP. If that fails, the connection can be made using
HTTP over TCP, which is not as ideal for streaming as MMS over UDP, but ensures
connectivity nonetheless.
It seems that it worked finally for you because the server in question had the
appropriate HTTP fallback in place.
1) I'd refile a bug about MPlayer not understanding asx files.
2) If you try playing the mms stream directly without the proxy specification,
it should work fine (the UDP stream wouldn't work through your HTTP proxy anyway).
This worked for me: