<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><DIV><SPAN class="hps" closure_uid_xetpkc="1035">I use</SPAN> <SPAN class="hps" closure_uid_xetpkc="1036">one thread to handle</SPAN> <SPAN class="hps" closure_uid_xetpkc="1037">16</SPAN> <SPAN class="hps" closure_uid_xetpkc="1038">data requests</SPAN><SPAN closure_uid_xetpkc="1039">, meaning that</SPAN> <SPAN class="hps" closure_uid_xetpkc="1040">doEventloop</SPAN> <SPAN class="hps" closure_uid_xetpkc="1041">handle</SPAN> <SPAN class="hps" closure_uid_xetpkc="1042">16</SPAN> <SPAN class="hps" closure_uid_xetpkc="1043">to accept</SPAN> <SPAN class="hps" closure_uid_xetpkc="1044">the data</SPAN><SPAN closure_uid_xetpkc="1045">.</SPAN> <SPAN class="hps" closure_uid_xetpkc="1046">But</SPAN> <SPAN class="hps" closure_uid_xetpkc="1047">in the experiment</SPAN><SPAN closure_uid_xetpkc="1048">, I found</SPAN> <SPAN class="hps" closure_uid_xetpkc="1049">a very high</SPAN> <SPAN class="hps" closure_uid_xetpkc="1050">CPU usage</SPAN><SPAN closure_uid_xetpkc="1051">,</SPAN> <SPAN class="hps" closure_uid_xetpkc="1052">memory</SPAN> <SPAN class="hps" closure_uid_xetpkc="1053">usage</SPAN> is <SPAN class="hps" closure_uid_xetpkc="1054">Continued growth</SPAN><SPAN class="hps" closure_uid_xetpkc="1058"></SPAN><SPAN closure_uid_xetpkc="1059">.</SPAN> <SPAN class="hps" closure_uid_xetpkc="1060">Do not know</SPAN> <SPAN class="hps" closure_uid_xetpkc="1061">why?</SPAN> <SPAN class="hps" closure_uid_xetpkc="1062">I think</SPAN> <SPAN class="hps" closure_uid_xetpkc="1063">the problem</SPAN> <SPAN class="hps" closure_uid_xetpkc="1064">is</SPAN> <SPAN class="hps" closure_uid_xetpkc="1065">the buffer</SPAN> <SPAN class="hps" closure_uid_xetpkc="1066">memory</SPAN> <SPAN class="hps" closure_uid_xetpkc="1067">settings</SPAN><SPAN closure_uid_xetpkc="1068">, but I</SPAN> <SPAN class="hps" closure_uid_xetpkc="1069">tried</SPAN> <SPAN class="hps" closure_uid_xetpkc="1070">several</SPAN> <SPAN class="hps" closure_uid_xetpkc="1071">methods</SPAN> <SPAN class="hps" closure_uid_xetpkc="1072">have not</SPAN> <SPAN class="hps" closure_uid_xetpkc="1073">changed</SPAN><SPAN closure_uid_xetpkc="1074">,</SPAN> <SPAN class="hps" closure_uid_xetpkc="1075">I do not know</SPAN> <SPAN class="hps" closure_uid_xetpkc="1076">how to</SPAN> <SPAN class="hps" closure_uid_xetpkc="1077">change</SPAN> <SPAN class="hps" closure_uid_xetpkc="1078">it?</SPAN> can you give me a hand? <SPAN class="hps" closure_uid_xetpkc="1079">Thank you</SPAN><BR><BR><BR></DIV>
<DIV>--<BR></DIV>
<DIV id="divNeteaseMailCard"></DIV>
<DIV><BR></DIV><PRE><BR>At 2011-12-20 09:46:00,live-devel-request@ns.live555.com wrote:
>Send live-devel mailing list submissions to
> live-devel@lists.live555.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.live555.com/mailman/listinfo/live-devel
>or, via email, send a message with subject or body 'help' to
> live-devel-request@lists.live555.com
>
>You can reach the person managing the list at
> live-devel-owner@lists.live555.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of live-devel digest..."
>
>
>Today's Topics:
>
> 1. Re: Live555 EventLoop Crash (Ross Finlayson)
> 2. SET_PARAMETER doesn't get handled in the RTSPServer over TCP
> (Jer Morrill)
> 3. Re: SET_PARAMETER doesn't get handled in the RTSPServer over
> TCP (Ross Finlayson)
> 4. question regarding recieving & unpacking TS over RTP,
> generated from testH264VideoToTransportStream (Ken Dunne)
> 5. Re: SET_PARAMETER doesn't get handled in the RTSPServer over
> TCP (Jer Morrill)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 19 Dec 2011 02:51:55 -0800
>From: Ross Finlayson <finlayson@live555.com>
>To: LIVE555 Streaming Media - development & use
> <live-devel@ns.live555.com>
>Subject: Re: [Live-devel] Live555 EventLoop Crash
>Message-ID: <02EA1F2B-C632-4833-8D86-C801A0EBFFEC@live555.com>
>Content-Type: text/plain; charset="windows-1252"
>
>> No I don?t see this error message, however I am seeing continuous truncations, almost every frame is truncated. My own debug output looks like this, at a rate of around 4 frames per second:-
>> deliverFrame(): newFrameSize:216054, fNumTruncatedBytes:66055
>> deliverFrame(): newFrameSize:108994, fNumTruncatedBytes:98217
>> deliverFrame():newFrameSize:96844, fNumTruncatedBytes :45293
>>
>> I?ve tried increasing OutPacketBuffer::maxSize from 1000000 to 5000000 (5 million) but this has no effect. Am I just trying to stream too much data, too quickly?
>
>No, the problem has nothing to do with 'speed'. There's a bug in your code somewhere. Sorry.
>
>
>Ross Finlayson
>Live Networks, Inc.
>http://www.live555.com/
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111219/c74d8084/attachment-0001.html>
>
>------------------------------
>
>Message: 2
>Date: Mon, 19 Dec 2011 23:08:13 +0000
>From: Jer Morrill <Jeremiah.Morrill@econnect.tv>
>To: "live-devel@lists.live555.com" <live-devel@ns.live555.com>
>Subject: [Live-devel] SET_PARAMETER doesn't get handled in the
> RTSPServer over TCP
>Message-ID:
> <80C795F72B3CB241A9256DABF0A04EC5F96DDA@SN2PRD0702MB101.namprd07.prod.outlook.com>
>
>Content-Type: text/plain; charset="us-ascii"
>
>Many apologies if this is a dupe, I don't think I properly signed up for the list before sending this earlier so I'm not sure if the email was "lost" or not.
>
>First I want to thank everyone involved in this project for such a high quality library. This is surely open-source done right!
>
>I am running the 12-2-2011 build of Live555. When I run RTSPClient::sendSetParameter(...) with a session that is running UDP to a live555 server implementation, the server parses and successfully runs the RTSPClientSession:: handleCmd_SET_PARAMETER (overridden in a subclass). If I run RTSPClient:sendSetParameter(...) with a session that is running via TCP, it does not ever get to the RTSPClientSession::handleCmd_SET_PARAMETER. Seems sending trickplay commands work fine in both TCP and UDP.
>
>I've searched the email list and found a few issues similar to this that were fixed, but couldn't find anyone reporting this afterwards. I can provide more debug details if needed, but it seems RTSPServer::RTSPClientSession::handleRequestBytes(...) doesn't successfully parse the full SET_PARAMETER command when using TCP (or is a symptom of something else).
>
>Thanks for any help and again, for the wonderful code!
>
>-Jer
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111219/eb496752/attachment-0001.html>
>
>------------------------------
>
>Message: 3
>Date: Mon, 19 Dec 2011 15:44:37 -0800
>From: Ross Finlayson <finlayson@live555.com>
>To: LIVE555 Streaming Media - development & use
> <live-devel@ns.live555.com>
>Subject: Re: [Live-devel] SET_PARAMETER doesn't get handled in the
> RTSPServer over TCP
>Message-ID: <1EB78808-10ED-490E-BCA1-6A614FE88CEB@live555.com>
>Content-Type: text/plain; charset="windows-1252"
>
>> I am running the 12-2-2011 build of Live555. When I run RTSPClient::sendSetParameter(?) with a session that is running UDP to a live555 server implementation, the server parses and successfully runs the RTSPClientSession:: handleCmd_SET_PARAMETER (overridden in a subclass). If I run RTSPClient:sendSetParameter(?) with a session that is running via TCP, it does not ever get to the RTSPClientSession::handleCmd_SET_PARAMETER. Seems sending trickplay commands work fine in both TCP and UDP.
>
>That's strange. (It's especially strange that other commands - e.g., "PLAY" - work OK for you in RTP-over-TCP mode, but that "SET_PARAMETER" does not.)
>
>> I can provide more debug details if needed
>
>Yes, please add
>#define DEBUG 1
>to the start of "liveMedia/RTSPServer.cpp", recompile and rerun your server, and access it both with a RTP-over-UDP client, and with a RTP-over-TCP client. Please send us the debugging output in each case.
>
>
>Ross Finlayson
>Live Networks, Inc.
>http://www.live555.com/
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111219/f2f522d5/attachment-0001.html>
>
>------------------------------
>
>Message: 4
>Date: Mon, 19 Dec 2011 17:10:40 -0800 (PST)
>From: Ken Dunne <ken@starseedsoft.com>
>To: "live-devel@lists.live555.com" <live-devel@ns.live555.com>
>Cc: "guru@starseedsoft.com" <guru@starseedsoft.com>
>Subject: [Live-devel] question regarding recieving & unpacking TS over
> RTP, generated from testH264VideoToTransportStream
>Message-ID:
> <1324343440.41379.YahooMailNeo@web1204.biz.mail.gq1.yahoo.com>
>Content-Type: text/plain; charset="iso-8859-1"
>
>
>I've used the example "testH264VideoToTransportStream" as a basis for generating a H264-TS-over-RTP stream of packets.
>
>I have used Wireshark to view the stream of RTP packets, and they appear to be correctly filled with an integer number of 188 byte Transport-Stream packets.
>
>I am trying to further validate this stream, and have used "testMPEG1or2VideoReceiver.cpp", and modified it to use the MP2T format (33) in the call to:
>
>????? sessionState.source = MPEG1or2VideoRTPSource::createNew( *env, &rtpGroupsock, 33, 90000 );
>
>This saves a file, but i am unable to play it with any player that i know of.
>
>Does anyone have any suggestions?
>
>Ken
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111219/a65f8333/attachment-0001.html>
>
>------------------------------
>
>Message: 5
>Date: Tue, 20 Dec 2011 01:25:29 +0000
>From: Jer Morrill <Jeremiah.Morrill@econnect.tv>
>To: LIVE555 Streaming Media - development & use
> <live-devel@ns.live555.com>
>Subject: Re: [Live-devel] SET_PARAMETER doesn't get handled in the
> RTSPServer over TCP
>Message-ID:
> <80C795F72B3CB241A9256DABF0A04EC5F96E11@SN2PRD0702MB101.namprd07.prod.outlook.com>
>
>Content-Type: text/plain; charset="us-ascii"
>
>Thanks for the quick response!
>
>I have attached a client debug output and server debug output text files (hope that's ok for this list). These are from the same rtsp session.
>
>Though the log does say RTSPServer::RTSPClientSession::handleRequestBytes(...) does say "parseRTSPRequestString() succeed...", it does not pass the next check:
>
>if (ptr + newBytesRead < tmpPtr + 2 + contentLength) break; // we still need more data; subsequent reads will give it to us
>
>At the point of the content length check the buffer looks like this:
>
>SET_PARAMETER rtsp://127.0.0.1/media?dev=1&source=archive&startTime=129661319116046065/ RTSP/1.0
>CSeq: 6
>User-Agent: HJT RTSP Client (LIVE555 Streaming Media v2011.12.02)
>Session: CA195293
>Content-Length: 30
>
>The complete command should also have (\r's and \n's excluded):
>GotoTime: 1234567890
>
>It does get these "GotoTime..." bytes afterwards the next calls to "handleRequestBytes", but the server never successfully parses the SET_PARAMETER command in RTP over TCP. Totally weird other messages get through just fine.
>
>Thanks again for all your help! Hope this is reproducible for you as I hate to send anyone on a wild goose chase!
>
>-Jer
>
>
>
>From: live-devel-bounces@ns.live555.com [mailto:live-devel-bounces@ns.live555.com] On Behalf Of Ross Finlayson
>Sent: Monday, December 19, 2011 3:45 PM
>To: LIVE555 Streaming Media - development & use
>Subject: Re: [Live-devel] SET_PARAMETER doesn't get handled in the RTSPServer over TCP
>
>I am running the 12-2-2011 build of Live555. When I run RTSPClient::sendSetParameter(...) with a session that is running UDP to a live555 server implementation, the server parses and successfully runs the RTSPClientSession:: handleCmd_SET_PARAMETER (overridden in a subclass). If I run RTSPClient:sendSetParameter(...) with a session that is running via TCP, it does not ever get to the RTSPClientSession::handleCmd_SET_PARAMETER. Seems sending trickplay commands work fine in both TCP and UDP.
>
>That's strange. (It's especially strange that other commands - e.g., "PLAY" - work OK for you in RTP-over-TCP mode, but that "SET_PARAMETER" does not.)
>
>
>I can provide more debug details if needed
>
>Yes, please add
>#define DEBUG 1
>to the start of "liveMedia/RTSPServer.cpp", recompile and rerun your server, and access it both with a RTP-over-UDP client, and with a RTP-over-TCP client. Please send us the debugging output in each case.
>
>Ross Finlayson
>Live Networks, Inc.
>http://www.live555.com/
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111220/4a3ff721/attachment.html>
>-------------- next part --------------
>An embedded and charset-unspecified text was scrubbed...
>Name: clientdebugout.txt
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111220/4a3ff721/attachment.txt>
>-------------- next part --------------
>An embedded and charset-unspecified text was scrubbed...
>Name: serverdebugout.txt
>URL: <http://lists.live555.com/pipermail/live-devel/attachments/20111220/4a3ff721/attachment-0001.txt>
>
>------------------------------
>
>_______________________________________________
>live-devel mailing list
>live-devel@lists.live555.com
>http://lists.live555.com/mailman/listinfo/live-devel
>
>
>End of live-devel Digest, Vol 98, Issue 25
>******************************************
</PRE></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>