[Bug 688188] videomixer: _sink_clip: GStreamer-CRITICAL **: _gst_util_uint64_scale_int: assertion `denom > 0' failed

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=688188
  GStreamer | gst-plugins-good | 1.x

--- Comment #17 from Sebastian Dröge <slomo at circular-chaos.org> 2013-05-06 14:17:55 UTC ---
<stormer> slomo: I was wondering if it was plausible to get a segment without
caps during the type finding ? like a byte segment
<slomo> stormer: yes, like for filesrc you never get caps
<slomo> stormer: but typefind should first forward caps, then segment
<slomo> stormer: and filesrc should never push caps after a segment
<stormer> slomo: we'll have to check that, never the less, we need code to
catch this, because the way it is done right now, it is really easy to break
the order, and the effect is visible much later, after the fact
<slomo> stormer: i'm fine with a check in gstpad that causes a g_warning() if
events happen out of order
<slomo> stormer: but silently fixing that up is just covering bugs elsewhere
<stormer> possibly, as said my filling was that there is cases where a segment
will stick, and (without flush) will get replaced by a pair of caps and
segment, but that leads to miss-ordering
<stormer> s/filling/feeling/
<stormer> slomo: it's also difficult to control when you try to do dynamic
linking
<slomo> stormer: do you have a scenario where that could happen but all
elements are doing their job correctly?
<__tim> if I'm not mistaken you only wrote that you and ocrete "had a feeling"
it could happen legitimately, but you didn't provide more details :)
<stormer> slomo: that's what I said, it takes hours to analyse what going on,
when I'll have to revisit, I just thought that one of you knew if such a
scenario exist or not
<__tim> when you link the sticky events should be dispatched in the right order
(and a predefined order) - is that not 
<slomo> stormer: i can't think of any, sorry :) but feel free to push a change
similar to your latest, that doesn't force the order but instead does a
g_warning()

-- 
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.