[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





------- Comment #3 from Akos Maroy  2005-12-27 11:30 UTC -------
Created an attachment (id=56433)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=56433&action=view)
sample code showing that setting pads to flushing doesn't solve the problem

see the sample code that shows that setting pads to flushing mode doesn't solve
the problem either.

the sample code contains a { filesrc ! mad ! audioconvert ! alsasink }
pipeline. both mad and audioconvert are locked, and their pads are set to
flushing.

but this does not prevent the pipeline to play right from the start.

the intended scenario for the sample code would be to stay silent for 2
seconds, and then start to play, when the audioconvert and mad plugins are set
into PLAYING state. (before that they are in PAUSED).


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