I use live555 as an RTSP server for some H264 media. I would like to stream them in flashplayer with Wowza.
It’s work fine for an audio only aac file but not for an H264 movie. But I can play h264 videos with VLC or openRTSP from my live555 server.
I’ve look at Wowza logs but everything seems fine :
INFO server comment - sortPackets[1]: sortBufferSize:500
INFO stream create - -
INFO server comment - MediaStreamMediaCasterPlay: startPlay
INFO server comment - RTPMediaCaster.create
INFO server comment - RTPMediaCaster.init
INFO server comment - RTPMediaCaster.Reconnector: start
INFO server comment - RTPSessionTracker.add[rtsp://ip_of_my_rtsp_server:5542/video.264]: 1
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPData: sessionId:4 sessionTimeout:0
INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP/RTP re-streaming. Success, received SDP data.
WARN server comment - RTPTrack.getCodecConfig(video): Missing NAL PPS(8)
INFO server comment - sortPackets[1]: sortBufferSize:500
INFO stream create - -
INFO stream create - -
INFO stream publish rtsp://ip_of_my_rtsp_server:5542/video.264 -
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionStart: PLAY: rtsp://ip_of_my_rtsp_server:5542/video.264
INFO server comment - RTPMediaCaster.Reconnector: stop
INFO server comment - senderReport[RTP-Info]: track1
INFO server comment - RTCPHandler.sendFirstRTCPRR[0,1,null]
INFO server comment - firstPacket: TCP:$0
INFO server comment - firstPacket: TCP:$1
But there’s no video in my flashplayer (jw).
And after few seconds wowza’s logs print this :
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose
INFO server comment - RTPSessionTracker.remove[rtsp://ftp.camtrace.com:5542/video.264]: 0:true
Turn on debug logging (edit conf/log4j.properties and change the log level on the first line from INFO to DEBUG). Give it a try with both forceInterleave true and false. Send the conf and logs folder to support@wowza.com.
It looks like the RTP packets do not conform to the specification. We are looking for a specific flag that tells us that a packet is the last packet of a group of packets that make up either a H.264 or AAC frame. We are not getting this flag.
Are there any error messages in the logs files. Also, try following these instructions to turn on a jitter buffer and packet loss logging. Almost looks like packet loss:
If you are re-streaming RTSP then you must use the rtp-live stream type. Are you sure the camera is sending RTP. Also it could be a packetization issue. I know some of the camera vendors use their own RTP packetization scheme (Sony being one of them).
I still don’t understand why every player can manage this stream, except wowza
Just to note: Wowza Media Server isn’t a player. The players that are included with Wowza Media Server are examples of client players, but you can use other players like JW Player or Flowplayer with Wowza Media Server
On your player test page, the IP camera stream is working for me. The DV camera is not, but you have it connecting to the same “rtplive” app, with (I presume) StreamType “rtp-live”. Try connecting the DV camera to app with StreamType “live” or “live-lowlatency”.
I’ve tried to add the SPS and PPS info in each keay frame, using ffmpeg and/or tsmuxer but when I play it with simplevideostreaming or jw player I only got this “crap” :=( : http://img19.imageshack.us/img19/2686/wowzabug.png
I still don’t understand why every player can manage this stream, except wowza
As I said in my email (and as you’ve told me) , because of my goal is to use a live stream, I must include SPS/PPS info in each keyframes (and I’m trying this with x264/ffmpeg).
If I am not mistaken, I can not use the “sprop-parameter-sets” because I do not know in advance the PPS and SPS nal units for the stream.
Just to note: Wowza Media Server isn’t a player. The players that are included with Wowza Media Server are examples of client players, but you can use other players like JW Player or Flowplayer with Wowza Media Server
Richard
Yes.
From the point of view of my RTSP server, wowza act like a client.
You don’t know rapidshare? Hum just click the link, click “download as free” or something like that, wait few seconds and you get the file. Or told me where I can upload my log file.
As I said I’ve got troubles with DV camera. When I tried to set StreamType to “live” or “live-lowlatency” Wowza can’t found the alias used in StreamNameAliasMap.txt and I don’t know how to fix this issue.
Have you noticed that I use an RTSP server on the computer where the DV cam is plugged? And that I use it for sharing my stream to Wowza?
What makes me think rtp-live is the best choice for what I want to do.
If you are re-streaming RTSP then you must use the rtp-live stream type. Are you sure the camera is sending RTP. Also it could be a packetization issue. I know some of the camera vendors use their own RTP packetization scheme (Sony being one of them).
Charlie
The DV camera is not an IP camera! My DV camera is just plugged to a computer (in firewire), running FreeBSD and Live555 for sharing stream in RTSP!
I want to play it into a flashplayer through Wowza.
But Wowza can’t manage correctly the stream and the flashplayer display only green squares. Wowza just suck at getting the stream from live555.
I am also using Live555 indirectly through our RTSP server mode on our hardware encoder (AVN420). Our RTSP server code was provided by an outside party and it is completely built on top of the open source Live555 libs.
I too am having trouble getting my encoder to play nice with Wowza in RTSP mode. In Transport Stream mode on the other hand, they behave like old pals and I can convert to rtmp and even send directly to my iphone / ipod touch.
What seems weird is that I am using the exact same underlying Elementary streams (h.264 baseline1.3 and AAC-LC) in the two different modes, but it only seems to work with my homemade TS multiplex transport, and not the externally provided RTSP/RTP transport. Based on that I think there may very well be a problem in the Live555 libs, or at least my current implementation there of…
I would really like to try and figure out where the problem is, and again I don’t actually think it is a problem on the Wowza side, but I do think you guys might be able to help me turn on some debug information that might help point me in the right direction.
I have successfully connected via RTSP using QT Broadcaster in the live example (auto announce mode) as well as with another manufacturers hw encoder using the .sdp retrieval example method. I have attempted using my encoder in RTSP mode in all 3 ways that I have found to try:
Automatic Unicast: (works with my enc and DSS, but not Wowza)
SDP file retrieval: (works with my enc and VLC/QT but not Wowza)
rtsp connect and re-stream: (works with my enc and DSS, but not Wowza)
In addition based on what I read above, I can say that (a) my stream does have the SPS and PPS NALs included in the sdp and (b) when I checked in Wireshark my stream shows that my end of access unit RTP markers are being set properly…
any information that anyone could provide would be very much appreciated.
