Official moOde 7.4.y support thread

[Tim Curtis]

I have 2 Pi based streamers, both running MoOde 7.4.0 and I have an issue with Spotify connect: I can initially connect to it, plays ok, but if I pause or change volume the connection drops and reverts to local/controlling device (usually my iPhone), on both MoOde streamers.
First I suspected my phone but I tried my wife's and it does the exact same thing.
Then I tried the same switching the stream between my phone and my laptop. It works flawlessly.
So I guess this points to some issue with the 7.4.0 version... or the librespot library? Anybody knows anything about this?

Works fine on my end using iPhone and iMac. 

You might try running it from SSH and see if it reports any errors. If so then you could submit an issue to the librespot team.

Code:

# Turn it off in Audio Config

# Run the command below substituting your Spotify name for "RP2 Spotify" after the  --name parameter.
sudo librespot --name RP2 Spotify --bitrate 320 --format S16 --initial-volume 0 --volume-ctrl log --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device _audioout --onevent /var/local/www/commandw/spotevent.sh

[suzywong]

Two systems happily running 7.3.0. Attempted "in-place" updates on both, via Check For Update in System Config page

1. Allo USBridge Signature (CM3) + Allo DigiOne Signature: no problem - in fact, the in-place upgrade process "just worked" LOL

2. RPi3B+ + IQAudio Digi+: "Software is up to date". System Info shows 7.3.0 2021-06-25.

Any thoughts on things to try on system 2 before I do a clean install? No rush on this as I won't get back to it until the weekend - the call of "parental duty" moving daughter across London Town!

Cheers

Chris

[Tim Curtis]

Reboot system 2 and post the following logs.

Code:

moodeutl -l

cat /var/local/www/update-r730.log

[brotakul]

I have 2 Pi based streamers, both running MoOde 7.4.0 and I have an issue with Spotify connect: I can initially connect to it, plays ok, but if I pause or change volume the connection drops and reverts to local/controlling device (usually my iPhone), on both MoOde streamers.
First I suspected my phone but I tried my wife's and it does the exact same thing.
Then I tried the same switching the stream between my phone and my laptop. It works flawlessly.
So I guess this points to some issue with the 7.4.0 version... or the librespot library? Anybody knows anything about this?

Works fine on my end using iPhone and iMac. 

You might try running it from SSH and see if it reports any errors. If so then you could submit an issue to the librespot team.

Code:

# Turn it off in Audio Config

# Run the command below substituting your Spotify name for "RP2 Spotify" after the  --name parameter.
sudo librespot --name RP2 Spotify --bitrate 320 --format S16 --initial-volume 0 --volume-ctrl log --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device _audioout --onevent /var/local/www/commandw/spotevent.sh

Thanks Tim for supporting.
I ran the command and it runs without errors. Also, I see no messages in journalctl when the drop event occurs. Should I also look somewhere else? Should I still also open a bug report with librespot? Thing is, I don't have much to support the bug claim at this point... just what I experience. Thanks again!

[ElmhurstFun]

Having problems with a missing Graphic EQ custom curve and curious if this is a bug or an expected result.  Here is the scenario:

-- I did an in-place upgrade from 7.3 to 7.4 - worked fine. 
-- I then used the backup feature to create a backup file.
-- Did a clean install of 7.4
-- Used the previously created backup file to do a restore of configs, etc.
-- My custom graphic EQ curves did not come back  

Any ideas?  Thanks

[ElmhurstFun]

Having problems with a missing Graphic EQ custom curve and curious if this is a bug or an expected result.  Here is the scenario:

-- I did an in-place upgrade from 7.3 to 7.4 - worked fine. 
-- I then used the backup feature to create a backup file.
-- Did a clean install of 7.4
-- Used the previously created backup file to do a restore of configs, etc.
-- My custom graphic EQ curves did not come back  

Any ideas?  Thanks

Looking at the backup file, looks like it backs up the parametric EQ values but not graphical EQ.   The alsaequal value got backed up as the name of my custom curve but that curve no longer exists

[bitlab]

@ElmhurstFun you are absolutely right, GEQ isn't currently part of the backup/autocfg. Sorry about that.
You can find the missing parts in the backup at https://github.com/moode-player/moode/issues/301.

[ElmhurstFun]

@ElmhurstFun you are absolutely right, GEQ isn't currently part of the backup/autocfg. Sorry about that.
You can find the missing parts in the backup at https://github.com/moode-player/moode/issues/301.

Thanks - not a huge deal to recreate manually, it's great having the overall backup/restore facility in general - I appreciate all the hard work in getting the current capabilities implemented!

[Jedrek]

@the_bertrum
@Tim Curtis
@TheOldPresbyope

I've spent the last two days trying to fix my UPNP and DLNA issues. It turns out that even if we go very deep when indexing DLNA content - to the level of a directory where there are only subdirectories with music and we will index through directories, the system freezes, which is manifested by continuous green LED lighting. After about a minute, when the system starts working normally, the "UPNP" directory in the "MNT" directory disappears. After which I get an endpoint access error.
You need to restart the player and force DLNA directory level to "Update this folder". Then indexing takes place again, but until now. A directory in which there are about 1000 subdirectories with music, and each directory has 10-15 songs, requires at least three reboots of the device and forcing the "Update this folder" option, of course after about a 1-minute break due to the lack of access to the player (green LED will be lit all the time).
I don't understand one more action. Well, if I clearly indicate the directories in DLNA resources that I want to be scanned, why does the cover scan scan the entire DLNA server anyway?
I don't understand that.

[brotakul]

I have 2 Pi based streamers, both running MoOde 7.4.0 and I have an issue with Spotify connect: I can initially connect to it, plays ok, but if I pause or change volume the connection drops and reverts to local/controlling device (usually my iPhone), on both MoOde streamers.
First I suspected my phone but I tried my wife's and it does the exact same thing.
Then I tried the same switching the stream between my phone and my laptop. It works flawlessly.
So I guess this points to some issue with the 7.4.0 version... or the librespot library? Anybody knows anything about this?

Works fine on my end using iPhone and iMac. 

You might try running it from SSH and see if it reports any errors. If so then you could submit an issue to the librespot team.

Code:

# Turn it off in Audio Config

# Run the command below substituting your Spotify name for "RP2 Spotify" after the  --name parameter.
sudo librespot --name RP2 Spotify --bitrate 320 --format S16 --initial-volume 0 --volume-ctrl log --cache /var/local/www/spotify_cache --disable-audio-cache --backend alsa --device _audioout --onevent /var/local/www/commandw/spotevent.sh

Thanks Tim for supporting.
I ran the command and it runs without errors. Also, I see no messages in journalctl when the drop event occurs. Should I also look somewhere else? Should I still also open a bug report with librespot? Thing is, I don't have much to support the bug claim at this point... just what I experience. Thanks again!

OK, I did another test: I streamed on both Spotify Connect and Airplay from my phone to the RPi streamer and I used a second phone as a "witness" displaying MoOde interface. Upon connecting the stream to the RPi, the "Spotify/Airplay Active" message appeared on the second phone, as expected. When I disconnected the stream from Spotify though, it didn't also appear disconnected on the second phone, even if the music did stop playing on MoOde. I had to manually disconnect the stream directly from the second phone so the RPi to become available again in the Spotify Connect devices list.
It seems that, for some reason, the connection is not closed gracefully, so the RPi remains hanging.

Is this of any help? Is there any way to further check this out? Something more.. technical, maybe? At least to verify if it's a MoOde or librespot issue?