After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611105 - MMS vs RTSP problem
MMS vs RTSP problem
Status: RESOLVED DUPLICATE of bug 578475
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.25
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-25 17:24 UTC by Tomasz Sałaciński
Modified: 2013-02-06 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tomasz Sałaciński 2010-02-25 17:24:29 UTC 
There seems to be a bug on how Totem parses MMS:// protocol handlers. I am using UPC Live TV from Poland (live television broadcasted using MMS protocol, available only to PL UPC ISP users). Totem takes ~15 minutes to connect to the stream. When looking at the page source, I see mms:// link to the stream. I've tried to connect with totem to this stream and I see some connection refused messages. However, if I replace the mms:// header with rtsp://, the stream opens successfully and works great. It seems that GStreaner tries to connect to this stream using mms protocol and waits a long time before it tries to use RTSP.  Windows Media Player takes ~15 seconds to start playing the stream. Maybe if MMS is unavailable GStreamer should try RTSP first and then wait for timeout for mms?
Comment 1 Mark Nauwelaerts 2010-09-15 08:36:08 UTC 
Likely one of the many problems with mms(src), moving to -bad.

Maybe totem (or whatever higher level) should try rtsp first, and then only mms, for some mms:// URL, which may very well be WMP approach nowadays.
Comment 2 ares703 2011-08-28 17:40:12 UTC 
I have the opposite problem, if I try to play mms://24.248.196.168:1038 it won't play when I go back and check it has changed it to rtsp://24.248.196.168:1038
Comment 3 Wim Taymans 2013-02-06 12:31:59 UTC 

*** This bug has been marked as a duplicate of bug 578475 ***