Re: [rtcweb] Screen sharing

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Fri, 02 December 2011 13:49 UTC

Return-Path: <stefan.lk.hakansson@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86F7C21F9338 for <rtcweb@ietfa.amsl.com>; Fri, 2 Dec 2011 05:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5TIMc3pY5Ha for <rtcweb@ietfa.amsl.com>; Fri, 2 Dec 2011 05:49:48 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 71ACE21F931D for <rtcweb@ietf.org>; Fri, 2 Dec 2011 05:49:48 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-fd-4ed8d77b84c3
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 64.A1.09514.B77D8DE4; Fri, 2 Dec 2011 14:49:47 +0100 (CET)
Received: from [150.132.142.245] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.3.137.0; Fri, 2 Dec 2011 14:49:47 +0100
Message-ID: <4ED8D77A.30209@ericsson.com>
Date: Fri, 02 Dec 2011 14:49:46 +0100
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111110 Thunderbird/8.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CAFD7886.20DF3%henry.sinnreich@gmail.com>
In-Reply-To: <CAFD7886.20DF3%henry.sinnreich@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [rtcweb] Screen sharing
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2011 13:49:52 -0000

On 12/02/2011 01:31 AM, Henry Sinnreich wrote:
> Can remote meeting attendees read the print on say a legal document
> under discussion?
All I can say is that in the little testing we did it looks quite OK. If 
you want to you can test our using our lib; depending on what GStreamer 
plug-ins you add Theora (no plug-in added), VP8 or H.264 would be used.

But probably Aron's/Justin's experiences are more valid as those are 
based on live services if I understand correctly.

My conclusion is that using video for screen sharing can be a quick way 
forward.
>
> If yes for commercial grade quality (I still have doubts), how is the
> codec tweaking enabled via the API?
I proposed that a "screen" option could be added to the API (now "audio" 
and "video" is there). If "screen" is selected, the codec parameters 
could be tweaked accordingly (we have no tweaking in our current lib though)
>
> Thanks, Henry
>
>
> On 12/1/11 5:05 PM, "Aron Rosenberg" <arosenberg@logitech.com> wrote:
>
>     Screen sharing works great over H.264 or VP8 for us. You have to
>     tweak the codec encoding parameters and FPS a bit, but you get great
>     quality even on text.
>
>     Aron Rosenberg
>     LifeSize, a division of Logitech
>
>
>
>     On Thu, Dec 1, 2011 at 11:18 AM, Henry Sinnreich
>     <henry.sinnreich@gmail.com> wrote:
>
>         Hi Stefan,
>
>         Video sucks for screen sharing, displaying documents or even
>         plain bullet
>         slides.
>         Displaying the screen and documents is in a completely other
>         league IMO.
>
>         Thanks, Henry
>
>
>         On 12/1/11 9:19 AM, "Stefan Håkansson LK"
>         <stefan.lk.hakansson@ericsson.com>
>         wrote:
>
>         >  Related to use-case 4.2.7 "Simple Video Communication Service with
>         >  sharing"
>         >
>         (<http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements
>         >  /?include_text=1>)
>         >  we had a student experimenting a bit.
>         >
>         >  Essentially, the screen was treated as another video source
>         (just as a
>         >  camera), and was transmitted to the other end as a MediaStream
>         over a
>         >  PeerConnection.
>         >
>         >  The implementation of getUserMedia allowed the screen to be
>         selected as
>         >  a video source.
>         >
>         >  Perhaps this could be a way forward for meeting this use-case? And
>         >  perhaps "screen" should be defined as a valid options argument to
>         >  getUserMedia?
>         >
>         >  (there is some more info about what the student did at
>         >
>         <https://labs.ericsson.com/developer-community/blog/screen-sharing>
>         <https://labs.ericsson.com/developer-community/blog/screen-sharing>>)
>         >
>         >  Stefan
>         >  _______________________________________________
>         >  rtcweb mailing list
>         >  rtcweb@ietf.org
>         >  https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>         _______________________________________________
>         rtcweb mailing list
>         rtcweb@ietf.org
>         https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>     ------------------------------------------------------------------------
>     _______________________________________________
>     rtcweb mailing list
>     rtcweb@ietf.org
>     https://www.ietf.org/mailman/listinfo/rtcweb
>