Wowza Community

Playback erors

Hello,

at the moment I have problems playing back my stream.

Attached I send you the log of vlc:

ts warning: discontinuity received 0x2 instead of 0xf (pid=256)
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0xc (pid=256)
httplive error: EXT-X-MEDIA-SEQUENCE gap in playlist (new=5738, old=5737)
ts warning: discontinuity received 0x2 instead of 0x0 (pid=256)
ts warning: discontinuity received 0x2 instead of 0x6 (pid=257)
main warning: playback too early (-92688): down-sampling
ts warning: discontinuity received 0x2 instead of 0xc (pid=256)
ts warning: discontinuity received 0x2 instead of 0x8 (pid=257)
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0xd (pid=257)
ts warning: discontinuity received 0x2 instead of 0x9 (pid=256)
ts warning: discontinuity received 0x2 instead of 0xb (pid=257)
main warning: playback too early (-111083): down-sampling
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0x9 (pid=256)
ts warning: discontinuity received 0x2 instead of 0x9 (pid=257)
httplive error: EXT-X-MEDIA-SEQUENCE gap in playlist (new=5743, old=5742)
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0xa (pid=257)
main error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 1000 ms)
main error: ES_OUT_RESET_PCR called
ts warning: discontinuity received 0x2 instead of 0x7 (pid=256)
main warning: picture is too late to be displayed (missing 46 ms)
ts warning: discontinuity received 0x2 instead of 0xd (pid=257)
main warning: playback too early (-77521): down-sampling
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0xb (pid=256)
ts warning: discontinuity received 0x2 instead of 0xc (pid=257)
main warning: picture is too late to be displayed (missing 42 ms)
httplive error: EXT-X-MEDIA-SEQUENCE gap in playlist (new=5746, old=5745)
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0xa (pid=256)
ts warning: discontinuity received 0x2 instead of 0x4 (pid=257)
main warning: picture is too late to be displayed (missing 25 ms)
main warning: picture is too late to be displayed (missing 29 ms)
ts warning: discontinuity received 0x2 instead of 0x5 (pid=256)
httplive warning: playback in danger of stalling
ts warning: discontinuity received 0x2 instead of 0x8 (pid=256)
ts warning: discontinuity received 0x2 instead of 0x7 (pid=257)
main warning: playback too early (-60521): down-sampling
httplive error: EXT-X-MEDIA-SEQUENCE gap in playlist (new=5749, old=5748)

I have following config:

Engine Version

4.1.0 (build 12602)

Engine Manager Version

4.1.0 (build 12602)

OS

Linux (amd64)

Java Information

Java Version

1.6.0_32

Java VM Version

23.25-b01

Java Architecture

64

Java Name

OpenJDK 64-Bit Server VM

Java Vendor

Sun Microsystems Inc.

Java Home

/usr/lib/jvm/java-6-openjdk-amd64/jre

Java Max Heap Size

9933MB

Server Data:

32GB Ram

Intel i7-3770

Hi,

The VLC messages do indicate issues with the stream.

Please post some of the entries seen in the error log, if any, during the playback period, ([install-dir]/logs/wowzastreamingengine_error.log).

That may provide more clues.

Daren

Hi,

Please see the cause for the message below.

Waiting for RTCP packet. See docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).

Cause: Sender Report (SR) packets, which are sent over the Real-time Control Protocol (RTCP) channel, didn’t arrive within the timeout period specifed by the RTP/MaxRTCPWaitTime property in [install-dir]/conf/[application-name]/Application.xml. SR packets provide timing information between the audio and video in the incoming RTP stream. If Wowza Media Server doesn’t detect SR packets for the incoming RTP stream, it writes this message to the log file and try to use RTP timecode values in the RTP packets to synchronize the audio and video channels.

