|This is the talk page for discussing improvements to the Real Time Streaming Protocol article.
This is not a forum for general discussion of the article's subject.
RTSP vs. RTP
- Let me answer that question with another question: How different is an airplane from an airport?
- Seriously, you're comparing two things that have totaly different functions. RTSP is your remote, RTP is your TV. —Preceding unsigned comment added by 18.104.22.168 (talk • contribs) 19:07, 15 September 2005
The article had a "Disadvantages", which only listed this: "Because RTSP is a real-time protocol, it is not as practical as http or ftp when trying to download files onto a hard drive for later use."
I removed it, because RTSP is NOT a "real time protocol" in this sense! As I explained above, RTSP is just the "remote". True, it's typically used with RTP to do the "real time streaming" part, but then this disadvantage is more appropriate with RTP.
By the way, RTSP CAN be used to download files using http or ftp. You just ask the server for a describe, and get an SDP file back, which tells the location of a http or ftp server (I'm quite sure SDP allows this). You wouldn't initiate the download using RTSP once you have the SDP. (I'd be surprissed if this is used anywhere, it's quite pointless.)
RtpRtspStack - I cant find it
RtpRtspStack. Google search results just show me same wiki pages as this one. So where do I find more information about RtpRtspStack? Does the author, who put the note to this streaming server in this article, make a typo error? —Preceding unsigned comment added by 22.214.171.124 (talk) 12:32, 27 February 2010 (UTC)
- Given the current page makes no mention of RtpRtspStack (and the only occurrence of 'stack' looks nothing like that), perhaps this comment needs to be deleted. --126.96.36.199 (talk) 01:40, 12 January 2016 (UTC)
FFMpeg has documentation on RTSP
The main article needs to be updated as it indicates that FFmpeg supports RTSP but without documentation.
The documentation can be found in:
- Yes, this seems like dated information, based on your link. Any objections to changing the article? —fudoreaper (talk) 03:52, 11 September 2012 (UTC)
- Okay guys I made the change. I cited the FFmpeg documentation, and removed all the chatter about no references. RTSP was already mentioned in FFmpeg#Protocols, but I did make a formatting change to make a bulletted list rather than prose. Should be good on those two articles for now. —fudoreaper (talk) 02:04, 12 September 2012 (UTC)
Deprecation of UDP transport?
Description of DESCRIBE request asserts that the UDP transport is: "deprecated and very rarely used". As a person, who is actively involved in software development in the area of IP video surveillance and security products, I would like to assure you, that this information is completely incorrect. The most valuable ability of a resource constrained IP CCTV camera/network server is the multi-cast ability of a media stream to multiple destinations. The multi-cast is available only by using the RTP-over-UDP protocol - a one of several RTSP transports. Not only that, but also, the UDP transport is the best way of achieving the maximum throughput of a video/audio stream between a producer and consumer device over an IP network. In fact, the most recent and arguably the most widely accepted standard in the area of IP-based physical security is the ONVIF standard (www.onvif.org), which requires the UDP transport as mandatory for any product claiming compatibility the the ONVIF standard. Please review the topic and correct any unconfirmed claims. — Preceding unsigned comment added by 188.8.131.52 (talk) 08:49, 9 October 2012 (UTC)
- You missed what it talked about. You're referring (explicitly) about RTP-over-UDP, and instead the article referred to RTSP-over-UDP. Which has nothing to do with video quality, throughput or whatever else. Sigh. Time to fix the article again I guess. Flameeyes (talk) 12:57, 4 May 2014 (UTC)
See Wikipedia:Administrators' noticeboard/Incidents#User: 109.77.xx.xx and the indefinite article and Talk:XMPP#Please discuss changes to the indefinite article. Andrewa (talk) 15:13, 24 May 2013 (UTC)
"RTSP using RTP and RTCP allows for the implementation of rate adaptation.[further explanation needed]"
I think that this statement is supposed to mean that packet loss feedback from RTCP reports tell the sender to lower bitrate, but I wouldn't mind some feedback regarding a better explanation and clarification of the sentence as it currently stands at the end of the lead section. korbnep «talk» 20:51, 15 August 2013 (UTC)
RTSP does not mandate use of RTP
It seems to be implied (incorrectly) that RTSP will trigger an RTP stream exclusively. Suggest using the more generic "stream" nomenclature (mirroring RFC 2326) when discussing RTSP unless discussing something specific to RTP in regards to RTSP. — Preceding unsigned comment added by 184.108.40.206 (talk) 18:53, 17 June 2016 (UTC)
The relationship between "RTSP" and "RTP" is confusing in this article (and in general). I'll accept my share of the blame for that.
I'm going to note my conflict-of-interest up front. I was one of the co-authors of RTSP 1.0 and RTSP 2.0, and I was RealNetworks' representative in our discussions with others at the IETF. However, I'm a very experienced Wikipedia editor (editing since 2001) and I haven't really been dealing with RTSP since leaving RealNetworks in 2005 (though Magnus Westerlund generously left several of us in the heading of the publication of RFC 7826 in 2016, even though many of us moved on to other things).
The paragraph about RealNetworks' use of the proprietary "RDT" alternative to RTP should be moved out of the introduction of the article, and into a new "#RTP section. I'm planning on making that change very soon, but I wanted to let people know why I'm making the change. All of the "Real-" this and "Real-" that references in the first paragraph make for a confusing introduction to readers of the article.