Re: [Live-devel] H264 over RTP/RFC 3984

For H264 over RTP, the rtpPayload type must be 31??? No! For H.264 over RTP, the payload format code must be dynamic. (The static code 31 is reserved for H.261.) (If you'd used our code for your server implementation, then you would have gotten this automatically!) -- Ross Finlayson Live

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? On Unix systems, you can kill the process with -HUP. However, there's no good way to do this in Windoze. It doesn't really matter, though; if the output file is empty, then that's significant. I

Re: [Live-devel] H264 over RTP/RFC 3984

For H264 over RTP, the rtpPayload type must be 31??? From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Larry Cui Sent: Wednesday, October 20, 2010 9:52 PM To: LIVE555 Streaming Media - development & use Subject: Re: [L

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 receiv

Re: [Live-devel] The first H.264 SPS packet gets skipped

I sub-classed H264VideoStreamFramer from FramedFilter class. I implemented currentNALUnitEndsAccessUnit() and isH264VideoStreamFramer() and returned TRUE for both since my encoder always provides me with a complete NAL. No, that's not what "currentNALUnitEndsAccessUnit()" is supposed to do (o

Re: [Live-devel] H264 over RTP/RFC 3984

I first send SDP information in RTSP only, but it does not work under VLC or Quicktime. Then I try to send SPS and PPS often. From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Jeremy Noring Sent: Wednesday, October 20

Re: [Live-devel] H264 over RTP/RFC 3984

Is there any Windows version openRTSP exe file? Or I have to find to way to compile the source code under Windows? From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Wednesday, October 20, 2010 3:2

Re: [Live-devel] H264 over RTP/RFC 3984

On Wed, Oct 20, 2010 at 3:12 PM, Larry Cui wrote: > I’m using RTSP, I did not use sdp file, but through RSTP DESCIBE. If the > PPS is a little bit different from SDP in RTSP, is it a problem? I really > could not find other issue. > > When I open VLC, I only input rtsp://169.254.1.5, nothing el

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" to read the stream. Check whether "openRTSP" receives data correctly from your stream (it should write a fil

Re: [Live-devel] H264 over RTP/RFC 3984

I'm using RTSP, I did not use sdp file, but through RSTP DESCIBE. If the PPS is a little bit different from SDP in RTSP, is it a problem? I really could not find other issue. When I open VLC, I only input rtsp://169.254.1.5, nothing else. Is this a problem? I'm reading the source code for VLC,

Re: [Live-devel] H264 over RTP/RFC 3984

My stream complies with RFC 3984, and I insert SPS and PPS at the front of every I frame. The problem is VLC always gives the message: "live555 no data received with 10s" than rtsp tear down . I'm pretty sure the rtp stream is there and rtp port number is right. Why VLC cannot receive the stre

Re: [Live-devel] H264 over RTP/RFC 3984

Thanks for your quick reply. I know this is a VLC related problem. But if anybody can give me a clue, so I can finish my project, that's great! My stream complies with RFC 3984, and I insert SPS and PPS at the front of every I frame. The problem is VLC always gives the message: "live555 no data

Re: [Live-devel] H264 over RTP/RFC 3984

Right now, I'm developing h264 over rtp streaming. My question is the current version of live555 needs SEI packet of h264 or just video data packet? That is, if I packet the H264 video data according RFC 3984, no SEI data, that's OK for live555 parsing? Yes, our implementation of H.264/RTP rec

[Live-devel] H264 over RTP/RFC 3984

Right now, I'm developing h264 over rtp streaming. My question is the current version of live555 needs SEI packet of h264 or just video data packet? That is, if I packet the H264 video data according RFC 3984, no SEI data, that's OK for live555 parsing? But VLC player cannot recognize the stream,

Re: [Live-devel] RTSP-over-HTTP question

I have problems connecting to RTSP server with HTTP tunneling. My server closes connection immediately after the first HTTP GET request fails with `HTTP/1.0 401 Unauthorized` error, so there is no second chance to send authentication credentials in the next requests. I presume that you are ta

[Live-devel] RTSP-over-HTTP question

Hi, I have problems connecting to RTSP server with HTTP tunneling. My server closes connection immediately after the first HTTP GET request fails with `HTTP/1.0 401 Unauthorized` error, so there is no second chance to send authentication credentials in the next requests. I have a question: Is

Re: [Live-devel] RTSP-over-HTTP and inconsistent SETUP requests.

Il 20/10/2010 10:34, Ross Finlayson ha scritto: OK, I've now installed a new version (2010.10.20) of the software that makes the "RTSP-over-HTTP tunneling" implementation more robust to the client bugs that you noted. Please try it out and let us know if there are any problems. Works like a

Re: [Live-devel] RTSP-over-HTTP and inconsistent SETUP requests.

OK, I've now installed a new version (2010.10.20) of the software that makes the "RTSP-over-HTTP tunneling" implementation more robust to the client bugs that you noted. Please try it out and let us know if there are any problems. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/

Re: [Live-devel] RTSP-over-HTTP and inconsistent SETUP requests.

Il 20/10/2010 03:40, Ross Finlayson ha scritto: (As there's no RFC on RTSP over HTTP, as far as I know, I use this document as a reference: http://developer.apple.com/quicktime/icefloe/dispatch028.html FYI, another document - with a little more detail - is here: http://images.apple.com/br/qu