Official moOde 7.2.0 support thread

[radu-]

Just updated from 7.1.0 to 7.2.0 on a RPi Zero with Hifiberry DAC+ and have no sound at all. So I checked and to my surprise there's no snd_rpi_hifiberry_dac module anymore.

Code:

$ sudo modprobe snd_rpi_hifiberry_dac
modprobe: FATAL: Module snd_rpi_hifiberry_dac not found in directory /lib/modules/5.4.77+

What should I do in this case?

[Tim Curtis]

There has never been such a module.

I2S audio devices use a Device Tree Overlay file thats in the /boot/overlays directory. Here's all the Hifiberry overlays.

Code:

pi@moode:/opt $ ls -l /boot/overlays/hifiberry*
-rwxr-xr-x 1 root root  779 Dec  7 22:43 /boot/overlays/hifiberry-amp.dtbo
-rwxr-xr-x 1 root root  655 Dec  7 22:43 /boot/overlays/hifiberry-dac.dtbo
-rwxr-xr-x 1 root root 2004 Dec  7 22:43 /boot/overlays/hifiberry-dacplusadc.dtbo
-rwxr-xr-x 1 root root 1921 Dec  7 22:43 /boot/overlays/hifiberry-dacplusadcpro.dtbo
-rwxr-xr-x 1 root root  699 Dec  7 22:43 /boot/overlays/hifiberry-dacplusdsp.dtbo
-rwxr-xr-x 1 root root 1916 Dec  7 22:43 /boot/overlays/hifiberry-dacplus.dtbo
-rwxr-xr-x 1 root root 2007 Dec  7 22:43 /boot/overlays/hifiberry-dacplushd.dtbo
-rwxr-xr-x 1 root root  959 Dec  7 22:43 /boot/overlays/hifiberry-digi.dtbo
-rwxr-xr-x 1 root root 1125 Dec  7 22:43 /boot/overlays/hifiberry-digi-pro.dtbo
pi@moode:/opt $

Per the in-place update instructions:
"After reboot open MPD Config and SAVE to update the settings." 

If you still have no sound after doing this, post the Moode startup log.

Code:

moodeutl -l

[radu-]

There has never been such a module.

I2S audio devices use a Device Tree Overlay file thats in the /boot/overlays directory. Here's all the Hifiberry overlays.

Code:

pi@moode:/opt $ ls -l /boot/overlays/hifiberry*
-rwxr-xr-x 1 root root  779 Dec  7 22:43 /boot/overlays/hifiberry-amp.dtbo
-rwxr-xr-x 1 root root  655 Dec  7 22:43 /boot/overlays/hifiberry-dac.dtbo
-rwxr-xr-x 1 root root 2004 Dec  7 22:43 /boot/overlays/hifiberry-dacplusadc.dtbo
-rwxr-xr-x 1 root root 1921 Dec  7 22:43 /boot/overlays/hifiberry-dacplusadcpro.dtbo
-rwxr-xr-x 1 root root  699 Dec  7 22:43 /boot/overlays/hifiberry-dacplusdsp.dtbo
-rwxr-xr-x 1 root root 1916 Dec  7 22:43 /boot/overlays/hifiberry-dacplus.dtbo
-rwxr-xr-x 1 root root 2007 Dec  7 22:43 /boot/overlays/hifiberry-dacplushd.dtbo
-rwxr-xr-x 1 root root  959 Dec  7 22:43 /boot/overlays/hifiberry-digi.dtbo
-rwxr-xr-x 1 root root 1125 Dec  7 22:43 /boot/overlays/hifiberry-digi-pro.dtbo
pi@moode:/opt $

Per the in-place update instructions:
"After reboot open MPD Config and SAVE to update the settings." 

If you still have no sound after doing this, post the Moode startup log.

Code:

moodeutl -l

OK.. went and saved MPD Config - then rebooted.

I still get

Code:

Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": Device or resource busy

Here's what [bold]moodeutl -l[/bold] output is:

Code:

