Opened 11 years ago
Last modified 11 years ago
#2105 new defect
rtmp streams fail to play
Reported by: | Owned by: | reimar | |
---|---|---|---|
Priority: | normal | Component: | core |
Version: | unspecified | Severity: | normal |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Reproduced by developer: | no | Analyzed by developer: | no |
Description
The attached script is supposed to play iheart radio station.
It first gets url for it, then plays it.
Except it doesn't play now. It either hangs in "Sending play command" state, or immediately deletes the stream.
rtmp @ 0xcaa4f0]Creating stream...
[rtmp @ 0xcaa4f0]Sending play command for 'Hou_TX_KTRH-AM...'
[rtmp @ 0xcaa4f0]Deleting stream...
Failed to open rtmp://cp20100.live.edgefcs.net/live/Hou_TX_KTRH-...
I know for sure this script used to work few months ago. Probably until some update.
SVN-r35040-snapshot-4.2.1
FreeBSD 9.1 amd64
Attachments (2)
Change History (6)
by , 11 years ago
Attachment: | run-iheart-x added |
---|
by , 11 years ago
Trace of all network operations leading to stream deletion
comment:1 by , 11 years ago
comment:2 by , 11 years ago
RTMP is handled via FFmpeg. I'd suggest trying with ffplay, if that fails as well the problem is not actually in MPlayer code.
comment:3 by , 11 years ago
I forgot: the most likely cause is that you used/linked against librtmp before but now use FFmpeg's internal RTMP implementation, so you should check that.
comment:4 by , 11 years ago
I am switching between --disable-librtmp and --enable-librtmp configure options.
But I am not seeing any difference in behavior. All logs look the same. And it hangs the same way.
Is there any way mplayer could be ignoring --enable-librtmp/--disable-librtmp setting and still doing the same thing?
ffmpeg "rtmp://..." for this stream says: Invalid data found when processing input
Script reproducing the problem