Official moOde 7.3.0 support thread

[Busybox]

Unless Tim has the image setup in an unusual way,  Win32 DiskImage will do exactly what you want.

Thanks, but I prefer to stay away from Windows for this sort of thing. Once the dust settles after upgrading my six moode systems to the new release, I'll try Clonezilla which runs on pretty much everything.

However the problem with such wholesale backups is that they can only be restored to their original sources. For example I can't take a backup from one moode system and restore it to another with a different audio card, even if all I really wanted to restore was non-hardware-specific data like my radio stations, playlists, audio files, etc.

Doing reliable, selective, intelligent backup/restore functionality requires a lot of coding. And probably not worth it for most users who, unlike me, have only one or two moode systems.

Cheers,

- Steve

[Blobby]

Whats the output from the command below?

Code:

Code:

./piano.sh

Thanks Tim for the reply.
I won't be able to do this for a day or two - will post the requested info then..

[ElliottDesigns]

a new fresh image fix the problem (i saved moodecfg.ini to make it quickly). Maybe there is a bug on upgrade script, something messing with the spotify overlay vs mdp

I've just done an inline update to 7.3.0 and I also see this oddness in the Spotify renderer.

Yes a bug due to a missing file in the the update package :-0

A new package was uploaded just a bit ago but it may take some time before the AWS CloudFront caches are refreshed.

-Tim

Is there a way to get this to apply to an already upgraded system Tim?

Give this a try.

Code:

sudo wget -q http://moodeaudio.org/test/r730patch1.zip
sudo unzip -q r730patch1.zip
sudo mv spotevent.sh /var/local/www/commandw/
sudo chown root:staff /var/local/www/commandw/spotevent.sh
sudo rm r730patch1.zip

Hi Tim,

Sorry to bother you again. It seems like the commands went through now, as in I wasn't getting any errors after I entered each command, but I didn't get any response back (to show it doing stuff) either. I figured it did it, so I restarted the device. Still not coming up on my Spotify account as a device to connect to (yes it's a premium account). Maybe the installation went wrong??? I did do it over SSH, don't really know another way to access the command line since it blacks out the screen once everything is loaded (as a headless system should), just saying I couldn't see if it would work locally. Hope you can help.

Many thanks,
Elliott Dyson.

[Tim Curtis]

The standard in Linux for command output is to only print a message if the command was not successful.

The symptom "...not coming up on my Spotify account as a device to connect to" is a different issue than the one the patch addresses.

If the Spotify renderer is running but not showing up as a device to connect to in the Spotify app it would suggest a network issue or something else external to moOde software. The command below will return a number if the Spotify renderer is running.

Code:

pgrep librespot

[ElliottDesigns]

The standard in Linux for command output is to only print a message if the command was not successful.

The symptom "...not coming up on my Spotify account as a device to connect to" is a different issue than the one the patch addresses.

If the Spotify renderer is running but not showing up as a device to connect to in the Spotify app it would suggest a network issue or something else external to moOde software. The command below will return a number if the Spotify renderer is running.

Code:

pgrep librespot

Ok, it did return a number (964 to be exact), but I'm not sure what's going wrong, I've tried running on my home network with both devices connected to the 2Ghz band, and with both devices connected to my phone's hotspot. Am I trying to access it wrong on the app? I just can't see what else it could be.

[grumbleweed]

Panels.css, in the source files, has a rouge semi-colon at the start of the declaration block on line 391.

Paul

[Tim Curtis]

Thanks, I'll fix that.

[varunpj]

Hi, I'm using moode audio in my digione signature. Using ethernet, all default settings.
In 7.3, Spotify connect is unusable. It keeps disconnecting, severe lag in controls and stuttering. Local files play perfectly.
I downgraded to 7.1, its working perfectly.
Are anyone else facing these issues?

[Stack]

Greetings,

I'd been using a very old version of Moode on two RPi 3B's. No special hardware. Just speakers plugged into the headphone jack. No monitor either and an NFS mount for the music. I upgraded to 7.3.0 and I could play streaming music and MP3's but not my FLAC files.

I re-did the install and only made a single tweak at a time to figure out which of the settings did it in. Turns out, my on the whim decision of "let's change to 64bit kernel" is what did me in. When I switch back to the 32bit kernel, all the music plays. When I switch back to the 64bit kernel only the stream (I tested on Swiss classical) and mp3's play.

I see the the "experimental" notice for the 64bit kernel and it isn't like I'm doing anything that really /needs/ the 64bit kernel anyway. I just thought I'd try it. And since I had issues, I thought I should report them.

Thanks!

[Tim Curtis]

Thanks. There are still many issues with 64-bit kernel and OS. The most common is that MPD crashes sometimes during database update.