tee pipeline

[horai]

Dear sir,

Thank you for you suggestion.

Rpicamsrc seems to have more benefits than any other source
element.As far as I understand,the most convenient souce element following
all the desired standards would be v4l2src.
Just to note,it I understand it correctly, rpicamsrc is written using mmal
proprietary api therefore not following v4l standard,anyway I tried v4l2src
and rpicsmsrc is still way more suitable for raspberry camera.
I hope that in near future,Raspberry v4l kernel driver for Raspberry will
improve camera compatibility.

Anyway,I don't think my problem lies in the source.
If I use rpicamsrc together with videotestsrc on two payloads,pay0 and pay1
in server pipeline, I can select whichever stream I want.
Since I cannot place two times rpicamsrc in server pipeline,I have to use
tee to split the stream coming from single rpicamsrc element.
I don't know why rtsp server cannot keep streaming upon client connection
and sends single image only.
The possitive aspect is that I can select the stream but stream from server
has to be already started externally from pipeline from command line.
What do I do so different in my client code instead of pipeline in command
line?
Stream freezes with single image in case I have select-stream signal 
handler added to my code,when this signal handler is commented,the client
behaves the same way as command line pipeline,but I cannot select the
desired stream.
One thing I am not happy with is that in this case server sends both streams
simultaneously but only one is being displayed therefore assume the problem
could lie in some timestamo,sychronization or even in the fact that
gst-rtsp-server might not be very friendly with tee element within the
pipeline.
Whoever resolves it I pay one beer.



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/