From: "Lannynd, Thorsten" <t-lannynd@ti.com>
To: "jcormier@criticallink.com" <jcormier@criticallink.com>,
"denis@denix.org" <denis@denix.org>
Cc: "meta-arago@lists.yoctoproject.org"
<meta-arago@lists.yoctoproject.org>,
"Eatmon, Ryan" <reatmon@ti.com>,
"Etheridge, Darren" <detheridge@ti.com>,
"Brnich, Brandon" <b-brnich@ti.com>,
"Christidis, Antonios" <a-christidis@ti.com>
Subject: RE: [meta-arago][master/wrynose][PATCH v2] meta-arago-distro: chromium: add force-h264-youtube extension
Date: Tue, 9 Jun 2026 18:25:48 +0000 [thread overview]
Message-ID: <cd75fd7e185645e690df5cf9eef0ed40@ti.com> (raw)
In-Reply-To: <CADL8D3Y-7wywm0qb+T=mdbRm=+tN8rzJQ3-uffnjXvdo2pZ8Fg@mail.gmail.com>
On 6/9/26 12:52 PM, Jon Cormier via lists.yoctoproject.org wrote:
> On Tue, Jun 9, 2026 at 1:43 PM Denys Dmytriyenko via lists.yoctoproject.org
> <denis=denix.org@lists.yoctoproject.org> wrote:
> >
> > On Tue, Jun 09, 2026 at 12:13:06PM -0500, Thorsten Lannynd via
> lists.yoctoproject.org wrote:
> > > Install a lightweight Chrome extension that forces YouTube to serve
> > > H.264 (avc1) by blocking VP8, VP9, and AV1 via
> MediaSource.isTypeSupported.
> > > This enables Wave5 hardware video decoding on YouTube, which only
> > > supports
> > > H.264 and HEVC.
> > >
> > > Installed at /usr/lib/chromium/extensions/force-h264-youtube
> > > and --load-extension flag is needed to enable the extension.
> > >
> > > Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
> > > ---
> > > v2:
> > > - Remove the flag that enables extension by default as not all SoCs support
> > > Wave5 and Chromium
> Why would disabling this extension help? Does this mean there are some SoCs
> which do support VP8, VP9, and AV1? Or if using CPU, decode those better
> than h.264?
H.264 and HEVC are the only codecs with hardware acceleration, however, we
have one SoC that supports Chromium with no hardware video decoder.
Not enabling the extension gives the user control over what codec YouTube
Is serving. I found the CPU utilization results to be roughly around the same,
at 480p 30 fps when using S/W acceleration for AV1 and H.264 with
significant playback stutters.
> >
> > This is also fine, though requires enabling it manually...
>
> >
> >
> >
> > > .../chromium/chromium-ozone-wayland-arago.inc | 13 +++++++++++++
> > > .../force-h264-youtube/force_h264.js | 4 ++++
> > > .../force-h264-youtube/manifest.json | 19 +++++++++++++++++++
> > > 3 files changed, 36 insertions(+)
> > > create mode 100644
> > > meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-brow
> > > ser/chromium/chromium-ozone-wayland/force-h264-youtube/force_h264.js
> > > create mode 100644
> > > meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-brow
> > > ser/chromium/chromium-ozone-wayland/force-h264-youtube/manifest.json
> > >
> > > diff --git
> > > a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland-arago.inc
> > > b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland-arago.inc
> > > index ab092fa1..d8eb0204 100644
> > > ---
> > > a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland-arago.inc
> > > +++ b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipe
> > > +++ s-browser/chromium/chromium-ozone-wayland-arago.inc
> > > @@ -1,5 +1,7 @@
> > > PR:append = ".arago0"
> > >
> > > +EXTENSION_DIR = "/usr/lib/chromium/extensions/force-h264-youtube"
> > > +
> > > FILESEXTRAPATHS:prepend := "${THISDIR}/chromium-ozone-wayland:"
> > >
> > > PACKAGECONFIG:append = " proprietary-codecs"
> > > @@ -9,4 +11,15 @@ SRC_URI:append = " \
> > > file://0002-chromium-gpu-sandbox-Allow-GPU-sandbox-access-
> to-V4L.patch \
> > > file://0003-chromium-gpu-v4l2-Fix-OUTPUT-queue-streaming-in-
> V4L2.patch \
> > >
> > > file://0004-media-gpu-v4l2-Avoid-placing-incomplete-H264-access-.pat
> > > ch \
> > > + file://force-h264-youtube/force_h264.js \
> > > + file://force-h264-youtube/manifest.json \
> > > "
> > > +
> > > +do_install:append() {
> > > + install -d ${D}${EXTENSION_DIR}
> > > + install -m 0644 ${WORKDIR}/sources/force-h264-youtube/force_h264.js
> \
> > > + ${WORKDIR}/sources/force-h264-youtube/manifest.json \
> > > + ${D}${EXTENSION_DIR}/ }
> > > +
> > > +FILES:${PN}:append = " ${EXTENSION_DIR}"
> > > diff --git
> > > a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland/force-h264-
> youtube/force_h264.
> > > js
> > > b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland/force-h264-
> youtube/force_h264.
> > > js
> > > new file mode 100644
> > > index 00000000..5e942321
> > > --- /dev/null
> > > +++ b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipe
> > > +++ s-browser/chromium/chromium-ozone-wayland/force-h264-
> youtube/for
> > > +++ ce_h264.js
> > > @@ -0,0 +1,4 @@
> > > +(function() {
> > > + var orig = MediaSource.isTypeSupported.bind(MediaSource);
> > > + MediaSource.isTypeSupported = function(t) { return
> > > +/vp8|vp09?|av01/i.test(t) ? false : orig(t); }; })();
> > > diff --git
> > > a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland/force-h264-
> youtube/manifest.js
> > > on
> > > b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-br
> > > owser/chromium/chromium-ozone-wayland/force-h264-
> youtube/manifest.js
> > > on
> > > new file mode 100644
> > > index 00000000..fc69be22
> > > --- /dev/null
> > > +++ b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipe
> > > +++ s-browser/chromium/chromium-ozone-wayland/force-h264-
> youtube/man
> > > +++ ifest.json
> > > @@ -0,0 +1,19 @@
> > > +{
> > > + "manifest_version": 3,
> > > + "name": "Force H.264",
> > > + "version": "1.0.0",
> > > + "description": "Lightweight extension that forces YouTube to play
> > > +H.264 (avc1) by blocking VP8, VP9, and AV1",
> > > + "content_scripts": [
> > > + {
> > > + "matches": [
> > > + "*://*.youtube.com/*",
> > > + "*://*.youtube-nocookie.com/*",
> > > + "*://*.youtu.be/*"
> > > + ],
> > > + "js": ["force_h264.js"],
> > > + "run_at": "document_start",
> > > + "world": "MAIN",
> > > + "all_frames": true
> > > + }
> > > + ]
> > > +}
> > > --
> > > 2.34.1
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#17560):
> > https://lists.yoctoproject.org/g/meta-arago/message/17560
> > Mute This Topic: https://lists.yoctoproject.org/mt/119726830/7902621
> > Group Owner: meta-arago+owner@lists.yoctoproject.org
> > Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
> > [jcormier@criticallink.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
> >
>
>
> --
> Jonathan Cormier
> Senior Software Engineer
>
> Office: 315.425.4045 x222
>
> http://www.CriticalLink.com
> 6712 Brooklawn Parkway, Syracuse, NY 13211
next prev parent reply other threads:[~2026-06-09 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 17:13 [meta-arago][master/wrynose][PATCH v2] meta-arago-distro: chromium: add force-h264-youtube extension Thorsten Lannynd
2026-06-09 17:34 ` PRC Automation
2026-06-09 17:42 ` Denys Dmytriyenko
2026-06-09 17:51 ` Jon Cormier
2026-06-09 18:25 ` Lannynd, Thorsten [this message]
2026-06-09 18:51 ` Jon Cormier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd75fd7e185645e690df5cf9eef0ed40@ti.com \
--to=t-lannynd@ti.com \
--cc=a-christidis@ti.com \
--cc=b-brnich@ti.com \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=jcormier@criticallink.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.