Chrome supports RTC H265 decoding starting from version 127. This eliminates the need for servers to transcode H265. USC and H5S will automatically detect the decoding types supported by the browser and determine whether to start transcoding. This way, clients don't need to worry about whether a camera supports H264 or H265. It is recommended to use client devices with GPUs as much as possible. This eliminates the need for servers to perform an H265-to-H264 conversion process, significantly saving server CPU resources.
The Chrome RTC H265 decoding function is disabled by default. You need to add the --enable-features=WebRtcAllowH265Receive --force-fieldtrials=WebRTC-Video-H26xPacketBuffer/Enabled startup parameters.
Take Windows as an example, open cmd.exe
cd C:\Program Files\Google\Chrome\Application
chrome.exe --enable-features=WebRtcAllowH265Receive --force-fieldtrials=WebRTC-Video-H26xPacketBuffer/Enabled
After starting in this way, the RTC decoder will contain H265.
You can use chrome://webrtc-internals/ to check H265 enable or not, and H5S support this from r18.
