Closed mimmus closed 4 months ago
:sigh: this is a repeat of https://github.com/MusicPlayerDaemon/MPD/issues/374#issuecomment-2208380566
In reply to that I said:
you need to make sure you use the correct mixer_device parameter
Now it is clear that you have not set that parameter at all.
So this issue has nothing to do with "white space". You just need to include
mixer_device "hw:3"
Sorry to bother you with cross-posting. I’m trying to set up native DSD with this integrated amplifier without vendor support, starting from needed USB quirks in the Linux kernel… Actually, I was able to see it as DSD-capable DAC but DSD file plays with a strange noise in background and I’m investigating volume settings.
I will re-try when at pc again. Thanks.
I missed:
mixer_device "hw:3"
Unfortunately, HW volume control doesn't help with my original issue (noise in the background of DSD files) but this is another issue.
Sorry and thanks for support.
Bug report
Describe the bug
Unfortunately, my DAC has these controls:
As you can see, there is an extra whitespace at the end of control name. Specifying:
mixer_control "MISSION USB Audio 2.0 "
in mpd.conf dosn't work, neithermixer_control "MISSION USB Audio 2.0\ "
or any other trick.Expected Behavior
A mixer-control with whitespace at its end should be supported as it's quite common, probably due to ALSA pitfalls.
Actual Behavior
mixer_control not recognized
Version
Configuration
Log
mixer: Failed to read mixer for "MISSION USB Audio 2.0": no such mixer control: MISSION USB Audio 2.0