Finally i was able to create /testAACAudioStreamer. thanks to you..
On Fri, Apr 5, 2013 at 2:32 PM, <live-devel-requ...@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-requ...@lists.live555.com > > You can reach the person managing the list at > live-devel-ow...@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: Capturing RTP H.264 stream with testOnDemandRTSPServer > (Ross Finlayson) > 2. how do i modify live555ProxyServer to make it work like > live555MediaServer (=?ISO-8859-1?B?YWxpYXM=?=) > 3. Re: how do i modify live555ProxyServer to make it work like > live555MediaServer (Ross Finlayson) > 4. Re: Not receiving frames from H264 stream (Kerry Loux) > 5. testRTSPClient / H.264 Network Camera Stream > (tboonefis...@clear.net) > 6. Re: live555ProxyServer freezes after upgrading from > 2012.12.24 (Roman Gaufman) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 Apr 2013 08:33:07 -0700 > From: Ross Finlayson <finlay...@live555.com> > To: LIVE555 Streaming Media - development & use > <live-de...@ns.live555.com> > Subject: Re: [Live-devel] Capturing RTP H.264 stream with > testOnDemandRTSPServer > Message-ID: <97361b39-4480-4285-bb77-315e55a02...@live555.com> > Content-Type: text/plain; charset="iso-8859-1" > > > What should I do for other types, i.e. RTP Payload Format for H.264 > Video (format code: 96)? > > I can't answer this unless you tell me specifically what kind of stream > this is - i.e., how it is delivered. > > Is this stream served with a RTSP server of its own? I.e., does it have > its own "rtsp://" URL. If so, you can either access it directly - using > this URL - without using an intermediate server. Or, alternatively, use > the "LIVE555 Proxy Server": http://www.live555.com/proxyServer/ > > 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/20130404/dc976999/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Thu, 4 Apr 2013 18:38:02 +0800 > From: "=?ISO-8859-1?B?YWxpYXM=?=" <842598...@qq.com> > To: "=?ISO-8859-1?B?bGl2ZS1kZXZlbA==?=" <live-de...@ns.live555.com> > Subject: [Live-devel] how do i modify live555ProxyServer to make it > work like live555MediaServer > Message-ID: <tencent_3d8404d336557d732076e...@qq.com> > Content-Type: text/plain; charset="iso-8859-1" > > how do i modify live555ProxyServer so let it work like > live555MediaServer, when i want to get a stream source that > live555ProxyServer hadn't create a link of this source when it started up, > live555ProxyServer can link this new source and brocasts it so i can get it > by another program like "openRtsp". > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.live555.com/pipermail/live-devel/attachments/20130404/ec48adce/attachment-0001.html > > > > ------------------------------ > > Message: 3 > Date: Thu, 4 Apr 2013 18:45:34 -0700 > From: Ross Finlayson <finlay...@live555.com> > To: LIVE555 Streaming Media - development & use > <live-de...@ns.live555.com> > Subject: Re: [Live-devel] how do i modify live555ProxyServer to make > it work like live555MediaServer > Message-ID: <dabd7168-384a-474f-a418-abb5c46a6...@live555.com> > Content-Type: text/plain; charset="iso-8859-1" > > Please DO NOT ask the same question on the mailing list multiple times. > (This is explained in the FAQ!) I already answered your question two days > ago. > > 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/20130404/5e037f8f/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Thu, 4 Apr 2013 12:36:40 -0400 > From: Kerry Loux <lou...@gmail.com> > To: live-de...@ns.live555.com > Subject: Re: [Live-devel] Not receiving frames from H264 stream > Message-ID: > <CANDyi=- > sjpdqfogjqr8lcn67t3e7d62edi0mteybgnmq+ko...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I should have finished working through the advice in the FAQ - openRTSP > successfully streamed from my cameras with the -t option, and setting the > fourth argument of setupSubsession() to true fixed my problems. > > I also found that I did not need to specify the video resolution in order > to get a proper stream, so I would still be interested in a response to my > second question. > > I apologize for not trying the advice in the FAQ before posting :-) > > Thanks, > > Kerry > > > On Thu, Apr 4, 2013 at 10:25 AM, Kerry Loux <lou...@gmail.com> wrote: > > > Hello, > > > > I'm just getting started with Live555, and have a couple questions that I > > haven't been able to resolve by searching. > > > > I have successfully compiled a test application that can connect and > > stream from this url: > > rtsp://184.72.239.149/vod/mp4:BigBuckBunny_175k.mov > > > > I'm using an H264VideoFileSink object and it works just fine. > > > > If I instead use the url for a local IP camera, I find that > > H264VideoFileSink::afterGettingFrame() is not called (and thus my file > has > > zero size). > > > > I can stream this url using VLC without any problems (VLC describes the > > stream as H264 - MPEG AVC (part 10) (h264)). The SDP string for my > camera > > is below: > > > > v=0 > > o=- 2251938208 2251938208 IN IP4 0.0.0.0 > > s=RTSP Session of ZheJiang Dahua Technology CO.,LTD. > > t=0 0 > > a=control:* > > a=range:npt=now- > > a=packetization-supported:DH > > m=video 0 RTP/AVP 96 > > a=control:trackID=0 > > a=framerate:30.000000 > > a=rtpmap:96 H264/90000 > > a=fmtp:96 > > > packetization-mode=1;profile-level-id=4D001F;sprop-parameter-sets=Z00AH9oBQBbpUgAAAwACAADAHjAgAB8/4AAIyf973wvCIRq,aM48gA== > > m=audio 0 RTP/AVP 8 > > a=control:trackID=1 > > a=rtpmap:8 PCMA/8000 > > > > By looking at the SDP string for the working stream, I found that the SDP > > from my camera lacks these lines under m=video...: (I modified these to > > match the size of the image provided by my camera) > > a=cliprect:0,0,1280,720 > > a=framesize:96 720-1280 > > > > I read in the FAQ for openRTSP that the video dimensions are important, > so > > I tried inserting these into the SDP prior to calling > > MediaSession::createNew, and of course it didn't work (this causes my > > application to crash - I knew it was a shot in the dark). > > > > So now my questions: > > 1. Any thoughts on why afterGettingFrame() isn't being called? > > 2. Do I need to worry about the height and width parameters? I'm > guessing > > they're included in maybe the sprop-parameter string, and this doesn't > > apply to H264 streams (or at least this stream) since VLC doesn't need to > > ask me for the resolution. > > > > Thanks, > > > > Kerry > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.live555.com/pipermail/live-devel/attachments/20130404/2c6220e8/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Thu, 4 Apr 2013 14:26:55 -0500 > From: <tboonefis...@clear.net> > To: <live-de...@ns.live555.com> > Subject: [Live-devel] testRTSPClient / H.264 Network Camera Stream > Message-ID: <83B9617CAE5B45F9A1F79D52ECF9F25D@tbxpnotebook> > Content-Type: text/plain; charset="iso-8859-1" > > THANKS!!! For a VERY NICE library. > > I am experimenting with the testRTSPClient app to develop a DirectShow > source filter to connect to a network camera outputting an H.264 > video stream. The app successfully connects to the camera and shows the > following continuous output: > ... > Stream "rtsp://192.168.1.7:65534/videoSub/"; audio/PCMU: Received > 960 bytes. Presentation time: 1365102232.117119 > Stream "rtsp://192.168.1.7:65534/videoSub/"; video/H264: Received > 411 bytes. Presentation time: 1365102232.186298 > Stream "rtsp://192.168.1.7:65534/videoSub/"; audio/PCMU: Received > 960 bytes. Presentation time: 1365102232.226244 > Stream "rtsp://192.168.1.7:65534/videoSub/"; video/H264: Received > 458 bytes. Presentation time: 1365102232.375975 > Stream "rtsp://192.168.1.7:65534/videoSub/"; audio/PCMU: Received > 960 bytes. Presentation time: 1365102232.359869 > Stream "rtsp://192.168.1.7:65534/videoSub/"; audio/PCMU: Received > 960 bytes. Presentation time: 1365102232.465869 > Stream "rtsp://192.168.1.7:65534/videoSub/"; audio/PCMU: Received > 960 bytes. Presentation time: 1365102232.585744 > Stream "rtsp://192.168.1.7:65534/videoSub/"; video/H264: Received > 950 bytes. Presentation time: 1365102232.666086 > ... > > Initially, I am only interested in the video portion of the stream. > Using the library, what is the most efficient way to get access to the > H.264 portion of the stream so that I can copy it downstream > in the FillBuffer(..) method of my source filter? > > I have attempted to browse the code to learn how/where to do this, but it > is not obvious to me;-(( > > I have (+-)intermediate level C++ skills at best, so any thoughts, > suggestions, constructive criticism > are(is) greatly appreciated. > > Thanks again for a VERY nice library. > > Tom Fisher EE > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.live555.com/pipermail/live-devel/attachments/20130404/fdf37292/attachment-0001.html > > > > ------------------------------ > > Message: 6 > Date: Fri, 5 Apr 2013 09:57:57 +0100 > From: Roman Gaufman <hacke...@gmail.com> > To: "LIVE555 Streaming Media - development & use" > <live-de...@ns.live555.com> > Subject: Re: [Live-devel] live555ProxyServer freezes after upgrading > from 2012.12.24 > Message-ID: > < > caas9bzp5cbg8usztkgbgkj3q5_vuhtdmq9o-fbxyyzmbfo8...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On 4 April 2013 10:16, Ross Finlayson <finlay...@live555.com> wrote: > > > I find this very difficult to believe - especially considering that > nobody > > else has reported this problem. > > > > I'm not sure what to say but GET_PARAMETER is causing problems with almost > all cameras I have here to test (excluding a Chinese no brand one > ironically). I've made one more stream publicly available, this time from > Axis - arguably the leaders in the market. > > The stream doesn't freeze as quickly as the Sony stream, but does freeze > after a few minutes or so: > > rtsp://viewer:password@86.162.35.136/axis-media/media.amp > > Instead of freezing after the first GET_PARAMETER like Sony, it seems to do > this after a few GET_PARAMETER requests around the 2 and a half minute > mark: > > Sending request: GET_PARAMETER > rtsp://86.162.35.136/axis-media/media.amp/RTSP/1.0 > CSeq: 11 > Authorization: Digest username="viewer", realm="AXIS_00408CC61141", > nonce="0003b3acY558862c87aa9f41d1bb2e0ce73a2ab572b750", uri="rtsp:// > 86.162.35.136/axis-media/media.amp/", > response="dba33206b01ca464ce5c693aeb55c6c1" > User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.01) > Session: 0E2C46CE > Content-Length: 2 > > > > Received 266 new bytes of response data. > Received a complete GET_PARAMETER response: > RTSP/1.0 401 Unauthorized > CSeq: 11 > Session: 0E2C46CE > WWW-Authenticate: Digest realm="AXIS_00408CC61141", > nonce="0003b442Y74661773895f565b0a7480ea3bff2193120c0", stale=TRUE > WWW-Authenticate: Basic realm="AXIS_00408CC61141" > Date: Fri, 05 Apr 2013 08:41:21 GMT > > > ProxyServerMediaSubsession["H264"]::closeStreamSource() > > > > > > Nonetheless, because you provided definitive evidence of at least one > > buggy server, I've now installed a new version (2013.04.04) of the code > > that should avoid crashing this server. The proxy code will now always > > sends "OPTIONS" - rather than "GET_PARAMETER" - as the 'liveness check' > > command, unless the server explicitly indicated (by a "Session:" header > > "timeout" parameter in the "SETUP" response) that it wants to receive > > periodic in-session "GET_PARAMETER" commands instead. (Some servers have > > another bug whereby they don't use RTCP "RR" packets - from the client > (or > > proxy) - to indicate client (or proxy) liveness.) > > > > I've compiled the latest version and unfortunately I'm seeing the exact > same output as above, after about 2 and a half minutes of streaming, I see > this: > > Sending request: GET_PARAMETER > rtsp://86.162.35.136/axis-media/media.amp/RTSP/1.0 > CSeq: 11 > Authorization: Digest username="viewer", realm="AXIS_00408CC61141", > nonce="0003b564Y2228267e47cfeaebe489a7adc01614e45c593", uri="rtsp:// > 86.162.35.136/axis-media/media.amp/", > response="68581b599686f52057b105915c628adf" > User-Agent: ProxyRTSPClient (LIVE555 Streaming Media v2013.04.05) > Session: F1965CF1 > Content-Length: 2 > > > > Received 266 new bytes of response data. > Received a complete GET_PARAMETER response: > RTSP/1.0 401 Unauthorized > CSeq: 11 > Session: F1965CF1 > WWW-Authenticate: Digest realm="AXIS_00408CC61141", > nonce="0003b5faY417690407232ac53139bf9e460a425d4722ba", stale=TRUE > WWW-Authenticate: Basic realm="AXIS_00408CC61141" > Date: Fri, 05 Apr 2013 08:48:42 GMT > > Yes, but I still find it strange that nobody else has reported this. (It > > would be nice to get independent confirmation of this from a professional > > user, and also have this bug reported to the camera manufacturer(s)!) > > > > > I noticed this problem back in January, but just used the 2012.12.24 > version assuming some kind of PEBKAC since I have a couple of patches I > used (like allowing to specify a port from the command line), but then > reproduced it with vanilla. I am also very surprised nobody reported this. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.live555.com/pipermail/live-devel/attachments/20130405/f0be48e6/attachment.html > > > > ------------------------------ > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel > > > End of live-devel Digest, Vol 114, Issue 8 > ****************************************** >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
