-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Couldn't read volume from alsa device with name... (alsa, usb dac) #261
Comments
I'm having the same issue on my laptop, which has an AMD HDMI audio out and built-in Realtek ALC3228 and to which I have a JDS Labs DAC connected (set as default). Both "default:CARD=DAC" and hw:0,0 result in messages such as "[ERROR] Couldn't read volume from alsa device with name "default:CARD=DAC".", "ALSA lib control.c:1373:(snd_ctl_open_noupdate) Invalid CTL hw:0,0", and "[ERROR] Couldn't set volume: Error("snd_mixer_attach", Sys(ENOENT))". |
Somehow the errors have disappeared after setting: |
@jvanwouw - could you post the output of "aplay -l" (lower-case el) and "aplay -L" on your system? Thanks! |
In the past had something similar, but could also be another application. |
I'm seeing similar errors. I'm running a self-compiled binary on i386 linux, with default settings. Previously I was running v0.2.8 without any issues, but after upgrading to v0.2.20, I' seeing errors:
Output of aplay -L:
my config file:
Note: the errors went away when I set |
I have same problem as OP. I have a Topping D70. I'm guessing the problem occurs from the space in the mixer control name - in my case its "D70 " (note trailing space). Quotes around the control name don't help. Hardware audio is supported in MPD provided the mixer control name includes the space: audio_output { |
Everything after the What might help would be passing down the value as a program argument: On fixing this issue. The "official" v1.0 release (the next release I will start working on after my finals) will include a lot of breaking changes (including moving to TOML), which will eliminate bugs like these and allows us to make a lot of name changes to the cli names to make them more stream-lined (like having all alsa specific arguments prepended with |
Many thanks, that got it working. Good luck with the exams! |
EDIT: If it happens that you stumble across this issue and your
alsa
device isn't recognized, it might be due to unusual naming. White-space doesn't work inside of the configuration and has to be passed through CLI arguments for now. Example:spotifyd --mixer "D70 "
~Sven (SirWindfield)
I'm using v0.2.11, precompiled armv6 version on a Raspberry Pi 3. My audio device is a USB DAC, the Topping DX3 Pro. Playback works as expected with the config
device = plughw:CARD=Pro
, but so far I've only been able to use software volume control (volume-control = softvol
). But the device supports hardware volume control; I'm using it in MPD. FWIW, here is the relevant section of my /etc/mpd.conf:In fact I use an MPD client's volume control to change the volume while actually listening through spotifyd. Either that or load up alsamixer in a terminal window.
Here is the output of aplay -l:
Click to expand
And here is the output of aplay -L:
I have tried all the following "control" params in my /etc/spotifyd.conf:
All of them result in an error like this:
Am I using the wrong value(s) for device, mixer, and/or control?
Thanks!
The text was updated successfully, but these errors were encountered: