Moode Audio Player for Raspberry Pi

Jump to Latest
#1,341
supra said:
I like Moode so much i have it in 2 systems, and soon 3 when my Aya2014 dem arrives.
On both systems i can control playback via wireless with mupeace or other app but can t access diyAudio server HTTPS page unless ethernet cable connected.
Same with old and test version of moode.
Any suggestions?
Click to expand...

All good now, must have pressed the right buttons, very hard to listen to usb now.
Mucho kudos timbo.
 
#1,342
Hello: new poster here.

I have been having horrible problems with Airplay using moode 2.4 on a Pi2 with the hifiberry Amp+

I know it can work, because it did on the first install. However, after a couple of reboots and restarts, the airplay went completely silent. Internet radio played, and so, sometimes, did music over DLNA/UpnP. But system preferences on my mac showed the airplay volume control at full but also muted and in any case greyed out so that the controls were unresponsive.

Nor could I ever get MPD to read the music on a (powered) USB disk. It would just claim to be updating for ages, but nothing showed up in the library. The "Browse" window would sometimes show USB connections, and sometimes just the radio. It never showed any music folders.

I tried wiping and reinstalling from scratch a couple of times. Nothing helped. At last I installed the 2.5 test release. This will also play internet radio but when I configured the IS2 player to be the hifiberry amp+ the alsa volume (which had been 100%) went blank, with a note underneath sayng "Hardware volume controller not detected".

I know how to ssh into the system and am happy to use a command line, but I can't find anything that looks like a diagnostic log for all this PHP. I assume there must be errors logged somewhere, but where?

Please advise
 
#1,343
Hi Tim

I too am having issues connecting via diyAudio server HTTPS page via wireless connections; On a wired connection I can type diyAudio server HTTPS page and access the player screen, but not on wireless. I get an error message that says DNS lookup failed. However if I type in the static IP address that I've given to the Raspberry pi, I can access the playback screen via my tablet (using wifi)

So the issue seems to be moode not resolving to the static IP address when using wireless. I've tried googling for answers, however I'm not a networking person so I got a bit lost with it all; I understand the principle of DNS, but not sure how I would go about solving it.

Any ideas? (although typing the static IP address isn't a problem, and takes as long as typing out diyAudio server HTTPS page, however I'm intrigued to know what the issue is).

Thanks
 
#1,344
Possibly relevant to my earlier complaint about loss of hardware volume are these lines from dmesg:

[ 3.393861] snd-hifiberry-amp sound: ASoC: CPU DAI (null) not registered
[ 3.429717] snd-hifiberry-amp sound: snd_soc_register_card() failed: -517
[ 3.452114] snd-hifiberry-amp sound: ASoC: CODEC DAI tas5713-hifi not registered
[ 3.464564] snd-hifiberry-amp sound: snd_soc_register_card() failed: -517
Click to expand...

Could this be a hardware failure?
 
#1,345
To Westers151

With a good help from Tim I finally got my working. I assume that you have the Edimax USB Wifi stick. The problem is apparently that some of the firmware editions of this needs a bit more to get rid of the power save mode.. If that is your problem you can install the patch from the link below.

https://www.raspberrypi.org/forums/viewtopic.php?t=61665

the commands is from a terminal (with the raspberry wired up) ssh root@ip address
passwd is moode. Then follow the instruction in the link. Or wait until Tim has finished his research and eventually have put this into the final version of the new software.
 
Last edited:
#1,346
Hi Tim and a Happy New Year

Long time no post. I upgraded to the latest Moode version recently. I was curious if one of the features I was interested in a while ago has any chance of making it to the to do list. I'm talking about the "add complete containing directory" item in the "hamburger" menu for files in the search results, for us people who sometimes like listening to complete albums start to finish 🙂 Currently I'm not aware of an easy way to do it. Thanks and keep up the good work.
 
Last edited:
#1,347
anewnadir said:
Tim, just so other users are aware of my fix I'm posting here. The problem may stem from having a large amount of .aif files in a library. I opened up /etc/mpd.conf and added the following value:

max_output_buffer_size "81920"

Restarted MPD and library pane now loads just fine after about 15 seconds of work. Per you, changing any MPD settings in the moode interface will delete this tweak, so it's best to have everything else set up to your liking before you try this.
Click to expand...

Hi,

Much appreciated 🙂

I'll include this in Test Release 2 (TR2) plus a new Library caching feature that generates a database file on server at first Library load and then via UPDATE LIBRARY DB button at any time after that. Once the DB file is generated, its used to feed the Library panel instead of always rerunning the lib loader. The Library panel loads very quickly using this approach.

TR2 will also include the EDIMax power mgt fix from Henry that prevents the adapter from sleeping. Apparently some versions of the EdiMax adapter ignore the global option "wireless-power off" in /etc/network/interfaces

Regards,
Tim
 
#1,348
AndrewBrown said:
Hello: new poster here.

I have been having horrible problems with Airplay using moode 2.4 on a Pi2 with the hifiberry Amp+

I know it can work, because it did on the first install. However, after a couple of reboots and restarts, the airplay went completely silent. Internet radio played, and so, sometimes, did music over DLNA/UpnP. But system preferences on my mac showed the airplay volume control at full but also muted and in any case greyed out so that the controls were unresponsive.

Nor could I ever get MPD to read the music on a (powered) USB disk. It would just claim to be updating for ages, but nothing showed up in the library. The "Browse" window would sometimes show USB connections, and sometimes just the radio. It never showed any music folders.

