Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 10e34010e28d267aeb51d1ab926244f6c91187b5
https://github.com/WebKit/WebKit/commit/10e34010e28d267aeb51d1ab926244f6c91187b5
Author: Youenn Fablet <[email protected]>
Date: 2026-04-13 (Mon, 13 Apr 2026)
Changed paths:
A LayoutTests/http/wpt/mediastream/webrtc-vp9-colorspace-expected.txt
A LayoutTests/http/wpt/mediastream/webrtc-vp9-colorspace.html
M LayoutTests/platform/glib/TestExpectations
M Source/WebCore/platform/mediastream/RealtimeOutgoingVideoSource.cpp
M Source/WebCore/platform/mediastream/RealtimeOutgoingVideoSource.h
M
Source/WebCore/platform/mediastream/cocoa/RealtimeOutgoingVideoSourceCocoa.cpp
M
Source/WebCore/platform/mediastream/libwebrtc/gstreamer/RealtimeOutgoingVideoSourceLibWebRTC.cpp
Log Message:
-----------
WebRTC VP9 encoders should propagate frame colorspace
rdar://174008548
https://bugs.webkit.org/show_bug.cgi?id=311410
Reviewed by Eric Carlson.
When sending a WebCore VideoFrame in RealtimeOutgoingVideoSource::sendFrame, we
make sure to populate the webrtc color space.
It is then up to each encoder to encode the color space so that the remote side
will get the propoer information.
The VP9 encoder is supporting this, we add a test to validate this.
Other encoders, like H264/H265 might need updates to support this.
Like done for LibWebRTCVPXInternalVideoEncoder::encode, when encoding RGB
frames, we use a BT709 color space as the encoder will do a conversion to YUV.
Covered by added test.
Canonical link: https://commits.webkit.org/311065@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
