Closed JesperWe closed 1 year ago
I was not familiar with snapcast, so I built and installed it to test. So far, I can't reproduce this problem, unfortunately. Snapclient runs fine and audio plays correctly. I can't imagine why it would work for you with aplay, but not with snapclient. Doesn't appear to be a locale-related problem as snapclient uses the default "C" locale (doesn't call setlocale()
, in other words).
Weirdly, it doesn't work if I try to use the default device but it works fine if I specify the dsp device by name or index.
Thanks a lot for confirming that I have not completely lost my marbles :-) Any pointers on additional debugging I could do?
(Snapcast is beautiful tool for vendor independent multi-room audio with latency compensation)
so I built and installed it to test
Made me think... So I went ahead and built it myself instead of using the release download. Works.
The fact that aplay works on your end but alsalib claims the plugin doesn't exist when you use snapclient is very odd. Is it possible that one is a 32-bin executable and the other is 64-bit? I'm not sure off hand whether Debian supports multilib on ARM, but you could try running
$ file $(which aplay snapclient)
to confirm. Install the file
package if it isn't already installed.
Good to hear it works if you build snapcast yourself.
This is most likely me doing something wrong but I have been staring at this for a whole day now, hoping for some tips...
Running on a RPi / Debian 11, it has a USB and an I2S DAC installed.
/etc/asound.conf
/etc/ladspa_dsp/config
/etc/ladspa_dsp/config_ute
The plugin is installed:
Playing an audio file works fine (plays on correct device with DSP processing):
But trying to use it from the player I want fails:
Can't figure what is wrong... Anything else I could check?