Moode Audio Player for Raspberry Pi

Jump to Latest
#8,942
Since I wrote that I've had three outages - but, with fixed IP I am able to reconnect, so something you are doing is working to reconnect 🙂 You're a marvel!

I think I'm going to go for a drive... my lovely little Alfa is going to a new home soon... and I live at the end of a long and very windy road. I'll go and check out how many slips there are and whether any trees have come down. Sheep are about to burst, hopefully I will have some new lambs before I leave!
 
#8,943
@Tim...Definitely grumpy ;-) ..

Or the effect of wild weather on ones patience...😉
We have 130kmh + raging winds at the moment....
Unfortunately Zoot's on a Hill while we're in a Valley so no probs here..

That's assuming he's not in Borneo right this minute 😕
 
#8,944
Zootalaws said:
Does anyone have an easy script or tool to automatically reconnect WiFi?

We get a LOT of small power outages and the Pi comes up much quicker than the router, resulting in an isolated Pi.

Maybe you could look at this as a ToDo? If wifi doesn't connect for, say, 2M then go back to AP mode?

Or maybe I'm just grumpy - it took three reboots in the middle of the night before I went and unplugged my Pi - damned auto-start >.<

I think I've counted about eight since 8am... it's only 10 🙁
Click to expand...

Hi Mike,

Its sort of an edge case to deal with but one approach would be have some code in Worker.php (runs every 3 secs) ping the Gateway address for each interface and then down/up the interface if the ping fails. Eventually, when the ping is successful i.e., Router comes back up, that final iface down/up will grab afresh DHCP address.

Maybe a feature "LAN/WiFi reconnect" ?

-Tim
 
#8,946
TimCurtis said:
Advanced-LL kernel and the Real-time FIFO and RR scheduler policies might not work well on low powered Pi for example Pi-1B, especially if its not over-clocked to 1 gHz and a USB DAC is being used. USB audio interface is less efficient than I2S interface. In this case I'd use TS policy.

It's also possible that FIFO and RR should only be used with the Real-time kernel because these policies assign MPD a fixed scheduler priority and this might not be best for the non-Real-time, Low Latency kernel.

In the upcoming 3.8.3 update I'm leaning toward the following combinations.

Standard: TS only
Adv-LL: TS only, Adjustable latencies
Adv-RT: TS, RR and FIFO
Click to expand...
On my Pi3 with USB attached storage I like LL / FIFO with the performance profile set to remove dynamic CPU scaling and even underclock things in config.txt but I use it with a spdif hat rather than a dac and don't oversample anything so mpd isn't doing a lot of work. There's no such thing as a free lunch, the low latency kernels sacrifice performance to get those results, if you're working your Pi hard they might not be a good fit.
 
#8,951
yannig said:
Hello Tim

This is not important, but when I click on "view Status of db update", it does not work.
It points to "moode:8200" who returns an error.


(And not to "moode.local:8200").
Click to expand...

philrandal said:
moode.local won't work on an Android device. Better to use the IP address as the link.

Phil
Click to expand...

I get the same result. Tim somehow manages to get name resolution without a domain. I've never been able to.
 
#8,952
Guys,

Anyone have tried the Librespot with 3.8.2 (fresh install)?
During setup, I'm getting the error message when enabling the service:

pi@moodesalon:~ $ sudo systemctl enable spotify-connect.service
Failed to execute operation: Bad message

I'm using the same config as with previous versions: PiZero with PlainDAC+

3.8.2 is the first 3.8 I'm using (Librespot was working on 3.7)
 
Last edited:
#8,953
mRqS said:
Guys,

Anyone have tried the Librespot with 3.8.2 (fresh install)?
During setup, I'm getting the error message when enabling the service:

pi@moodesalon:~ $ sudo systemctl enable spotify-connect.service
Failed to execute operation: Bad message

I'm using the same config as with previous versions: PiZero with PlainDAC+

3.8.2 is the first 3.8 I'm using (Librespot was working on 3.7)
Click to expand...

Have a look at the logs, they will tell you what the cause of the error is.

syslog in /var/log

you can look at the whole log: 'cat syslog'
you can watch a 'live' presentation of the last 10 syslog entries, updated: 'tail -f syslog' (ctrl+c to exit)
you can look through the log and only show errors, a specific executable, etc.: 'cat syslog|grep spotify' or 'cat syslog|grep error' for example.

I would start by performing a 'tail-f syslog' and then in another terminal window execute 'sudo systemctl enable spotify-connect.service' and see what happens in the other window.

If you don't get enough info, turn on debugging and do it again.
 
Last edited:
#8,957
Woohoo,

Raspbian Stretch has been released:

2017-08-16:
* Based on Debian Stretch (Debian version 9)
* Version 60 of Chromium browser included
* Version 3.0.1 of Sonic Pi included
* Version 6.1.1 of RealVNC included
* Version 0.17.4 of NodeRED included
* Bluetooth audio routed via ALSA rather than Pulseaudio
* SenseHAT extension added to Scratch 2
* Various desktop applications modified to prompt for sudo password if needed
* lxinput control options for mouse speed simplified
* lxpanel plugins moved into separate packages
* Wireless firmware for Pi 3 and Pi 0W modified to address Broadpwn exploit
* Latest kernel and firmware
* Various small tweaks, bug fixes and theme modifications

Cheers,

Phil
 
Last edited:
#8,960
philrandal said:
Woohoo,

Raspbian Stretch has been released:

2017-08-16:
* Based on Debian Stretch (Debian version 9)
* Version 60 of Chromium browser included
* Version 3.0.1 of Sonic Pi included
* Version 6.1.1 of RealVNC included
* Version 0.17.4 of NodeRED included
* Bluetooth audio routed via ALSA rather than Pulseaudio
* SenseHAT extension added to Scratch 2
* Various desktop applications modified to prompt for sudo password if needed
* lxinput control options for mouse speed simplified
* lxpanel plugins moved into separate packages
* Wireless firmware for Pi 3 and Pi 0W modified to address Broadpwn exploit
* Latest kernel and firmware
* Various small tweaks, bug fixes and theme modifications

Cheers,

Phil
Click to expand...

Hi Phil,

Nice 🙂 I see the BT stack is back to using ALSA so there is hope.

-Tim
 
You must log in or register to reply here.
Top Bottom