>As for approach to deal with it. I simply have NO idea Roland... The
>problem is that it basically affects all data between (in your sample
>208 and 212) to go "bad" which is quite a large gap of course. I you
>have a briljant idea, i'll welcome it :D
I'm taking Ross's advice and liberally
On 25 jul 2008, at 22:09, Ross Finlayson wrote:
It seems that your server is buggy. I've seen this before with some
versions of Apple's QuickTime (aka. Darwin) Streaming Server.
Therefore, receivers need to be on the lookout for unusual changes
(decreases or large increases) in presentation
It seems that your server is buggy. I've seen this before with some
versions of Apple's QuickTime (aka. Darwin) Streaming Server.
Therefore, receivers need to be on the lookout for unusual changes
(decreases or large increases) in presentation time, and reset their
internally-maintained off
Yes, you found a bug on the code. The second declaration of ourSocket
was incorrect. This will get fixed in the next release of the code.
Also, "do { ... } while (0);" is a common C++ idiom used to create a
block of code that's easy to break out of (if an error occurs),
without using except
Hi Ross
>I really wish people would stop thinking that they need to do their
>own implementation of the RTP/RTCP protocol (e.g., look at RTP
I'm thinking exactly the opposite, I'd love to use and contribute to
a open source library that takes care of all the intricacies of
RTP/RTCP. I'm just t
Hi Ross.
Don't worry, this is not an help request, only an explanation one.
Watching this code
TSPServer*
RTSPServer::createNew(UsageEnvironment& env, Port ourPort,
UserAuthenticationDatabase* authDatabase,
unsigned reclamationTestSeconds) {
int ourSocket = -1;
do {
in
Ross Finlayson wrote:
> The problem is probably that QuickTime does not implement the same
> H.264 'profile' that your server's encoder generates.
I'm not sure, because within .mov/.mp4 containers QuickTime can play
video fine.
> However, you should check on a QuickTime mailing list to confirm t
We have implemented rtsp server using live555 framework. Also we are
using libx264 as encoder. Open source clients like VLC and mplayer can
get and play H.264 stream w/o any problem. So I think our implementation
of H264VideoStreamFramer is correct.
However QuickTime(7.4.5) is seems different sto
Judging by what your IP camera sent, it is not using RTSP in any
standard way, so it is unlikely that our software will be able to
communicate with it.
However, have you just tried running "openRTSP" with the "-T
" option, as described in the online documentation?
If that doesn't work, then y
Hi Gents.
The topic of this message is little bit off-topic, but because it's
related to live555 software too I think I can describe my problem here.
We have implemented rtsp server using live555 framework. Also we are
using libx264 as encoder. Open source clients like VLC and mplayer can
get and
Dear All,
I would like to use live555 to capture the Video stream from a IP camera.
I can use IE to get the video stream from the IP camera. But I find there are
3 HTTP sessions between IE and IP Camera. I would like to use openRTSP on it,
but how to separate 3 different sessions by openRTSP ?
Hi:
I downloaded the cross-compiler that vlc support(
wince-arm-gcc4.0.0-cvs-linux-crosscompiler-20050517.tar.bz2)
when I --enable-livedotcom, it always display many errors
finally, I found when I include in .cpp file, then the errors always
exist
I solve this problem is comment out this line(#
12 matches
Mail list logo
