Re: [Tools-discuss] Live coding with Meetecho

Lorenzo Miniero <lorenzo@meetecho.com> Wed, 20 March 2024 01:44 UTC

Return-Path: <lorenzo@meetecho.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE52C1654FE for <tools-discuss@ietfa.amsl.com>; Tue, 19 Mar 2024 18:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aruba.it
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmtbKOPfnNaE for <tools-discuss@ietfa.amsl.com>; Tue, 19 Mar 2024 18:44:52 -0700 (PDT)
Received: from smtpcmd01-sus.aruba.it (smtpcmd01-sus.aruba.it [62.149.158.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63659C15154E for <tools-discuss@ietf.org>; Tue, 19 Mar 2024 18:44:51 -0700 (PDT)
Received: from lminiero ([31.130.230.86]) by Aruba Outgoing Smtp with ESMTPSA id ml0XrqXNpY4MEml0ZrYDXe; Wed, 20 Mar 2024 02:44:49 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aruba.it; s=a1; t=1710899089; bh=RIhL3qJnUoDtXZZ45K3Dx1w2a9EbTyyknzEncg6/sB0=; h=Date:From:To:Subject:MIME-Version:Content-Type; b=LRmRQtNo/W+SqVK3HIZeJuGLIe9Dvw2UhA8STfPfMFRf7r9x1fK6qkay3kCEy7PKN /cxoyrEEYRlay2IMw6aao2yqLBjSEaQUi6NLJ3WQh+Vf+e8fnDyGIZwjRGg1ZlJTeY BifWhI9n/RRvn3UnjX/pRu3rAlGcm95Oo5n8sxoyBEyBGUse86ZAb54BV9gWgbeuWr lpt5PGuNplcBkLO0f4OxZ5dpcKHQCrRVdC7LIS+fGVCrpkODUA3WrmrMBE6lHUB4vm o88tHanPWRGnn/3FFlbjw7mZErIg9+xjMU1cAk0xCJ+HFfpey/uwqGOXSF7xRvzABT szO04FO8xZDkA==
Date: Wed, 20 Mar 2024 02:44:39 +0100
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: Meetecho IETF support <ietf@meetecho.com>, tools-discuss@ietf.org
Message-ID: <20240320024439.6c398fbd@lminiero>
In-Reply-To: <9192f666-5e03-4b16-974a-34a300deb161@petit-huguenin.org>
References: <0b8bef83-fbcd-4f20-9824-1f50d5b78102@petit-huguenin.org> <917a4618-97e0-430c-acac-12821853a1ae@meetecho.com> <9192f666-5e03-4b16-974a-34a300deb161@petit-huguenin.org>
Organization: Meetecho
X-Mailer: Claws Mail 4.2.0 (GTK 3.24.41; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-CMAE-Envelope: MS4xfCPEfxL2l6Cq2l5L+calVqIz5gs+QdOunpnaWxqglGqmt9Nh90z7fbeeKndjXMvYpGRDp2POFpmTAstNdV6lQ3j2oY370iQd3PN3sD3k31g740Vw/Tha uO3ydRUf7oBNiT0SDoISLmpoHq5zeyXMSqrMGog2kbHBFgaj1YxaQqwccdB9uIpuFO9hy8eQ4ZqbtGxrhMh6SuESVsVT1hYZrV4bSKiYqdfjtDTze72fCyuD tyTLQgu08vjlT5E+XQmegA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/sILQLYucdjOqjJJcPpTyHKIaFNk>
Subject: Re: [Tools-discuss] Live coding with Meetecho
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 01:44:57 -0000

On Mon, 18 Mar 2024 18:15:48 -0700
Marc Petit-Huguenin <marc@petit-huguenin.org> wrote:

> On 3/18/24 5:38 PM, Meetecho IETF support wrote:
> > Hi Marc,
> > 
> > can you please elaborate a bit on the scenario? How is it different
> > from screen sharing (which of course is doable with Meetecho)?  
> 
> In my case, the live coding is done on a separate computer (for
> security reasons, the computer holding my IP has no camera or
> microphone connected).  That computer HDMI output feeds into a
> machine running OBS, which itself has an HDMI output that feeds into
> the machine that is running all my video clients (Zoom, Webex,
> Meetecho...) through an HDMI adapter.  That means that the live code
> is accessible only through this HDMI connection, so I can control
> precisely what I share publicly.  I remember doing a test with
> Meetecho at some point exchanging my camera with that HDMI source,
> but the result was not great because of the reason explained below.
> Zoom (and apparently WebEx now) have this great feature where it is
> possible to share a second camera, which is exactly what I use when
> doing demos of my stuff (the OBS machine is also connected to a
> document camera, a whiteboard camera, and a mobile camera, all which
> expand the possibilities when doing a demo remotely).
> 


Hi Marc,

if this HDMI adapter shows up as a video capture device (or you use OBS
to expose a virtual camera), it should indeed show up as an alternative
way to share your webcam when listing capture devices in the preflight.
But you're right that this would prevent you from sharing your normal
webcam at the same time, since we currently only expose ways to share a
single webcam stream at a time.

A simple approach may be using OBS for the job: you configure a scene
where the background is your HDMI capture, and you add your webcam as a
picture-in-picture on top of that, so that both appear in the video
that is exposed via the OBS virtual camera (and shared in Meetecho).

That said, I believe there's a different approach you could try that
might be better. You could open the captured HDMI stream in a viewer
(which could be OBS itself or something else) in a way that displays the
content full screen (maybe on a second screen, or, as I sometimes do, a
virtual second screen using a null-HDMI dongle) and then from Meetecho
use the screensharing functionality to share it with the other
participants. This way, you'd be able to share both webcam and live
coding as separate streams. This would also have the advantage of
having the live coding video stream being automatically recognized as a
screen, which would render it properly in recordings too.

Lorenzo


> > 
> > Thanks,
> > Alex
> > 
> > Il 18/03/24 16:15, Marc Petit-Huguenin ha scritto:  
> >> Hello,
> >>
> >> I read the Meetecho documentation, but it seems that there is no
> >> possibility of using it for live coding -- which is basically
> >> having the video coming from a participant set to a fixed size, so
> >> the live coding window is always completely visible to all
> >> participants.  Here I am assuming that the live coder has a way to
> >> set up a virtual camera that Meetecho can use.
> >>
> >> Did I miss something?  If not, is there a plan to get that one
> >> day?  Meanwhile, any other solution to live code?
> >>
> >> Thanks.
> >>
> >>
> >> ___________________________________________________________
> >> Tools-discuss mailing list - Tools-discuss@ietf.org -
> >> https://www.ietf.org/mailman/listinfo/tools-discuss  
> > 
> > ___________________________________________________________
> > Tools-discuss mailing list - Tools-discuss@ietf.org -
> > https://www.ietf.org/mailman/listinfo/tools-discuss  
> 



-- 
I'm getting older but, unlike whisky, I'm not getting any better
https://lminiero.it