Moode Audio Player for Raspberry Pi

Prolly this month, but u know that a few things just kind of popped up without much notice last month like the incredible Pi-3B+, the new release of Raspbian Stretch, new Bluetooth stack, WiFi 5GHz, Linux 4.14 kernel mainline, etc.

I thought it best to delay the 4.1 launch until all the new audio and platform improvements could be integrated into moOde software.

If you follow moOde Twitter feed you can get a current view of where moOde is at.

-Tim
 
Help!
I'm testing Moode as a replacement for my ancient Linksys NSLU2 running Twonkyvision media server. I have a couple of Roku/Pinnacle Soundbridges to play the music.
I've installed Moode 4.0 on a Raspberry Pi 3 coupled to a Suptronics X5000 DAC and also an SSD as storage. Moode has found the music files on the SSD and has installed them in the library. I can play individual tracks and also radio stations such as Radio Paradise. Sounds great!
However (I'm sure through stupidity) I can't find any way to create playlists from tracks in the library that I can then play. In the old Twonkyvision software, I would create a playlist in iTunes, export as m3u and then the Rokus could play the playlist, with or without shuffle. I'd hoped this would be easier in Moode, but I can't find any way to create a playlist at all - ideally I could pull entire folders and sub-folders into a playlist - I have too many tracks to select individually, about 17000.
Many thanks, Andy
 
Linux advice... peripheral to Moode conversation

When I muck around with my Moode builds and login via ssh I get the following warning (on Mac OSX):

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
--DELETED JUST IN CASE IT MAKES MY SYSTEM VULNERABLE--
Please contact your system administrator.
Add correct host key in /Users/rhaaland/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/rhaaland/.ssh/known_hosts:8
ECDSA host key for moode.local has changed and you have requested strict checking.
Host key verification failed.


This prevents me from logging in to moode so... each time, I go in and edit the "known_hosts" file... deleting lines that appear to be relevant (though somewhat blindly). Retry ssh and all is good. Is there something I'm doing wrong or should set on my system to prevent this 'annoyance'?

All my Moode systems are working just fine.

Thanks for the advice.

Ryan
 
When I muck around with my Moode builds and login via ssh I get the following warning (on Mac OSX):

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
--DELETED JUST IN CASE IT MAKES MY SYSTEM VULNERABLE--
Please contact your system administrator.
Add correct host key in /Users/rhaaland/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/rhaaland/.ssh/known_hosts:8
ECDSA host key for moode.local has changed and you have requested strict checking.
Host key verification failed.


This prevents me from logging in to moode so... each time, I go in and edit the "known_hosts" file... deleting lines that appear to be relevant (though somewhat blindly). Retry ssh and all is good. Is there something I'm doing wrong or should set on my system to prevent this 'annoyance'?

All my Moode systems are working just fine.

Thanks for the advice.

Ryan
First of all, you shouldn't be guessing what to delete. You have the "offending" line number in that message:
Code:
Offending ECDSA key in /Users/rhaaland/.ssh/known_hosts:[B]8[/B]
In this case it's line no. 8. So first of all, when you encounter this, delete only that line and try again. If this happens again, then there's something weird going on. A host shouldn't change the key unless you generate a new one.
 
Thanks!

Yes, i understand and was not so much "guessing." I deleted the offending line based on IP address etc. The clarification on the line number is very helpful. Question: do the lines continue onto the next and if so, is there a delimiter that indicates that? ... some lines end with a "=" sign. That is different from others in the file.

Thanks again!
Ryan
 
Some time ago i was able to build moode with Pi2, than i tried to build moode on Pi3. Tried different sd cards, two different Pi3 and for some unknown reason Pi was always crashing during the build process, mostly after the new kernel installation.

Than i connected the display to pi and i noticed, that sometimes a message "undervoltage" appeared. The power supply was 2.4A (not offical ps from Pi foundation), so it was theoretically OK, but ...

I connected "The official and recommended universal micro USB power supply for Raspberry Pi" and all problems disappeared. :D:D:D
 
Some time ago i was able to build moode with Pi2, than i tried to build moode on Pi3. Tried different sd cards, two different Pi3 and for some unknown reason Pi was always crashing during the build process, mostly after the new kernel installation.

Than i connected the display to pi and i noticed, that sometimes a message "undervoltage" appeared. The power supply was 2.4A (not offical ps from Pi foundation), so it was theoretically OK, but ...

I connected "The official and recommended universal micro USB power supply for Raspberry Pi" and all problems disappeared. :D:D:D

Power seems all important when using the Pi, I noticed the other day on one of my Pi3 B's when installing software the little lightening symbol kept appearing on the TV screen top right, the program kept crashing and not loading :yikes:, I was using a 2.5amp supply but I had used a different USB A-microUSB cable - it was a little thinner, that was the problem the cable couldn't handle the current, replaced with a thicker one and no power issues. Worth checking out for some......... always use a good heavy grade cable when used with a USB socket out supply.
 
When I muck around with my Moode builds and login via ssh I get the following warning (on Mac OSX):

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
--DELETED JUST IN CASE IT MAKES MY SYSTEM VULNERABLE--
Please contact your system administrator.
Add correct host key in /Users/rhaaland/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/rhaaland/.ssh/known_hosts:8
ECDSA host key for moode.local has changed and you have requested strict checking.
Host key verification failed.


This prevents me from logging in to moode so... each time, I go in and edit the "known_hosts" file... deleting lines that appear to be relevant (though somewhat blindly). Retry ssh and all is good. Is there something I'm doing wrong or should set on my system to prevent this 'annoyance'?

All my Moode systems are working just fine.

Thanks for the advice.

Ryan

Hi, Ryan.

While this message should always be taken seriously, in this case the cause is simply that when building moOde on a host a new key is generated which doesn't match the previous one for the same host.

I assume you are running on a simple home network in which case the easiest fix is simply to delete the ~/.ssh/known_hosts file. It will be rebuilt as you SSH into various hosts.

If you must edit the known_hosts file, keep in mind that the hashed entries are long lines which may wraparound on a small screen, so be careful how you go about deleting them. The power-user tool ssh-keygen is useful
Code:
ssh-keygen -R moode
---or possibly---
ssh-keygen -R moode.local

Regards,
Kent
 
I installed version 4.0 and for a long time everything was fine. Lately, straming is interrupted even with mp3 files. I tried to increase the buffer but the problem remains.
Do you have any suggestion ?

@supertrichi

Insufficient information.

With problems like this you always need to provide some background:

What model RPi?
Is the network connection via wired Ethernet or WiFi? (Or is moOde running standalone in AP mode?)
If WiFi are you also using Bluetooth?
In the cases of WiFi and/or Bluetooth, are you using integrated adapters (such as those on the RPi3B) or external ones?
What do you mean by "str[e]aming"? Are you playing local files or files from a NAS or streaming from a remote source such as a radio station or Tidal/QOBuzz/GMusic/Spotify?

Whenever I'm told something used to work and now it doesn't, my first question is, what has changed?

In your case, what has changed between when moOde was working to your satisfaction and now? New RPi, new location, more equipment/cabling, turned on Bluetooth, different access point, additional interfering WiFi sources, different power supply/cable...the list goes on.

Regards,
Kent
 
Last edited: