Moode Audio Player for Raspberry Pi

I see, it can select the driver correctly... and guess you already know about it 🙂 ...was suggesting an update to the description in the UI dropdown.

HDMI: 30ma power savings and possibly less noise. It's easy to do from command line: tvservice -o.

Hi Scott,

Yes, description for the Pro will be added to first Moode 2.7 update (soon) 🙂

I'll add "Disable HDMI" as setting on System config.

-Tim
 
Hi,

Run a 30 sec ping test from Pi#2 to Pi#1 and then examine the ping statistics for excessively long round trip times, packet loss, dropped packets, etc.

-Tim

Hi Tim,

ping was fine for 30 s. Running longer, Pi No1 (with Ethernet) lost connection and Pi No 2 obviously stopped playing music from the nas Share. To be sure about the network itself I observed no stops before changing to moode for Pi1 (before there was volumio on it) and no stops listening to radio on pi1. Any idea greatly appreciated!

Best regards GM
 
Hi Tim,

ping was fine for 30 s. Running longer, Pi No1 (with Ethernet) lost connection and Pi No 2 obviously stopped playing music from the nas Share. To be sure about the network itself I observed no stops before changing to moode for Pi1 (before there was volumio on it) and no stops listening to radio on pi1. Any idea greatly appreciated!

Best regards GM

Hi, GM.

Pi No1 lost connection?

I'm interpreting this to mean it could no longer talk to the local network. How did this manifest itself? Is it that you were pinging it from Pi No2 and suddenly Pi No1 was no longer accessible? And, at this point, using a web browser on another device you could access the Moode GUI on Pi No2 but not on Pi No1? And, at this point, the same is true for ssh'ing to Pi No2 and No1? If you could still access Pi No1 via GUI or ssh then we need to look beyond the network connection itself.

Out of curiosity, what raspberry pi model is Pi No1? What does it connect to via ethernet (e.g., how does it reach your local network)?

Once we understand your installation we can suggest logs to post.

Regards,
Kent
 
Hi Tim,

ping was fine for 30 s. Running longer, Pi No1 (with Ethernet) lost connection and Pi No 2 obviously stopped playing music from the nas Share. To be sure about the network itself I observed no stops before changing to moode for Pi1 (before there was volumio on it) and no stops listening to radio on pi1. Any idea greatly appreciated!

Best regards GM

Hi,

Run 30 sec ping test again and post back the ping statistics.

The symptom "Pi No1 (with Ethernet) lost connection" suggests an issue with either the network or the Pi.

-Tim
 
Hi Kent,

thank you for taking the time. I answered your clarifying questions in bold letters.

Pi No1 lost connection?

I'm interpreting this to mean it could no longer talk to the local network. How did this manifest itself? Is it that you were pinging it from Pi No2 and suddenly Pi No1 was no longer accessible?

That is true.

And, at this point, using a web browser on another device you could access the Moode GUI on Pi No2 but not on Pi No1?

That is true as well.

And, at this point, the same is true for ssh'ing to Pi No2 and No1?

At this time I could ssh to Pi No2 but not to Pi No 1

If you could still access Pi No1 via GUI or ssh then we need to look beyond the network connection itself.

So it seems to possibly be a network issue? Ethernet itself seemed to work since radio music on Pi No1 did not stop at any time, even though the stream to Pi2 got lost at one time for more than 30 s.

Out of curiosity, what raspberry pi model is Pi No1? What does it connect to via ethernet (e.g., how does it reach your local network)?

Both Pis are Pi3. Pi No1 connects to my network using dlan(powerlan). Pi No2 uses integrated wlan or as a test same type of dlan device.

Once we understand your installation we can suggest logs to post.

Regards,
Kent[/QUOTE]

Regards and thanks for the effort.
 
Hi Kent,

thank you for taking the time. I answered your clarifying questions in bold letters.

Pi No1 lost connection?

I'm interpreting this to mean it could no longer talk to the local network. How did this manifest itself? Is it that you were pinging it from Pi No2 and suddenly Pi No1 was no longer accessible?

That is true.

And, at this point, using a web browser on another device you could access the Moode GUI on Pi No2 but not on Pi No1?

That is true as well.

And, at this point, the same is true for ssh'ing to Pi No2 and No1?

At this time I could ssh to Pi No2 but not to Pi No 1

