C.Marchand

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • 25. Mai 2018 at 15:25 #35885

    That solves the problem.
    Thanks a lot for your support and your help.

    Best,
    Christophe

    18. Mai 2018 at 8:26 #35753

    Sorry for being so long.
    It still doesn’t work.
    I may provide config files or log files. Which ones do you need ?

    Best,
    Christophe

    30. April 2018 at 14:02 #35390

    We should always at least tell if a problem is solved, or not !

    I have a similar problem, but with a Amp2 HifiBerry card, and a WiFi access-point activated. All other configuration is identical. Error message in mpd.log is very simple : „Failed to open Alsa Mixer…“, without anymore specificities. I can change the volume from the Raspberry config tab, but not from YMPD.

    Any idea ?

    Best,
    Christophe

    25. April 2018 at 21:51 #35332

    Ticking „Disable build-in audio“ and setting back mixer_control to „Master“ solved the problem.

    Thanks a lot,
    Christophe

    23. April 2018 at 10:43 #35264

    Hello,
    I’ve a similar problem with the same config. Well, it is not a multi-room, only a simple player with MPD and speakers wired to HifiBerry Amp+.

    No Kodi installed – or not visible.

    mpd.log shows this :

    Apr 23 10:32 : avahi: Service 'Music Player' successfully established.
    Apr 23 10:32 : client: [0] opened from 127.0.0.1:53234
    Apr 23 10:32 : alsa_mixer: Failed to read mixer for 'Max2Play ALSA Device': failed to attach to hw:0;0: No such device

    mpd.conf contains only one audio_output, which is :

    audio_output {
            type    "alsa"
            name    "Max2Play ALSA Device"
            device  "default:CARD=sndrpihifiberry"
            format  "192000:24:2"
            mixer_device    "hw:0;0"
            mixer_control   "PCM"
    }

    Using hw:0,0 for mixer_device produces the same result.
    I can not change the volume.

    Version 2.45, license activated.

    Any help will be much appreciated.

    31. Mai 2017 at 21:28 #29150

    Problem solved. /var/log/mpd/mpd.log contains explicit message on problem. I had mis-written mixing thing, with hw0 instead of hw:0.

    Maybe a possibility to inspect log files from web interface could facilitate things…

    Best regards,
    Christophe

Viewing 6 posts - 1 through 6 (of 6 total)