commit 8ca090ecf9fcb51daaa549bbce830511b62f00aa
author Qiu Jianlin <jianlin.qiu@intel.com> Wed Apr 24 22:22:25 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed Apr 24 22:22:25 2024
tree 6bd15e94b18bc564840ee7af5ae01cdf8eae6d78
parent c423d38b941d7e282dcfdf1238d942845553b644

RTC encoder/decoder factory support for H.265 behind flag.

This allows H.265 to be negotiated when build with RTC H.265 support, and at the same time necessary runtime flags are turned on for H.265.

A few flags needs to be provided at runtime for H.265 streaming:
First, to allow H.265 to be included in sender's capabilities,
--enable-features=PlatformHEVCEncoderSupport should be specified so that
encoder GPU factory will enumerate HW H.265 encoders;
--enable-features=WebRtcAllowH265Send should be specified so that RTC
encoder factory allows H.265 to be included in supported formats when GPU encoder factory reports supporting H.265.
--enable-features=WebRtcAllowH265Receive should be specified so that RTC
decoder factory allows H.265 to be included in supported formats when GPU decoder factory reports supporting H.265.
--force-fieldtrials=WebRTC-Video-H26xPacketBuffer/Enabled needs to be specified to switch frame assembly implementation to H.26x specific instead of using generic packet buffer.

Bug: webrtc:13485
Change-Id: Ifb2a3e3b7f09fa1c2307629e08d855a8ece53531
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5456050
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Jianlin Qiu <jianlin.qiu@intel.com>
Reviewed-by: Sergey Silkin <ssilkin@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1292129}