If you could still access Pi No1 via GUI or ssh then we need to look beyond the network connection itself.

So it seems to possibly be a network issue? Ethernet itself seemed to work since radio music on Pi No1 did not stop at any time, even though the stream to Pi2 got lost at one time for more than 30 s.

Out of curiosity, what raspberry pi model is Pi No1? What does it connect to via ethernet (e.g., how does it reach your local network)?

Both Pis are Pi3. Pi No1 connects to my network using dlan(powerlan). Pi No2 uses integrated wlan or as a test same type of dlan device.

Once we understand your installation we can suggest logs to post.

Regards,
Kent

Regards and thanks for the effort.[/QUOTE]

On a RPi3B, you could be connected to your local network simultaneously via two separate interfaces: the wireless WiFi adapter (usually wlan0) and the wired ethernet adapter (usually eth0). When you are able to ssh to PI No1, try the ifconfig command. It will report the internet addresses (inet addr🙂 for any adapters which are "up". A network sniffer would also show this. You should be able to connect to Pi No1 using either address.

At a guess, your Pi No1 is getting the internet radio stream via one of these adapters while the apps on your Pi No2 (e.g., ssh and web browser) are talking to it via the other adapter. Still don't know what's causing the drop out you see but this would explain why the radio music continues.

Sorry, I have to run for an appointment. Will check back later.

Regards,
Kent
 
commercial free radio stations

Hi folks,

I am listening with moode (sadly V2.6, but V2.7 is going to follow soon...) and I really enjoy it. Just one thing to mention: In the radio stations list there are many stations that are not commercial free. Maybe this is caused by the region where the listener is located, but if it is a general item this should be changed. If somebody wants commercials he can add these stations by himself - I can renounce them 😉 - for pure listening pleasure.

Nice work Tim, go ahead :cheers:
 
Hi folks,

I am listening with moode (sadly V2.6, but V2.7 is going to follow soon...) and I really enjoy it. Just one thing to mention: In the radio stations list there are many stations that are not commercial free. Maybe this is caused by the region where the listener is located, but if it is a general item this should be changed. If somebody wants commercials he can add these stations by himself - I can renounce them 😉 - for pure listening pleasure.

Nice work Tim, go ahead :cheers:

Hi,

There are some stations that have minimal commercials for example the AddictedToRadio stations, and I'm sure there are others.

Which stations are u referring to?

-Tim
 
Hi Tim, Hi all
Since upgrading to 2.7 i can't connect via my pi3's wifi. When I try to enter in the SSID in the configuration menu it tells me 'Please match the configuration format'.
I've also made the changes /boot/moodecfg.txt and it appeared to take it, but then won't actually work when i take out the ethernet cable. I wondered whether my wifi on the pi3 board might be bust but i swapped in the sd card from another of my pi3's on moode 2.6 and all worked perfectly. Any ideas what's going on?
 
Hi Tim
It was simply that I hadn't spotted the new addition of 'Pi3 WiFi-BT adapter' option in the Maintenance part of the system config page. It was set to 'off' on mine by default. Put simply, I was being an idiot!

Thanks Tim

Hi,

In Moode 2.7 image it should default to ON for Pi-3 and for other Pi's the setting will not appear.

Do u by any chance turn it off at some point?

-Tim
 
Regards and thanks for the effort.

On a RPi3B, you could be connected to your local network simultaneously via two separate interfaces: the wireless WiFi adapter (usually wlan0) and the wired ethernet adapter (usually eth0). When you are able to ssh to PI No1, try the ifconfig command. It will report the internet addresses (inet addr🙂 for any adapters which are "up". A network sniffer would also show this. You should be able to connect to Pi No1 using either address.

At a guess, your Pi No1 is getting the internet radio stream via one of these adapters while the apps on your Pi No2 (e.g., ssh and web browser) are talking to it via the other adapter. Still don't know what's causing the drop out you see but this would explain why the radio music continues.

Sorry, I have to run for an appointment. Will check back later.

Regards,
Kent[/QUOTE]

Hi Kent,

I tried ifconfig. It shows eth0 at one ip and local loopback at another ip. As I understand, local loopback should not conflict? Maybe I will try this weekend using wlan for pi No1 which will need a little relocation work. Still hoping to get it work. If not maybe I will just use a second harddisc on pi 2 and stop trying to use nas services...

Best regards GM