running openRTSP -q -w 704 -h 576
rtsp://192.168.0.101/axis-media/media.amp test.mov
and sending kill -HUP sometimes ends with a segfault. This is with
live555 2010.06.18 but I didn't see this with 2010.04.09
Aha! You've found a bug in the openRTSP code. We're closing the
output file(s)
Quoting Ross Finlayson finlay...@live555.com:
This is wrong. It should be npt, not ntp.
I just found another camera not working anymore.
The error message is still about invalid range header, but this time npt is well
written.
It seems live555 doesn't accept now- :
Received 119 new bytes of
I just found another camera not working anymore.
The error message is still about invalid range header, but this time
npt is well
written.
It seems live555 doesn't accept now- :
OK, this is definitely a bug in our code, because npt=now- is
legal, according to the RTSP specification.
This
Please try the following, which should fix this problem:
In testProgs/playCommon.cpp, line 1104, move the statement
closeMediaSinks();
down 5 lines, so that it now takes place after
Medium::close(session);
It turns out that I didn't have this quite right. The correct
sequence
Zugangsdaten für den mmg-server1:
Username: ebel
Passwort: ebel
freier Platz auf /Datastore/public/ebel/
jens.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
On Tuesday 22 June 2010 04:50:01 Ross Finlayson wrote:
I don't use any revision control system myself. When I'm developing
this code, I use exactly two commands: emacs and make.
Well, I see myself several years ago :-) Lately I have learned git and now I'm
using it for every project. But it
22 jun 2010 kl. 11.26 skrev Ross Finlayson:
Please try the following, which should fix this problem:
In testProgs/playCommon.cpp, line 1104, move the statement
closeMediaSinks();
down 5 lines, so that it now takes place after
Medium::close(session);
It turns out that I didn't
I suspect that the real reason why some people want to use a revision
control system is that they want to easily update to the latest
version of the code after they've made custom modifications to it
(i.e., without losing their modifications).
Yes :-), at least in my case.
You are
