Talk:Music Player Daemon

From ArchWiki
Revision as of 19:53, 22 January 2011 by Misc (talk | contribs) (Output with ALSA at 44.1 KHz @ 16 bit depth, MPD daemon as separate user, more than one program at a time)
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)

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)

Output with ALSA at 44.1 KHz @ 16 bit depth, MPD daemon as separate user, more than one program at a time

I'll dump the settings here because a) I'm not sure if this is worthy of inclusion in the article and b) how that would best be done.

Why these formats? Because it's standard CDA, because ALSA on its own allows more than one program "to sound" only with dmix — whose resampling algo blows — and because that by default resamples anything lower to 48 KHz (or whatever higher format is playing at the time). Also, I get clicking sounds if I don't change at least Template:Filename this way.

What's the downside? It is that these settings cause everything (if necessary) to be resampled to this format. (Such as material from DVD or TV, which usually is at 48 KHz.) My rationale is that there's no known way to have ALSA dynamically change the format, that I listen to far more CDs than anything else and that 48 → 44.1 isn't too great a loss.

The following assumes that there are not already other settings which conflict resp. overwrite it. This applies especially to the current user's potential Template:Filename — which MPD as its own user ignores, of course, therefore Template:Filename:



Note: MPD gives the mp3 format a special treatment at decoding: It's always outputted as 24 bit. (The conversion as forced by the format line only comes after that.)

If one wants to leave the bit depth decision to ALSA resp. MPD, change the format to "44100:*:2" and comment out resp. omit dmix.format.

Note: Crossfading between files decoded at two different bit depths (say, one mp3 and one 16 bit flac) does not work unless conversion is active.