Date: Mon, 05 Jun 2023 09:11:39 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 261898] www/firefox: audio glitches with media.cubeb.backend="oss" Message-ID: <bug-261898-21738-vhWgOSBZaV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261898-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-261898-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261898 Tatsuki Makino <tatsuki_makino@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #8 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- Now, I think 114, or 113 after bug 270436 has been fixed, media.cubeb.backe= nd settings are working as intended. But 114 has a broken about:support, so we can't see where audio is being ou= tput to in browser. So it seems that the only way to check is to use the following method. fstat -f /dev/ | grep dsp If firefox uses oss directly, then the firefox line will appear. If any sound server lines appear, they are routed through it. sockstat -u -c | grep firefox Sound servers of some kind are often routed through unix domain sockets. If pulseaudio is used, pulse-*/ line will appear. If sndio is used, sndio/sock line will appear. If jack is used, /jack_ line will appear. As for ALSA, I don't know how to see any sort of status. Is it possible to determine by writing the following line to ~/.asoundrc th= at the sound will not be emitted, etc.? pcm.!default pcm.null ... First, why not make sure that we are really outputting directly to oss = by these? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261898-21738-vhWgOSBZaV>