Re: [Live-devel] openRTSP exit() in BasicTaskScheduler::SingleStep() due to socket error 10038(WSAENOTSOCK)

Step()] max fd %d, there %d fds in reset fReadSet while %d ones in readSet\n", fMaxNumSockets - 1, fReadSet.fd_count, readSet.fd_count); for(size_t i = 0; i < readSet.fd_count; i++) fprintf(fp, "[BasicTaskScheduler::SingleStep()] reset readSet has fd %d while fReadSet has fd %d

Re: [Live-devel] openRTSP exit() in BasicTaskScheduler::SingleStep() due to socket error 10038(WSAENOTSOCK)

seem the same as in fReadSet. So I force readSet to be reset for each socket number in handlers and it works finally. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] openRTSP exit() in BasicTaskScheduler::SingleStep() due to socket error 10038(WSAENOTSOCK)

others not. Any ideas? Also, no problem with the testMPEG4VideoStreamer(no need to set forMulticastUnspecified) on such PCs. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] Vulnerabilities in RTPInterface::handleRead()

1, the above code may cause problem. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] Consider TCP connection with timeout in RTSPClient::describeURL().

Dear Sir: connect() in RTSPClient::openConnectionFromURL() is blocking. A practical application may not accept such a behavior. The following functions provide connect() with timeout setting on Windows(maybe work on Linux). Not very elegant but work. Please take them into consideration. Boolean m

[Live-devel] Just in case the server responses nothing

is detected, the next time calling RTSPClient::describeURL() succeeds. It seems nobody should be blamed. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

Re: [Live-devel] Lost consideration about SSM on Windows XP with VS6.

> >#define IP_PKTINFO19 /* receive packet information for > ipv4*/ > >#define IP_RECEIVE_BROADCAST 22 /* allow/block broadcast reception > */ > > No, I won't be defining those, because they're not used anywhere in our > code. > -- They are mentioned just in case. It's welcome to ignore them currently. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] Lost consideration about SSM on Windows XP with VS6.

IP group/source */ #define IP_BLOCK_SOURCE 17 /* block IP group/source */ #define IP_UNBLOCK_SOURCE 18 /* unblock IP group/source */ #define IP_PKTINFO19 /* receive packet information for ipv4*/ #define IP_RECEIVE_BROADCAST 22 /* a

[Live-devel] An implicit bug in RTSPClient::getResponse()1 on Windows

); break; } This should ends the probelm. BR. Brain Lai ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

Re: [Live-devel] Unable to receive multicast video stream on Windows XP

t in its SETUP request and may ignore this recommendation. If the server has no preference, it SHOULD set the port number value to zero. Example: m=audio 0 RTP/AVP 31 BR. Brain Lai 2007/11/12, Brain Lai <[EMAIL PROTECTED]>: > > Dear Sir: > > Multicast applicatio

[Live-devel] Unable to receive multicast video stream on Windows XP

join the multicast group but the VC6 compiled version doesn't. I am not familiar with Windows socket programming but there seems something missing or wrong. Do you ever get into this trouble and solve it? BTW, all the tests link to the latest live555. BR. Brai