AMD encoder, Chrome client, 1440p60 profile
The narrow question was whether this Lume chain could deliver AV1 at 2560 × 1440 and about 60 fps. It produced 60.1 fps with an 11.31 Mbps median. That does not make AV1 universal in Chrome: both endpoints and the browser path must support it efficiently.
11 ms RTT and 0.9 ms decode are different components
Adding RTT and decode does not yield end-to-end latency. Capture, encode, queues, presentation and display response are missing.
11.31 Mbps describes this content and chain
Required bitrate changes with motion, detail, quality settings and encoder behavior. Keep capacity above the observed video bitrate, especially on the host upload path.
Codec fallback is part of the product
Lume can negotiate HEVC or H.264 when AV1 is unavailable. A hardware-accelerated older codec may be more useful than software-decoded AV1. Check the compatibility matrix.
Feasibility validated, total coverage not established
The tested AMD-to-Chrome chain delivered AV1 1440p60 at the stated metrics. Broader claims require more GPUs, browsers, content and session lengths.