[prev in list] [next in list] [prev in thread] [next in thread] 

List:       voyage-linux
Subject:    Re: [Voyage-linux] mpd warnings about "config option was not recognized" when options are valid
From:       Mark Schlegel <moschleg () verizon ! net>
Date:       2012-09-16 1:01:34
Message-ID: 505524EE.2000602 () verizon ! net
[Download RAW message or body]

Punky:

'mpd --version'  is:

      mpd (MPD: Music Player Daemon) 0.16.7

and 'dpkg -s mpd' gets:

      Version: 0.16.7-2

Mark

On 09/15/2012 05:22 AM, Punky Tse wrote:
> Hi Mark,
>
> Please show me mpd version by "mpd --version"
>
> On 9/15/2012 4:02 PM, Mark Schlegel wrote:
>>
>> I'm using Voyage 0.8.5 fully updated to today (9/15/2012) and each
>> time I boot Voyage mpd, I see a group of warnings in
>> /var/log/mpd/mpd.log that don't make sense to me:
>>
>> Sep 15 07:49 : config: option 'mixer_device' on line 206 was not
>> recognized
>> Sep 15 07:49 : config: option 'mixer_control' on line 207 was not
>> recognized
>> Sep 15 07:49 : config: option 'mixer_index' on line 208 was not
>> recognized
>>
>> When I check those lines (206-208) in /etc/mpd.conf I have:
>>
>>         mixer_device    "default"       # optional
>>         mixer_control   "PCM"           # optional
>>         mixer_index     "0"             # optional
>>
>> which to me looks like completely correct values for those options. So
>> why is mpd complaining about those. BTW, the mpd is working so it's
>> nothing fatal, I just like to have the system working correctly.
>>
>> the entire stanza is for this audio_output:
>>
>> audio_output {
>>         type            "alsa"
>> #       name            "My ALSA Device"
>>         name            "Stello DAC sw mixer"
>>         device          "hw:0,0"        # optional
>> #       format          "44100:16:2"    # optional
>>         mixer_device    "default"       # optional
>>         mixer_control   "PCM"           # optional
>>         mixer_index     "0"             # optional
>>         # allow volume to change remotely via mixer_type
>>         mixer_type      "software"
>> }
>>
>> Since all three of those are the default settings I suppose I could
>> remove them but I was wanting them shown explicitly. Does mpd have
>> some problem with the default value being set redundantly like this?
>> Maybe "was not recognized" is kind of the programmer's dumb way of
>> really meaning that the setting had no effect because it was already
>> the default?
>>
>>
>>
>> Mark
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux@list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>
>

-- 
Mark Schlegel
Phone: (301) 498-2888
Email: moschleg@verizon.net  moschlegel@safe-mail.net

_______________________________________________
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux
[prev in list] [next in list] [prev in thread] [next in thread]