Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 2505dd003363bb15630b09de3570e750aeb6ebb4
https://github.com/WebKit/WebKit/commit/2505dd003363bb15630b09de3570e750aeb6ebb4
Author: Enrique Ocaña González <[email protected]>
Date: 2025-07-29 (Tue, 29 Jul 2025)
Changed paths:
M Source/WebCore/platform/graphics/gstreamer/GStreamerRegistryScanner.cpp
Log Message:
-----------
[GStreamer] Fix content type frame rate limit
https://bugs.webkit.org/show_bug.cgi?id=296572
Reviewed by Philippe Normand.
Decoder limits are set by a build configuration in the form of
widthxheight@framerate. However, framerate limit is only considered when
the width and height are the ones in the build config. If the actual
requested resolution is different, no framerate limit is ever
considered.
See: https://github.com/WebPlatformForEmbedded/WPEWebKit/pull/1547
This change introduces a behavior where limits where considered for each
variable independently. While not ideal, as lower resolutions might
support higher frame rates, and the way the build config ties
semantically the framerate to the resolution specified, an alternative
fix would require either an absolute max rate to be specified, or
possibly different sets of resolution + framerate limits, which might be
overkill to this purpose.
Original autor: Filipe Norte <[email protected]>
* Source/WebCore/platform/graphics/gstreamer/GStreamerRegistryScanner.cpp:
(WebCore::GStreamerRegistryScanner::isContentTypeSupported const): Limit
framerate even when the dimensions are smaller than the max limit set for them.
Canonical link: https://commits.webkit.org/297974@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
