Comment 7 for bug 988522

Revision history for this message
Florian Echtler (floe) wrote :

Same for me. When running "totem --gst-debug-level=2", I get lots of output along the lines of

  0:00:38.039119153 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.747033333 compared to last timestamp: 0:00:12.839413376
  0:00:38.078117061 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.787033333 compared to last timestamp: 0:00:12.839413376
  0:00:38.111948530 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.827033333 compared to last timestamp: 0:00:12.839413376
  0:00:38.147027498 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.867033333 compared to last timestamp: 0:00:12.839413376
  0:00:38.193047320 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.907033333 compared to last timestamp: 0:00:12.839413376
  0:00:38.241357790 4090 0xb490ab80 WARN mpegtsdemux gstmpegtsdemux.c:1289:gst_mpegts_demux_data_cb:<mpegtsdemux1> looks like we have a corrupt packet because its timestamp is buggered timestamp: 24:02:06.947033333 compared to last timestamp: 0:00:12.839413376