OK, I think what's happening here is that although your JPEG frame rate is low,
your JPEG frame sizes are exceeding 6 bytes - the default buffer size
that's used by the proxy's "RTPSink"s.
Try adding the following line to "live555ProxyServer.cpp" - at the start of
"main()":
OutPacke
> Basically I understand RTSP protocol, but I want to see a sample
> source code which includes ANNOUNCE and RECORD in the
> RTSP client.
You may wish to look at the code for the "testMPEG1or2AudioVideoToDarwin" and
"testMPEG4VideoToDarwin" demo applications - in the "testProgs" directory.
The
The MJPEG stream is only 3fps, there is no packet loss, it's a 1gbit
network and nothing else is streaming on the network.
Opening the camera RTSP stream with VLC works fine, no errors, opening the
RTSPRoxy stream with VLC, I get audio only. Opening direct from the camera
with openRTSP works just
Thank you for your kind reply!
I am sorry I didn't say which kind of media server I am using.
I understand live555 server does not support clients to push stream.
I am using a Wowza server which supports the function.
I have to implement a RTSP client in a embedded system which will
be installed
> I have an IP camera that gives MJPEG over RTSP, I'm trying to proxy the
> stream with:
>
> $ live555ProxyServer rtsp://192.168.0.221/live2.sdp
>
> When I use the openRTSP client like so:
>
> $ ./openRTSP rtsp://127.0.0.1:10110/proxyStream
>
> The output looks like this: http://pastie.org/716
> I updated to live555 with the 03072013 code because of the problems I was
> having with a new camera.
>
> My app still had trouble with a certain camera.
>
> I then started connecting to many cameras that had worked in the past with
> the openRTSP app.
It wasn't clear from your message whe
The debug output from live555ProxyServer looks like this:
$ live555ProxyServer -V rtsp://192.168.0.221/live2.sdp
LIVE555 Proxy Server
(LIVE555 Streaming Media library version 2013.03.07)
Opening connection to 192.168.0.221, port 554...
RTSP stream, proxying the stream "rtsp://192.168.0.221/live
Hi there,
I have an IP camera that gives MJPEG over RTSP, I'm trying to proxy the
stream with:
$ live555ProxyServer rtsp://192.168.0.221/live2.sdp
When I use the openRTSP client like so:
$ ./openRTSP rtsp://127.0.0.1:10110/proxyStream
The output looks like this: http://pastie.org/7167135 - liv
I updated to live555 with the 03072013 code because of the problems I was
having with a new camera.
My app still had trouble with a certain camera.
I then started connecting to many cameras that had worked in the past with the
openRTSP app.
A few connect, but most go thru the whole conversatio
Yes, this seems like a reasonable addition, and will be included in the next
version of the software.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/l
The attached patch adds unconditional URL decoding to the "urlSuffix"
part of the URL only.
I added this so I could have spaces in file names, though it has other
benefits. For one thing, since RTSP specifies that header info is to be
interpreted as UTF-8, it means we get Unicode file name su
> I want to implement a RTSP client to send streams to the RTSP server.
> But testRTSPClient, openRTSP don't have upstreaming function.
> Can you show me a sample code to implement it?
Sorry, but we don't support this (our servers only 'pull' data; they do not
support data getting 'pushed' to the
I want to implement a RTSP client to send streams to the RTSP server.
But testRTSPClient, openRTSP don't have upstreaming function.
Can you show me a sample code to implement it?
Thanks,
Sungsoo Kim
___
live-devel mailing list
live-devel@lists.live555.
13 matches
Mail list logo
