Opened 14 years ago

Closed 12 years ago

#314 closed defect (invalid)

RTSP stream hangs

Reported by: diego@… Owned by: r_togni@…
Priority: normal Component: streaming
Version: HEAD Severity: normal
Keywords: Cc: compn
Blocked By: Blocking:
Reproduced by developer: Analyzed by developer:

Description

The stream mentioned in the URL hangs indefinitely, playback does not start,
adding -playback to the command line makes no difference. Here is -v output:

STREAM_RTSP, URL:
rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_80k.rm
Filename for url is now
rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_80k.rm
Filename for url is now
rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_80k.rm
Resolving rx-lvl3-tex09.rbn.com for AF_INET...
Connecting to server rx-lvl3-tex09.rbn.com[209.247.111.148]:554 ...
librtsp: server responds: 'RTSP/1.0 400 Bad Request'
librtsp: server responds: 'RTSP/1.0 400 Bad Request'
Cache size set to 640 KBytes
STREAM: [realrtsp]
rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_80k.rm
STREAM: Description: RealNetworks? rtsp streaming
STREAM: Author: Roberto Togni, xine team
STREAM: Comment: ported from xine
CACHE_PRE_INIT: 0 [0] 0 pre:131072 eof:0
Cache fill: 0.00% (0 bytes)

Change History (3)

comment:1 Changed 14 years ago by diego@…

When trying to play the stream with RealPlayer? 10.0.4.750 I get the message

The player does not have the capabilities to play back this content.
The following components are required:
application/x-pn-imagemap

comment:2 Changed 14 years ago by diego@…

  • Cc patriotact@… added

comment:3 Changed 12 years ago by compn

  • bug_file_loc changed from rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_ 80k.rm to rtsp://rx-lvl3-tex09.rbn.com/farm/*/usanet/usanet/g2demand/scifi/tripping/full_80k.rm
  • Resolution set to invalid
  • Status changed from new to closed

marking invalid, the sample url is gone forever...
also the tcp timeout patch may have fixed this particular bug.

Note: See TracTickets for help on using tickets.