From: Thomas L. <la...@gm...> - 2008-08-28 18:06:40
|
Hi, i would like to reuse parts of my pipeline which in principle works, but it uses the "wrong" clock. It's an dynamic build pipeline which looks like this: neonhttpsrc->flutsdemux-> multiple audio + single video pipelines On the first start it uses the "correct" GstAudioSinkClock, but on the second start it selects the GstSystemClock. On stop the CLOCK_LOST signal is send (because the audiosink was removed from the pipeline), on start the NEW_CLOCK is immediately send and the systemclock is selected (because at this time there is no audiosink in the pipeline). But after the pipeline is build the audiosink will not be selected as new master. What's wrong or missing here? Thank you, Thomas -- View this message in context: http://www.nabble.com/reuse-partial-pipeline%3A-clock-problems--tp19205508p19205508.html Sent from the GStreamer-devel mailing list archive at Nabble.com. |
From: Wim T. <wim...@gm...> - 2008-08-29 08:50:07
|
On Thu, 2008-08-28 at 11:06 -0700, Thomas Loewe wrote: > Hi, > > i would like to reuse parts of my pipeline which in principle works, but it > uses the "wrong" clock. > > It's an dynamic build pipeline which looks like this: > > neonhttpsrc->flutsdemux-> multiple audio + single video pipelines > > On the first start it uses the "correct" GstAudioSinkClock, but on the > second start it selects the GstSystemClock. > > On stop the CLOCK_LOST signal is send (because the audiosink was removed > from the pipeline), on start the NEW_CLOCK is immediately send and the > systemclock is selected (because at this time there is no audiosink in the > pipeline). But after the pipeline is build the audiosink will not be > selected as new master. > > What's wrong or missing here? The clock is selected when going from PAUSED to PLAYING. If you are dynamically building and destroying the pipeline it's a good idea to bring the pipeline back to PAUSED before adding the new sinks. When all sinks are added, you can put it back to PLAYING to make it select a clock from all available clock providers. Wim > > Thank you, > Thomas |
From: Thomas L. <la...@gm...> - 2008-08-29 14:07:49
|
Now it works, Thank you! Wim Taymans-2 wrote: > > The clock is selected when going from PAUSED to PLAYING. If you are > dynamically building and destroying the pipeline it's a good idea to > bring the pipeline back to PAUSED before adding the new sinks. When all > sinks are added, you can put it back to PLAYING to make it select a > clock from all available clock providers. > > Wim > -- View this message in context: http://www.nabble.com/reuse-partial-pipeline%3A-clock-problems--tp19205508p19220659.html Sent from the GStreamer-devel mailing list archive at Nabble.com. |
From: Thomas L. <la...@gm...> - 2008-08-30 10:19:43
|
Hm, it seems only to work when the source stream is the same. Only removing and readding the demuxer works for different source streams too. Is there a way to avoid this like flushing/resetting the flutsdemux or something like this? -- View this message in context: http://www.nabble.com/reuse-partial-pipeline%3A-clock-problems--tp19205508p19232091.html Sent from the GStreamer-devel mailing list archive at Nabble.com. |