We have things working now by avoiding the issue by creating our own
customized DiscreteFramer. It avoids the problem by directly using
the output buffer and does not touch the Bank buffers. I suspect
there is a problem with the H264VideoStreamFramer.
No, I think it's OK. However, it expects
Thanks. This will be fixed in the next release 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/listinfo/live-devel
We have discovered a problem with the following patch, introduced in
live.2010.12.05:
- Added a sanity check to "MultiFramedRTPSink" and "BasicUDPSink" to
allow for the possibility of the system clock jumping ahead in time,
and thereby messing up the calculation of how long to wait before
Ross,
We have things working now by avoiding the issue by creating our own
customized DiscreteFramer. It avoids the problem by directly using the
output buffer and does not touch the Bank buffers. I suspect there is a
problem with the H264VideoStreamFramer.
BTW, does it conflict with the H264 sta
Ross,
The following patch fixes a problem that the H264 Profile Level Id was being
built and then truncated in u_int8_t profile_level_id; it needs to be
u_int32_t profile_level_id.
$ svn diff lib/live/liveMedia/H264VideoRTPSink.cpp
Index: lib/live/liveMedia/H264VideoRTPSink.cpp
==
Hi,
I have a camera which is not working anymore with recents versions of
live555. Error is : "Bad "Range:" header"
"clock" range seems to be defined in rtsp specs.
Here is the play request :
Sending request: PLAY rtsp://192.43.185.31:554/MediaInput/mpeg4/
RTSP/1.0
CSeq: 5
User-Agent: LibVLC/1.2