You can extend the amount of time that the server waits to receive SR packets by changing the RTP/MaxRTCPWaitTime property in [install-dir]/conf/[application-name]/Application.xml or you can change the default method by which Wowza Media Server synchronizes the audio and video by changing the RTP/AVSyncMethod property in [install-dir]/conf/[application-name]/Application.xml from the default value (senderreport) to either rtptimecode or systemclock. If set to rtptimecode, Wowza synchronizes the audio and video channels based on RTP timecodes in the RTP packets (as previously mentioned). If set to systemclock, Wowza Media Server synchronizes the audio and video channels based on the system time that the first audio and video packets arrive at the server, assuming that they arrive at the same time.

Please see the article below for reference.

How to troubleshoot error messages

Regards,

Jason

Sorry there are noi errors in the log that are significant

WARN    server  comment 2014-10-28      11:37:05        -       -       -       -       -       11.293  -       -       -       -       -       -       -       -       HTTPStreamerAdapterCupertinoStreamer.onPlaylist: Stream not found [live/diasporatv_720p/chunklist_w561815374.m3u8]: diasporatv_720p
WARN    server  comment 2014-10-28      11:37:05        -       -       -       -       -       11.343  -       -       -       -       -       -       -       -       HTTPStreamerAdapterCupertinoStreamer.onPlaylist: Stream not found [live/diasporatv_720p/chunklist_w561815374.m3u8]: diasporatv_720p
WARN    server  comment 2014-10-28      11:37:05        -       -       -       -       -       11.396  -       -       -       -       -       -       -       -       HTTPStreamerAdapterCupertinoStreamer.onPlaylist: Stream not found [live/diasporatv_720p/chunklist_w561815374.m3u8]: diasporatv_720p
WARN    server  comment 2014-10-28      11:37:06        -       -       -       -       -       14.512  -       -       -       -       -       -       -       -       RTCPHandler.isTimeSyncReady: Hit MaxRTCPWaitTime synchronizing on system clock.
WARN    server  comment 2014-10-28      11:37:06        -       -       -       -       -       14.514  -       -       -       -       -       -       -       -       RTCPHandler.isTimeSyncReady: Hit MaxRTCPWaitTime synchronizing on system clock.

#Version: 1.0
#Start-Date: 2014-10-28 12:14:10 CET
#Software: Wowza Streaming Engine 4.1.0 build12602
#Date: 2014-10-28
#Fields: x-severity     x-category      x-event date    time    c-client-id     c-ip    c-port  cs-bytes        sc-bytes        x-duration      x-sname x-stream-id     x-spos  sc-stream-bytes cs-stream-bytes x-file-size     x-file-length        x-ctx   x-comment
WARN    server  comment 2014-10-28      12:14:11        -       -       -       -       -       1.553   -       -       -       -       -       -       -       -       REST Documentation Server has been disabled.
WARN    server  comment 2014-10-28      12:14:20        -       -       -       -       -       10.409  -       -       -       -       -       -       -       -       Waiting for RTCP packet. See docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).
WARN    server  comment 2014-10-28      12:14:20        -       -       -       -       -       10.415  -       -       -       -       -       -       -       -       Waiting for RTCP packet. See docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).
WARN    server  comment 2014-10-28      12:14:20        -       -       -       -       -       10.526  -       -       -       -       -       -       -       -       Waiting for RTCP packet. See docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).
WARN    server  comment 2014-10-28      12:14:20        -       -       -       -       -       10.56   -       -       -       -       -       -       -       -       Waiting for RTCP packet. See docs for (Application.xml: RTP/AVSyncMethod and RTP/MaxRTCPWaitTime).
WARN    server  comment 2014-10-28      12:14:24        -       -       -       -       -       14.406  -       -       -       -       -       -       -       -       RTCPHandler.isTimeSyncReady: Hit MaxRTCPWaitTime synchronizing on system clock.
WARN    server  comment 2014-10-28      12:14:24        -       -       -       -       -       14.42   -       -       -       -       -       -       -       -       RTCPHandler.isTimeSyncReady: Hit MaxRTCPWaitTime synchronizing on system clock.