Reduce the scope of set_state?

[Lautaro Woites]

Hi Adrian,
      I think your example is different from mine because you are not
changing the state of  the src elements.
  I' ve followed this to achieve my pipeline =>
http://gstreamer-devel.966125.n4.nabble.com/change-quot-location-quot-of-filesrc-element-without-breaking-tcpserversink-connection-tt4661248.html#a4661273
.
And it works fine! But my program has crashed from time to time. (When i've
tried to change two src at aprox the same time, apparently one state change
affects the others, so I need a mutex I Suppose)

Sebastian, I've Tried using gst_element_set_locked_state, but seeing the
logs I am still viewing that my the elements post messages like:

child 'img_src_bkg_src' changed state to 3(PAUSED) successfully

I will keep trying.

Thanks a lot for your answers!




> normally you would block the pads, unlink the element and then put it
> on another pipeline (or just remove it from the main until it's needed
> again) so it is not affected by the state changes on the main pipeline
> of your program. Something like what is shown here:
>
> http://groakat.wordpress.com/2012/12/05/gstreamer-stream-h264-webcam-data-to-series-of-files/
> (but that use case is a bit different). Keep in mind that some
> elements don't really like to be reused so perhaps removing and adding
> a fresh one is the way to go. Let me know if you need a hand.
>
> Best regards.
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20131111/5110ac4a/attachment.html>