Moode Audio Player for Raspberry Pi

I had the same issue
Tried a different sd card and all is well.




Hello Tim!
Thank you for the latest release! been waiting for quite a while for that one :)
I have installed the latest version using the image builder, and everything seemed to go to plan with the pi rebooting several times, as I was watching the process using moslog.
After the final step, everything seemed to work fine and I was able to access the pi using the browser.
But then a problem arose: everytime I try to navigate between configuration windows (from source to network or any other option) the interface hangs, and then very briefly flashes (Had to slo mo film it to read it) "Reconnect system rebooting" and then back.
Any idea why that might be?
(attached pics below)
To be noted that any changes do not get saved anymore, And as such I am unable to mount my NAS drive nor a usb hard drive
 
Downloaded latest version again and saved to sdcard (used usb boot last time), set it up via wifi in the bedroom, running with no problems. Moved it to the living room and same problem as last time, moode not connecting via wifi, Fing on my ipad reports pi as connected but it will not boot into moode. Replaced sdcard with card with Volumio 2 and booted first time no problem. Any one have any ideas? Thinking of trying a static ip address for wifi, worked with no problems on earlier versions of moode.
 
Downloaded latest version again and saved to sdcard (used usb boot last time), set it up via wifi in the bedroom, running with no problems. Moved it to the living room and same problem as last time, moode not connecting via wifi, Fing on my ipad reports pi as connected but it will not boot into moode. Replaced sdcard with card with Volumio 2 and booted first time no problem. Any one have any ideas? Thinking of trying a static ip address for wifi, worked with no problems on earlier versions of moode.

@kit1cat

I'm having trouble connecting the dots.

1) when you say "running with no problems" in the bedroom, do you mean moOde is running on your Pi and you can communicate with it from your iPad through the moOde UI?

2) when you say "moode not connecting via wifi" in the living room, do you mean you can't communicate with it from your iPad through the moOde UI? What does your browser report? Something like "this site can't be reached"?

3) when you say "Fing on my ipad reports pi as connected" do you mean the entry in Fing's Devices list for your moOde pi is in bold and when you select it you get "Device is online" among other things? [note, I'm using Fing on an Android device so the screens may vary.]

4) I don't understand "but it will not boot into moOde." I have to assume you mean what I described in 2).

If the answer to 3) is true then your moOde Pi has booted and its WiFi interface is active. Have you looked at your router/access point's administration page(s) to see what it reports about this host? Have you tried to ping this host from another device? Have you tried to ssh into it?

What model Pi are you using? If a RPi3B or RPi0W, are you using the onboard WiFi transceiver or an external USB-WiFi adapter? In the living room, is the Pi buried in a cabinet, surrounded by wires, or otherwise in a difficult WiFi environment? Are you using the same power supply in the bedroom and living room?

I don't know why a static IP address would make a difference. Fing (or your router) will tell you the address that has been assigned. (Depending on your router setup, it is possible for the IP address to change when you shut off your Pi in the bedroom and reboot it in the living room.)

When you try to connect to your Pi do you used the numeric IP address or do you use the hostname? ("moode" is the default, but you know there's lots of variations among routers which may dictate adding a domain name.)

Without delving into Volumio 2's networking code, I don't have a clue why you can connect to it and not to moOde. Naively, I would not expect much difference in the two players' system-level networking code.

Regards,
Kent
 
Hi @kit1cat,

Post output from System info.

-Tim

Hi Tim, system info

S Y S T E M P A R A M E T E R S

Date and time = 2018-02-01 16:12:51
System uptime = up 1 minute
Timezone = Europe/London
moOde = Release 4.0 2018-01-26

Host name = moode
ETH0 IP = unassigned
ETH0 MAC = b8:27:eb:0f:c8:0f
WLAN0 IP = 192.168.1.215
WLAN0 MAC = b8:27:eb:5a:9d:5a

HDWR REV = Pi-3B 1GB v1.2
SoC = BCM2835
CORES = 4
ARCH = armv7l
KERNEL = 4.9.79-v7+
KTIMER FREQ = 100 Hz
USB BOOT = enabled
Warranty = OK

ROOT size = 2.9G
ROOT used = 75%
ROOT avail = 697M
FS expand = not expanded
MEM free = 718 MB
MEM used = 53 MB
Temperature = 35.9°C

CPU GOV = performance
MPD SCHDPOL = TS
P3-WIFI = On
P3-BT = Off
HDMI = Off
ETH0 CHECK = Off
MAX USB CUR = Off
UAC2 FIX = Off
SSH server = Off

LED0 = on
LED1 = on

C O R E S E R V E R S

PHP-FPM = 7.0.27
NGINX = 1.10.3
SQLite = 3.16.2
Bluetooth = 5.43

C P U L O A D

CPU %usr %sys %idle
all 0.13 0.00 99.87
0 0.00 0.00 100.00
1 0.00 0.00 100.00
2 0.50 0.00 99.50
3 0.00 0.00 100.00

P R O C E S S L O A D

PRI RTPRIO COMMAND %MEM PSR %CPU
19 - systemd 0.6 1 2.0
19 - sysinfo.sh 0.2 3 1.3
19 - systemd-journal 0.4 0 0.6
19 - systemd-udevd 0.3 3 0.5
29 - mpd 2.1 2 0.4
19 - sudo 0.3 2 0.3
19 - mmcqd/0 0.0 1 0.2
19 - worker.php 1.1 2 0.2
19 - kworker/1:3 0.0 1 0.1

C L O C K F R E Q U E N C I E S

arm = 1200 MHz pwm = 0 MHz
core = 400 MHz emmc = 249 MHz
h264 = 300 MHz pixel = 0 MHz
isp = 300 MHz vec = 0 MHz
v3d = 300 MHz hdmi = 0 MHz
uart = 47 MHz dpi = 0 MHz

SD card = 50 MHz

S Y S T E M V O L T A G E S

core = 1.3250V
sdram controller = 1.2000V
sdram I/O = 1.2000V
sdram chip = 1.2250V

cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory
cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory
U I C U S T O M I Z A T I O N S

Theme = Standard
Accent color = Amethyst
Alpha blend = 1.0
Adaptive background = No
Background image = No
Playback history = No
Extra metadata = Yes
Library = Use Artist

A U D I O P A R A M E T E R S

Audio device = Allo Boss DAC
Interface = I2S
Hdwr volume = Invalid card number.
Mixer name = Digital
Output stream = Closed
ALSA version = 1.1.3-5+rpi3
SoX version = 0.1.2-2

Volume knob = 44
Volume mute = Off
Volume limit = 80

Bluetooth controller = Off
Airplay receiver = On
Squeezelite = Off
UPnP renderer = Off
DLNA server = Off

Rotary encoder = Off
Encoder params = 100 2 3 4 5
Crossfeed = Off
Parametric EQ = Off
Graphic EQ = Off
Auto-shuffle = Off
Autoplay = Off
MPD crossfade = Off

M P D S E T T I N G S

Version = 0.20.12
Volume control = hardware
ALSA device = hw:0
SoX resampling = disabled
SoX quality = very high
SoX multithreading = off
Audio buffer (kb) = 4096
Buffer before play = 10%
Output buffer size (kb) = 81920
Volume normalization = no
DSD over PCM (DoP) = no
Replay gain = off

A I R P L A Y S E T T I N G S

Version = 3.1.7
Friendly name = Moode Airplay
Metadata display = Off
ALSA device = hw:0
Volume mixer = auto
Resume MPD after = No
Output bit depth = S16
Output sample rate = 44100
Session interruption = no
Session timeout (ms) = 120
Audio buffer (secs) = 0.0

S Q U E E Z E L I T E S E T T I N G S

Version = 1.8.7-1020 "DSD/SRC enabled"
Friendly name = Moode
ALSA device = hw:0
ALSA params = 80:4::1
Output buffers = 40000:100000
Task priority = 45
Codec list = flac,pcm,mp3,ogg,aac,alac,dsd
Other options = -W -D 500 -R E

M O O D E L O G

20180201 160942 worker: - Start
20180201 160942 worker: Successfully daemonized
20180201 160942 worker: - Init
20180201 160942 worker: Session loaded
20180201 160942 worker: Debug logging (off)
20180201 160944 worker: Host (moode)
20180201 160944 worker: Hdwr (Pi-3B 1GB v1.2)
20180201 160944 worker: Arch (armv7l)
20180201 160944 worker: Kver (4.9.79-v7+)
20180201 160944 worker: Ktyp (Standard)
20180201 160944 worker: Gov (performance)
20180201 160944 worker: Rel (Moode 4.0 2018-01-26)
20180201 160944 worker: Upd (None)
20180201 160944 worker: MPD (0.20.12)
20180201 160944 worker: USB boot enabled
20180201 160944 worker: File system not expanded yet
20180201 160944 worker: HDMI port off
20180201 160944 worker: File check ok
20180201 160944 worker: - Network
20180201 160944 worker: eth0 exists
20180201 160945 worker: eth0 address not assigned
20180201 160945 worker: wlan0 exists
20180201 160945 worker: wlan0 trying SSID (Belkinb17a7c)
20180201 160945 worker: wlan0 (192.168.1.215)
20180201 160945 worker: - Audio
20180201 160945 worker: ALSA outputs unmuted
20180201 160945 worker: Audio out (I2S audio device)
20180201 160945 worker: Audio dev (Allo Boss DAC)
20180201 160945 worker: ALSA mixer name (Digital)
20180201 160945 worker: MPD volume control (hardware)
20180201 160945 worker: Hdwr volume controller exists
20180201 160945 worker: Chip options (Burr Brown PCM5122)
20180201 160945 worker: - Services
20180201 160947 worker: MPD started
20180201 160947 worker: MPD scheduler policy (time-share)
20180201 160947 worker: MPD output 1 ALSA default (on)
20180201 160947 worker: MPD output 2 ALSA crossfeed (on)
20180201 160947 worker: MPD output 3 ALSA parametric eq (on)
20180201 160947 worker: MPD output 4 ALSA graphic eq (on)
20180201 160947 worker: MPD crossfade (off)
20180201 160947 worker: Airplay receiver started
20180201 160947 worker: Airplay volume mgt (auto)
20180201 160947 worker: - Last
20180201 160947 worker: USB sources (Ext Drive)
20180201 160947 worker: NAS sources (mountall initiated)
20180201 160947 worker: Volume level (44) restored
20180201 160947 worker: Maintenance interval (21600)
20180201 160947 worker: Watchdog started
20180201 160947 worker: Ready
 
@kit1cat

I'm having trouble connecting the dots.

1) when you say "running with no problems" in the bedroom, do you mean moOde is running on your Pi and you can communicate with it from your iPad through the moOde UI?

2) when you say "moode not connecting via wifi" in the living room, do you mean you can't communicate with it from your iPad through the moOde UI? What does your browser report? Something like "this site can't be reached"?

3) when you say "Fing on my ipad reports pi as connected" do you mean the entry in Fing's Devices list for your moOde pi is in bold and when you select it you get "Device is online" among other things? [note, I'm using Fing on an Android device so the screens may vary.]

4) I don't understand "but it will not boot into moOde." I have to assume you mean what I described in 2).

If the answer to 3) is true then your moOde Pi has booted and its WiFi interface is active. Have you looked at your router/access point's administration page(s) to see what it reports about this host? Have you tried to ping this host from another device? Have you tried to ssh into it?

What model Pi are you using? If a RPi3B or RPi0W, are you using the onboard WiFi transceiver or an external USB-WiFi adapter? In the living room, is the Pi buried in a cabinet, surrounded by wires, or otherwise in a difficult WiFi environment? Are you using the same power supply in the bedroom and living room?

I don't know why a static IP address would make a difference. Fing (or your router) will tell you the address that has been assigned. (Depending on your router setup, it is possible for the IP address to change when you shut off your Pi in the bedroom and reboot it in the living room.)

When you try to connect to your Pi do you used the numeric IP address or do you use the hostname? ("moode" is the default, but you know there's lots of variations among routers which may dictate adding a domain name.)

Without delving into Volumio 2's networking code, I don't have a clue why you can connect to it and not to moOde. Naively, I would not expect much difference in the two players' system-level networking code.

Regards,
Kent

Hi Kent, thanks for your reply.

answer to questions 1 to 4 are yes.

not checked my router, but it has been working fine with my other items.

pi3 with onboard wifi, pi is in an open cabinet and has been working via wifi for months with only minor problems, I normally connect using ip address. I am using a different power supply in the living room.
 
Security

Gentle persons:

Several of us have posted in past years about following good computer security practices at home and with moOde.

Almost everything you enter in moOde is stored in clear text. This includes your WiFi credentials and your TIDAL, Google Play Music, and QOBUZ credentials. I suspect this is true for many rival players as well.

Now that I have tested that Google Play Music works in moOde 4.0 I think I'm going to delete my account from it. Why? While the other music services stand alone, your Google Play Music credentials are your Google account credentials. If someone were to grab them and you haven't enabled two-factor authentication in Google, then they could impersonate you on Gmail, buy items on your account in the Google Play Store, and otherwise do material harm.

Obviously, two-factor authentication is becoming a necessity on the Google end, yet a recent report says fewer than 1 in 10 Gmail users have enabled it. On the home front, a strong firewall on your network, use of good non-default login passwords everywhere, and other good security practices should be employed but I'd bet the 1-in-10 number applies here too.

Just my gloomy 2-cents worth.

Regards,
Kent
 
Hi Tim, system info

S Y S T E M P A R A M E T E R S

Date and time = 2018-02-01 16:12:51
System uptime = up 1 minute
Timezone = Europe/London
moOde = Release 4.0 2018-01-26

Host name = moode
ETH0 IP = unassigned
ETH0 MAC = b8:27:eb:0f:c8:0f
WLAN0 IP = 192.168.1.215
WLAN0 MAC = b8:27:eb:5a:9d:5a

HDWR REV = Pi-3B 1GB v1.2
SoC = BCM2835
CORES = 4
ARCH = armv7l
KERNEL = 4.9.79-v7+
KTIMER FREQ = 100 Hz
USB BOOT = enabled
Warranty = OK

ROOT size = 2.9G
ROOT used = 75%
ROOT avail = 697M
FS expand = not expanded
MEM free = 718 MB
MEM used = 53 MB
Temperature = 35.9°C

CPU GOV = performance
MPD SCHDPOL = TS
P3-WIFI = On
P3-BT = Off
HDMI = Off
ETH0 CHECK = Off
MAX USB CUR = Off
UAC2 FIX = Off
SSH server = Off

LED0 = on
LED1 = on

C O R E S E R V E R S

PHP-FPM = 7.0.27
NGINX = 1.10.3
SQLite = 3.16.2
Bluetooth = 5.43

C P U L O A D

CPU %usr %sys %idle
all 0.13 0.00 99.87
0 0.00 0.00 100.00
1 0.00 0.00 100.00
2 0.50 0.00 99.50
3 0.00 0.00 100.00

P R O C E S S L O A D

PRI RTPRIO COMMAND %MEM PSR %CPU
19 - systemd 0.6 1 2.0
19 - sysinfo.sh 0.2 3 1.3
19 - systemd-journal 0.4 0 0.6
19 - systemd-udevd 0.3 3 0.5
29 - mpd 2.1 2 0.4
19 - sudo 0.3 2 0.3
19 - mmcqd/0 0.0 1 0.2
19 - worker.php 1.1 2 0.2
19 - kworker/1:3 0.0 1 0.1

C L O C K F R E Q U E N C I E S

arm = 1200 MHz pwm = 0 MHz
core = 400 MHz emmc = 249 MHz
h264 = 300 MHz pixel = 0 MHz
isp = 300 MHz vec = 0 MHz
v3d = 300 MHz hdmi = 0 MHz
uart = 47 MHz dpi = 0 MHz

SD card = 50 MHz

S Y S T E M V O L T A G E S

core = 1.3250V
sdram controller = 1.2000V
sdram I/O = 1.2000V
sdram chip = 1.2250V

cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory
cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory
U I C U S T O M I Z A T I O N S

Theme = Standard
Accent color = Amethyst
Alpha blend = 1.0
Adaptive background = No
Background image = No
Playback history = No
Extra metadata = Yes
Library = Use Artist

A U D I O P A R A M E T E R S

Audio device = Allo Boss DAC
Interface = I2S
Hdwr volume = Invalid card number.
Mixer name = Digital
Output stream = Closed
ALSA version = 1.1.3-5+rpi3
SoX version = 0.1.2-2

Volume knob = 44
Volume mute = Off
Volume limit = 80

Bluetooth controller = Off
Airplay receiver = On
Squeezelite = Off
UPnP renderer = Off
DLNA server = Off

Rotary encoder = Off
Encoder params = 100 2 3 4 5
Crossfeed = Off
Parametric EQ = Off
Graphic EQ = Off
Auto-shuffle = Off
Autoplay = Off
MPD crossfade = Off

M P D S E T T I N G S

Version = 0.20.12
Volume control = hardware
ALSA device = hw:0
SoX resampling = disabled
SoX quality = very high
SoX multithreading = off
Audio buffer (kb) = 4096
Buffer before play = 10%
Output buffer size (kb) = 81920
Volume normalization = no
DSD over PCM (DoP) = no
Replay gain = off

A I R P L A Y S E T T I N G S

Version = 3.1.7
Friendly name = Moode Airplay
Metadata display = Off
ALSA device = hw:0
Volume mixer = auto
Resume MPD after = No
Output bit depth = S16
Output sample rate = 44100
Session interruption = no
Session timeout (ms) = 120
Audio buffer (secs) = 0.0

S Q U E E Z E L I T E S E T T I N G S

Version = 1.8.7-1020 "DSD/SRC enabled"
Friendly name = Moode
ALSA device = hw:0
ALSA params = 80:4::1
Output buffers = 40000:100000
Task priority = 45
Codec list = flac,pcm,mp3,ogg,aac,alac,dsd
Other options = -W -D 500 -R E

M O O D E L O G

20180201 160942 worker: - Start
20180201 160942 worker: Successfully daemonized
20180201 160942 worker: - Init
20180201 160942 worker: Session loaded
20180201 160942 worker: Debug logging (off)
20180201 160944 worker: Host (moode)
20180201 160944 worker: Hdwr (Pi-3B 1GB v1.2)
20180201 160944 worker: Arch (armv7l)
20180201 160944 worker: Kver (4.9.79-v7+)
20180201 160944 worker: Ktyp (Standard)
20180201 160944 worker: Gov (performance)
20180201 160944 worker: Rel (Moode 4.0 2018-01-26)
20180201 160944 worker: Upd (None)
20180201 160944 worker: MPD (0.20.12)
20180201 160944 worker: USB boot enabled
20180201 160944 worker: File system not expanded yet
20180201 160944 worker: HDMI port off
20180201 160944 worker: File check ok
20180201 160944 worker: - Network
20180201 160944 worker: eth0 exists
20180201 160945 worker: eth0 address not assigned
20180201 160945 worker: wlan0 exists
20180201 160945 worker: wlan0 trying SSID (Belkinb17a7c)
20180201 160945 worker: wlan0 (192.168.1.215)
20180201 160945 worker: - Audio
20180201 160945 worker: ALSA outputs unmuted
20180201 160945 worker: Audio out (I2S audio device)
20180201 160945 worker: Audio dev (Allo Boss DAC)
20180201 160945 worker: ALSA mixer name (Digital)
20180201 160945 worker: MPD volume control (hardware)
20180201 160945 worker: Hdwr volume controller exists
20180201 160945 worker: Chip options (Burr Brown PCM5122)
20180201 160945 worker: - Services
20180201 160947 worker: MPD started
20180201 160947 worker: MPD scheduler policy (time-share)
20180201 160947 worker: MPD output 1 ALSA default (on)
20180201 160947 worker: MPD output 2 ALSA crossfeed (on)
20180201 160947 worker: MPD output 3 ALSA parametric eq (on)
20180201 160947 worker: MPD output 4 ALSA graphic eq (on)

20180201 160947 worker: MPD crossfade (off)
20180201 160947 worker: Airplay receiver started
20180201 160947 worker: Airplay volume mgt (auto)
20180201 160947 worker: - Last
20180201 160947 worker: USB sources (Ext Drive)
20180201 160947 worker: NAS sources (mountall initiated)
20180201 160947 worker: Volume level (44) restored
20180201 160947 worker: Maintenance interval (21600)
20180201 160947 worker: Watchdog started
20180201 160947 worker: Ready

The items in red indicate some breakage somewhere in your build or config.

There should only be 1 MPD output on. This can be fixed by either toggling one of the DSP features on/off or by cmd: mpc enable only 1.

The other items indicate an error reading the hardware (ALSA) volume for your DAC. This should never occur.

-Tim
 
Hi Kent, thanks for your reply.

answer to questions 1 to 4 are yes.

not checked my router, but it has been working fine with my other items.

pi3 with onboard wifi, pi is in an open cabinet and has been working via wifi for months with only minor problems, I normally connect using ip address. I am using a different power supply in the living room.

Hmmm. Do you have the onboard BlueTooth interface enabled as well? Posters on a number of Pi forums have reported difficulties with the RPi3B's integrated WiFi/Bluetooth capability vis-a-vis individual signal strength and mutual interaction.

In my case, I have an RPi3B in an entertainment cabinet which also contains other WiFi and Bluetooth sources (such as a Roku player), not to mention a rats-nest of cables. I disabled the integrated WiFi on the Pi and added an external WiFi adapter on the end of an 18-in USB extension to get it out to clear space behind the cabinet. The WiFi connection seem quite robust.

As for the different power supply, keep in mind that the RPi3B is more power-hungry that its predecessors. Opinions vary, but I try to use reputable supplies rated at or above 2.5 amp current capacity.

Hope you can find a solution.

[Added in edit] now that I've seen Tim's reply above I think you should first fix your build problems before chasing WiFi.

Regards,
Kent
 
Last edited:
Did you perform this task?



I don't know if it is pertinent to your problem or not :dunno::)
Just guessing:rolleyes:

ronnie

That step can be done once LocalUI starts and I see the browser. But seconds after localUI starts, I get that error, and the whole system becomes unresponsive. The only thing I have managed to do is to connect through ssh and disable localui. Then the system works ok (without touchscreen, that is).

In another SD card I have MoOde Beta 11, working ok with Touchscreen. If I put in that card, everything works ok.

I may to build for a third time, but first I'd like to know this is even possible.

Can somebody confirm they have MoOde 4.0 working with an official Touchscreen?
 
Gentle persons:

Several of us have posted in past years about following good computer security practices at home and with moOde.

Almost everything you enter in moOde is stored in clear text. This includes your WiFi credentials and your TIDAL, Google Play Music, and QOBUZ credentials. I suspect this is true for many rival players as well.

Now that I have tested that Google Play Music works in moOde 4.0 I think I'm going to delete my account from it. Why? While the other music services stand alone, your Google Play Music credentials are your Google account credentials. If someone were to grab them and you haven't enabled two-factor authentication in Google, then they could impersonate you on Gmail, buy items on your account in the Google Play Store, and otherwise do material harm.

Obviously, two-factor authentication is becoming a necessity on the Google end, yet a recent report says fewer than 1 in 10 Gmail users have enabled it. On the home front, a strong firewall on your network, use of good non-default login passwords everywhere, and other good security practices should be employed but I'd bet the 1-in-10 number applies here too.

Just my gloomy 2-cents worth.

Regards,
Kent
As a couple of extras.

For Qobuz you can enter the MD5 hash of your password, this does not work on the website only the API.

For Google you should enable 2fa and then assign an application password to your mood player. There is a link upmpdcli website I will try and dig up.

I think this is why the upmpdcli programmer tried to change the owner and permissions on the config file to the upmpdcli user. However that seemed to cause issues.
 
As a couple of extras.

For Qobuz you can enter the MD5 hash of your password, this does not work on the website only the API.

For Google you should enable 2fa and then assign an application password to your mood player. There is a link upmpdcli website I will try and dig up.

I think this is why the upmpdcli programmer tried to change the owner and permissions on the config file to the upmpdcli user. However that seemed to cause issues.
Of course these are not total mitigations and Kent's recommendations about your firewall and changing your Moode PW are advisable.
 
Hi Tim,

I ran the mpc enable only 1 command on my first build, can you see any other errors in my system info file, thanks.

S Y S T E M P A R A M E T E R S

Date and time = 2018-02-01 17:56:52
System uptime = up 5 minutes
Timezone = Europe/London
moOde = Release 4.0 2018-01-26

Host name = moode
ETH0 IP = unassigned
ETH0 MAC = b8:27:eb:0f:c8:0f
WLAN0 IP = 192.168.1.215
WLAN0 MAC = b8:27:eb:5a:9d:5a

HDWR REV = Pi-3B 1GB v1.2
SoC = BCM2835
CORES = 4
ARCH = armv7l
KERNEL = 4.9.78-v7+
KTIMER FREQ = 100 Hz
USB BOOT = enabled
Warranty = OK

ROOT size = 2.9G
ROOT used = 76%
ROOT avail = 693M
FS expand = not expanded
MEM free = 713 MB
MEM used = 54 MB
Temperature = 41.9°C

CPU GOV = performance
MPD SCHDPOL = TS
P3-WIFI = On
P3-BT = Off
HDMI = Off
ETH0 CHECK = Off
MAX USB CUR = Off
UAC2 FIX = Off
SSH server = Off

LED0 = on
LED1 = on

C O R E S E R V E R S

PHP-FPM = 7.0.27
NGINX = 1.10.3
SQLite = 3.16.2
Bluetooth = 5.43

C P U L O A D

CPU %usr %sys %idle
all 0.00 1.15 98.85
0 0.00 0.00 100.00
1 0.00 0.00 100.00
2 0.00 4.81 95.19
3 0.00 0.00 100.00

P R O C E S S L O A D

PRI RTPRIO COMMAND %MEM PSR %CPU
19 - kworker/2:2 0.0 2 8.4
19 - sysinfo.sh 0.2 3 2.0
19 - systemd 0.6 1 0.6
19 - sudo 0.3 1 0.5
19 - systemd-journal 0.4 1 0.2
19 - systemd-udevd 0.3 3 0.2
19 - worker.php 1.1 1 0.2
29 - mpd 2.0 0 0.1
19 - kthreadd 0.0 2 0.0

C L O C K F R E Q U E N C I E S

arm = 1200 MHz pwm = 0 MHz
core = 400 MHz emmc = 249 MHz
h264 = 300 MHz pixel = 0 MHz
isp = 300 MHz vec = 0 MHz
v3d = 300 MHz hdmi = 0 MHz
uart = 47 MHz dpi = 0 MHz

SD card = 0.195217 MHz

S Y S T E M V O L T A G E S

core = 1.3250V
sdram controller = 1.2000V
sdram I/O = 1.2000V
sdram chip = 1.2250V

U I C U S T O M I Z A T I O N S

Theme = Standard
Accent color = Emerald
Alpha blend = 1.0
Adaptive background = No
Background image = No
Playback history = No
Extra metadata = Yes
Library = Use Artist

A U D I O P A R A M E T E R S

Audio device = Allo Boss DAC
Interface = I2S
Hdwr volume = 84
Mixer name = Digital
Output stream = Closed
ALSA version = 1.1.3-5+rpi3
SoX version = 0.1.2-2

Volume knob = 52
Volume mute = Off
Volume limit = 80

Bluetooth controller = Off
Airplay receiver = On
Squeezelite = Off
UPnP renderer = Off
DLNA server = Off

Rotary encoder = Off
Encoder params = 100 2 3 4 5
Crossfeed = Off
Parametric EQ = Off
Graphic EQ = Off
Auto-shuffle = Off
Autoplay = Off
MPD crossfade = Off

M P D S E T T I N G S

Version = 0.20.12
Volume control = hardware
ALSA device = hw:0
SoX resampling = disabled
SoX quality = very high
SoX multithreading = off
Audio buffer (kb) = 4096
Buffer before play = 10%
Output buffer size (kb) = 81920
Volume normalization = no
DSD over PCM (DoP) = no
Replay gain = off

A I R P L A Y S E T T I N G S

Version = 3.1.7
Friendly name = Moode Airplay
Metadata display = Off
ALSA device = hw:0
Volume mixer = auto
Resume MPD after = No
Output bit depth = S16
Output sample rate = 44100
Session interruption = no
Session timeout (ms) = 120
Audio buffer (secs) = 0.0

S Q U E E Z E L I T E S E T T I N G S

Version = 1.8.7-1020 "DSD/SRC enabled"
Friendly name = Moode
ALSA device = hw:0
ALSA params = 80:4::1
Output buffers = 40000:100000
Task priority = 45
Codec list = flac,pcm,mp3,ogg,aac,alac,dsd
Other options = -W -D 500 -R E

M O O D E L O G

20180201 174919 worker: - Start
20180201 174919 worker: Successfully daemonized
20180201 174919 worker: - Init
20180201 174919 worker: Session loaded
20180201 174919 worker: Debug logging (off)
20180201 174920 worker: Host (moode)
20180201 174920 worker: Hdwr (Pi-3B 1GB v1.2)
20180201 174920 worker: Arch (armv7l)
20180201 174920 worker: Kver (4.9.78-v7+)
20180201 174920 worker: Ktyp (Standard)
20180201 174920 worker: Gov (performance)
20180201 174921 worker: Rel (Moode 4.0 2018-01-26)
20180201 174921 worker: Upd (None)
20180201 174921 worker: MPD (0.20.12)
20180201 174921 worker: USB boot enabled
20180201 174921 worker: File system not expanded yet
20180201 174921 worker: HDMI port off
20180201 174921 worker: File check ok
20180201 174921 worker: - Network
20180201 174921 command/moode: Connection to MPD failed
20180201 174921 worker: eth0 exists
20180201 174921 worker: eth0 address not assigned
20180201 174921 worker: wlan0 exists
20180201 174921 worker: wlan0 trying SSID (Belkinb17a7c)
20180201 174921 worker: wlan0 (192.168.1.215)
20180201 174921 worker: - Audio
20180201 174922 worker: ALSA outputs unmuted
20180201 174922 worker: Audio out (I2S audio device)
20180201 174922 worker: Audio dev (Allo Boss DAC)
20180201 174922 worker: ALSA mixer name (Digital)
20180201 174922 worker: MPD volume control (hardware)
20180201 174922 worker: Hdwr volume controller exists
20180201 174922 worker: Chip options (Burr Brown PCM5122)
20180201 174922 worker: - Services
20180201 174924 worker: MPD started
20180201 174924 worker: MPD scheduler policy (time-share)
20180201 174924 worker: MPD output 1 ALSA default (on)
20180201 174924 worker: MPD output 2 ALSA crossfeed (off)
20180201 174924 worker: MPD output 3 ALSA parametric eq (off)
20180201 174924 worker: MPD output 4 ALSA graphic eq (off)
20180201 174924 worker: MPD crossfade (off)
20180201 174924 worker: Airplay receiver started
20180201 174924 worker: Airplay volume mgt (auto)
20180201 174924 worker: - Last
20180201 174924 worker: USB sources (Ext Drive)
20180201 174924 worker: NAS sources (mountall initiated)
20180201 174924 worker: Volume level (52) restored
20180201 174924 worker: Maintenance interval (21600)
20180201 174924 worker: Watchdog started
20180201 174924 worker: Ready
 
Hello Eric thanks for answering.
I'm in the office and I will try again tonight but I suspect I'm on a different issue.
Let me explain better.

As I mentioned in my post I originally tried the "manual" way.

Started by flashing a Stretch image, then followed the various steps taking them from the 2.3 procedure script.

Going through the list, I issued the various "sudo reboot" commands after each "STEP", and all went well. I mean, after the reboot the system regularly came up again, I could ssh into it, it stayed stable and I could go on issuing more configuration commands until the subsequent reboot.
All OK. Until step 9.

After rebooting after step 8, in facts, the system does come up, I can ssh into it, but shortly after I start issuing STEP 9 commands it goes down (SSH connection is lost).
Green light on the Pi stays solid green, but the system won't apparently actually reboot, letting me regain control and continue the procedure.
I did not "wait for long", tbh.

Again, I'll try again tonight and I'll let you know.

Ciao
Alberto

Is there a reason you are issuing commands manually and not running it as a script, as it was intended?
 
As a couple of extras.

For Qobuz you can enter the MD5 hash of your password, this does not work on the website only the API.

For Google you should enable 2fa and then assign an application password to your mood player. There is a link upmpdcli website I will try and dig up.

I think this is why the upmpdcli programmer tried to change the owner and permissions on the config file to the upmpdcli user. However that seemed to cause issues.

@Serverbaboon

Thanks for that. I had not twigged on the notion of a Google "application password".

Regards,
Kent
 
Hi,
Can you describe some real-world scenarios where moOde users will be affected by your claim below?
"SMB 1 is risky due to ransomware WanaCry vulnerability. So that would be better to look for another player"

If you can provide evidence that this is a real concern than I can investigate some options in Samba.
-Tim
Hope nobody was and will be affected in the future. My father in law has a company PC unfortunately without updated windows and this malware encrypted all standard files (docs, pictures, pdfs etc.) no way to bring it back so I am scary.
Thanks to my IT colleague and 3 days of research we found a way how to share WIN10 files without spacieal setup. Just need to create/use account with password, than share files (add mentioned account permission) and the most important thing to do is wuallaaaa use Mount flags like this: vers=2.0 :cheers::violin::wave: no need to use SMB 1.0 in windoze
Enjoy!