[Bug 770375] New: TS play few seconds playback stuck(drop frame)

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=770375

            Bug ID: 770375
           Summary: TS  play  few seconds playback stuck(drop frame)
    Classification: Platform
           Product: GStreamer
           Version: 1.8.2
                OS: All
            Status: NEW
          Severity: critical
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: shakin at outlook.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 334120
  --> https://bugzilla.gnome.org/attachment.cgi?id=334120&action=edit
mpegtspacketizer_basesink_level_6_log

There is a TS file（https://pan.baidu.com/s/1gfgA9Kv）
With ffplay, VLC playback is OK,but once with GStreamer It only play few
seconds then playback will stuck.

I try to dig mpegtspacketizer.c：mpegts_packetizer_pts_to_ts（）’　code as follows:
--------
GstClockTime
mpegts_packetizer_pts_to_ts (MpegTSPacketizer2 * packetizer,
    GstClockTime pts, guint16 pcr_pid)
{
  GstClockTime res = GST_CLOCK_TIME_NONE;
  MpegTSPCR *pcrtable;
 .....


 if (refpcr != G_MAXINT64) {
/*************!!!!Modifid here!!!!*************************/
      res = pts;
//    res =
//        pts - PCRTIME_TO_GSTTIME (refpcr) + PCRTIME_TO_GSTTIME
(refpcroffset);
/***********************************************************/    
    }
    else
      GST_WARNING ("No groups, can't calculate timestamp");
  } else
    GST_WARNING ("Not enough information to calculate proper timestamp");

  PACKETIZER_GROUP_UNLOCK (packetizer);

  GST_DEBUG ("Returning timestamp %" GST_TIME_FORMAT " for pts %"
      GST_TIME_FORMAT " pcr_pid:0x%04x", GST_TIME_ARGS (res),
      GST_TIME_ARGS (pts), pcr_pid);
  return res;
}
--------
The above modification is just not to make a PCR <=> PTS conversion, while
using the original PTS,the result is more smoother playback than before.But,I
don't know what causes this phenomenon, so I file a new bug to track this
issue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.