[gstreamer-bugs] [Bug 519878] New: [basesink] Superfluous critical warning on segment format mismatches.

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=519878

  GStreamer | gstreamer (core) | Ver: 0.10.17
           Summary: [basesink] Superfluous critical warning on segment
                    format mismatches.
           Product: GStreamer
           Version: 0.10.17
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: manauw at skynet.be
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


[hm, bit long story for a short item ...]

Consider (a.o.) a fragment as follows
... ! muxer ! filesink
muxer will presumably send buffers that may or may not have valid timestamps
(buffers with media content versus some container format buffers).
At EOS time, it will likely send a BYTE based NEW_SEGMENT to have filesink
perform seeking, which may be the first NEW_SEGMENT to arrive there (e.g.
avimux).  This triggers a set_new_segment_full, which then g_return_if_fail
because the basesink's segment is then already set to TIME format (strangely
enough).

The latter behaviour has been introduced in response to bug 494245, by forcing
the running/stream time calculations to occur in TIME format.
Both gst_segment_to_stream_time/running_time have the side-effect to change the
segment's format to the given (TIME) one, if it is presently UNDEFINED and the
input timestamp is valid.

So, the segment gets into TIME format (with no real added value) along the way,
and complains later on about the received BYTE segment.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=519878.