On 25/08/2020 16:41, Ross Finlayson wrote:
...
(In any case, this will be my last posting on this topic.)
Ross Finlayson
Understood, and many thanks for your help.
Simon
--
Microvideo
Copley Hill Business Park
Cambridge Road
Babraham
CB22 3GN
tel: +44 1223 834119
_
> On Aug 25, 2020, at 9:51 PM, 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 st
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
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
> 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 pr
On 24/08/2020 16:29, Simon Brown wrote:
On 24/08/2020 15:08, Ross Finlayson wrote:
Is there any reason why or how test testOnDemandRTSPServer would be
blocking my main program from running?
No, but it sounds like there’s something wrong in the way that you’re
“spawning the testOnDemandRTSPSer