[Wish] Is there a way for client to communicate intended resolution and frame rate with WHIP?

Ying Yin <yingyin@google.com> Wed, 23 March 2022 18:01 UTC

MIME-Version: 1.0
From: Ying Yin <yingyin@google.com>
Date: Wed, 23 Mar 2022 14:01:26 -0400
Message-ID: <CADqNPWp1Fzgc_d8PEywQMjBQuCr4mnFXGZj1mJJr7r2rz4Qj+g@mail.gmail.com>
To: wish@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005049be05dae6855c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wish/lh0YK9-2yksAM6fzRe16MZclddQ>
Subject: [Wish] Is there a way for client to communicate intended resolution and frame rate with WHIP?
Precedence: list

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] 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