[Live-devel] H264 over RTP/RFC 3984

Larry Cui Larry.Cui at zoran.com
Wed Oct 20 22:18:01 PDT 2010


For H264 over RTP, the rtpPayload type must be 31???

________________________________
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Larry Cui
Sent: Wednesday, October 20, 2010 9:52 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] H264 over RTP/RFC 3984

File name created, but it is empty, I have to Ctrl+C to terminate. How terminate it gracefully?

The weird part is stream is sending to the port 169.254.1., but nothing is written to the file,

================================================================
The following message:

Created receiver for "video/H264" subsession (client po
Sending request: SETUP rtsp://169.254.1.5/stream1/track
CSeq: 4
User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010
Transport: RTP/AVP;unicast;client_port=54716-54717


Received 193 new bytes of response data.
Received a complete SETUP response:
RTSP/1.0 200 OK
CSeq: 4
Date: Thu, Jan 01 1970 00:08:37 GMT
Transport:RTP/AVP;unicast;destination=169.254.1.1;sourc
Session: 1


Setup "video/H264" subsession (client ports 54716-54717
Created output file: "XXXvideo-H264-1"
Sending request: PLAY rtsp://169.254.1.5/stream1/ RTSP/
CSeq: 5
User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010
Session: 1
Range: npt=0.000-


Received 176 new bytes of response data.
Received a complete PLAY response:
RTSP/1.0 200 OK
CSeq: 5
Date: Thu, Jan 01 1970 00:08:37 GMT
Range: npt = 0.000 -
Session: 1
RTP-Info: url=rtsp://169.254.1.5/stream1/track1;seq=651


Started playing session
Receiving streamed data...

________________________________
From: live-devel-bounces at ns.live555.com [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Wednesday, October 20, 2010 3:24 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] H264 over RTP/RFC 3984

I'm using RTSP, I did not use sdp file, but through RSTP DESCIBE.

OK, that will help a lot.  Rather than using VLC (at first), try using "openRTSP" <http://www.live555.com/openRTSP/> to read the stream.

Check whether "openRTSP" receives data correctly from your stream (it should write a file called "video-H264-1" or something like that).  Does "openRTSP" write such a file (and is it nonempty)?  If so, then the problem is probably a VLC decoding problem (and therefore, for a VLC mailing list instead).  If, however, "openRTSP" doesn't record a file (or the file is empty), then there's apparently a problem with your RTSP/RTP stream (and therefore, something of interest to us).

--

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/20101021/b2f88424/attachment-0001.html>


More information about the live-devel mailing list