[Live-devel] The question on how to handle the incoming H.264 RTP data of live555 server

[Lan Zang]

Ross,

Thanks for your reply. I did not read the "live555 proxy server" yet. But from the name I guess this server will work as a proxy. But I am expecting to do a little different. I'd like the live555 will support the source to publish the video directly. I suppose the supporting of "RECORD" and "ANNOUNCE" in RTSP shall be added. I wander if there is any special consideration that the live555 does not support them.

And for the H264VideoStreamDiscreteFramer thing, you are right. I changed to this class, and now the errors are eliminated.

Regards,
Lan Zang(Sander)


________________________________
 From: Ross Finlayson <finlayson at live555.com>
To: LIVE555 Streaming Media - development & use <live-devel at ns.live555.com> 
Sent: Saturday, April 28, 2012 5:32 PM
Subject: Re: [Live-devel] The question on how to handle the incoming H.264 RTP data of live555 server
 

I am new to this live555 media server. I am trying to make a server running on ubuntu that can perform the following task:
>It gets h.264 video data over RTP from others (e.g. ffmpeg), then it will broadcast the video to other viewers( e.g. vlc player) via rtsp protocol.
>

If your H.264 video source is accessible via RTSP, then you could use our new "LIVE555 Proxy Server" application, which already does all of this:http://www.live555.com/proxyServer/



After reading the codes of live555MediaServer.cpp and testOnDemandRTSPServer.cpp and some other files plus a little guessing, I think I shall prepare a class that will treat h.264 RTP data derived from OnDemandServerMediaSubsession. I call it H264VideoUDPServerMediaSubsession.
>
> In this class, function createNewStreamSource() will create an instance of class H264VideoStreamFramer
Almost.  Because the data source (a "H264VideoRTPSource") delivers discrete H.264 NAL units (i.e., one at a time), rather than a byte stream, you must use a "H264VideoStreamDiscreteFramer", not a "H264VideoStreamFramer".

Everything else looks correct, as far as I can tell.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/ 

_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120428/3a6d9e9b/attachment.html>