RTSP is a protocol, so is HTTP, you need a plugin. Browsers natively handle HTTP but they do not yet directly support RTSP, it requires a plug-in. Players like VLC, Quicktime and Flash can handle RTSP and usually have a plugin avail, indeed flash is the most common defacto plugin out there.
I personally am on a team responsible for our own plugin and it uses livee555 as the client together with libavcodec for the decoding part. 1)Running on 64 bit windows: most apps running on windows 64 bit are still running 32bit. Windows provided a set of emulation libraries called "Windows on Windows" that seemlessly handles running 32 bit code on 64 bit windows. This still is a big step forward because each 32 bit app runs with an up to 2Gig memory space so it allows you to use all that extra memory (my boxes have 4G - 12G). You can aso compile for 64 bit, but in for a penny, in for a pound; check and make sure the browser or rest of your app is also compiled for 64bit! 2)True RTSP: I connect directly to various RTSP sources directly from the browser. From commercial restreamers to embedded devices. I have seen at least 10 differnt brands work fine and 2 that will not connect for a yet unknown reason, but I need to update. 3) see description in 1 of who's responsibility for what protocols and how it is used. RTSP will be listening by default on port 554, apache by default is port 80. These are defined as default by the protocol and apache's job ends at telling other software the address and specs of the connection string. Remember, data obtained from RTSP is encoded (compressed) the other main part of any client is to decode it. Some browser can handle decodeing directly if you use HTTP Live Streaming. Which apache can serve out and live555 can do part of the transformation, but it is a missnomer that it is live, it has a built in delay. WIkipedia is your friend on all this. ________________________________ From: live-devel-boun...@ns.live555.com [live-devel-boun...@ns.live555.com] on behalf of WADE POLK [gunslin...@gmail.com] Sent: Tuesday, August 21, 2012 3:58 PM To: live-de...@ns.live555.com Subject: [Live-devel] Fwd: live555 on demand, apache and win 7 64bit ---------- Forwarded message ---------- From: WADE POLK <gunslin...@gmail.com<mailto:gunslin...@gmail.com>> Date: Tue, Aug 21, 2012 at 4:45 PM Subject: live555 on demand, apache and win 7 64bit To: live-devel@lists.live555.com<mailto:live-devel@lists.live555.com> Hi all, I have good web page setup, the only thing lacking is the streaming server and I've been scouring the internet for many weeks studying and looking for the best possible solution. I'm using the latest version of WAMP server on win 7 64 bit. A few questions: 1. is there a way to get live555 to work in 64 bit windows? 2. Can it handle "true" rtsp on demand streaming effectively? I think it can from what I am reading in the documentation. 3. Assuming I get live555 up and running on the same server that runs apache, how the heck do I get my webpage to communicate with the streaming server? Its a console application right? There needs to be a way to integrate on demand streaming with my existing page. What gets played to who will be dictated by what hyperlinks my users press on the webpage, some hyper links need to open streams of my radio station, others need to open streams of a users playlist, and some of just a single file... who has access to what is dictated by my sql database. thanks
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
