[gstreamer-bugs] [Bug 559250] segments need identifiers.

[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=559250

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thaytan at mad.scientist.com




------- Comment #1 from Jan Schmidt  2008-11-04 11:02 UTC -------
I have previously conceived something that sounds really close to what you've
just described, but never gotten to actually doing anything about it.

I foresee some complexity in dealing with the reality of GstSegments in any
useful pipeline - there's likely to be moments where multiple segments are
active, and in some pipelines there'll *always* be multiple segments active, in
different formats (BYTES -> TIME through a demuxer or parser for e.g.).
Creating a unified segment identification across those sorts of boundaries
probably requires the cooperation of the elements involved. gnonlin is another
use case to examine, where there are bins sending their own seeks and changing
segments about. 

I'm not sure about the "It would be ideal if the application only got non-stale
segment-done messages" statement. I think uniformity and predictability of the
expected messages is valuable, without worry about races caused by thread
interactions - one guy sending a seek just after an element queues segment-done
onto the bus for example. If there's a unique way to identify which
segment-done message you're receiving, then it doesn't matter if you get
'stale' ones.


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