<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>A big blunder indeed. HTML5 video adds a lot of restrictions. The
only two options I found to work are:</p>
<p>1) Demux the RTSP stream, re-mux it into fragmented MP4, send
this over HTTP (using EOF encoding, that is: no keepalive, no
content-length, "message" ends when the server closes the socket);
may also require transcoding to make sure the right audio and
video codecs are used, and can be tricky with one-to-many
streaming<br>
</p>
<p>2) Similar to (1), but transmit using HLS or DASH instead - these
may be more useful for one-to-many streaming (since chunks can be
shared between connections), but they are considerably more
complex, and can cause problems if the stream isn't always there
(for example, if an HLS stream starts on-demand, when the first
client connects, then in the beginning, there is no .m3u8 file
present yet)</p>
<p>Without HTML5, it becomes considerably easier, yes. Although I
prefer Matroska over MPEGTS.<br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-01-20 09:54, Dimitrios Katsaros
wrote:<br>
</div>
<blockquote
cite="mid:CAHpJRnxsbEsi7ENWgWuXSQUHMa+di93jV4Z1frMzB-oq5CORhw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>The video tag in html is a bit problematic. The idea behind
it was to be able to play any video in a browser but it
requires that the browser implement the logic for handing the
media types, which is a big blunder. Here is a table with a
few media types:<br>
<br>
<a moz-do-not-send="true"
href="https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats">https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats</a><br>
<br>
From what I see you are trying to reencode h264. Is there any
reason why h264parse is not enough? h264 is a video
compression standard but it does not provide any information
on duration, metadata about the stream etc. You need to put
the video in a container format that will handle all that for
you. If you intend on streaming to a media player you can use
tsmux to get an mpegts stream. However, you will need a
compatible player on the client side like the vlc embedded
player. That has it's own problem in that you need to assume
that the client has vlc or any other player installed. One
other alternative is to go for hls or mpeg dash. That will
require that you create a fragmented stream, create the media
descriptor file for the fragmented stream and then provide it
via a http server. The nice thing about this approach is that
there are javascript based players you can embed in your
webpage. But it requires a lot of work to implement all the
requirements. <br>
<br>
</div>
<div>I am sure people can suggest more alternatives, but these
are the ones I have played around with. If you want something
simple I would try the mpegts stream to vlc. you will have a
client to start with and can then work towarsd embedding it
into your site. <br>
<br>
</div>
<div>Dimitrios<br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jan 18, 2017 at 9:07 PM,
ITwrx.org <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:info@itwrx.org" target="_blank">info@itwrx.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
<br>
i'm trying to use gstreamer to get an rtsp stream from an ip
cam into my<br>
browser(html video tag). I'm currently trying to use<br>
<br>
"gst-launch-1.0 rtspsrc location=rtsp://<a
moz-do-not-send="true"
href="http://user:password@192.168.1.5:554"
rel="noreferrer" target="_blank">user:password@<wbr>192.168.1.5:554</a>
!<br>
rtph264depay ! h264parse ! decodebin ! x264enc !
tcpserversink<br>
host=127.0.0.1 port=8080"<br>
<br>
which seems to be sending something, but firefox won't
display the video<br>
and reports that it has mime type "text/plain".<br>
<br>
Could anyone recommend the proper command for accomplishing
this?<br>
<br>
thanks<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Information Technology Works<br>
<a moz-do-not-send="true" href="https://ITwrx.org"
rel="noreferrer" target="_blank">https://ITwrx.org</a><br>
@ITwrxorg<br>
<br>
______________________________<wbr>_________________<br>
gstreamer-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.<wbr>freedesktop.org</a><br>
<a moz-do-not-send="true"
href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/gstreamer-<wbr>devel</a><br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>