[gstreamer-bugs] [Bug 123775] [api] setting state on element should force highest state change on parent

bugzilla-daemon at bugzilla.gnome.org bugzilla-daemon at bugzilla.gnome.org
Sat Jan 29 18:10:04 PST 2005


Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=123775
 GStreamer | gstreamer (core) | Ver: 0.8.0





------- Additional Comments From Ronald Bultje  2005-01-29 21:10 -------
My next step was to add a no-recurse flag to GstBin to make it not recurse onto
children when doing a non-recursive state-change (so this flag would be set in
gst_bin_change_state_norecurse()). I'm getting further now, my pipeline actually
starts to play again, and it even EOS'es. However, somewhere in between there
and going to NULL, it hangs.

More tomorrow...

(Note that the FIXME at the bottom of GstBin's _change_state() is very true:
setting a recursive state-change will set the bin's state already through the
kid's states, which may not be what you want. This works, though, so it's not a
bad thing.)

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.




More information about the Gstreamer-bugs mailing list