Ross, Thanks for the response. Unfortunately, the environment in which the needed solution needs to be deployed is restricted by a few non-negotiables -- such as the need to store / transcode at the server, and a second client app which cannot be disrupted. So in other words, what is needed is this:
1) Desktop / Notebook with video cam captures H.264 ---> 2) Server needs to receive MP4 over RTP (not LIVE555, this existing server cannot be swapped out) ---> 3) Desktop / Notebook app consumes video in format other than H.264, this app cannot be disrupted. Basically, the scope of what needs to be accomplished is the streaming from 1) to 2). The server in 2) cannot be swapped out for several reasons. I just need to get the video from the source desktop / notebook to the server. Any further recommendations would be appreciated. Thanks, Brad On Jul 9, 2012, at 12:43 AM, Ross Finlayson wrote: >> What is the recommended approach / LIVE555 sample app I should be looking >> app to push MP4/H.264 video to a server via RTP? > > The best approach is to have the server directly integrated with your H.264 > video source (rather than have the H.264 video source 'pushing' to anything). > I.e., don't stream data to a server, and then have the server stream to > clients; instead, just stream data directly to clients (via RTSP/RTP). The > FAQ describes how to modify our RTSP server implementation (e.g., the > "testOnDemandRTSPServer" demo application) to read from a video data source. > > But if you don't want to have clients accessing the data source directly > (usually because you don't want more than one concurrent client doing so), > then you could instead use a 'proxy' server (such as our existing "LIVE555 > Proxy Server") sitting in front of your H.264 server. Then, remote clients > (possibly multiple concurrent clients) would access the proxy server, which > would then act as a (single) client to your H.264 server. > > Note that in each case you're not 'pushing' data at all. Instead, you are > setting up a server for your H.264 video source, and a client (possibly a > proxy) is 'pulling' from it. > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
