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