Opened 17 years ago
Last modified 14 years ago
#1077 new defect
mplayer throws a sig13 on Hannover96 TV
Reported by: | Owned by: | reimar | |
---|---|---|---|
Priority: | normal | Component: | streaming |
Version: | 1.0rc2 | Severity: | normal |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Reproduced by developer: | no | Analyzed by developer: | no |
Description
The stream is linked from http://tv.hannover96.de/de/f/index.php, which is the online TV of my home football club Hannover 96.
Mplayer is from the Fedora 8 livna repo.
$ mplayer mms://lpc-streaming-01.odmedia.net/p_dfl_paid/808/testvideo.wmv
MPlayer 1.0rc2-4.1.2 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz (Family: 6, Model: 15, Stepping: 6)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
Playing mms://lpc-streaming-01.odmedia.net/p_dfl_paid/808/testvideo.wmv.
STREAM_ASF, URL: mms://lpc-streaming-01.odmedia.net/p_dfl_paid/808/testvideo.wmv
Resolving lpc-streaming-01.odmedia.net for AF_INET6...
Couldn't resolve name for AF_INET6: lpc-streaming-01.odmedia.net
Resolving lpc-streaming-01.odmedia.net for AF_INET...
Connecting to server lpc-streaming-01.odmedia.net[87.238.137.97]: 1755...
Connected
MPlayer interrupted by signal 13 in module: open_stream
- MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug.
The video runs fine on Flip4mac/Quicktime on Mac OS X, but also does not work under libmms ( see http://bugzilla.livna.org/show_bug.cgi?id=1961 )
Use mmshttp:// instead of mms://.
The server is probably misconfigured and allows a connection to the mms port but then suddenly closes the connection. MPlayer does not handle that kind of behaviour, at least not yet.