Summary: | www/chromium: Enable sndio by default | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Baptiste Daroussin <bapt> |
Component: | Individual Port(s) | Assignee: | freebsd-chromium (Nobody) <chromium> |
Status: | Closed FIXED | ||
Severity: | Affects Some People | CC: | chromium, jrm, lme |
Priority: | --- | Keywords: | needs-patch, needs-qa |
Version: | Latest | Flags: | koobs:
maintainer-feedback?
(chromium) |
Hardware: | Any | ||
OS: | Any | ||
See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246449 |
Description
Baptiste Daroussin
2020-10-15 15:01:58 UTC
How well chromium works when sndiod is NOT running? See bug 218188. For comparison, pulseaudio doesn't support serverless mode, so the daemon is started on demand by libpulse. From Makefile: # With SNDIO=on we exclude audio_manager_linux from the build (see # media/audio/BUILD.gn) and use audio_manager_openbsd which does not # support falling back to ALSA or PulseAudio. I have used Chromium with only SNDIO on for a few months. As jbeich points out we currently have SNDIO_PREVENTS=ALSA PULSEAUDIO, so there will probably be some disruption, but based on my experience as a user, +1 for this change. A commit references this bug: Author: jrm Date: Fri Oct 23 20:48:38 UTC 2020 New revision: 553141 URL: https://svnweb.freebsd.org/changeset/ports/553141 Log: www/chromium: Use SNDIO instead of ALSA for audio by default There are stuttering sound issues when using ALSA, so switch to something that works. PR: 250370 Changes: head/www/chromium/Makefile |