I’m not sure what exactly you’re asking here. When receiving a
RTP/RTCP-over-TCP stream (i.e., on the RTSP TCP connection), we certainly do
handle socket read errors, if they occur. But the actual socket itself (for
the RTSP TCP connection) is not closed until the “RTSPClient” decides that it
I have realized that streaming in interleaved mode and having the state
AWAITING_PACKET_DATA, we use fReadHandlerProc as incomingReportHandler1()
for RTPInterface for rtcp
networkReadHandler1() for RTPInterface for rtp.
But I don't see the remote close event(readSocket returning -1) being
handled h
> So rather than using our existing video sources, I've been looking at using
> the OpenRTSP client to record streams from testOnDemandRTSPServer. I have a
> test H264 file in a Matroska container and can (sort of) successfully record
> a "raw" H264 file, playable by VLC using the following:
>
Hi,
I've been investigating the Live555 library with a view to using it in an
embedded platform for (initially) the recording of H264 video received over RTP
into AVI files. I don't have a great deal of knowledge about the innards of
H264, I'm hoping that in using this library I won't need to..
> Yes i am using “mpeg2TransportStreamFromUDPSourceTest” example code(i.e.,
> lines 404-430 of “testOnDemandRTSPServer.cpp”) and my input source is MPEG
> Transport Stream data.
> When i set inputStreamIsRawUDP = False i got that warning, but when i set
> inputStreamIsRawUDP = True no warning me
Yes i am using “mpeg2TransportStreamFromUDPSourceTest” example
code(i.e., lines 404-430 of “testOnDemandRTSPServer.cpp”) and my input
source is MPEG Transport Stream data.
When i set inputStreamIsRawUDP = False i got that warning, but when i
set inputStreamIsRawUDP = True no warning message disp
As you presumed I just run single program and we use another tiny RTSP client
to generate heavy load. (just stream, not decoding)
Regarding socket descriptor limitation,
I already increase it to 1024. Before do this, we stopped at 32 clients (32 * 2
sockets, RTP, RTCP)
some strange thing is
Why
Hi,
We are currently facing a socket descriptor leak for the source through
which we stream using live555 as proxy. I was looking for a location where
sockets are closed for the source. I looked into the networkReadHandler
callback to check if we close sockets if readSocket returns -1(for
bytesRea
Are you using the “mpeg2TransportStreamFromUDPSourceTest” example code (i.e.,
lines 404-430 of “testOnDemandRTSPServer.cpp”? If so, are you sure that your
input source is MPEG Transport Stream data, and are you setting the
“inputStreamIsRawUDP” Boolean variable correctly, depending on whether o
Hello,
I am new to live555 and i have issue in using MPEG-2 Transport Stream,
coming from a live UDP (raw-UDP or RTP/UDP) source. I am running
TestOnDemandRTSPServer sample from testProgs.
Issue is warning message:
"MultiFramedRTPSource::doGetNextFrame1(): The total received frame size
exce
10 matches
Mail list logo
