From what you describe, it sounds like you’re not just behind a ‘router’, but
that you’re behind a NAT box (that translates IP addresses). RTSP was never
intended to work in such an environment, but the fact that you’re able to get
it to work may just be luck (and something specific to your par
Does the “testRTSPClient” demo application work OK for you (with the same
RTSP/RTP (I assume) source)? If so, you should start by modifying the
implementation of the “DummySink” class.
Note that - for H.264 video - each ‘frame’ that gets delivered from a H.264
RTSP/RTP stream (via a “H264Video
Hi Ross,
we have an issue regarding a RTSP server behind a router.
The client is able to access the streaming but it displays the first
frame
after more than 12 seconds from the start time,
then usually playback stops after about 40 seconds.
If we access the streamin
Good morning. Our C++ CustomH264Sink derived classes' afterGettingFrame
methods shown below are not recognizing the IFrame bytes supposed to be
contained in a H264 packet generated from a file containing 5 minutes of
Live555 H264 video data. Please tell me what we are doing incorrectly or
for
Thank you for your comments.
ChaSeop Im
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Yes, I think you’ve found a bug in the code.
Note, however, that you seem to be using an old version of the code, because:
> In this case, foundRequest can’t access because it is deleted. But,
> handleRequestBytes accesses foundRequest on 1835 line. It occurs crash.
In the current version of th
HI.
I think that RTSPClient is occurred crash in handleRequestBytes.
handleRequestBytes could called resendCommand when received 401 response
code.
resendCommand call sendRequest and sendRequest checks openConnection.
When openConnection returned -1, sendRequest delete request(this is
foundR
