Hi,
Only one of the MPD outputs should be on. I assume you are not using any of the DSP features so either toggle ON/OFF one of Crossfeed, Parametric EQ or Graphic EQ or alternatively run the command below to enable only the ALSA default output.
mpc enable only 1
I don't know if this will fix the missing id in the log line below.
20180211 134548 worker: Auto-playing id ()
You could also examine MPD status output and verify that it lists a pongid for the last song that was played before rebooting.
pi@rp3:~ $ telnet localhost 6600
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
OK MPD 0.20.0
status
volume: 18
repeat: 0
random: 0
single: 0
consume: 0
playlist: 8
playlistlength: 76
mixrampdb: 0.000000
state: stop
song: 4
songid: 5
nextsong: 5
nextsongid: 6
OK
-Tim
My MPD log is a huge file with track names. The initial portion of the log file is getting erased. Totally confused.
Hi Tim,
this is new output after reboot but autoplay still not working!
Any idea?!
Thank you
Matteo
pi@moode:~ $ cat /var/log/moode.log
20180211 172208 worker: - Start
20180211 172208 worker: Successfully daemonized
20180211 172208 worker: - Init
20180211 172208 worker: Session loaded
20180211 172208 worker: Debug logging (off)
20180211 172212 worker: Host (moode)
20180211 172212 worker: Hdwr (Pi-Zero W 512MB v1.1)
20180211 172212 worker: Arch (armv6l)
20180211 172212 worker: Kver (4.9.79+)
20180211 172212 worker: Ktyp (Standard)
20180211 172212 worker: Gov (performance)
20180211 172212 worker: Rel (Moode 4.0 2018-01-26)
20180211 172212 worker: Upd (None)
20180211 172212 worker: MPD (0.20.12)
20180211 172212 worker: USB boot not enabled yet
20180211 172212 worker: File system expanded
20180211 172212 worker: HDMI port on
20180211 172213 worker: File check ok
20180211 172213 worker: - Network
20180211 172214 worker: eth0 does not exist
20180211 172214 worker: eth0 address not assigned
20180211 172214 worker: wlan0 exists
20180211 172214 worker: wlan0 trying SSID (G&M)
20180211 172214 worker: wlan0 (192.168.1.190)
20180211 172214 worker: - Audio
20180211 172214 worker: ALSA outputs unmuted
20180211 172214 worker: Audio output (USB audio device)
20180211 172215 worker: ALSA mixer name (Mic)
20180211 172215 worker: MPD volume control (disabled)
20180211 172215 worker: Hdwr volume controller exists
20180211 172215 worker: - Services
20180211 172217 worker: MPD started
20180211 172217 worker: MPD scheduler policy (time-share)
20180211 172217 worker: MPD output 1 ALSA default (on)
20180211 172217 worker: MPD output 2 ALSA crossfeed (off)
20180211 172218 worker: MPD output 3 ALSA parametric eq (off)
20180211 172218 worker: MPD output 4 ALSA graphic eq (off)
20180211 172218 worker: MPD crossfade (off)
20180211 172218 worker: - Last
20180211 172218 worker: USB sources (none attached)
20180211 172218 worker: NAS sources (mountall initiated)
20180211 172218 worker: Volume level (0) restored
20180211 172218 worker: Auto-playing id (1)
20180211 172218 worker: Maintenance interval (21600)
20180211 172218 worker: Watchdog started
20180211 172218 worker: Ready
Hi Guys,
Newbie here. I've just come back to look at Moode Volumio to make a player for the office. I have tested Moode on Pi3 and it has worked really well and the BT is better. I know it is not hi fidelity, but I use the bluetooth option to play to a speaker in the office which allows anyone to shut it off on the web interface when we get a call.
Having tested it with music on the server and a number of radio stations, I rebuilt Moode on a Pi Zero W thinking it would be a great little player for BT. I think there is a lot of potential to stuff these into older devices.
The Zero runs fine generally at first. Setting the background image was a bit glitchy. We normally stream 6music, but I had a crash when tried to change radio statio after 1-2hrs and Pi wouldn't come back after that.
If it connects at all, the web interface only partly loads. I gave up and plugged in the Pi3.
To try and test it I had to reimage the Pi from my back-up and ran it for 5hrs yesterday on one radio station with "htop" running over shh. It never hit more than 20% processor and stayed cool. I tried to change the radio station again and all hell broke loose, same as before.
I don't really know where to start diagnosing this, but I am rebuilding on another SD card in case that was the fault.
Is there a known issue with Pi zeros, am I expecting too much form it?
Interfacing is generally over WIFI after inital setup. Using a USB ethernet doesn't help. The interface is still crashed. Htop doesn't show much load during or after the crash.
Regards,
Frank
Newbie here. I've just come back to look at Moode Volumio to make a player for the office. I have tested Moode on Pi3 and it has worked really well and the BT is better. I know it is not hi fidelity, but I use the bluetooth option to play to a speaker in the office which allows anyone to shut it off on the web interface when we get a call.
Having tested it with music on the server and a number of radio stations, I rebuilt Moode on a Pi Zero W thinking it would be a great little player for BT. I think there is a lot of potential to stuff these into older devices.
The Zero runs fine generally at first. Setting the background image was a bit glitchy. We normally stream 6music, but I had a crash when tried to change radio statio after 1-2hrs and Pi wouldn't come back after that.
If it connects at all, the web interface only partly loads. I gave up and plugged in the Pi3.
To try and test it I had to reimage the Pi from my back-up and ran it for 5hrs yesterday on one radio station with "htop" running over shh. It never hit more than 20% processor and stayed cool. I tried to change the radio station again and all hell broke loose, same as before.
I don't really know where to start diagnosing this, but I am rebuilding on another SD card in case that was the fault.
Is there a known issue with Pi zeros, am I expecting too much form it?
Interfacing is generally over WIFI after inital setup. Using a USB ethernet doesn't help. The interface is still crashed. Htop doesn't show much load during or after the crash.
Regards,
Frank
Hi,
log shows "Auto-playing id (1)"
I'd check mpd log to confirm that MPD actually was successful at playing songid 1.
-Tim
Also other radio give the same error with autoplay but function with play button!
Feb 11 17:45 : player: played "http://stream.srg-ssr.ch/m/rsp/mp3_128"
Feb 11 17:46 : exception: Not seekable
Feb 11 18:04 : player: played "http://lb.zenfm.be/zenfm.mp3"
Feb 11 18:05 : exception: Not seekable
Feb 11 17:45 : player: played "http://stream.srg-ssr.ch/m/rsp/mp3_128"
Feb 11 17:46 : exception: Not seekable
Feb 11 18:04 : player: played "http://lb.zenfm.be/zenfm.mp3"
Feb 11 18:05 : exception: Not seekable
The symptom would suggest that Internet is not yet reachable when auto-play is attempted at the end of moOde startup sequence.
Maybe try checking Router logs?
-Tim
Ah! Thanks Tim, that was indeed the case. These functions are fabulous, I'm finally getting my speakers balanced to match my damaged hearing range. Thanks for your wonderful program. Donation headed yer way.
Last edited:
The donation is much appreciated. Thanks for your support!
Its not something I would add to moOde without confirming that in fact "Internet not reachable at end of startup" is a more common failure case. My own Zero-W does not exhibit this. Autoplay works fine.
-Tim
I do find a raspotify(moode) device in Spotify and can connect, no sound at all is the result. Im using a USB Creative Labs X-fi HD. No problems playing radio or files.
Never hand modify the Raspotify/Librespot files, or don't mod Moose files?
Last edited:
Hi.
Can anyone help me trigger a WiFi or similar switch to turn off my amp when the playlist finishes?
Case:
1.- RPi 3B+ MoOde 4.0 > miniDSP > Tube Amp/Sub.
2.- The Tube Amp generated a LOT of heat ~250c, uses 340w constantly and has no auto off.
3.- I sometimes fall asleep.
I'd like to trigger something to kill the power.
Btw I'm a MoOde/RPi/Linux n00b.
Thanks.
Can anyone help me trigger a WiFi or similar switch to turn off my amp when the playlist finishes?
Case:
1.- RPi 3B+ MoOde 4.0 > miniDSP > Tube Amp/Sub.
2.- The Tube Amp generated a LOT of heat ~250c, uses 340w constantly and has no auto off.
3.- I sometimes fall asleep.
I'd like to trigger something to kill the power.
Btw I'm a MoOde/RPi/Linux n00b.
Thanks.
Interesting project idea...
You would need to get some kind flag from Moode (or internal part therof) indicating that playing is occurring, have it set some kind of watchdog timer that would time out X amount of time after playing stopped. Then, you'd need a piece of external hardware that could give a 12v trigger, or drive a 15A relay to switch the AC to the amp, depending on what you need, that the timer would control thru one of the Pi I/O pins. Tada... a "shut amp off X min after last play" device and feature.
A doable thing, unfortunately not really a Pi programming and electronics hardware newbie thing. I could help w the hardware, if you really want this. OTOH, are there WiFi controlled power strips out there? Then its all on the software side. Wonder how many might want something like this?
Thanks.
I think I can handle the relay/HW and RPi call to it, I just need the trigger from MoOde.
My MoOde experience started last night, but if it could call an endpoint with it's status I could handle the rest.
I currently use a WiFi switch (so I can get Alexa to turn it off WeMo), I also have a IR relay switch I can use... there are RPi relay boards (Raspberry Pi Relay Board v1.0 - Boards for Raspberry pi - Seeed Studio) and there are sample RPi projects controlling WeMo (Raspberry Pi WEMO Control Center: 8 Steps).
Last edited: