Re: Issue 25573 in chromium: Add RTSP support to Chrome
chro...@googlecode.com
Comment #5 on issue 25573 by logan.greenlee: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
I think this would be a valuable addition to Chrome. Please consider adding
streaming
support via RTSP and RTP to chrome. This will truly begin to "solve the
problem" of
including video without plugins.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
chro...@googlecode.com
Comment #8 on issue 25573 by xiechc: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
I also think it's a good idea to support rtsp:///xx.xx.xx.xx/abc.mpg in
chrome
browser, now the html5 video tag can only support http:// ftp:// file://
video
chro...@googlecode.com
Comment #10 on issue 25573 by sche...@chromium.org: Add RTSP support to
Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
We do some cool tricks with HTTP to allow random access seeking via range
requests.
It's not as nifty as RTSP but Chromium rarely ever downloads the whole
video and
relies on "streaming" audio/video over HTTP.
chro...@googlecode.com
Comment #11 on issue 25573 by thadwooster: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Lack of live streaming support is the only thing holding HTML5 from getting
flash out
of the picture. I'd suggest adopting apple's support on the iPhone for .m3u8
playlists with streaming audio and video items. You can do stuff like this:
http://www.ioncannon.net/programming/452/iphone-http-streaming-with-ffmpeg-and-an-open-source-segmenter/
chro...@googlecode.com
Comment #12 on issue 25573 by sche...@chromium.org: Add RTSP support to
Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Oh I've looked at that and would definitely prefer an HTTP solution over
supporting a
whole new protocol.
The unfortunate part is the only client-side implementation is in
QuickTime. I'm not
aware of any open source implementation.. it's not that it's a very
challenging spec
to implement, but more a matter of finding the time :\
chro...@googlecode.com
Comment #13 on issue 25573 by akarpo: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
I'm having some issues however with Chrome (5.0.342.9) using range request
with this html5 video demo
here; http://www.annodex.net/~silvia/itext/mediafrag_multiple_servers.html
With the video under 'URI Fragment Example', when I drag the timeline
scrubber (the progress bar) to a
random position, I'm getting pixelation/no playback even though the timer
continues forward. Firefox 3.6.3
seems to handle it fine though. But the dealbreaker is that Firefox won't
be supporting h.264 anytime
soon/ever.
I've been researching streaming/range requests with html5 video (on Chrome,
or any browser for that matter)
for a few days now and I think I've reached an impasse. I'm not sure if
it's yet possible to have html5 video
(specifically, .mp4's w/h.264 stream; .ogg is meh. I'd much rather use
h.264) with a responsive streaming
experience. I believe the implication of this would be vast - having html5
video (h.264 underneath) in
conjunction with range requests (duration header or hard coded
into .htaccess?) would allow a experience very
similar to that of the Youtube we know today.
Any examples that would demonstrate otherwise? Is 'streaming' that type of
video under html5 possible at this
junction?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
chro...@googlecode.com
Comment #14 on issue 25573 by hc...@google.com: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
One simple way to do HTTP streaming is to serve an endless "file" with
content-length
equals to -1. You can implement this by having a php program that output
a "file" of
say ogg streaming or mp4 formatted stream with no content length. This way
Chrome will
just play whatever it gets, I believe Firefox does the same thing too.
chro...@googlecode.com
Comment #15 on issue 25573 by jeremy.visser: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
With regards to comment #12, RTSP is not only supported in QuickTime. It's
supported
in RealPlayer, as well as GStreamer and VLC. (VLC uses the Live555
libraries, but not
sure about GStreamer.)
That said, while live streaming over RTSP is nifty in theory (RTP/UDP
doesn't require
TCP's ACK packets which are superfluous for a live stream), in practice,
the ubiquity
of NAT causes it to fall back to wrapping RTP inside TCP anyway, which
makes it not
much different from HTTP (as opposed to RTSP supporting a UDP-only RTP
stream if a NAT
were not present).
Not saying that HTTP streaming is better (it is worse, for live streaming
at least —
video on demand is another matter), but more that RTSP is impractical in
today's use
cases.
Not only that, but RTSP doesn't support IPv6. Bit of a waste implementing a
protocol
that we'll be throwing out in a few years anyway.
My $0.02 is that we don't bother with RTSP, and just implement RTP instead,
while
including RTP multicast support. That is supported over IPv6, and is
probably more
useful for the long-term.
chro...@googlecode.com
Comment #18 on issue 25573 by ysjdxcn: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
can u tell me if there is some way that I can play a http streaming on the
chromium?
chro...@googlecode.com
Comment #17 on issue 25573 by ysjdxcn: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
can u tell me if there is sth way that I can play a http streaming on the
chro...@googlecode.com
Comment #19 on issue 25573 by aaronshaf: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Would love to see support for this.
chro...@googlecode.com
Comment #20 on issue 25573 by da...@retroneo.com: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Apple's HTTP Live Streaming is now used by Justin.tv and Ustream. It would
be excellent to see support in
Chrome.
It currently works in Safari on Mac, iPhone and iPad. Broader browser
support would see more sites using it, a
win-win for everyone.
chro...@googlecode.com
Comment #21 on issue 25573 by jeremy.visser: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
HTTP Live Streaming is not the same thing as RTSP.
chro...@googlecode.com
Comment #25 on issue 25573 by chris.sh...@cox.net: Add RTSP support to
Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Can anyone tell me if comment 14 is correct? I am trying to do exactly
that, without success. Should Content-Length be -1, or 0, or absent?
chro...@googlecode.com
Comment #26 on issue 25573 by jeremy.visser: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Content-Length should be absent. I have used an Icecast2 video source as
the src="" parameter of <video>, which works fairly reliably in Firefox,
but is still a little flaky in Chrome. Above all, Firefox is capable of
timeshifting within a live stream, whereas Chrome is not.
chro...@googlecode.com
Comment #28 on issue 25573 by nilsatwlonk: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
This bug is for RTSP support. I have created Issue 54198 - Support HTTP
Live Streaming. (I'm surprised it didn't exist already!)
chro...@googlecode.com
Comment #29 on issue 25573 by adamfisk: Add RTSP support to Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
Regarding comment #14, the ubiquity of NATs doesn't affect this case except
for in particularly locked-down networks, typically within corporate
environments. The reason is the NAT is most often only on the client side,
and most NATs will properly map incoming UDP packets to clients that have
previously sent outgoing ones. As long as the setup for the RTP stream
first sends outgoing UDP packets to the server (typically using RTSP), the
stream should be successfully established. The cases where it can't are
typically networks that do some global UDP blocking, and you don't have
much chance their in any scenario. The cases where NATs really get tricky
are when both sides are NATted, but that's atypical for the browser-based
use case.
chro...@googlecode.com
Comment #30 on issue 25573 by eva_domi...@hotmail.com: Add RTSP support to
Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
I would love this feature was supported
chro...@googlecode.com
Comment #31 on issue 25573 by scherbak...@gmail.com: Add RTSP support to
Chrome
http://code.google.com/p/chromium/issues/detail?id=25573
This will be very nice!