After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607122 - [mpegtsdemux] desynched sound, weird timecode showing up in totem, incorrect framerates and resolution
[mpegtsdemux] desynched sound, weird timecode showing up in totem, incorrect ...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-16 02:28 UTC by Jean-François Fortin Tam
Modified: 2012-09-26 20:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2010-01-16 02:28:08 UTC
Sample file: http://jeff.ecchi.ca/public/00068.MTS

In totem 2.28.2:
- The sound is not synched with the video
- A timecode is displayed on top of the video (it shouldn't; VLC doesn't show it, and editors such as Vegas don't show it either)

Looking at the codec info in totem (or by right-clicking the file properties in nautilus), we also see that gstreamer thinks it is a 1440x1080 video at 59,940 fps, while in reality (I think) it is a 1920x1080 video at 29.970 fps.

In pitivi:
- trying to import the file results in a traceback.
Comment 1 Jean-François Fortin Tam 2010-01-16 02:30:46 UTC
The duration is also incorrect: totem thinks it is 13 seconds, but it's 24 seconds or so.
Comment 2 kxra 2010-01-16 02:36:41 UTC
Confirming this. Another problem is not being able to seek through the video

Basically, the demuxer needs to be rewritten otherwise everyone with HD camcorders will remain a pack of sad pandas.
Comment 3 Edward Hervey 2011-05-31 11:56:35 UTC
tsdemux plays those files fine now, I still need to merge the seeking support though.

As for the size, 1440x1080 is indeed the proper *pixel* resolution.

The framerate bogusness might be because of interlaced content.
Comment 4 Edward Hervey 2012-05-24 08:25:46 UTC
This is normally fixed upstream. Jeff, Danny, can you confirm ?
Comment 5 Tobias Mueller 2012-09-26 20:39:42 UTC
So we're thinking this is fixed, right? Please reopen if it's not.