Hi all,
i'm using mpd for almost a decade now and it always
works great. I had used the oss output drivers, because
it was very easy to get mpd installed and configured
with in in 5 minutes. I had only to look for
what /dev/dsp are available and point mpd to the right one.
These days and OSS are gone now and configuring of mpd
is IMO a nightmare. We not only have to deal with the
pulseaudio crap, but also with the undocumented alsa
configuration.
The funny thing is, that i can write any garbage
in the device section of audio_output:
audio_output {
type "alsa"
name "Audigy"
device "mpd_with_alsa_sucks"
MPD forwards anything under device to the function
snd_pcm_open. MPD even don't check if there is something
valid in there. With the config line above, mpd
starts without errors. If i try to play something,
then the following lines is reported in mpd.log:
output: Failed to open "Audigy" [alsa]: Failed to open ALSA device
"mpd_with_alsa_sucks": No such file or directory
Of course, it fails!
We should IMO update the documentation to point users in
the right direction to configure MPD. I think, that we have
enough experts that understand alsa enough to write something
that helps other users:
1. How do i get a list of the available channels in
MPD/Alsa notation (hw:x,x or plughw:x,x)?
2. How can if configure that channel (SPDIF, volume)?
3. How do i get diagnostic information and how can
i track problems down if mpd doesn't work?
In my case, i have two soundcards installed and trying to
get mpd using the SPDIF output of a Audigy 1.
Any help is welcome.
Best Regards,
Carsten
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Musicpd-dev-team mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
