[gstreamer-bugs] [Bug 615466] New: mpegts clock starting at large nonzero offset

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=615466
  GStreamer | gst-plugins-good | git

           Summary: mpegts clock starting at large nonzero offset
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: xiphmont at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


As of head, the hdv input using the hdv1394src, mpegtsdemux and mpeg2dec works,
though the clock as reported is starting from some large offset (the absolute
clock in the mpegts stream?)  It appears to be reporting from the time when the
firewire link started, not when the script started, and this offset means it
can't work with any other source as the other sources are starting from zero
and the pipeline timings can't reconcile.  This means, eg, we can't use an HDV
cam with an ALSA audio input. 

fishcore:~/icecast> ./gst-icecast
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: MpegTSClock
progressreport0 (00:00:05): 219 seconds
progressreport0 (00:00:10): 224 seconds
progressreport0 (00:00:15): 229 seconds
progressreport0 (00:00:20): 234 seconds

script producing this:

gst-launch \
       hdv1394src \
             ! mpegtsdemux \
             ! mpeg2dec \
             ! progressreport \
             ! filesink location=/dev/null

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.