W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2013

Re: Client/server (non-p2p) video

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Mon, 1 Apr 2013 11:10:09 +1100
Message-ID: <CAHp8n2m9eBWLSKS+iCuT6w_PRiuc8m_2gCtrLQMy-d449hmU2Q@mail.gmail.com>
To: Kevin Day <kevinday@gmail.com>
Cc: cowwoc <cowwoc@bbs.darktech.org>, public-webrtc@w3.org
If your capture does not happen in a Web browser, I would not even use any
WebRTC technology for this, but instead go with an existing open source
streaming server such as icecast or flumotion or VLC streaming server or
GStreamer streaming server or ffserver. All of these can serve video that
the <video> element can receive. I believe most of these will now support
VP8 streaming and also recording for later viewing.

Silvia.

On Mon, Apr 1, 2013 at 9:50 AM, Kevin Day <kevinday@gmail.com> wrote:

> Sorry if I wasn't clear - just to elaborate what we're doing in Flash now
> and what we want to accomplish:
>
> 1) A "broadcaster" sends a video/audio stream to the server. (Publishing)
> 2) The server then does a one-to-many replication of the stream to clients
> who wish to view the stream. They can join/leave at any point. (Subscribing)
> 3) The server also saves a copy of the stream for later viewing.
> (Archiving)
>
> The server does no transcoding of the video/audio stream, the protocol is
> basically designed so that when a new viewer wishes to subscribe to the
> stream, the server can fake a new header, and beginning at the next
> keyframe start sending the stream.
>
> A quick skim of the documentation makes it appear that this is at least
> possible now if the server pretends to be a peer, but I'd need to dig
> deeper to confirm that there's nothing in the stream that would require the
> server to do a lot more work along the way. (i..e if keyframes wren't
> easily detectable without decompressing the stream, or if it would require
> rewriting frame numbers to new clients joining, etc)
>
> Can anyone with experience with the more low levels of how things stand
> now comment on if this would work without a lot of server overhead?
>
> -- Kevin
>
>
>
> On Mar 31, 2013, at 5:41 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>
> wrote:
>
> Indeed, #2 is a different use case, but the question that Kevin asked in
> the email that started this thread seems to be focused on solving #1.
> Silvia.
>
> On Mon, Apr 1, 2013 at 5:23 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>
>>
>>     It sounds like we're talking about two separate use-cases:
>>
>>
>>    1. Broadcasting a one-way video stream to many clients
>>    2. Using gateway as an intermediary for N-party video chat
>>
>>
>>     I am interested in #2 which isn't addressed by your suggestion.
>>
>> Gili
>>
>
Received on Monday, 1 April 2013 00:10:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:33 UTC