[gstreamer-bugs] [Bug 324725] gst_element_set_locked_state() doesn't have effect

[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=324725
 GStreamer | gstreamer (core) | Ver: 0.10.0


Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wim at fluendo.com




------- Comment #2 from Wim Taymans  2005-12-21 19:30 UTC -------
Two problems:

1) the debug output is deceiving, the element does not actually change state,
we just report success to the caller, which prints that the state changed.

2) pad are initially created in the non-flushing state so that you can stream
data to them before they are activated. mad happens to work fine in the NULL
state and so this pipeline works fine.

The proper fix is to initialize a newly created pad in the flushing state. It
unfortunatly made ghostpads fail right before the 0.10 release, need to
reinvestigate.


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