Talk:Music Player Daemon

From ArchWiki
Revision as of 23:31, 16 December 2012 by Hatten (talk | contribs)
Jump to: navigation, search

I think this article needs to be reworked. Right now it's just single user with weird permissions (which did not work for me.) This needs to be more generalized for multiple users so it can be done properly. I'll look into it and consider some major modifications. --Statix 01:01, 5 October 2008 (EDT)

Still planning to?--stefanwilkens 20:31, 5 March 2009 (EST)

Because MPD is running as another user, it takes full control over the sound device and any other programs starting up as my user cannot open the sound device, i received the error Error opening ALSA device "hw:0,0": Device or resource busy. This differs slightly from the error in the article. As seen here the two lines here ipc_key_add_uid and falseipc_perm 0666 in /etc/asound.conf resolved the issue which allowed more than one user to read the sound device. This may help someone although its more of an issue with dmix than mpd but i only discovered it due to dmix running as a different user.

--Tama00 08:42, 22 June 2009 (EDT)

I do not understand why installing with MPD running as root initially and then switching over to user 'mpd', is given as the preferred method. I'd like to see an explanation in the page of why this is preferred ,as opposed to installing MPD just like any other program (e.g. putting the config in your normal ~, etc.). For me, the second way seemed more logical and easier.

Mollison 02:52, 15 August 2009 (EDT)

I think it's quite clearly described that you need it to be able to autostart from your rc.d directory. Wuncidunci

So I guess you're saying that the answer is: "because it's a daemon." That suffices, thanks. Mollison 01:12, 16 August 2009 (EDT)

I'm going to resurrect this because, based on my recent install (and from comments in many of the posts on the forums) I think it makes far more sense to detail two clear options:

1. Install for single user use (all files in ~/.mpd) - flagged 'recommended'
2. Install for multi-user use (files in {/etc,/var,/lib})

For the single user, it is just as simple to start mpd from .xinitrc and it means you don't have issues with permissions etc...


Jasonwryan 01:34, 7 December 2009 (EST)

That sounds good, I just thought about the same when browsing through the article. Guessing from the timestamp, I think no one has committed to this idea yet :)
I'll see when I have some time to spare. I also think that lots of Tips and Tricks are scattered throughout the page. It would be nicer if they were tied up in one section and referred to from other sections.
What I had in mind was:
1. Divide up the two ways of setting up mpd (on system start, per-user-basis) after explaining the internal workings of mpd a little (server/client, database, although that may perhaps be a bit too technical)
2. Bind up the good advices scattered throughout the article into the Tips&Tricks/Troubleshooting sections and refer to them from within the other sections.
3. Rewrite some passages and be a little moar formal :)
--n0stradamus 17:15, 8 August 2011 (CEST)

Hatten (talk) 23:31, 16 December 2012 (UTC) I just managed to get an install of mpd going, and that was way harder than it should've been. Made an account here for the sole purpose of complaining that the article is hard to use, which it looks like I'm not the only one to think. If nobody else is gonna do the changes proposed the last few years I might give it a try, being a newbie to wiki editing it will be far from perfect, but I can at least hopefully incorporate some of my experiences trying to install this. Aside from the whole article needing a rewrite, i suggest (and will do unless somebody stops me :p) Switch single-user install and global install around, making single-user be the first thing a newbie sees. make it use ~/.mpd/log instead of ~/.mpd/mpd.log (doing the same for the rest), as that's closer to the example config file. Inserting it being an option to launch it with .xinitirc, cause i thought that was the easiest way to get it going.

Section 5.4: MPD & ALSA

This section is dealing with issue about hardware mixing not working, and telling to the user to use dmixer. I've get issue with this way of doing thing, enable to set the volume of mpd. Upstream have pointing me to the mixer_type option, which tell to mpd to use hardware or software mixing, what we want to do with dmixer.

The syntax for this audio_output's option is ` mixer_type "software" `. It replace ` option "dev=dmixer" device "plug:dmix" ` --Gkrnours 18:28, 22 March 2010 (EDT)

Article title: acronyms and i18n

Some of the translated pages have different titles schemes, others do not. Should the main title be MPD or Music Player Daemon? Dres 19:08, 23 January 2010 (EST)

I favor the expansion of acronyms in titles; this eliminates ambiguity. -- pointone 21:59, 23 January 2010 (EST)
I agree with this, yet Music Player Daemon already exists. I'll move the international pages that are eligible in the meantime. Dres 22:57, 23 January 2010 (EST)

mpd.pd permission issue

I had an error with the mpd user setup technique with mpd not having permission to access /var/run/mpd/ . I ended up commenting out that line in the mpd.conf file and things worked. --Mustard 22:50, 29 March 2011 (EDT)

I guess my solution (I just described it in the article) is more clean, for it keeps the functionality of the pid-file. --FlorianJW 09:51, 29 March 2012 (EDT)