Moode Audio Player for Raspberry Pi

While on the subject of DHCP/DNS, can someone with an Android phone do a test?

'Forget' your current home Wifi connection, then reconnect and select 'advanced' then choose 'static' instead of 'DHCP'

In your static setting pick a free IP address, a mask of 255.255.255.0 and your router as the Gateway and DNS. If there are more than one option for DNS, put the same (router) address in both.

Connect to your wifi

Then, try and navigate to moode.local and tell me whether it works, or if you get an error, what that error is.

....

Sorry, I can't futz with the router here at the moment.

I tried static IP- and local DNS-addresses on both Android 6 and Android 7 devices here. After the change, I could access the world (moodeaudio.org) so DNS is working. I could access my moode player via its fully qualified domain name (in this case moode-rpi2b.fios-router.home) but I can't access it via the zero-configuration networking name moode-rpi2b.local which returns "ERR_NAME_NOT_RESOLVED" on both devices. The same name does resolve on the Linux laptop I'm typing on.

Regards,
Kent
 
new release

Tim,

I've been away from Moode and this forum for some time. It was a pleasant surprise to return to discover Release: 3.0 is available on moodeaudio.org. I installed it without a hitch on an RPi2B I had at hand and as expected the update went fine.

Props to you for your dedication to this project. I am beyond impressed by your continuing developmental efforts as well as your responsiveness to your users.

Regards,
Kent
 
Sorry, I can't futz with the router here at the moment.

I tried static IP- and local DNS-addresses on both Android 6 and Android 7 devices here. After the change, I could access the world (moodeaudio.org) so DNS is working. I could access my moode player via its fully qualified domain name (in this case moode-rpi2b.fios-router.home) but I can't access it via the zero-configuration networking name moode-rpi2b.local which returns "ERR_NAME_NOT_RESOLVED" on both devices. The same name does resolve on the Linux laptop I'm typing on.

Regards,
Kent

Thanks Kent.
 
Hi Nopdon!

I have cuesheets in all of my album-folders.
Just open the album, you will find your cuesheet file at the end of album-tracks. Then just tip it and select play or whatever choosable- it works for me. Moode then loads the album-tracks immediately into playback area with all of the metadata.

Greetingz, Robert
 
hello Tim,

I have added an NFS share to Moode with the DLNA server turned on, and on boot the delay mounting it is long enough for
the music index database /var/lib/minidlna/files.db to be removed, presumably because minidlna thinks the files are no longer there.
I have to rebuild it each time.
do know what's going on?
thanks....
 
Thank you Tim, DRONE7 & Zootalaws, you all speak with much sense and lucidity. My system presents a rather long chain of possibilities for error, so it is great to have some light shed on where to look first.

A shame to hear about the Zyxel/homeplug issues - I installed these assuming that they would be more reliable than wi-fi. Netflix & Amazon Video (in my Samsung telly) which share the connection through these with the Pi (not at the same time!) never falter but they did buffer a lot on wi-fi.

However, since then I have a new router which I understand has solid wi-fi, so I will try that option first with the Pi as it is easy to try and if it works I'll be done. If still necessary, I will try wired ethernet for diagnosis purposes, but unfortunately it is not a practical solution as it would mean rewiring the house. I will also trying pinging from the Pi and Paessler's PRTG (it sounds like it could be a useful tool on an ongoing basis.)


Thank you again

Just checking-in to say all has been glitch free since I moved over to wifi from homeplug and thanks again for everybody's help on this.
 
hello Tim,

I have added an NFS share to Moode with the DLNA server turned on, and on boot the delay mounting it is long enough for
the music index database /var/lib/minidlna/files.db to be removed, presumably because minidlna thinks the files are no longer there.
I have to rebuild it each time.
do know what's going on?
thanks....

Hi,

Very odd.

There are only two ways in Moode 3.0 that the minidlna database gets wiped. Both of these are in the Audio config page.

1) Clicking "Rebuild DLNA database"

This action stops minidlna, deletes all files in /var/lib/minidlna including the minidlna database, unmounts /mnt/UPNP, then starts minidlna and performs a djmount to /mnt/UPNP. When minidlna is started and sees no database file it creates one and begins indexing everything at /var/lib/mpd/music.

2) Setting DLNA server to OFF

This action stops minidlna, deletes all files in /var/lib/minidlna including the minidlna database then unmounts /mnt/UPNP.

-Tim
 
I'm not doing either of those.
so running /etc/init.d/minidlna stop, unmounting the NFS drive. then restarting, _does_ remove the database!
so a race between mounts and starting the service?

Hi,

I ran a quick set of tests with a USB HDD and did not experience the issue where if the source is not available then the minidlna database file gets deleted.

- Turn on DLNA server
- Verify database indexed
- Verify files in /var/lib/minidlna
- Reboot
- Verify files in /var/lib/minidlna
- Verify database not reindexing
- Unplug USB drive
- Reboot
- Verify files in /var/lib/minidlna
- Verify database not reindexing

-Tim
 
Can someone provide an example on how this screen should be populated:
attachment.php

Thanks
Ray