I tried wiping and reinstalling from scratch a couple of times. Nothing helped. At last I installed the 2.5 test release. This will also play internet radio but when I configured the IS2 player to be the hifiberry amp+ the alsa volume (which had been 100%) went blank, with a note underneath sayng "Hardware volume controller not detected".

I know how to ssh into the system and am happy to use a command line, but I can't find anything that looks like a diagnostic log for all this PHP. I assume there must be errors logged somewhere, but where?

Please advise
Click to expand...

Hi Andrew,

Email tim at moodeaudio dot org and I'll help troubleshoot 🙂

Could be a bug in code that handles the AMP+

Regards,
Tim
 
#1,349
mr_push_pull said:
Hi Tim and a Happy New Year

Long time no post. I upgraded to the latest Moode version recently. I was curious if one of the features I was interested in a while ago has any chance of making it to the to do list. I'm talking about the "add complete containing directory" item in the "hamburger" menu for files in the search results, for us people who sometimes like listening to complete albums start to finish 🙂 Currently I'm not aware of an easy way to do it. Thanks and keep up the good work.
Click to expand...

Hi,

Likewise, happy new year!

You mean from Library panel Albums column?

Regards,
Tim
 
#1,350
TimCurtis said:
Hi,

Likewise, happy new year!

You mean from Library panel Albums column?

Regards,
Tim
Click to expand...
I actually mean the Browse panel:
4nvEJJk.png
 
#1,351
westers151 said:
Hi Tim

I too am having issues connecting via diyAudio server HTTPS page via wireless connections; On a wired connection I can type diyAudio server HTTPS page and access the player screen, but not on wireless. I get an error message that says DNS lookup failed. However if I type in the static IP address that I've given to the Raspberry pi, I can access the playback screen via my tablet (using wifi)

So the issue seems to be moode not resolving to the static IP address when using wireless. I've tried googling for answers, however I'm not a networking person so I got a bit lost with it all; I understand the principle of DNS, but not sure how I would go about solving it.

Any ideas? (although typing the static IP address isn't a problem, and takes as long as typing out diyAudio server HTTPS page, however I'm intrigued to know what the issue is).

Thanks
Click to expand...

Hi,

If host name "moode" resolves when using Ethernet interface on Pi but not when using WiFi interface, it indicates a network configuration issue that is external to the Pi.

Try using "moode.local". This will cause mDNS queries to be used instead of plain DNS queries. Note that Router must support IP multicast and pass multicast packets over WiFi for this to work.

Regards,
Tim
 
#1,354
Thanks Tim (and Henry), however, that's not worked either - I think there might be some confusion as well. To clarify my setup:

  1. Pi 2 hard wired to my router via eth0
  2. My router is also my wireless access point
  3. Hard wired home PC
  4. Android tablet connected to my network via wireless

Typing "moode" into my browser on the PC takes me straight to the Moode player interface. If I type "moode" into the browser on my tablet, it throws the DNS error. However typing the static IP address of the PI into the browser on my tablet takes me to the moode player interface.

This is most likely an external issue from the PI; I just don't get why the hard wired PC works fine, but the wireless connected tablet needs the IP address. All I can think is that having the PC and PI hard wired into the router means DNS works; however when connecting to the wireless interface on the router, and then trying to access a device that is coming in via the hard wired interface, DNS doesn't work.

No idea why that would be the case though.
 
#1,356
westers151 said:
Thanks Tim (and Henry), however, that's not worked either - I think there might be some confusion as well. To clarify my setup:

  1. Pi 2 hard wired to my router via eth0
  2. My router is also my wireless access point
  3. Hard wired home PC
  4. Android tablet connected to my network via wireless

Typing "moode" into my browser on the PC takes me straight to the Moode player interface. If I type "moode" into the browser on my tablet, it throws the DNS error. However typing the static IP address of the PI into the browser on my tablet takes me to the moode player interface.

This is most likely an external issue from the PI; I just don't get why the hard wired PC works fine, but the wireless connected tablet needs the IP address. All I can think is that having the PC and PI hard wired into the router means DNS works; however when connecting to the wireless interface on the router, and then trying to access a device that is coming in via the hard wired interface, DNS doesn't work.

No idea why that would be the case though.
Click to expand...

Hi,

I recall that this is specific issue to some Android devices. I think it was user DRONE7 in this thread that had a fix for this.

Regards,
Tim
 
#1,358
I just did a bit of googling and found the reason for this. Apparently Android ignores any offered DNS servers from your ISP, and instead uses it's own Google DNS service. Google DNS knows nothing about your local names, hence why typing "moode" comes back with a DNS error.

There is a work around, but it seems too much hassle to implement (creating your own local DNS server, etc), so I'll stick with the static IP address. This link talks about what's involved.
 
#1,359
Hi,
I'm using MoOde 2.4 on a Pi2. I 've got an issue with the DLNA server wich doesn't recognize AIFF files on my SDCARD. Is it an issue of miniDLNA ?

Moreover, I've tweaked a SatelliteCCRMA with Squeezelite and LMS, to know if a real time management of the player is an improvement or not. It sounds good, but not really stable... so I go back to MoOde. Is there anybody who tried something like this on MoOde ? with nice or with CPUSchedulingPolicy=fifo
CPUSchedulingPriority=99 commands ?

Is it useful to do an apt-get upgrade or dist-upgrade ?

Finally, any tips to update MoOde without doing a fresh install ?

regards
 
#1,360
Last edited:
You must log in or register to reply here.
Top Bottom