[FR]: Optional native sample-rate output on Linux (PipeWire/ALSA), bypassing Chromium's fixed 48 kHz mixer when possible.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 34/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- linux, shell
- Domain
- audio-video-rtc
Research direction
The issue names no source files, tests, or implementation entry points. Start by tracing how Helium configures Chromium audio output on Linux and how its PipeWire/ALSA backends handle sample rates; determine whether an optional setting can bypass the fixed 48 kHz mixer. Done means native-rate output is available when supported while existing behavior remains available.
Written by the indexing model from the issue text.
Description
Description
Optional native sample-rate output on Linux (PipeWire/ALSA), bypassing Chromium's fixed 48 kHz mixer when possible.
Who's implementing?
- I'm willing to implement this feature myself
The problem
Currently, Helium always outputs audio at 48 kHz, regardless of the source. For example:
YouTube (48 kHz) → output 48 kHz ✅
44.1 kHz music stream → output 48 kHz ❌ (internally resampled)
Firefox behaves differently and outputs the native sample rate, allowing PipeWire/ALSA and the DAC to switch automatically between 44.1 kHz and 48 kHz.
For users with external DACs, this enables bit-perfect playback without unnecessary sample-rate conversion.
An optional setting to disable Chromium's fixed 48 kHz output (when supported by the Linux audio backend) would be greatly appreciated.
Thanks for the great browser!
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days