[gstreamer-bugs] [Bug 326736] New: gconf(audio|video)sink response to key changes

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=326736
 GStreamer | gst-plugins-good | Ver: HEAD CVS

           Summary: gconf(audio|video)sink response to key changes
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: thaytan at mad.scientist.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


When the GConf key for the gconf(audio|video)sink changes, the element responds
by replacing the contained objects, even if they're currently PLAYING or
PAUSED. 

This means that suddenly a new sink appears inside the bin, and it gets fed
data, but it has missed the newsegment information, and does not have the
correct synchronisation information to sync with the clock. 

While this would be a rocking nice feature to have (dynamic switching of output
backend in mid stream) at the moment it's just broken. A quick fix is that the
gconfaudio/videosink should only change during PAUSED->READY/NULL->READY state
transitions.

A few thoughts on the requirements to do dynamic backend switching:
* the gconf elements need to remember the most recent NEWSEGMENT and provide it
to the new output pipeline
* for video, gconfvideosink should keep a reference to the most recent frame
and push it into the the child pipeline. This will trigger new xoverlay
interface embedding.
* Clock should be set, and any other required synchronisation information
passed to the child sinks.


-- 
Configure bugmail: http://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.