Closed wooque closed 2 years ago
Seems that Chromium 95 broke VAAPI and that needs to be patched (Arch linux patch for Chromium 95: https://github.com/archlinux/svntogit-packages/commit/5316f38b605306e6f0627a8ee9e818550abec826#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a). On Arch Linux Chromium 95 works by just passing --enable-features=VaapiVideoDecoder, Brave does not. All flags passed to both browsers
--enable-features=VaapiVideoDecoder
--enable-features=OverlayScrollbar,VaapiVideoDecoder --enable-gpu-rasterization --enable-zero-copy --disable-smooth-scrolling --password-store=gnome
--use-gl=egl
--use-gl=desktop
Chromium Brave
Brave uses hardware accelerated VDAVideoDecoder like Chromium
Always
Brave 1.31.87 Chromium: 95.0.4638.54 (Official Build) (64-bit) Revision d31a821ec901f68d0d34ccdbaea45b4c86ce543e-refs/branch-heads/4638@{#871} OS Linux JavaScript V8 9.5.172.21 User agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36 Command Line /usr/lib/brave-bin/brave --enable-features=OverlayScrollbar,VaapiVideoDecoder --enable-gpu-rasterization --enable-zero-copy --disable-smooth-scrolling --password-store=gnome --enable-crashpad --disable-client-side-phishing-detection --disable-domain-reliability --enable-dom-distiller --no-pings --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --sync-url=https://sync-v2.brave.com/v2 --lso-url=https://no-thanks.invalid --variations-server-url=https://variations.brave.com/seed --enable-features=AutoupgradeMixedContent,SafetyTip,WebUIDarkMode,PasswordImport,ReducedReferrerGranularity,PrefetchPrivacyChanges,LegacyTLSEnforced,DnsOverHttps,VaapiVideoDecoder,OverlayScrollbar --disable-features=AutofillServerCommunication,WebOTP,AutofillEnableAccountWalletStorage,FledgeInterestGroupAPI,ConversionMeasurement,FederatedLearningOfCohorts,AppDiscoveryRemoteUrlSearch,ComputePressure,NotificationTriggers,TrustTokens,DirectSockets,ReadLater,TextFragmentAnchor,InterestCohortFeaturePolicy,FledgeInterestGroups,SettingsLandingPageRedesign,CopyLinkToText,NetworkTimeServiceQuerying,SubresourceWebBundles,SignedExchangePrefetchCacheForNavigations,InterestCohortAPIOriginTrial,FirstPartySets,IdleDetection,PrivacySandboxSettings2,NavigatorPluginsFixed,SignedExchangeSubresourcePrefetch,HandwritingRecognitionWebPlatformApiFinch,FlocIdComputedEventLogging,LiveCaption --flag-switches-begin --flag-switches-end Executable Path /usr/lib/brave-bin/brave Profile Path /home/vuk/.config/BraveSoftware/Brave-Browser/Default Variations AdRewardsStudy:NextPaymentDay BraveTalkStudy:Enabled ConversionsStudy:NewDefaultPattern EphemeralStorageStudy:Enabled NativeCosmeticFilteringStudy:Enabled PermissionLifetimeReleaseStudy:Enabled SpeedreaderReleaseStudy:Disabled
I'm seeing this fixed in 1.32.106. Can someone confirm the same?
Yes, it's fixed now
Description
Seems that Chromium 95 broke VAAPI and that needs to be patched (Arch linux patch for Chromium 95: https://github.com/archlinux/svntogit-packages/commit/5316f38b605306e6f0627a8ee9e818550abec826#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a). On Arch Linux Chromium 95 works by just passing
--enable-features=VaapiVideoDecoder
, Brave does not. All flags passed to both browsersSteps to Reproduce
--enable-features=VaapiVideoDecoder
to both Chromium 95 and Brave 1.31.87--use-gl=egl
or--use-gl=desktop
Actual result:
Chromium Brave
Expected result:
Brave uses hardware accelerated VDAVideoDecoder like Chromium
Reproduces how often:
Always
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information: