combination of the two that causes the problem.
So is there something that can be optimised with using pipes? Or would
it be better to change the input of myTestOnDemandRTSPServer to use a
UDP source for the stream?
Regards,
Simon Brown
--
Microvideo
Copley Hill Business Park
Cambridge Road
On Sep 8, 2020, at 12:52 AM, Simon Brown wrote:
If I take our transport stream and convert it to raw H264 using
FFmpeg with this command line:
ffmpeg -i udp://:61110 -c:v copy -an -f h264 test.264
and then ask testOnDemandRTSPServer to play it by asking for
rtsp://192.168.1.13
On Sep 8, 2020, at 12:52 AM, Simon Brown wrote:
If I take our transport stream and convert it to raw H264 using FFmpeg with
this command line:
ffmpeg -i udp://:61110 -c:v copy -an -f h264 test.264
and then ask testOnDemandRTSPServer to play it by asking for
rtsp://192.168.1.13
the ffmpeg command to pipe out the raw 264 data,
and then the RTSP server to accept stdin as the file for h264ESVideoTest
I get a single frame displayed and nothing more. Is there any reason for
this?
Regards,
Simon Brown
--
Microvideo
Copley Hill Business Park
Cambridge Road
Babraham
CB22 3GN
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 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.
W
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
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
Instead,
simply do all of this from your shell's command line. That’s one of the good
things about Unix.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
Simon Brown
--
Microvideo
Copley Hill Business Park
Cambridge Road
Babraham
CB22 3GN
tel: +44 1223 834119
__
ile connected to stdin the
stdin doesn't work).
Is there any reason why or how test testOnDemandRTSPServer would be
blocking my main program from running?
Simon Brown
--
Microvideo
Copley Hill Business Park
Cambridge Road
Babraham
CB22 3GN
tel: +44 1223 834119
__
Hi,
I'm trying to send a live transport stream over RTSP. I initially
tested with testMPEG2TransportStreamer having modified it to pull from
stdin and got results, though there was significant picture break
up/dropped frames because it was using UDP. So instead I've started
using live555Med
11 matches
Mail list logo
