On Mon, Jan 18, 2021 at 12:00:40PM +0100, Peter J. Philipp wrote: > On Mon, Jan 18, 2021 at 11:29:54AM +0100, Alexandre Ratchov wrote: > > On Mon, Jan 18, 2021 at 10:16:53AM +0100, Peter J. Philipp wrote: > > > Hi, > > > > > > I recently switched my desktop workstation to a raspberry pi 4B with 8 GB > > > RAM. > > > Since the sound there doesn't work yet, I got a USB sound card, the make > > > of > > > the sound card is best read from usbdevs -v: > > > > > > addr 08: 0ccd:00b1 TerraTec Electronic GmbH, Aureon 7.1 USB > > > full speed, power 500 mA, config 1, rev 0.10 > > > driver: uaudio0 > > > driver: ugen0 > > > > > > Like the other AUREON card in the usb drivers I put this in usb quirks to > > > not > > > attach as a uhiddev (not sure if that was the right thing to do?). > > > > > > Now to my real question: mplayer sounds horrible, but iridium sound from > > > youtube sounds OK. There is a lot of static interference when I play with > > > mplayer. So what is it doing different than iridium? I tried messing > > > with > > > audioctl buffer sizes and nblocks but I don't really know what I'm doing > > > here, > > > so I'm writing to the list. The sound did not improve when I messed with > > > the > > > buffers. > > > > > > > Everything looks OK in dmesg. Try to run sndiod in the foreground, ex: > > > > doas sndiod -ddd -a on > > > > and see what happens while mplayer sounds bad. Without stopping > > mplayer, run audioctl multiple times and see if play.errors or > > record.errors counters increase continuously. > > > > Hmmm this is elusive. My -current is from December 26th. When I put the > sndiod in -ddd -a on mode everything started working well. Could it be that > all it needs is a restart after a reboot? I can crontab that to be 5 minutes > after reboot...
The next time it fails, try to stop and start playback to see if this helps. My bet is that an usb transfer fails (heavy load may cause this) and the device doesn't recover properly. > Other than that my sndiod config looks like this in /etc/rc.conf.local: > > sndiod_flags="-f rsnd/0 -f rsnd/1" > > Odd stuff, is the -a on important? No, "-a on" is only to force sndiod to keep the device open (or exit if it can't), it's useful for testing to be sure another process doesn't grab the device.
