[Solved] MPD failed to open ALSA device

d_fajardo · 2019-08-31 12:03:20

I used to have a fully working mpd using a Cambridge Audio DAC as sound card and it worked exceedingly well. I needed a complete reinstall of Arch and am now trying to configure mpd and the DAC back to work but this time I am getting errors.

First I set up mpd as a systemd per user and it is enabled. Status is without error.
systemctl --user status mpd.service:

● mpd.service - Music Player Daemon
   Loaded: loaded (/usr/lib/systemd/user/mpd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-08-31 12:43:57 BST; 8min ago
     Docs: man:mpd(1)
           man:mpd.conf(5)
 Main PID: 5093 (mpd)
   CGroup: /user.slice/user-1000.slice/user@1000.service/mpd.service
           └─5093 /usr/bin/mpd --no-daemon

Aug 31 12:43:57 taichi-z270 systemd[679]: Starting Music Player Daemon...
Aug 31 12:43:57 taichi-z270 systemd[679]: Started Music Player Daemon.

However, I can't play any music. ncmpcpp always stuck in 'pause' and Cantata just don't play.
Here is part of mpd.log:

Aug 31 12:44 : exception: Failed to open "Cambridge Audio DAC" (alsa)
Aug 31 12:44 : exception: nested: Failed to open ALSA device "hw:0,0": Device or resource busy

I've searched the internet but can't find a satisfactory solution. I do however get a sound - browsers, Spotify and so I know ALSA is working. But note that I don't use pulseaudio.
Here is part of my mpd.conf:

audio_output {
	type                       "alsa"
	name                       "Cambridge Audio DAC"
	device                     "hw:0,0"
	#auto_resample              "no"
	#auto_format                "no"
	#auto_channels              "no"
	#replay_gain_handler        "none"
	#mixer_device               "default"
	#mixer_type                 "hardware"
}

Any reason why I get device or resource as busy?

Last edited by d_fajardo (2019-08-31 13:02:23)

seth · 2019-08-31 12:30:15

How many pulseaudio daemons are running?

d_fajardo · 2019-08-31 12:51:52

Thanks seth. I am not using pulseaudio but is it possible that a daemon is running even if I don't have it installed? How do you find that out?

loqs · 2019-08-31 12:56:29

fuser -v /dev/snd/* #see what is accessing the sound cards
systemctl status --user pulseaudio.service
ps aux | grep pulseaudio #check globally for pulseaudio

d_fajardo · 2019-08-31 13:02:04

Thanks both of you. I found the culprit:
fuser -v /dev/snd/*

/dev/snd/pcmC0D0p:   brightchip    687 F...m timidity
/dev/snd/seq:        brightchip    687 F.... timidity
/dev/snd/timer:      brightchip    687 f.... timidity

This was because I was checking out some midi's. Solved!

Arch Linux

#1 2019-08-31 12:03:20

[Solved] MPD failed to open ALSA device

#2 2019-08-31 12:30:15

Re: [Solved] MPD failed to open ALSA device

#3 2019-08-31 12:51:52

Re: [Solved] MPD failed to open ALSA device

#4 2019-08-31 12:56:29

Re: [Solved] MPD failed to open ALSA device

#5 2019-08-31 13:02:04

Re: [Solved] MPD failed to open ALSA device

Board footer