GNOME Bugzilla – Bug 725047
tsdemux offsetting timestamp
Last modified: 2014-12-01 14:25:13 UTC
I am using gstreamer-1.2.2 version. I have a MPTS file, if I run the below given pipeline timestamp is getting offseted to 3 hours. Does any path in tsdemux is broken in 1.2.2 version?? gst-launch filesrc location=timestamp_issue.ts ! tsdemux program-number=1310 ! video/mpeg ! checksumsink you reproduce the issue using this file: http://goo.gl/DKYnS7 Thanks in advance.
Also happens in master
FWIW, there *is* a 3 hour discontinuity in that file. pcr 0x02db 1151437431105 (11:50:45.830781666) offset:12130324 pcr 0x02db 1444639404849 (14:51:45.163142555) offset:12442968 We do detect the PCR GAP correctly ... but that PCR arrives after the already-shifted PTS. Not sure how to handle that efficiently. Detect if PTS is "in line" with the previous ones ? If not return GST_CLOCK_TIME_NONE ? Don't push it and wait for next PCR to recalculate proper ts ?
How was this file created ? Where does it come from ? It's full of a *lot* of weirdness.
Hello Edward, thank you very much for your help. This file was captured from a TV channel. The file I have uploaded is a very small piece of bigger TS (65GB) file. When I analyse this stream, I found that timestamp is abruptly jumping to huge values. I can upload 200 Mb File snippet which could be helpful for your analysis. Thanks for your time. Good day.
Can you upload a bigger snippet somewhere ? It might help understand why i'm seeing such erratic PTS/PCR values.
Created attachment 270471 [details] PCR/PTS/DTS on pid 0x02DB This is a zoom on PID 0x02DB just after the PCR jump. the PCR jump in itself is not that much of a problem. What's a lot more concerning is the weird PTS behaviour (the staircase effect). The PTS/DTS should be at a (more or less) constant offset from the PCR. In this case ... it's not.
Edward, I lost the bigger file chunk I had. Now I am capturing the live content again. Once it is done, I will upload the file and let you know the link for downloading. Thank you so much for your time. Good day.
Hello Edward, My apologies for delay in replying. Here I am attaching 200 MB file chunk using which you can reproduce this issue. File link: http://goo.gl/DRFMNw I hope it will help you to analyse tsdemux behavior. Many thanks for looking into this issue. Good day.
Is this still a problem with recent versions (1.4.x or git master)?
Both those samples work fine in git master and 1.4, in pull and push mode. Closing bug