Alex313031 / Alex313031/Thorium-Raspi

Cannot use the hardware codec when playing video

Open
#16 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
50
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Raspberry Pi 4B (8GB) + radiator + Сooler Noctua => stress test cpu = 43-45 C
Power supply = reliable with ample current capacity
MX Linux last
`glxinfo -B

name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Broadcom (0x14e4)
Device: V3D 4.2.14.0 (0xffffffff)
Version: 24.2.8
Accelerated: yes
Video memory: 7393MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 3.1
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2.14.0
OpenGL core profile version string: 3.1 Mesa 24.2.8-1~bpo12+rpt4
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)

OpenGL version string: 3.1 Mesa 24.2.8-1~bpo12+rpt4
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 24.2.8-1~bpo12+rpt4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
`
Raspberry Pi configuration file
config.txt (attached)

When playing a video, for example from YouTube in Thorium, the decoder section is empty chrome://gpu
It appears to play any video using software decoding, bypassing the hardware codec. All four cores are running at 60% capacity

[thorium.txt](https://github.com/user-attachments/files/26040962/thorium.txt)

[config\[RPi4\]\[overburn\]\[work\].txt](https://github.com/user-attachments/files/26040974/config.RPi4.overburn.work.txt)

- The output command is empty

sudo v4l2-ctl -d /dev/video11 --stream-mmap=3 --stream-count=1
or
sudo lsof -c thorium-browser 2>/dev/null | grep "/dev/video"
or
sudo v4l2-ctl -d /dev/video11 --stream-mmap=3 --stream-count=10 2>&1 | head -20

Here's an example of `chrome://gpu` for Chromium,
but it doesn't use hardware-accelerated video playback either—only software-based.

[chromium.txt](https://github.com/user-attachments/files/26040986/chromium.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the attached thorium.txt, chromium.txt, and config.txt files, then reproduce the report by checking chrome://gpu while playing a YouTube video in Thorium. Use the listed v4l2-ctl and lsof commands to inspect video-device usage; done means the hardware decoder is identified and video playback no longer relies on software decoding.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, raspberry-pi
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.