Date: Tue, 28 Jul 2026 18:10:29 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: Adrian Chadd <adrian@freebsd.org> Cc: Nuno Teixeira <eduardo@freebsd.org>, Sulev-Madis Silber <freebsd-current-freebsd-org111@ketas.si.pri.ee>, freebsd-current@freebsd.org Subject: Re: Tragic State of FreeBSD Audio/Sound Message-ID: <20260728181029.f4aeaf7a0bfbaf565f3468c6@dec.sakura.ne.jp> In-Reply-To: <CAJ-Vmok5_mp2_Qak_7ApEdVSS_7Y1cnuY=3HiF8xnUYuD_PF-g@mail.gmail.com> References: <hkttyyfmuguexmliuhmg@ewtn> <CALH631mZWS9e9FDXPUT8N8W8WnNnpfYaoPuRyqXhqNTW9=atLw@mail.gmail.com> <CAK7dMtC0f7SgU7k6Yvbqg94eksd5UJ1meX7o2_0ukAteZPb-9g@mail.gmail.com> <20260722085416.407316d393dce1884c29a3c7@dec.sakura.ne.jp> <CAK7dMtBDQTwFkQ2UKgz1LtniZBdaWBnfL4iwUo1kFT5d34xSdQ@mail.gmail.com> <20260724001549.c947af418add25dd00ac0344@dec.sakura.ne.jp> <CAK7dMtBO4C5H9uexDfLjzL-ovuXMU8s-t5D-rTDxJcfNq%2BAMmg@mail.gmail.com> <20260724193239.d2eb613e0c4f42b90925eb46@dec.sakura.ne.jp> <20260726090359.4082568fe922add2dc01deb2@dec.sakura.ne.jp> <CAJ-VmonRmyrhpmAFkf7dAg2VdVFQKjeYtWMBYPSBvohuGBg-9w@mail.gmail.com> <wizxwdgtrmwqlrhgojon@qeft> <0AC6B63B-2A37-4F8D-BDBD-36D09F584913@ketas.si.pri.ee> <20260727190324.4b14bd9d7581c02c1cb001db@dec.sakura.ne.jp> <CAJ-VmomrsF0TDC7LDP1khyXgMREc98ysmn75NwL8Qm0C7qKnGQ@mail.gmail.com> <CAFDf7UKq92Ke7_DFvtY%2BHLUsy6-Wyi85o4bSQgDE7=R6KxDWSA@mail.gmail.com> <CAJ-Vmok5_mp2_Qak_7ApEdVSS_7Y1cnuY=3HiF8xnUYuD_PF-g@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Mon, 27 Jul 2026 20:24:09 -0700 Adrian Chadd <adrian@freebsd.org> wrote: > On Mon, 27 Jul 2026 at 15:09, Nuno Teixeira <eduardo@freebsd.org> wrote: > > > > > >> If you're experiencing "buzz" like I think you are then it's the same > >> frame being queued > >> over and over again to the DAC. Typically I've only seen that happen here when I > >> have the kernel panic (we're not stopping audio DMA at this point, and > >> I don't know > >> why it's looping over.) > >> > >> <snip> > >> > >> Even in the year of our lord "LLMs are available" there's only so much > >> one can do > >> in long email threads; at some point bugs need reproducing, PRs need filing and > >> developer / user time needs to happen. Let's be methodical about it to help out > >> the sound folks in figuring it out. > >> > >> > >> > >> -adrian > >> > > > > Hello, > > > > I usually linten to youtube when doing poudriere builds. Music helps the process and poudriere build better. > > > > I use an usb dac with: > > > > hw.snd.latency=10 > > hw.usb.uaudio.buffer_ms=8 > > > > IMHO it helps a little. > > neat. again, if you can reproduce this then please file a bug, include > information about your hardware > and what you're doing on it to elicit the terrible behviour. > > > > > -adrian In my case, the issue rarely (about once per several months, including "stop playing" cases) happens, thus, hard to reproduce. Possibly (too wild guess, though) race conditions between *I/O pressures by heavy poudriere builds *timing to send payload to USB audio *timing to send/receive I/O from/to USB peripherals *reading audiofile (in my case, mostly FLAC) *processing audio data to send to USB audio In some cases, buzz sounds. In some other cases, sound stops, but audacious thinks it's sanely playing (slider moves, spectrum moves). I think the "sound stops" case would be PCM payload to USB audio is clamped to zero, instead of random value for buzz cases. Creating reproducer may be... too hard for me. Regards. -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20260728181029.f4aeaf7a0bfbaf565f3468c6>