over a netcat pipe or something. How does the
HTTP server pick up the output from the proxy, is it by some RPC? On Wed,
03 Jun 2020 12:22:44 -0400 Ross Finlayson wrote >
On Jun 4, 2020, at 2:34 AM, Admin via live-devel
wrote:> > Help a newbie? I would like to have an RTSP prox
documentation that the HTTP server must be on the same computer, so
maybe over a netcat pipe or something. How does the HTTP server pick up the
output from the proxy, is it by some RPC? On Wed, 03 Jun 2020 12:22:44
-0400 Ross Finlayson wrote > On Jun 4, 2020, at
2:34 AM, Admin via live-de
--- Begin Message ---
Help a newbie? I would like to have an RTSP proxy running on a Raspberry Pi
advertising to an HLS proxy running on a server. I noticed the HLS proxy has a
-R "REGISTER" flag to listen for an advertised RTSP stream, but how do I
configure the RTSP proxy to advertise?
Here's
> The best way to handle data loss is to stream over UDP, but also
configure your encoder so that ‘key frames’ are sent as a series of
‘slices’, rather than as a single ‘frame’ (or NAL unit, in H.264
terminology). That way, the loss of a packet will cause only a single
‘slice’ to be lost; the res
I really wanted to post this as a learning check. I think I was able to
finally wrap my head around an RTSP/RTP issue I've been having.
Specifically, I have been playing around with a coupld of different IP
cameras.
I've found that I have no real issues streaming (or proxying) 720p or less
cameras
Another approach I was thinking, if I split the incoming stream into 5-10
seconds chunks with time-stamp as filename, run a watcher script to
generate index files, can the code amended to continue to the next chunk?
Sorry I am not very familiar with C and couldn't find the source which
checks for E
Is it possible to (i) configure live mpeg-ts udp input (ii) store it in
mpeg-ts and (iii) create timecode (MPEG2TransportStreamIndexer) on the fly
to allow trick play?
Thank you.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live5
I just noticed that my forked h264 process is dying on startup due to a
thrown integer exception in StreamParser.cpp NO_MORE_BUFFERED_INPUT.
Looking into H264VideoStreamParser::parse() method as an example I see
that this is caught and treated as non fatal. However, the code I'm
working on doesnt a
Seemed to be some sort of circular linking dependency. Relinking all of
the libraries a second time fixed the issue. Thanks for the help! I was
surprised at how easy live555 was to cross compile for arm, everything
just worked.
-Thanks
Alex Wright
___
Alright, I've updated to the latest version of live555 and added the
function calls, but am running into some odd linking problems. I can see
the function definitions in the code, but the linker doesnt. If anyone
could give me some insight I'd appreciate it. It's most likely a
makefile issue on my
Hello, I have a camera with a modified version of wis-streamer and wanted to know whether wis-streamer supported RTSP over HTTP. I've tried connecting to the ports it streams on with telnet and it doesnt seem to respond to HTTP requests. Although it streams fine and responds to describe requests. H
11 matches
Mail list logo
