RESOLVED FIXED 196346
[GStreamer] imxvpudecoder detection and handling
https://bugs.webkit.org/show_bug.cgi?id=196346
Summary [GStreamer] imxvpudecoder detection and handling
Philippe Normand
Reported 2019-03-28 04:27:23 PDT
When the imxvpudecoder is used, the texture sampling of the directviv-uploaded texure returns an RGB value, so there's no need to convert it.
Attachments
Patch (11.01 KB, patch)
2019-03-28 04:48 PDT, Philippe Normand
calvaris: review+
calvaris: commit-queue-
Philippe Normand
Comment 1 2019-03-28 04:48:32 PDT
Xabier Rodríguez Calvar
Comment 2 2019-03-28 05:28:29 PDT
Comment on attachment 366165 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=366165&action=review > Source/WebCore/ChangeLog:9 > + directviv-uploaded texure returns an RGB value, so there's no need texture > Source/WebCore/ChangeLog:11 > + ImageRotation flag handling. The flat is now computed once only flag > Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:858 > + bool shouldWait = m_videoDecoderPlatform == WebKitGstVideoDecoderPlatform::Video4Linux; > auto proxyOperation = > - [shouldWait = m_isVideoDecoderVideo4Linux, pipeline = pipeline()](TextureMapperPlatformLayerProxy& proxy) > + [shouldWait, pipeline = pipeline()](TextureMapperPlatformLayerProxy& proxy) nit: is there any problem in using this in one line? > Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.h:294 > + mutable WebKitGstVideoDecoderPlatform m_videoDecoderPlatform; Does this need to be mutable?
Philippe Normand
Comment 3 2019-03-29 02:55:51 PDT
Comment on attachment 366165 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=366165&action=review >> Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.h:294 >> + mutable WebKitGstVideoDecoderPlatform m_videoDecoderPlatform; > > Does this need to be mutable? It indeed does not!
Philippe Normand
Comment 4 2019-03-29 03:43:47 PDT
Radar WebKit Bug Importer
Comment 5 2019-03-29 03:45:40 PDT
Note You need to log in before you can comment on or make changes to this bug.