Re: Uploadable slides (Re: New Meetecho feature)

Meetecho IETF support <> Mon, 26 July 2021 22:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D19673A14CA for <>; Mon, 26 Jul 2021 15:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4z6qYmqRGOVX for <>; Mon, 26 Jul 2021 15:04:38 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 46A683A14C5 for <>; Mon, 26 Jul 2021 15:04:37 -0700 (PDT)
Received: from [] ([]) by Aruba Outgoing Smtp with ESMTPSA id 88iBm4ZtjxC2n88iBmembt; Tue, 27 Jul 2021 00:04:35 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=a1; t=1627337075; bh=RWjkNAeOuHYbZ7ETvuilK0HWcerJlYj0vmgzzsWhHy4=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=j5V+an3ceD3YvC5L1N3SOXHGcmkdSKJSHBrHQbKVZ5zJL9mCV5Alxzv9Nop0gXswX yG+ajgGvrSphVa8gvMtrUJdkVYfUHUi6zKEnnLYUj5CsAMMRLVbuzTc2sucKuHkEcQ KNYkMcj5l8Bd40Zq16JCMC7KdvaY9h7bslFBbrNHOAW/ORPNR69imBjJBtH4wyXFnf KFzye6HFRM8WNWtAZXjTQ2Ii+lsjwBluSfrhnhYF+R2Vsj2Vtrac0NQhaM4M2zYKSI Q/TAmUDD68MozRCA+v97PgqAq5rlLaon6/9ktGnnCfYdKTWILxaZpADbE99ykjTK2J ld95kNXd7akfQ==
Subject: Re: Uploadable slides (Re: New Meetecho feature)
To: Working Group Chairs <>
References: <> <> <> <> <> <>
From: Meetecho IETF support <>
Message-ID: <>
Date: Tue, 27 Jul 2021 00:04:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfOs39y688nx+MMi1jePiTJIfTcNwhPszDQz1e3HZSLgPU3ARsDvAmpzeR6h0GWFSlUfc/1hBiFRq1rUAXHfEpfxNvXQa+ARWr3U0QcJa/3va4ZKKtOUf yvTXjKcx65xeX+u8l3ooG66qqdcy42p+RDwuutqBVct9GYA17/V9S/OC
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 26 Jul 2021 22:04:44 -0000

As some of you noticed, Meetecho is currently generating slides images 
by picking the very same size as the source pdf. This sometimes causes 
issues when the original size is too small, making slides blurred or 

While we work on a fix for this issue, David Schinazi shared a 
workaround he found when generating pdf files from Google Slides: go to 
File > Page Setup > Custom and replace "10 x 5.63 inches" with "64 x 36 
inches" (or any other ratio that is much higher). This does not change 
the PDF file size at all (it's vectorized) but looks much better in 

Hope this helps,
the Meetecho team

Il 20/07/21 17:31, Carsten Bormann ha scritto:
> On 2021-07-20, at 16:34, Toerless Eckert <> wrote:
>> I had never tried o analyse efffective resolution in meetecho.
>> How does the resolution of the uploaded slide now (720x405)
>> compare in your eperience with the resolutions you would
>> get when live presenting the slides in meetecho ?
> I didn’t look at the actual resolution (video coding!) for screen sharing.  But I had less problems reading the same kind of slides.
> Note that you can make the window larger and that should potentially renegotiate the video (no idea whether meetecho does all that recoding).
> Grüße, Carsten