On 25/08/2020 10:51, Simon Brown wrote:
On 25/08/2020 10:44, Ross Finlayson wrote:
It would transpire that the onDemandRTSP server doesn't open stdin
or pull data from it until it gets an RTSP request from the outside
world. But our encoder is pushing data out on stdout continuously.
Why is it doing that? Is it doing non-blocking writes to ’stdout’?
If so, then it probably shouldn’t. If you do blocking writes to
’stdout’, and nothing is currently reading from the other side, then
your encoder will just block until the other side needs data.
It does non-blocking writes because otherwise everything else stalls.
We're only sending one of the streams to live555, the other streams
can't stop just because no-one is pulling the RTSP stream.
Is there any way for the onDemandRTSPServer to signal when it has a
request for a stream? If I set my stdout to non-blocking (it wasn't
before which was causing my encoder to stall) then the main stream
continues to run smoothly even if RTSP isn't being asked for, but the
RTSP stream fails to lock onto the signal properly, so outputs very little.
Regards,
Simon
--
Microvideo
Copley Hill Business Park
Cambridge Road
Babraham
CB22 3GN
tel: +44 1223 834119
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
