Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


MPD crashed when using UPnP
#1
So I have been streaming some audio from my computer to Moode via UPnP. While it does play for a while it will eventually crash MPD (which is what I am told by Moode (see attached screenshot).

Here is a snip of the log as it happens:
Code:
20221011 151355 worker: USB volume knob (Off)
20221011 151355 worker: USB auto-mounter (udisks-glue)
20221011 151355 worker: Saved MPD vol level (0)
20221011 151355 worker: Preamp volume level (0)
20221011 151355 worker: MPD volume level (0) restored
20221011 151355 worker: ALSA volume level (None)
20221011 151355 worker: Auto-play (Off)
20221011 151355 worker: CoverView toggle (-off)
20221011 151355 worker: Library scope (all)
20221011 151355 worker: Maintenance interval (360 minutes)
20221011 151355 worker: Screen saver activation (Never)
20221011 151355 worker: Session permissions (OK)
20221011 151355 worker: Mount monitor (Off)
20221011 151355 worker: Watchdog started
20221011 151355 worker: Ready
20221011 161752 command/index.php: Connection to MPD failed
20221011 161756 getMpdSock(): Connection to MPD failed
20221011 161909 getMpdSock(): Connection to MPD failed
20221011 161913 getMpdSock(): Connection to MPD failed
20221011 161913 getMpdSock(): Connection to MPD failed
20221011 162242 worker: File check (OK)
20221011 162243 worker: Session vacuumed
20221011 162243 worker: Session loaded
20221011 162243 worker: Debug logging (OFF)
20221011 162243 worker: --
20221011 162243 worker: -- Audio debug
20221011 162243 worker: --
20221011 162243 worker: ALSA cards: (0:sndrpihifiberry | 1:empty | 2:empty | 3:empty
20221011 162243 worker: MPD config: (0:HiFiBerry Digi+ Pro | mixer:(none) | card:0)
20221011 162243 worker: ALSA mixer actual (none)
20221011 162243 worker: ALSA volume (none)
20221011 162243 worker: --
20221011 162243 worker: -- System
20221011 162243 worker: --
20221011 162243 worker: Host      (moode)

The only way to get it working again is the reboot, or restart the servers (moodeutl -r).


Attached Files Thumbnail(s)
   
Reply
#2
Maybe try turning on MPD verbose logging in MPD Config and then examine /var/log/mpd/log to see if there is any clue as to what might be happening.

Also try playing the same files directly w/o using UPnP and see of the issue occurs.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
Where is the MPD log located?
NM, found it in the moodeutl.
Reply
#4
It finally did it again:

Code:
Oct 13 13:00 : player: played "http://192.168.1.10:49152/audirvana/audio_0_0.wav"
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:00 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:01 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:01 : alsa_output: Decoder is too slow; playing silence to avoid xrun
Oct 13 13:01 : alsa_output: Decoder is too slow; playing silence to avoid xrun

I was playing a 16/44.1 file when it happened, so the ‘decoder too slow’ sounds wrong.

I’m going to try another app to stream the audio to Moode.
Reply
#5
@hestehandler

Speaking only for myself, I didn't respond before now because there is so little information to act on here.

I'm not a regular UPnP user but I set up a test today where the mConnect Control Point app on my iPad has been directing the UPnP Renderer on a moOde 8.2.0 player to play tracks from the minimserver UPnP Media Server on my Linux laptop for hours. There's been no interruption to the playback in several hours. 

I'm guessing you may be suffering interruptions in your LAN traffic or from your Media Server which can give rise to those underrun error messages.

Regards,
Kent
Reply
#6
(10-16-2022, 03:01 AM)TheOldPresbyope Wrote: @hestehandler

Speaking only for myself, I didn't respond before now because there is so little information to act on here.

I'm not a regular UPnP user but I set up a test today where the mConnect Control Point app on my iPad has been directing the UPnP Renderer on a moOde 8.2.0 player to play tracks from the minimserver UPnP Media Server on my Linux laptop for hours. There's been no interruption to the playback in several hours. 

I'm guessing you may be suffering interruptions in your LAN traffic or from your Media Server which can give rise to those underrun error messages.

Regards,
Kent

I was myself suspecting the same. I have been getting other weird errors involving the LAN. Something is wrong and I suspect my switch or cable.
Reply
#7
Hello,

 I have got recently the same issue.

I'm using moode as an upnp renderer controlled by Bubbleupnp.

Until a month ago my library was essentially a local ums server.

But for now on (after getting fiber connected) i'm using primarily my dropbox account, where a copy of my library is.

And I noticed that sometimes moode upnp service seems to crash. I had a look on system info which indicates the following message:

Getmpdsock() : connection to mpd failed

At this point Renderer cannot be seen anymore

I tried to restart upnp, but that's doesn't fix the issue.

I have to restart the system in order to use it again as a renderer.

After reading your previous posts, i went to consider that it could be streaming stability issue coming from the wan (even fiber connection doesn't guaranty a perfectly stable stream, especially when there are very large DSD files.

So I tried yesterday to modify resource allocation in MPD settings: Audio Buffer to 64 MB, Output Buffer to 512 MB, Max queue items to 32768 and Input cache to 1 GB.

Today, i played almost exclusively DSD files via Dropbox and haven't got any issue.

Let's see the next days...

Sincerely

François
Reply
#8
(01-24-2023, 09:52 PM)Grenelle Wrote: So I tried yesterday to modify resource allocation in MPD settings: Audio Buffer to 64 MB, Output Buffer to 512 MB, Max queue items to 32768 and Input cache to 1 GB.

Sincerely

François

Do you mind pointing me to where to find out how to do those changes? 
(Background is that I am battling with moOde on a RPI zero w and I am also seeing crashes and a freezing Web GUI all while streaming 16/44.1 via UPnP)
i.e.
Code:
alsa_output: Decoder is too slow; playing silence to avoid xrun 
Listening with the latest moOde on a RPI zero w with a MiniBoss DAC PCM5122 32bit 384kHz and a Volt+ AMP on a pair of Monitor Audio Bronze 100 speakers.

pi@moody:~ $ moodeutl -m 
CPU: 1.0 GHz, LOAD: 35% 47C | MEM: 63% used | DISK: 39% used, 4.1G free | PHP: 7 workers
Reply
#9
(02-08-2023, 05:36 PM)izii Wrote:
(01-24-2023, 09:52 PM)Grenelle Wrote: So I tried yesterday to modify resource allocation in MPD settings: Audio Buffer to 64 MB, Output Buffer to 512 MB, Max queue items to 32768 and Input cache to 1 GB.

Sincerely

François

Do you mind pointing me to where to find out how to do those changes? 
(Background is that I am battling with moOde on a RPI zero w and I am also seeing crashes and a freezing Web GUI all while streaming 16/44.1 via UPnP)
i.e.
Code:
alsa_output: Decoder is too slow; playing silence to avoid xrun 

You can look into Configuration => MPD, at the bottom of the page.
Reply
#10
Ummm...

The original Pi Zero W has only 512MB of RAM so increasing buffer sizes beyond the default settings is unlikely to buy much.

Also, the Pi Zero W has a older, single-core armv6 CPU so it's seriously under-powered compared to any of the armv7-based Pi models.

I dig mine out of the drawer only for testing purposes these days. Firing it up with moOde 8.2.5 and a USB DAC and playing Qobuz tracks via BubbleUPnP on my phone to moOde's UPnP renderer, I see sluggish UI response but once a track is playing I have no trouble with playback.

Keep in mind that the WiFi adapter and antenna of the Zero W aren't super either so performance can suffer if the Zero W isn't close to the WiFi access point or there's lots of competing sources.

Of course having a good power supply is a necessity with Pis but we've beat that subject to death in other threads.


I know every model Pi is either unobtainium or 2expensium these days, but IMHO the Zero W has effectively reached the end of its useful life.

Just my 2-cents worth.


Regards,
Kent
Reply


Forum Jump: