Moode Audio Player for Raspberry Pi

Another happy Moode convert here. I have tried all of the audiophile pi distributions but still kept going back to the handbuild raspbian/mpd install i made back in early 2013. This looks good, and weirdly I agree that it does sound better. Am running v2.1 on a B+ with Amanero USB interface.

A couple of issues:

1. Like many others there's nothing in my library. MPD is scanning but no files show. running 'mpc stats' confirms that the library is empty.

I worked around it by changing mpd's user to 'root' and editing mpd.conf to look for music in '/mnt/NAS/' instead. Now I get a working library but only that. No USB, Webradio etc.

2. The Amanero USB interface is not available as an option despite being detected and available. I only have onboard audio or I2S audio devices from which to select.

I worked around this by editing mpd.conf to use (hw:0,0) instead so now I get audio. However the hardware mixer does not work despite the Amanero having sliders to adjust in alsamixer.

Additionally, due to these manual changes to mpd.conf when I use the web interface to update mpd settings the two tweaks mentioned above get erased and i have to keep adding them in to enable audio after any other tweaks.
 
Another happy Moode convert here. I have tried all of the audiophile pi distributions but still kept going back to the handbuild raspbian/mpd install i made back in early 2013. This looks good, and weirdly I agree that it does sound better. Am running v2.1 on a B+ with Amanero USB interface.

A couple of issues:

1. Like many others there's nothing in my library. MPD is scanning but no files show. running 'mpc stats' confirms that the library is empty.

I worked around it by changing mpd's user to 'root' and editing mpd.conf to look for music in '/mnt/NAS/' instead. Now I get a working library but only that. No USB, Webradio etc.

2. The Amanero USB interface is not available as an option despite being detected and available. I only have onboard audio or I2S audio devices from which to select.

I worked around this by editing mpd.conf to use (hw:0,0) instead so now I get audio. However the hardware mixer does not work despite the Amanero having sliders to adjust in alsamixer.

Additionally, due to these manual changes to mpd.conf when I use the web interface to update mpd settings the two tweaks mentioned above get erased and i have to keep adding them in to enable audio after any other tweaks.

Hi,

Glad to hear u are liking Moode :)

Here are responses to your issues:

1. Like many others there's nothing in my library. MPD is scanning but no files show. running 'mpc stats' confirms that the library is empty.

MPC stats showing 0 songs suggests that MPD Database Update did not find any song files in any path. Did u mean that after pressing the Library tab the Library panel was blank and "0 tracks" was displayed in the lower right? Or was it that no songs showed up in the Browse panel under NAS?

I worked around it by changing mpd's user to 'root' and editing mpd.conf to look for music in '/mnt/NAS/' instead. Now I get a working library but only that. No USB, Webradio etc.

Shouldn't need to make either of these changes. MPD configuration already has symlink to /mnt/NAS. If there are song files under /mnt/NAS then MPD Database Update should pick them up.

Does your music collection show up in the Browse panel under NAS?

2. The Amanero USB interface is not available as an option despite being detected and available. I only have onboard audio or I2S audio devices from which to select.

This is a bug. "I2S audio device" appears in the "MPD audio output" field on MPD config screen when certain USB devices are attached, but it only affects the text displayed not the actual USB connection. The display issue has been fixed for release 2.2 :)

I worked around this by editing mpd.conf to use (hw:0,0) instead so now I get audio. However the hardware mixer does not work despite the Amanero having sliders to adjust in alsamixer.

Probably because "On-board audio device" was selected which configures mpd.conf for hw:1,0 and thus u would get no sound from USB output since audio is being routed to the Pi's on-board audio chip. This is likely due to the confusion caused by the bogus "I2S audio device" text being displayed.

Additionally, due to these manual changes to mpd.conf when I use the web interface to update mpd settings the two tweaks mentioned above get erased and i have to keep adding them in to enable audio after any other tweaks.[/QUOTE]

The MPD config screen will overwrite any manual changes to the conf file. The approach is to manage the conf file through the UI.

I would recommend a fresh 2.1 image, leave MPD audio output set to "I2S audio device" since we know that its only a display issue, and then send email to tim at moodeaudio dot org and I can help troubleshoot getting your music collection to show up in the Browse panel and the Library panel :)

Regards,
Tim
 
Testing MoOde2.1 on a B+ with HiFiBerry Digi+, and this is what happens.
Starting up was easy, up to VERIFY/SET ALSA VOLUME. At this point, the player (via Chrome on a Win7 PC) sat 'Waiting for moode...'. The menu worked inasfar as a reboot started as requested with the popup that the volume had been set. The screen *didn't* refresh after the reboot, I had to go back to diyAudio server HTTPS page.
Testing the playback via a radio station looked good as the radio station display on the player changed as requested and the timer restarted as expected, but without any sound. On trying to get to the Configuration/System menu to check the I2S setting, I'm back 'Waiting for moode...'. Most things I've tried with MoOde end up with this, which means that I go back to Volumio to have music again. I'll check on the next release.
 
Testing MoOde2.1 on a B+ with HiFiBerry Digi+, and this is what happens.
Starting up was easy, up to VERIFY/SET ALSA VOLUME. At this point, the player (via Chrome on a Win7 PC) sat 'Waiting for moode...'. The menu worked inasfar as a reboot started as requested with the popup that the volume had been set. The screen *didn't* refresh after the reboot, I had to go back to diyAudio server HTTPS page.
Testing the playback via a radio station looked good as the radio station display on the player changed as requested and the timer restarted as expected, but without any sound. On trying to get to the Configuration/System menu to check the I2S setting, I'm back 'Waiting for moode...'. Most things I've tried with MoOde end up with this, which means that I go back to Volumio to have music again. I'll check on the next release.

Hi,

Very odd. I test w/Chrome on Windows 7 and no issues. This morning in fact I was testing the "Overlay Scrollbar" flags setting in Chrome and pushed a Tweet out about it.

Are u getting "Waiting for cache" message from Chrome?

Send email to tim at moodeaudio dot org and I can help troubleshoot :)

Regards,
Tim
 
Hi Tim,

I've been a loyal Volumio user for a while now, but your project looks interesting and seems to have a faster update rate as well as a few features I've been yearning for.

Anyway, apologies if these have already been requested or implemented (I could only scan the previous forum posts), but here are some requests of my own:

1. Cuesheet support. I tried playing a cue file through the webUI, but it didn't work for me. This may help explain cuesheets.

2. Speed up boot process when using wifi. See here.

Thanks for developing Moode!
 
Hi Tim,

I've been a loyal Volumio user for a while now, but your project looks interesting and seems to have a faster update rate as well as a few features I've been yearning for.

Anyway, apologies if these have already been requested or implemented (I could only scan the previous forum posts), but here are some requests of my own:

1. Cuesheet support. I tried playing a cue file through the webUI, but it didn't work for me. This may help explain cuesheets.

2. Speed up boot process when using wifi. See here.

Thanks for developing Moode!

Hi,

Glad to hear that Moode is working for u :) I try to release a new version near the end of each month and I post dev and feature information frequently on Moode Twitter Feed

In the readme for Moode there is procedure #4 under CUSTOM CONFIGS for fast boot but the suggestion at the link you provided is much simpler and requires no ssh by user.

Replace "auto eth0" with "allow-hotplug eth0"

I will test it out. Thanks!

I have not had time to investigate CUE support but hope to get to at some point :)

Regards,
Tim Curtis
 
One of the things I prefer about Moode vs Volumio et al is that the video port is on.
I would be happy with a switch in the config menu for opt in/out.

Using Moode at a remote location (my rural workshop) means no wifi so I control it from the keyboard.
Mostly I can do this blind but when I sometimes mistype or need to check what errors are throwing then the console output is invaluable.
 
Last edited:
Hello,
First time to posted here,I appreciate Tim who is taking time
to built Moode excellent player.
My system is used Raspberry PI 2 with IQaudio DAC+ that works perfectly, sound quality is better than both Volumio and Runeaudio sure.
I'm looking for how to build it into chassis and control with IR remote. Would you please advise or guidance where to find information that makes it.

Thank you very much
BK
 
One of the things I prefer about Moode vs Volumio et al is that the video port is on.
I would be happy with a switch in the config menu for opt in/out.

Using Moode at a remote location (my rural workshop) means no wifi so I control it from the keyboard.
Mostly I can do this blind but when I sometimes mistype or need to check what errors are throwing then the console output is invaluable.

I've been doing a lot of work with wifi lately - not Raspberry Pi, other MCUs.

As a result, I have also been playing with using the Pi as an AP/wireless Hotspot for exactly this sort of situation - where there's no wifi infrastructure.

It's pretty straightforward:

You need a wifi adapter that supports Master mode - such as an Edimax or Ralink RT5370/RT5372 (my personal fave USB Wifi adapter).

SSH into the Pi: ssh root@moode.local
Install DHCP server udhcpd: sudo apt-get install hostapd udhcpd
Edit DHCP config file: nano /etc/udhcpd.conf

Code:
# Moode udhcpd configuration file (/etc/udhcpd.conf)

# The start and end of the IP lease block
start		192.168.10.20	#default: 192.168.10.20
end		192.168.10.40	#default: 192.168.10.40

# The interface that udhcpd will use
interface	wlan0		#default: wlan0
max_leases	254		#default: 254
remaining	yes		#default: yes

#DHCP options
opt	dns	192.168.10.1 
option	subnet	255.255.255.0
opt	router	192.168.10.1
opt	wins	192.168.10.1
option	domain	local
option	lease	864000 #10 Days

Edit /etc/default/udhcpd to enable DHCP services: nano /etc/default/udhcpd

Code:
#DHCPD_ENABLED="no"

Give the Wifi adapter an IP address: sudo ifconfig wlan0 192.168.10.1

Edit /etc/network/interfaces to make the IP address permanent: nano /etc/network/interfaces

Add or alter to the following:
Code:
iface wlan0 inet static
  address 192.168.10.1
  netmask 255.255.255.0

Configure HostAPD: nano /etc/hostapd/hostapd.conf

If you want an open (no password) wifi AP:

Code:
interface=wlan0
ssid=Music
hw_mode=g
channel=6
auth_algs=1
wmm_enabled=0

If you want a secured wifi AP:

Code:
interface=wlan0
driver=nl80211
ssid=Music
hw_mode=g
channel=6
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wpa=2
wpa_passphrase=My_Passphrase
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

You can make the SSID anything you want - but short and simple and plain characters is always easier.

If you are securing your AP, 'wpa_passphrase' is the AP password.

Edit the hostapd file: nano /etc/default/hostapd

Code:
DAEMON_CONF="/etc/hostapd/hostapd.conf"

Now we need to configure NAT (Network Address Translation)

Set up IP forwarding: sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
Make it permanent: nano /etc/sysctl.conf

Code:
net.ipv4.ip_forward=1

Set up NAT in the kernel:

Code:
sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
sudo iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT
sudo sh -c "iptables-save > /etc/iptables.ipv4.nat"


Edit to add the ip tables to your interfaces: nano /etc/network/interfaces

Code:
up iptables-restore < /etc/iptables.ipv4.nat

Now we are ready to test:

sudo service hostapd start
sudo service udhcpd start

You should now see the 'Music' SSID.
 
Hello,
First time to posted here,I appreciate Tim who is taking time
to built Moode excellent player.
My system is used Raspberry PI 2 with IQaudio DAC+ that works perfectly, sound quality is better than both Volumio and Runeaudio sure.
I'm looking for how to build it into chassis and control with IR remote. Would you please advise or guidance where to find information that makes it.

Thank you very much
BK

Hi,

I'm interested in understanding your usage scenario for IR based remote control :)

Moode UI scales nicely to Smartphone sized displays which makes it easy to just use your Smartphone as remote control over WiFi.

Regards,
Tim.
 
Yay!

I am really pleased with V2.1 - it (re)boots rally fast and functionality is excellent.

My installed base of Moode devices is growing every week - my son and daughter now have one and I'm about to head off to NZ for a few months, so my Dad and sister and other daughter will no doubt end up with them shortly.

Thanks Tim!
 
Hi,

I'm interested in understanding your usage scenario for IR based remote control :)

Moode UI scales nicely to Smartphone sized displays which makes it easy to just use your Smartphone as remote control over WiFi.

Regards,
Tim.

I found it in volumio that they did with remote here https://volumio.org/forum/using-remote-with-volumio-t1923.html
I'm trying to learn how to apply to use with moode. Unfortunately I'm newbie for linux. Anyway, will keep post if feasible to do.
One more question, about USB thump drive using that was often stuck with shown none of song files while browsing into that drive. Just reboot that would fix to show the files. And would found this issue , repeat the issue again then plugging other thump drive in, its still showing last files from previous usb drive that already were removed instead of newly drive that just plugged. I tried to clear system and history play but didn't help to resolve
I was SSH look into "dmesg" that show error message "buffer I/O error on dev sda1" . I tried to re-fromatted the usb drive and copied the song back to drive, plug it into usb port onto Ras Pi again and the issue is still the same. I tried with 2 usb drives with brand Sandisk 16Gb and Sandisk 64Gb that both found the same issue. Any advise ?

Thank you
Benkit
 
I found it in volumio that they did with remote here https://volumio.org/forum/using-remote-with-volumio-t1923.html
I'm trying to learn how to apply to use with moode. Unfortunately I'm newbie for linux. Anyway, will keep post if feasible to do.
One more question, about USB thump drive using that was often stuck with shown none of song files while browsing into that drive. Just reboot that would fix to show the files. And would found this issue , repeat the issue again then plugging other thump drive in, its still showing last files from previous usb drive that already were removed instead of newly drive that just plugged. I tried to clear system and history play but didn't help to resolve
I was SSH look into "dmesg" that show error message "buffer I/O error on dev sda1" . I tried to re-fromatted the usb drive and copied the song back to drive, plug it into usb port onto Ras Pi again and the issue is still the same. I tried with 2 usb drives with brand Sandisk 16Gb and Sandisk 64Gb that both found the same issue. Any advise ?

Thank you
Benkit

Hi,

The procedure at that link looks like it would work but I've never tried it. The only MPD command that will be problematic with Moode is the "volume" command. Yes it will set MPD volume but the value will not be reflected in the UI because the Moode volume control is not bound to the MPD volume control.

What I do with USB stick or USB HDD/SSD is plug device in, reboot, and then run MPD Database Update from the Source config screen. I've never had an issue using this approach.

If u need to remove the USB storage device then shutdown, remove device, power up, run MPD Database Update.

Regards
TC
 
Hi,

This is excellent! Couple of Q's:

1) It would be really cool if you could add an (optional) feature to the UI to turn an external amplifier on/off. If you could make a GPIO pin output High/Low then a relay could be used to switch the amp on/off. Then you could also make the Clock Radio use this to switch the amp on at wake up and off at the end of the time. Or maybe if you want to keep the UI streamline, you could make the GPIO go High while playing and go Low after nothing has played for a while, like say 10 minutes.

2) Is there anyway to sync two Moode players? I have L shaped living room/kitchen with and amp at each end - would be nice to play the same music on both amps.

Cheers!
Miles
 
Hi,

This is excellent! Couple of Q's:

1) It would be really cool if you could add an (optional) feature to the UI to turn an external amplifier on/off. If you could make a GPIO pin output High/Low then a relay could be used to switch the amp on/off. Then you could also make the Clock Radio use this to switch the amp on at wake up and off at the end of the time. Or maybe if you want to keep the UI streamline, you could make the GPIO go High while playing and go Low after nothing has played for a while, like say 10 minutes.

2) Is there anyway to sync two Moode players? I have L shaped living room/kitchen with and amp at each end - would be nice to play the same music on both amps.

Cheers!
Miles

Hi Miles,

Thats a nice idea, i'll add to my to-do list :) There already is code to set GPIO pin 22 high for un-muting IQaudIO+ devices at startup. See /var/www/command/unmute.sh. Which pin would u suggest?

Synconized multi-room audio will be possible in Release 2.2 via shairport-sync, the amazing rewrite by Mike Brady of the original really nice shairport code. Turn on the Airplay receiver in Moode and then use an Airplay sender for example iTunes. The audio will be in perfect to-the-ear sync at each Airplay receiver:)

If u were referring to using Moode as both the sender and receiver for example having Moode1 playing and also streaming its audio output to Moode2, Moode3... such that all audio is to-the-ear sync, this is not possible yet.

It would require dev of either Airplay sender module or some other audio distribution method that interfaced with MPD/ALSA.

Regards,
Tim
 
Hi Miles,

Thats a nice idea, i'll add to my to-do list :) There already is code to set GPIO pin 22 high for un-muting IQaudIO+ devices at startup. See /var/www/command/unmute.sh. Which pin would u suggest?

Hi Tim,

I've only used Moode for a few days through the audio jack. I was planning on buying HiFi Berry DAC, and I see that GPIO23 is not used by any of their products, so that would seem suitable. I do not know if there are any other makes of DAC that fit on the header that would conflict with GPIO23. If you know of any other DACs I can try and find a common free pin.

Thanks
Miles