[PROBLEM] "Autoplay after start" broken in 7.6.1

[Busybox]

I don't see a 7.6.1 support thread yet, so I'm posting this here. Feel free to move it if a 7.6.1 support thread is started.

"Autoplay after start" worked fine in 7.6.0; moode would begin playing the same radio station that was active when powered down. In 7.6.1, moode starts up playing an apparently random station in my playlist, not the station that was active before the last power down or restart.

- Steve

[Tim Curtis]

Works fine on my end after power off/on or reboot.

Post Moode startup log and I'll have a look.

Code:

moodeutl -l

[Busybox]

Hmm, it also works fine on two other moode systems I have. I've pasted the log from the problematic system below (I'm not sure why I can't attach a text file.) Anyway unless you have some other suggestions, I'm thinking I should just reinstall 7.6.1 from scratch and see if that fixes things.

Code:

--- Log file follows ---

20220115 095436 worker: -- Start
20220115 095436 worker: Successfully daemonized
20220115 095438 worker: Integrity check (passed)
20220115 095443 worker: File check (OK)
20220115 095446 worker: Session vacuumed
20220115 095446 worker: Session loaded
20220115 095446 worker: Debug logging (ON)
20220115 095446 worker: -- Audio debug
20220115 095446 worker: ALSA cards: (0:sndrpihifiberry | 1:empty | 2:empty | 3:empty
20220115 095446 worker: MPD config: (0:HiFiBerry DAC | mixer:(none) | card:0)
20220115 095447 worker: ALSA mixer actual (none)
20220115 095447 worker: ALSA volume (none)
20220115 095447 worker: -- System
20220115 095509 worker: Host     (moode-1)
20220115 095509 worker: moOde    (7.6.1 2021-12-17)
20220115 095509 worker: RaspiOS  (10.6)
20220115 095509 worker: Kernel   (5.4.77+ #1371)
20220115 095509 worker: Platform (Pi-B 1.0 256MB)
20220115 095509 worker: ARM arch (armv6l, 32-bit kernel)
20220115 095509 worker: MPD ver  (0.23.4_p0x3)
20220115 095509 worker: CPU gov  (ondemand)
20220115 095509 worker: USB boot not available
20220115 095509 worker: File system expanded
20220115 095510 worker: HDMI port off
20220115 095510 worker: -- Network
20220115 095510 worker: IP address check timeout (90 secs)
20220115 095510 worker: eth0 adapter exists
20220115 095510 worker: eth0 IP address check (No)
20220115 095510 worker: IP addr (172.17.2.2)
20220115 095510 worker: Netmask (255.255.0.0)
20220115 095510 worker: Gateway (172.17.1.10)
20220115 095511 worker: Pri DNS (172.17.1.10)
20220115 095511 worker: Domain  (localdomain)
20220115 095511 worker: wlan0 adapter does not exist
20220115 095511 worker: -- Audio config
20220115 095513 worker: MPD conf updated
20220115 095513 worker: ALSA card number (0)
20220115 095513 worker: MPD audio output (HiFiBerry DAC)
20220115 095513 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20220115 095513 worker: ALSA mixer name (none)
20220115 095513 worker: MPD mixer type (software)
20220115 095514 worker: Hdwr volume controller not detected
20220115 095514 worker: ALSA output mode (Default: plughw)
20220115 095514 worker: ALSA loopback (Off)
20220115 095514 worker: Reset renderer active flags
20220115 095514 worker: CamillaDSP (off)
20220115 095514 worker: -- MPD startup
20220115 095514 worker: MPD started
20220115 095514 openMpdSocket(): error: connection failed (1) 111, Connection refused
20220115 095515 openMpdSocket(): error: connection failed (2) 111, Connection refused
20220115 095515 openMpdSocket(): error: connection failed (3) 111, Connection refused
20220115 095516 openMpdSocket(): error: connection failed (4) 111, Connection refused
20220115 095516 openMpdSocket(): error: connection failed (5) 111, Connection refused
20220115 095517 worker: MPD accepting connections
20220115 095517 worker: MPD output 1 ALSA Default (on)
20220115 095517 worker: MPD output 2 ALSA Bluetooth (off)
20220115 095517 worker: MPD output 3 HTTP Server (off)
20220115 095517 worker: MPD crossfade (off)
20220115 095517 worker: MPD ignore CUE files (yes)
20220115 095517 worker: -- Feature availability
20220115 095517 worker: Source select (available)
20220115 095517 worker: Source select (source: MPD)
20220115 095517 worker: Source select (output: HiFiBerry DAC)
20220115 095517 worker: Bluetooth (available)
20220115 095517 worker: Airplay renderer (available)
20220115 095517 worker: Spotify renderer (available)
20220115 095517 worker: Squeezelite (available)
20220115 095517 worker: RoonBridge renderer (not installed)
20220115 095517 worker: Multiroom sender (available)
20220115 095517 worker: Multiroom receiver (available)
20220115 095517 worker: UPnP renderer (available)
20220115 095517 worker: DLNA server (available)
20220115 095517 worker: UPnP browser (available)
20220115 095517 worker: GPIO button handler (available)
20220115 095517 worker: Stream recorder (n/a)
20220115 095517 worker: -- Music sources
20220115 095518 worker: USB sources (none attached)
20220115 095519 sourceMount(): Command=(mount -t nfs -o ro,nolock "mothership:/mnt/RaidZ1/media/Audio/JazzPopRock" "/mnt/NAS/mothershipJazzPopRock")
20220115 095519 worker: NAS and UPnP sources (mountall initiated)
20220115 095519 worker: -- Other
20220115 095519 worker: USB volume knob (Off)
20220115 095519 worker: Shellinabox SSH started
20220115 095519 worker: USB auto-mounter (udisks-glue)
20220115 095520 worker: LED0 (On)
20220115 095520 worker: LED1 (On)
20220115 095520 worker: Saved MPD vol level (0)
20220115 095520 worker: Preamp volume level (0)
20220115 095520 worker: MPD volume level (22) restored
20220115 095520 worker: ALSA volume level (None)
20220115 095520 worker: Auto-play (On)
20220115 095520 worker: Auto-playing id (17)
20220115 095520 worker: Maintenance interval (3 hours)
20220115 095520 worker: Screen saver activation (Never)
20220115 095520 worker: Session permissions (OK)
20220115 095520 worker: Watchdog started
20220115 095520 worker: Ready

[Tim Curtis]

Maybe the underpowered 1B is contributing to the issue.

20220115 095509 worker: Platform (Pi-B 1.0 256MB)

[DRONE7]

Hmm, it also works fine on two other moode systems I have. I've pasted the log from the problematic system below (I'm not sure why I can't attach a text file.) Anyway unless you have some other suggestions, I'm thinking I should just reinstall 7.6.1 from scratch and see if that fixes things.

Use code tags for your text file contents...
https://moodeaudio.org/forum/showthread.php?tid=4654

[Busybox]

Maybe the underpowered 1B is contributing to the issue.

20220115 095509 worker: Platform (Pi-B 1.0 256MB)

It's true it's a dinosaur, but it's worked fine up until now. My other two moode systems that work are newer: not sure what versions offhand, but they at least have 40-pin IO connectors. This one has the old 26-pin connector, but the 26-pin audio card I have for it seems to work fine so I'd like to keep it running as long as possible. During normal operations its load factor ranges from 0.20 to 0.30, which I don't think is too bad. But it's slow to boot, taking about 1:20. I wonder if there might be some sort of race condition in the startup sequence that doesn't show up on faster CPUs since they run through their tasks quicker.

Anyway when I restart moode from a browser, sometimes I see a dialog that says:

MPD Error
Unexpected end of JSON input

This line in the log:

20220115 095520 worker: Auto-playing id (17)

sometimes comes up with the proper id and things work, but usually it's a random value, and occasionally it's null like this:

20220115 131825 worker: Auto-playing id ()

in the null case, moode's webpage usually shows the proper id, but auto-play doesn't start. It's as if autoplay wasn't selected.

Hope this helps,

- Steve

[Tim Curtis]

I'd try a fresh image on a new SDCard.

[Busybox]

After backing up moode, I flashed a new SD card with the 7.6.1 image, then did a restore. Everything seemed to restore correctly except all the radio stations in my playlist are missing: those I added from the moode collection, and those I added myself. Perhaps my station data were corrupted to begin with, which could cause all of this. Although my stations didn't restore, I still see the dialog with:

MPD Error
Unexpected end of JSON input

multiple times during the restart process. So I'm not sure if my (corrupted?) station data got "restored" and ignored, or was never restored and there's a different problem. I made a backup of the restored system, and I'll look for differences in the two backups, but is there anything else I can check? I can see that JPGs for stations I added are present in both backups, but I'm not sure how to grok the JSON files. The two JSON files are very close in size: old is 125,894 and new is 125,861.

In any case, "autoplay after start" works as expected now.

- Steve

[TheOldPresbyope]

@Busybox

Are you saying you added custom radio stations via the Library/Radio Folder and then they weren't backed up/restored? That's working for me.

OTOH, I don't think moOde yet backs up/restores custom playlists (but I've been known to be wrong before ).


Regards,
Kent

[Tim Curtis]

Playlists are not backed up by the System Config Backup/Restore utility but they can easily be backed up by copying them from the Samba share named "Playlists".