Issue with aacparse element- Timestamp jumbled

[Baby Octopus]

Hi,

I have a transport stream which has packet losses. 

When I run the following pipeline, I see no issue
gst-launch-1.0  filesrc ! tsdemux ! audio/mpeg ! checksumsink

Timestamps monotonically increase(though there are packet losses)

PTS: 0:00:10.736391296  DTS: 99:99:99.999999999
PTS: 0:00:10.928391296  DTS: 99:99:99.999999999
PTS: 0:00:11.099057963  DTS: 99:99:99.999999999
PTS: 0:00:11.269724629  DTS: 99:99:99.999999999
PTS: 0:00:11.440391296  DTS: 99:99:99.999999999
PTS: 0:00:11.632391296  DTS: 99:99:99.999999999
PTS: 0:00:11.803057963  DTS: 99:99:99.999999999
PTS: 0:00:11.973724629  DTS: 99:99:99.999999999
PTS: 0:00:12.165724629  DTS: 99:99:99.999999999


2. But when I add aacparse after tsdemux, timestamps get jumbled at certain
places as follows(BOLD ones)

PTS: 0:00:10.897044356  DTS: 0:00:10.736391296
PTS: 0:00:10.918377689  DTS: 0:00:10.736391296
PTS: 0:00:10.939711022  DTS: 0:00:10.736391296
PTS: 0:00:10.961044355  DTS: 0:00:10.736391296
PTS: 0:00:10.982377688  DTS: 0:00:10.736391296
PTS: 0:00:11.003711021  DTS: 0:00:10.736391296
PTS: 0:00:11.025044354  DTS: 0:00:10.736391296
*PTS: 0:00:10.928391296  DTS: 0:00:10.928391296
PTS: 0:00:10.949724629  DTS: 0:00:10.928391296
PTS: 0:00:10.971057962  DTS: 0:00:10.928391296
PTS: 0:00:10.992391295  DTS: 0:00:10.928391296
PTS: 0:00:11.013724628  DTS: 0:00:10.928391296*
PTS: 0:00:11.035057961  DTS: 0:00:10.928391296
PTS: 0:00:11.056391294  DTS: 0:00:10.928391296
PTS: 0:00:11.077724627  DTS: 0:00:10.928391296

As you see, the timestamp is reducing and this is causing playback issue.
I'm not sure of this is is a bug. Is it? Should I file it in Bugzilla?

~BO




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Issue-with-aacparse-element-Timestamp-jumbled-tp4667373.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.