Re: [Wish] Is there a way for client to communicate intended resolution and frame rate with WHIP?
James Hurley <jamehurl@twitch.tv> Thu, 24 March 2022 15:30 UTC
Return-Path: <jamehurl@justin.tv>
X-Original-To: wish@ietfa.amsl.com
Delivered-To: wish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 779E83A1081 for <wish@ietfa.amsl.com>; Thu, 24 Mar 2022 08:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.761
X-Spam-Level:
X-Spam-Status: No, score=-6.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=twitch.tv
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y0Zgf7olJ8yA for <wish@ietfa.amsl.com>; Thu, 24 Mar 2022 08:30:20 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A8313A10CB for <wish@ietf.org>; Thu, 24 Mar 2022 08:30:20 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id s18so5308285vsr.1 for <wish@ietf.org>; Thu, 24 Mar 2022 08:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=twitch.tv; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=w2L910eYGzL8MVoF4ZnlYhSOL49PlnUGLJbO3SapG7U=; b=og4Tfi8OVTF0+g6CEaRVj1DN2kQiV1LlcwuUDa/xxt+sJWO1x0KuNLkGE3+bF7Uihd ta2GxyCO/fjT/tjnhmWxRJGxaLjeQjRhdWcwdlC2ORuq1F7kxsdfEg5UOY+tbbFr6bOF Ax88QifP3QGL3slh6CGgSU2NsfZsURqLaPPk4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=w2L910eYGzL8MVoF4ZnlYhSOL49PlnUGLJbO3SapG7U=; b=hWAtbHv7wWB7M2FKntRPgwXenBKkRxJyWNwqvmY4kdyfpnu63Ya17iKLRdFg6H0YY1 NmwNUTQMYyZJNAwHWlRqfapdVS18bWJLox7tVgHUzO2Dzcylrv9kxsineHRAIUKWvujl IsH97jQUTyFxGcOP2hVFa834gPkViCEJFXQ4m0diKsHGAA7+VS/Rf67bLKLo/uOqxOp1 xCELvdF6Vjb2nEbKGn+JnmmCgspfgGqYx4fR/ETsQPUQWGtc1ns5gq5fvPivUELQtWMr 1/TpSpsg289ktnsqmKQOWVbRcisl9fbdXniScif4Z4hWo8NJMUUryAGjN5Nz7Fg7e2mZ mTKw==
X-Gm-Message-State: AOAM531BLu28fkhLxMfqJulI1xeT8GhthhffrMEfdBfRXiSxkg6XqaeT yVQD6/7bn5COojhdzk+x6sJKYMBDW5nk8Wew1j6fYQ==
X-Google-Smtp-Source: ABdhPJydwbDRmh9xI1fx74GMTHJ8dCDPsz/TYjuvgS/I4FxhJ41Cn6lPFfkIWEXWrtQmAXXH3d2G4jnrJBAaww5+S9M=
X-Received: by 2002:a05:6102:4ae:b0:31e:aa37:9922 with SMTP id r14-20020a05610204ae00b0031eaa379922mr2883115vsa.63.1648135818597; Thu, 24 Mar 2022 08:30:18 -0700 (PDT)
MIME-Version: 1.0
References: <CADqNPWp1Fzgc_d8PEywQMjBQuCr4mnFXGZj1mJJr7r2rz4Qj+g@mail.gmail.com>
In-Reply-To: <CADqNPWp1Fzgc_d8PEywQMjBQuCr4mnFXGZj1mJJr7r2rz4Qj+g@mail.gmail.com>
From: James Hurley <jamehurl@twitch.tv>
Date: Thu, 24 Mar 2022 16:30:07 +0100
Message-ID: <CAKbQtx5GdgtmipnTeeA5HMS-C=gV+-u6w5u=4aX2c=xGPcKTDg@mail.gmail.com>
To: Ying Yin <yingyin=40google.com@dmarc.ietf.org>
Cc: wish@ietf.org
Content-Type: multipart/alternative; boundary="000000000000026d5005daf8862b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/MuVlXJ8AxlRFfAhYSAAEh0jlNPQ>
Subject: Re: [Wish] Is there a way for client to communicate intended resolution and frame rate with WHIP?
X-BeenThere: wish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: WebRTC Ingest Signaling over HTTPS <wish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wish>, <mailto:wish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wish/>
List-Post: <mailto:wish@ietf.org>
List-Help: <mailto:wish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wish>, <mailto:wish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2022 17:14:28 -0000
+1 this would be very useful to see codified. On Wed, Mar 23, 2022 at 7:01 PM Ying Yin <yingyin= 40google.com@dmarc.ietf.org> wrote: > Hello, > > With WHIP, is there a standard way for the client to indicate the intended > broadcast resolution and framerate? WebRTC could temporarily adapt down > resolution and framerate, and it could start at a lower resolution than the > intended one. If the server side is transcoding and providing multiple > output resolutions, they don't necessarily want to adjust the set of > broadcast output resolutions as the ingestion changes resolutions. I > suppose there could be solutions such as setting the intended > resolution and frame rate as parameters in the url. Just wondering if this > has been considered and if there is a standard way. > > Thanks, > Ying > -- > Wish mailing list > Wish@ietf.org > https://www.ietf.org/mailman/listinfo/wish >
- [Wish] Is there a way for client to communicate i… Ying Yin
- Re: [Wish] Is there a way for client to communica… James Hurley
- Re: [Wish] Is there a way for client to communica… Sergio Garcia Murillo