pi@dormi:~$ moodeutl -l
20210429 212115 worker: -- Start
20210429 212117 worker: Successfully daemonized
20210429 212118 worker: Integrity check (passed)
20210429 212122 moode.php: MPD connect failed: cmd=(playlist)
20210429 212123 worker: File check (OK)
20210429 212126 moode.php: MPD connect failed: cmd=(playlist)
20210429 212127 worker: Session vacuumed
20210429 212127 worker: Session loaded
20210429 212127 worker: Debug logging (OFF)
20210429 212127 worker: -- Audio debug
20210429 212127 worker: ALSA cards: (0:sndrpihifiberry | 1:empty | 2:empty | 3:empty
20210429 212127 worker: MPD config: (0:HiFiBerry DAC/DAC+ Zero | mixer:(none) | card:0)
20210429 212127 worker: ALSA mixer actual (none)
20210429 212127 worker: ALSA volume (none)
20210429 212127 worker: -- System
20210429 212201 worker: Host     (dormi)
20210429 212201 worker: moOde    (7.2.0 2021-04-24)
20210429 212201 worker: RaspiOS  (10.6)
20210429 212201 worker: Kernel   (5.4.77+ #1371)
20210429 212201 worker: Platform (Pi-Zero W 1.1 512MB)
20210429 212201 worker: ARM arch (armv6l, 32-bit kernel)
20210429 212201 worker: MPD ver  (0.22.6_p0x3)
20210429 212201 worker: CPU gov  (ondemand)
20210429 212201 worker: USB boot not available
20210429 212201 worker: File system expanded
20210429 212201 worker: HDMI port off
20210429 212201 worker: -- Network
20210429 212201 worker: eth0 does not exist
20210429 212201 worker: eth0 address not assigned
20210429 212201 worker: wlan0 exists
20210429 212201 worker: wifi country (RO)
20210429 212201 worker: wlan0 trying SSID (AddamsFamily24)
20210429 212202 worker: IP addr (10.11.12.106)
20210429 212202 worker: Netmask (255.255.255.0)
20210429 212202 worker: Gateway (10.11.12.1)
20210429 212202 worker: Pri DNS (10.11.12.77)
20210429 212202 worker: Domain  (None)
20210429 212202 worker: -- Audio config
20210429 212203 worker: MPD conf updated
20210429 212203 worker: ALSA card number (0)
20210429 212203 worker: MPD audio output (HiFiBerry DAC/DAC+ Zero)
20210429 212204 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20210429 212204 worker: ALSA mixer name (none)
20210429 212204 worker: MPD volume control (software)
20210429 212204 worker: Hdwr volume controller not detected
20210429 212204 worker: ALSA loopback (Off)
20210429 212204 worker: Reset renderer active flags
20210429 212207 worker: CamillaDSP (off)
20210429 212207 worker: -- MPD startup
20210429 212207 worker: MPD started
20210429 212214 worker: MPD accepting connections
20210429 212214 worker: MPD output 1 ALSA Default (on)
20210429 212214 worker: MPD output 2 ALSA Bluetooth (off)
20210429 212214 worker: MPD output 3 HTTP Server (off)
20210429 212214 worker: MPD crossfade (off)
20210429 212215 worker: MPD ignore CUE files (yes)
20210429 212215 worker: -- Feature availability
20210429 212215 worker: Source select (available)
20210429 212215 worker: Source select (source: MPD)
20210429 212215 worker: Source select (output: HiFiBerry DAC/DAC+ Zero)
20210429 212215 worker: Bluetooth (available)
20210429 212215 worker: Airplay renderer (available)
20210429 212215 worker: Spotify renderer (available: started)
20210429 212216 worker: Squeezelite (available: started)
20210429 212217 worker: RoonBridge renderer (not installed)
20210429 212217 worker: UPnP renderer (available)
20210429 212217 worker: DLNA server (available)
20210429 212217 worker: UPnP browser (available)
20210429 212217 worker: GPIO button handler (available)
20210429 212217 worker: Stream recorder (n/a)
20210429 212217 worker: -- Music sources
20210429 212217 worker: USB sources (none attached)
20210429 212219 worker: NAS and UPnP sources (mountall initiated)
20210429 212219 worker: -- Other
20210429 212219 worker: USB volume knob (Off)
20210429 212219 worker: USB auto-mounter (udisks-glue)
20210429 212220 worker: LED0 (On)
20210429 212220 worker: LED1 (sysclass does not exist)
20210429 212220 worker: Saved MPD vol level (0)
20210429 212220 worker: Preamp volume level (0)
20210429 212221 worker: MPD volume level (49) restored
20210429 212221 worker: ALSA volume level (None)
20210429 212221 worker: Auto-play (Off)
20210429 212221 worker: Maintenance interval (3 hours)
20210429 212221 worker: Screen saver activation (60)
20210429 212221 worker: Session permissions (OK)
20210429 212222 worker: Watchdog started
20210429 212222 worker: Ready

[Tim Curtis]

Prolly the Squeezelite renderer hogging the audio output. Try turning it off in Audio Config or power off in LMS.

Code:

20210429 212216 worker: Squeezelite (available: started)

[radu-]

Prolly the Squeezelite renderer hogging the audio output. Try turning it off in Audio Config or power off in LMS.

Code:

20210429 212216 worker: Squeezelite (available: started)

Whoooo! Thanks for the suggestion. I disabled a lot of renderers I don't use and now sound works - but this is the first time after an update I find them enabled. I never had bluetooth or squeezelite enabled.

[boafrich]

Hi Tim,

Looking forward to the new version, thanks.  Just trying the in-place update, I get the message 'Insufficient space.  Update cannot proceed without at least 500M space'.  Never had this before.  Running on a Pi-3B 1.2 1GB.
I have tried clearing cache, playback history etc. and rebooting but still the same.  Is there anything else I can try or do you think I will have to do a full install, i.e. burn image from scratch?

Thanks,
Boaf

Have you not expanded the filesystem? Configure > System > Filesystem > [EXPAND]

Hi,

Thanks for the reply: I have never needed to expand the filesystem before, so it didn't occur to me.  Are there any benefits of doing so if I'm not using the Pi to store music locally?  In any case, that has fixed the problem and it is now updated and working perfectly again, thank you.

Many thanks,
Boaf

[the_bertrum]

Hi Tim,

I just upgraded to 7.2.0, all went smoothly, no issues at all, many thanks!
But I need an explanation about UPNP and OpenHome implementation, because I exclusively use moode as UPNP renderer in conjunction with MinimServer+BubbleUpnp server running on a Synology-NAS.

As I correctly understand it, the upmpdcli is by now devided in two separate services, the "UPnP-A/V service only" configured by "UPnP service type=UPnP-A/V" and the "UPnP-A/V service and OpenHome service" configured by "UPnP service type=OpenHome".
So I can bypass the OpenHome implementation in upmpdcli and use the OpenHome renderer implemented by BubbleUPnP-server on the Synology-NAS if "UPnP service type=UPnP-A/V" is configured.

Is it correct so?

Thank a lot!

My understanding is that UPnP-AV and OpenHome services are mutually exclusive.

Thank you, but I don't know why the BubbleUPnP app see the Moode UPNP as renderer anyway after I have configured "UPnP service type=OpenHome"?

Short answer is yes.  Set moOde to the AV service, let your Bubble server create an OpenHome version of it and carry on as you were.

Slightly longer answer.  Does your Bubble server do anything else (like transcoding or making the service available over the internet)?  If not, you could swap to using the OpenHome service in moOde and just ditch the Bubble server.

Even longer answer.  If you only use moOde as a UPnP renderer, you have a set up a bit like those folks who have a Range Rover but only go to the shops in it.  You could mount your music from the NAS directly into moOde and take advantage of all the other goodies it provides (take your Range Rover off-road), or you could streamline things and just have a basic renderer (like upmpdcli ) on your Pi.

[the_bertrum]

Are there any benefits of doing so if I'm not using the Pi to store music locally?

The main benefit is the one you just found: enough space for the updates . Other than that, you can't use the space for anything else so it might as well be available to moOde even if it never gets used there either.

[maehld]

Hi. I've started with 7.1.0 and primarily used Airplay. This worked perfectly in 7.1 but is not working in 7.2.

My output is a USB DAC.

The difference I observed:

In 7.1.0 this is how shairport is started: /usr/local/bin/shairport-sync -a Moode Airplay -- -d plughw:2

In 7.2 it says -d _out

Any ideas?

Airplay on my test 710 -> 720 updated system works fine.

With Debug logging on here is what is printed in the Moode log after turning on Airplay.

Code:

20210429 110547 worker: Job airplaysvc
20210429 110547  startAirplay(): (/usr/local/bin/shairport-sync -vv -a "Moode Airplay" -- -d _audioout > /var/log/shairport-sync.log 2>&1 &)

Where do I activate debug logging? I've tried a clean install of 7.2 yesterday and had the same problem. Are you using an USB-DAC as well?

[boafrich]

Are there any benefits of doing so if I'm not using the Pi to store music locally?

The main benefit is the one you just found: enough space for the updates .  Other than that, you can't use the space for anything else so it might as well be available to moOde even if it never gets used there either.

Good to know.  Thanks for the reply!