Charlene Wendling: > So i've stopped sndiod in the chroot, restarted sndiod on my main > install, then started audacious in the chroot: the white noise > issue is back.
The chrooted audacious doesn't see the /tmp/sndio/sock0 socket. It acts as if there was no sndiod running. libsndio will try talking directly to the audio device, but without daemon it's short on format conversions. I guess the device is eventually fed data in a format it doesn't support. Not sure if that is supposed to happen; ask ratchov@. :-) I don't see a sndiod option to create an extra Unix domain socket, but you can make sndiod listen on a network socket with the -L<addr> option and use an environment setting like AUDIODEVICE=snd@127.0.0.1/0 inside the chroot to let the inside libsndio talk to the outside sndiod over the network. > And the problem only occurs with audacious: mpv, ffplay, mpg321 > and cmus work fine in the same conditions! I suspect audacious is different in that it defaults to a 32-bit format instead of a 16-bit one. That's why it works when you set audacious' bit depth option to 16. > INFO output.cc:175 [setup_output]: Setup output, format 0, 2 channels, 44100 > Hz. > DEBUG sndio.cc:171 [open_audio]: format=0 > INFO output.cc:199 [setup_output]: Falling back to format 12. > DEBUG sndio.cc:171 [open_audio]: format=12 > DEBUG sndio.cc:186 [open_audio]: bits=32 bytes=4 sign=1 le=0 Yeah, it first tries FMT_FLOAT (0) and then falls back to FMT_S32_NE, which is FMT_S32_BE (12) on powerpc. That's fine. > I'm sending a diff with that bit removed at least. -snip- ok -- Christian "naddy" Weisgerber na...@mips.inka.de
