Autoplay after start - troubles

[Gabor]

Hello All,

After having tried a few programs, I've been using the previous versions of the fantastic Moode Audio for while and a few days ago I've installed 4.1 without any problems. The dedicated and structured forum made me register and begin to post, so here comes my first one:

"Autoplay after start" works as intended when rebooting.

When I finish listening I normally just cut the power to the RPi but when powering up again, the list in the Playback tab is cleared and so Autoplay does not... autoplay anything. I then add a radio station but then have to click play and all the previous entries appear on the Playback tab.

[Tim Curtis]

When the failure occurs, post the moOde log.

cat /var/log/moode.log

-Tim

[Gabor]

When the failure occurs, post the moOde log.

cat /var/log/moode.log

-Tim

Powered up RPi (with IQaudIO Pi-DAC+) and got a blank playlist (but with volume 43 restored from the last session). Below is the moode.log which looks OK to me.

I then clicked the Play button, the 5 radio stations appeared and the first one started to play.

I'm using Firefox on Windows 10 to access moOde Player.

Code:

20180507 111555 worker: - Start
20180507 111555 worker: Successfully daemonized
20180507 111555 worker: - Init
20180507 111555 worker: Session loaded
20180507 111555 worker: Debug logging (off)
20180507 111557 worker: Host (moode)
20180507 111557 worker: Hdwr (Pi-3B 1GB v1.2)
20180507 111557 worker: Arch (armv7l)
20180507 111557 worker: Rasp (9.4)
20180507 111557 worker: Kver (4.14.32-v7+)
20180507 111557 worker: Ktyp (Standard)
20180507 111557 worker: Gov  (performance)
20180507 111557 worker: Rel  (Moode 4.1 2018-04-02)
20180507 111557 worker: Upd  (None)
20180507 111557 worker: MPD  (0.20.18)
20180507 111557 worker: USB boot not enabled yet
20180507 111557 worker: File system expanded
20180507 111557 worker: HDMI port off
20180507 111557 worker: File check ok
20180507 111557 worker: - Network
20180507 111557 worker: eth0 exists
20180507 111557 worker: eth0 address not assigned
20180507 111557 worker: wlan0 exists
20180507 111557 worker: wifi country (GB)
20180507 111557 worker: wlan0 trying SSID (BTHub6-Barton-2.4)
20180507 111557 worker: wlan0 (192.168.1.169)
20180507 111557 worker: - Audio
20180507 111558 worker: ALSA outputs unmuted
20180507 111558 worker: Audio out (I2S audio device)
20180507 111558 worker: Audio dev (IQaudIO Pi-DAC+)
20180507 111558 worker: ALSA mixer name (Digital)
20180507 111558 worker: MPD volume control (software)
20180507 111558 worker: Hdwr volume controller exists
20180507 111558 worker: Chip options (Burr Brown PCM5122)
20180507 111558 worker: - Services
20180507 111600 worker: MPD started
20180507 111600 worker: MPD scheduler policy (time-share)
20180507 111600 worker: Configure MPD outputs
20180507 111600 worker: MPD output 1 ALSA default (off)
20180507 111600 worker: MPD output 2 ALSA crossfeed (on)
20180507 111600 worker: MPD output 3 ALSA parametric eq (off)
20180507 111600 worker: MPD output 4 ALSA graphic eq (off)
20180507 111600 worker: MPD output 5 ALSA bluetooth (off)
20180507 111600 worker: MPD crossfade (off)
20180507 111600 worker: - Last
20180507 111600 worker: USB sources (none attached)
20180507 111600 worker: NAS sources (mountall initiated)
20180507 111600 worker: Volume level (43) restored
20180507 111600 worker: Auto-playing id (1)
20180507 111600 worker: Maintenance interval (21600)
20180507 111600 worker: Watchdog started
20180507 111600 worker: Ready

[Tim Curtis]

Nothing suspicious in moode startup log.

Instead of pulling the plug try Shutdown from the menu. If auto-play works after powering up it would suggest that possibly MPD state file is corrupted when just pulling plug.

Another log to check when the failure occurs is MPD log

cat /var/log/mpd/log

It may show errors trying to playtime item id or opening the audio output.

-Tim