They might. What is your rates?
Thanks,
Craig
On 11/19/2013 11:58 AM, Ross Finlayson wrote:
I've been running for two days with openRTSP on a camera that had problems,
openRTSP is still capturing video to the output file and the console last
message has not changed.
One thing to note is when
> I've been running for two days with openRTSP on a camera that had problems,
> openRTSP is still capturing video to the output file and the console last
> message has not changed.
>
> One thing to note is when streaming stops from the proxy of the camera, if I
> connect to the camera directl
> Started playing session
> Receiving streamed data (signal with "kill -HUP 14502" or "kill -USR1 14502"
> to terminate)...
> Data packets have begun arriving [1384803098725]
>
>
> MultiFramedRTPSource::doGetNextFrame1(): The total received frame size
> exceeds the client's buffer size (10)
I had a a second system setup at work and when I got into work today I saw the
following from the openRTSP. It does appear there was a failure, would this
cause a problem with the proxy server?
Date: Mon, 18 Nov 2013 12:31:37 GMT
Session: 400662;timeout=80
RTP-Info: url=rtsp://192.168.3.217/liv
I've been running for two days with openRTSP on a camera that had problems,
openRTSP is still capturing video to the output file and the console last
message has not changed.
One thing to note is when streaming stops from the proxy of the camera, if I
connect to the camera directly it will stre
> After running openRTSP the last thing displayed is Data packets have begun
> arriving [#], I did not here any beep. After browsing the source I found
> that the playCommon.cpp has this message and a \007, which apparently did not
> cause the beep (no big deal). Now I see I have started s
After running openRTSP the last thing displayed is Data packets have begun
arriving [#], I did not here any beep. After browsing the source I found
that the playCommon.cpp has this message and a \007, which apparently did not
cause the beep (no big deal). Now I see I have started streaming
> So I have verified the source device is streaming data. I have connected to
> it's RTSP stream directly, using gstreamer and vlc. I will connect the
> openRTSP to the source back-end when it fails and see if it works.
No! You should test your back-end stream using "openRTSP" *FIRST*, befor
On a side note, I gave Vivotek engineers the mailing list info and I hoped they
would join. We are working directly with them and I will see them tomorrow.
Thanks,
Craig
On 11/17/2013 11:13 PM, Ross Finlayson wrote:
What is the best way to determine that a proxy server is streaming from
an RTS
So I have verified the source device is streaming data. I have connected to
it's RTSP stream directly, using gstreamer and vlc. I will connect the
openRTSP to the source back-end when it fails and see if it works.
Thanks,
Craig
On 11/17/2013 11:13 PM, Ross Finlayson wrote:
What is the best wa
> What is the best way to determine that a proxy server is streaming from
> an RTSP source?
The best way is to run, on the computer on which you would run the proxy server
openRTSP -n rtsp://
(The "-n" option tells "openRTSP" to display a report (with a beep) when the
first RTP packet ar
What is the best way to determine that a proxy server is streaming from
an RTSP source? I see OPTION commands sent and responding using verbose
logging, but this does not indicate to me that the stream is sending data?
Thanks,
Craig
___
live-devel mai
12 matches
Mail list logo
