Moode Audio Player for Raspberry Pi

Hi,
I have attached an USB pen drive with my FLAC files to the Pi Zero. After reboot the pen drive is not available and the library is empty.
I have to login via ssh to mount the drive manually "sudo mount /mnt/USB".
If I note the pen drive in /etc/fstab manually the drive is there at start but the samba share is not available anymore.

So mount the drive via ssh is my work around.
How can I fix this?
 
In the past I've installed minimserver on Moode without any issues but decided to run it on its own Pi. Now, due to Pi shortages, I need to use the minimserver Pi for something else and was wondering if a minimserver installation was mostly likely to survive a Moode self update...
 
Hi All,

After months of study in unfamiliar fields, manual work, frustration and elation, I have finally managed to complete my audio system which includes:

Raspberry pi 3b+, Moode player and an usb flash 3.1, 256 GB, to store the music
SMSL C200 DAC
hypex NC122mp amp
2 manzanita speakers you can see the details here.

I am getting familiar with Moode, which has taken a bit so far but it's a great piece of software kudos and thanks to the developer.

There's one thing I still haven't figured out: can you delete a track from the Moode browser page? Or do you have to unplug the usb flash connect to a pc and manually delete them, which would be extremely painful? Deleting from the SSH terminal should be possible but similarly annoying...

Thanks for your help.


David
 
This is probably a stupid question, but does anyone else route audio from an external source (USB or DAC) through their Pi running moOde to take advantage of the DSP functionality? I searched through this thread but couldn't find quite what I'm after.

My hope is that I could send my PC audio via moOde to use the crossover in my Piano 2.1 and CamillaDSP for all PC sound. I know I could use a multichannel sound card and CamillaDSP on Windows to achieve the same effect, but would like to use existing hardware if possible.

I came across this post on the wonderful bitlab.nl which describes one way to do it. However, it's fairly involved for the average user, and I was wondering whether there's an easier way.

Sending audio via Airplay works, but the delay is killer. BT doesn't work at all due to my PC's wireless card being bad at finding devices.

I'd really prefer to be able to select a direct wired input in moOde (digital if possible, like a USB mic input) - is there a relatively straightforward way?
 
Hi All,

After months of study in unfamiliar fields, manual work, frustration and elation, I have finally managed to complete my audio system which includes:

Raspberry pi 3b+, Moode player and an usb flash 3.1, 256 GB, to store the music
SMSL C200 DAC
hypex NC122mp amp
2 manzanita speakers you can see the details here.

I am getting familiar with Moode, which has taken a bit so far but it's a great piece of software kudos and thanks to the developer.

There's one thing I still haven't figured out: can you delete a track from the Moode browser page? Or do you have to unplug the usb flash connect to a pc and manually delete them, which would be extremely painful? Deleting from the SSH terminal should be possible but similarly annoying...

Thanks for your help.


David
Troubleshooting etc is provided in our Forum. Info on requesting a Forum account is in the Support section at moodeaudio.org.

In any case, there is no capability to delete or modify song files through the WebUI because it doesn't support authentication. Without authentication anyone could delete your files. You can try turning on the SMB (Samba) server in System Config and then access the share point from your PC file manager. IIRC you can add/modify/delete files through the share.

There is a section named FILE SHARING in the Setup Guide that has some additional info.
 
  • Like
Reactions: davirix
Have done a little more research on streaming PC audio through RPi.

I can see someone on here wanted to achieve pretty much the same thing in 2018 (though not necessarily with moOde), and the suggested solutions all were along the lines of "stream your music using DLNA," seemingly ignoring his desire for all PC audio to be routed to the Pi (not just media player output). I should probably just accept that it's not possible and run DSP on Windows instead I guess....
 
I'm new to Moode, and I tried to make a basic setup where I use Cammilla DSP to EQ the speakers response.
The idea is to use Camilla DSP as active XO in the future, but for now I'm only trying it out to see how it works etc It needs to be stable not to blow tweeters as active XO.. Is anybody using it like that?

For some reason, DSP only seems to be active when I stream internet radio, but not when using Spotify connect, or using Bluetooth.
I'm guessing it's a user error, since I only read some instructions online and tried to follow them, but I have no understanding of the actual inner workings of the software. Hoping somebody can give some pointers of what could be wrong?
I also find Spotify connect a bit unstable, seems it just stops playing after running some time (varies). Bluetooth seems more stable though, but I would prefer connect.
I have not tried stored music files, I'm on vacation and have nothing available at the moment.

I will post some screenshots below, if more info is needed I will try to supply it. The hardware is RPi3 I think.

Here is the example with internet radio:
1691047735497.png


1691047749294.png


Here is Bluetooth
1691047875398.png

1691047893898.png


And finally Spotify connect
1691047945880.png

1691047977562.png

Interestingly, Spotify connect seems to work now, but it did not before..

I guess now the question is, how can I get it to work with BT?
 
Hi all, I have used Moode for a long time on rpi zero w + phat dac, everything worked fine. I switched to rpi 2b + IQaudIO Pi-DAC+, and whatever I do I get "Failed to open "ALSA Default" (alsa); Failed to open ALSA device "_audioout": No such file or directory". Is there a solution to this? Thanks!
 
Have done a little more research on streaming PC audio through RPi.

I can see someone on here wanted to achieve pretty much the same thing in 2018 (though not necessarily with moOde), and the suggested solutions all were along the lines of "stream your music using DLNA," seemingly ignoring his desire for all PC audio to be routed to the Pi (not just media player output). I should probably just accept that it's not possible and run DSP on Windows instead I guess....
Seems doable to use the RPi as a DSP, no idea if the below is compatible with Moode.
"fairly involved" is relative.
I am not a wizard (as my questions in this thread attest) but I have been able to put things like this together before, the result is usually fragile though (specifically it will work for a while but are not necessarily robust to updates or configuration changes).

https://code.vt.edu/vibes-lab/dspi
https://github.com/dddomin3/DSPi
https://news.mkme.org/?p=28375
https://mod.audio/ (apparently uses RPi)
https://blokas.io/modep/docs/
https://blokas.io/
 
  • Like
Reactions: Arctophile
Hi,
I'm not new to Moode but I've lately succeed at making it work on my Tinkerboard's volumio primo within a system-d docker version of raspbian-bullseye (sharing cgroup and /dev/snd with my host to explain a little...)
It's quite pleasant and fun time 🙂 but since couple of day I 'm struggling at making my external USB audio DAC working with volume control, only I2S dac is correctly detected and operational or USB DAC through host MPD session
I didn't find any recipe to manualy modify any moode configuration file the proper way, I know this is not part of moode initial purpose bu maybe there's a trick to do so

Here are some relevant data (I hope)

Capture.JPG


USB Audio Onboard is Card 1 not Card 5, it doesn't work

20230803 183851 worker: --
20230803 183851 worker: -- Start moOde 8 series
20230803 183851 worker: --
20230803 183851 worker: Successfully daemonized
20230803 183852 worker: Waiting for Linux startup...
20230803 183858 worker: Linux startup complete
20230803 183858 worker: Boot config backed up
20230803 183903 worker: File check (OK)
20230803 183905 worker: Session vacuumed
20230803 183905 worker: Session loaded
20230803 183905 worker: Debug logging (OFF)
20230803 183905 worker: --
20230803 183905 worker: -- Audio debug
20230803 183905 worker: --
20230803 183905 worker: ALSA cards: (0😀AC | 1:OnBoard | 2:empty | 3:empty
20230803 183905 worker: MPD config: (0: | mixer🙁Digital) | card:0)
20230803 183905 worker: ALSA mixer actual (Digital)
20230803 183906 worker: ALSA Digital volume set to (0%)
20230803 183906 worker: --
20230803 183906 worker: -- System
20230803 183906 worker: --
20230803 183907 worker: Host (moode)
20230803 183907 worker: Hardware (Pi- )
20230803 183907 worker: moOde (8.3.3 2023-06-08)
20230803 183907 worker: RaspiOS (11.7)
20230803 183907 worker: Kernel (4.4.71+ #23)
20230803 183907 worker: Procarch (armv7l, 32-bit)
20230803 183907 worker: MPD ver (0.23.12)
20230803 183907 worker: CPU gov (ondemand)
20230803 183907 worker: Userid (pi)
20230803 183907 worker: Homedir (/home/pi)
20230803 183907 worker: Timezone (Europe/Paris)
20230803 183907 worker: Keyboard ()
20230803 183907 worker: USB boot (not available)
20230803 183907 worker: File sys (not expanded)
20230803 183907 worker: HDMI port (On)
20230803 183908 worker: Sys LED0 (On)
20230803 183908 worker: Sys LED1 (On)
20230803 183908 worker: --
20230803 183908 worker: -- Network
20230803 183908 worker: --
20230803 183908 worker: eth0 adapter exists
20230803 183908 worker: eth0 address check (Off)
20230803 183908 worker: IP addr ()
20230803 183908 worker: Netmask ()
20230803 183908 worker: Gateway ()
20230803 183908 worker: Pri DNS (208.67.222.222)
20230803 183908 worker: Domain ()
20230803 183908 worker: wlan0 adapter exists
20230803 183908 worker: wlan0 country (US)
20230803 183908 worker: wlan0 configured SSID ()
20230803 183908 worker: wlan0 SSID alternates (None)
20230803 183908 worker: wlan0 router mode (Off)
20230803 183908 worker: wlan0 address check (up to 90 secs)
20230803 183908 worker: wlan0 connected to SSID ()
20230803 183909 worker: IP addr ()
20230803 183909 worker: Netmask ()
20230803 183909 worker: Gateway ()
20230803 183909 worker: Pri DNS (208.67.222.222)
20230803 183909 worker: Domain ()
20230803 183909 worker: --
20230803 183909 worker: -- Software update
20230803 183909 worker: --
20230803 183909 worker: Automatic check (Off)
20230803 183909 worker: --
20230803 183909 worker: -- Audio config
20230803 183909 worker: --
20230803 183910 worker: MPD conf updated
20230803 183910 worker: ALSA card number (0)
20230803 183910 worker: MPD audio output ()
20230803 183910 worker: Audio formats (S16_LE, S32_LE)
20230803 183910 worker: ALSA mixer name (Digital)
20230803 183910 worker: MPD mixer type (hardware)
20230803 183910 worker: Hdwr volume controller exists
20230803 183910 worker: Max ALSA volume (100%)
20230803 183910 worker: ALSA output mode (Default: plughw)
20230803 183910 worker: ALSA loopback ()
20230803 183910 worker: Reset renderer active flags
20230803 183910 worker: CamillaDSP configuration (off)
20230803 183910 worker: CamillaDSP volume sync (Off)
20230803 183910 worker: CamillaDSP volume range (60 dB)
20230803 183910 worker: --
20230803 183910 worker: -- File sharing
20230803 183910 worker: --
20230803 183910 worker: SMB file sharing (Off)
20230803 183910 worker: NFS file sharing (Off)
20230803 183910 worker: --
20230803 183910 worker: -- MPD startup
20230803 183910 worker: --
20230803 183911 worker: MPD started
20230803 183911 worker: MPD accepting connections
20230803 183911 worker: MPD output 1 ALSA Default (On)
20230803 183911 worker: MPD output 2 ALSA Bluetooth (Off)
20230803 183911 worker: MPD output 3 HTTP Server (Off)
20230803 183911 worker: MPD crossfade (off)
20230803 183911 worker: MPD ignore CUE files (yes)
20230803 183911 worker: --
20230803 183911 worker: -- Music sources
20230803 183911 worker: --
20230803 183911 worker: USB sources
20230803 183911 worker: BOOT
20230803 183911 worker: volumio
20230803 183911 worker: volumio_data
20230803 183911 worker: NAS sources
20230803 183911 worker: None configured
20230803 183911 worker: --
20230803 183911 worker: -- Feature availability
20230803 183911 worker: --
20230803 183911 worker: Input select (available)
20230803 183911 worker: Input (MPD)
20230803 183911 worker: Output ()
20230803 183911 worker: Bluetooth (available)
20230803 183911 worker: AirPlay renderer (available)
20230803 183911 worker: Spotify renderer (available)
20230803 183911 worker: Squeezelite (available)
20230803 183911 worker: RoonBridge renderer (not installed)
20230803 183911 worker: Multiroom sender (available)
20230803 183911 worker: Multiroom receiver (available)
20230803 183911 worker: UPnP renderer (available)
20230803 183911 worker: DLNA server (available)
20230803 183911 worker: GPIO button handler (available)
20230803 183911 worker: Stream recorder (available: not installed)
20230803 183911 worker: HTTPS-Only mode (n/a)
20230803 183911 worker: --
20230803 183911 worker: -- Other
20230803 183911 worker: --
20230803 183911 worker: USB volume knob (Off)
20230803 183911 worker: USB auto-mounter (udisks-glue)
20230803 183911 worker: Saved MPD vol level (0)
20230803 183911 worker: Preamp volume level (0)
20230803 183911 worker: MPD volume level (100) restored
20230803 183912 worker: ALSA Digital volume (100%)
20230803 183912 worker: Auto-play (Off)
20230803 183912 worker: LocalUI (Off)
20230803 183912 worker: Automatic CoverView (Off)
20230803 183912 worker: On-screen keyboard (Off)
20230803 183912 worker: Library scope (all)
20230803 183912 worker: View reset to playback
20230803 183913 worker: Maintenance interval (360 minutes)
20230803 183913 worker: Screen saver activation (Never)
20230803 183913 worker: Session permissions (OK)
20230803 183913 worker: --
20230803 183913 worker: -- Startup complete
20230803 183913 worker: --
20230803 183913 worker: Mount monitor (off)
20230803 183914 worker: Watchdog monitor (started)
20230803 183914 worker: Ready



* Scanning for playback devices *
Card 0, ID `DAC', name `ES90x8Q2M DAC'
Device 0, ID ES90x8Q2M DAC es90x8q2m-dac-dai-0', name ', 1 subdevices (1 available)
2 channels, sampling rate 8000..192000 Hz
Sample formats: S16_LE, S32_LE
Buffer size range from 64 to 131072
Period size range from 32 to 65536

Subdevice 0, name `subdevice #0'
Card 1, ID `OnBoard', name `USB Audio OnBoard'
Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
2 channels, sampling rate 8000..8000 Hz
Sample formats: S16_LE
Buffer size range from 32 to 262144
Period size range from 16 to 131072

Subdevice 0, name `subdevice #0'
Device 1, ID `USB Audio', name `USB Audio #1', 1 subdevices (1 available)
2 channels, sampling rate 44100..192000 Hz
Sample formats: S16_LE, S24_3LE
Buffer size range from 90 to 262144
Period size range from 45 to 131072

Subdevice 0, name `subdevice #0'
Device 2, ID `USB Audio', name `USB Audio #2', 1 subdevices (1 available)
2 channels, sampling rate 44100..192000 Hz
Sample formats: S16_LE, S24_3LE
Buffer size range from 90 to 262144
Period size range from 45 to 131072

Subdevice 0, name `subdevice #0'
Card 5, ID `DAC10', name `NuPrime DAC-10'
Device 0, ID `USB Audio', name `USB Audio', 1 subdevices (1 available)
2 channels, sampling rate 44100..384000 Hz
Sample formats: S16_LE, S32_LE, SPECIAL
Buffer size range from 16 to 262144
Period size range from 8 to 131072

Subdevice 0, name `subdevice #0'



I would like to get my card 5 `NuPrime DAC-10' to appear in moode as an output option !

I've played a lot with google and chatgpt to find my way without any success, the only static configuration file I found is "moodecfg.ini" but I didn't find any recipe to modify the ALSA section to change card, /etc/mpd.conf is generated automatically so not really editable, and asound or modprobe command didn't help me 🙁
Is there any way ? Please help

Thank you by advance

Vincent
 
ok maybe hacking /inc/alsa.php
function getAlsacards() and getAlsaMixer() by setting $maxCards to 6 or 7 will do the trick for example

1691146910797.png


I Will test "php tricks" this evening and report here
++
 

Attachments

  • 1691146990054.png
    1691146990054.png
    4.7 KB · Views: 84
Last edited by a moderator:
Hi,

I am having some trouble with the Bluetooth functionality on moode. I recompiled the kernel as I wanted to use the CPU activity LED trigger (which is not enabled by default), however after the recompile bluetooth no longer works.

From the web interface everything appears to work but I cannot pair my phone, as moode does not show up. From SSHing in I can see the bluetooth service is running, and the hciuart service is not. I believe this to be the issue but I do not know if it is. I'm quite new to linux, so I imagine its quite an obvious issue that I am just overlooking.

Thanks in advance!
 
In the past I've installed minimserver on Moode without any issues but decided to run it on its own Pi. Now, due to Pi shortages, I need to use the minimserver Pi for something else and was wondering if a minimserver installation was mostly likely to survive a Moode self update...
Pi Hut has some RPI4B as well as other models in stock at reasonable prices - even though I am in the U.S. this is where I go to get them (usually with a bunch of other stuff to soften the blow of shipping costs.)
 
Hello,

I a moodeaudio running on a Rpi 3 rev B using Rpi 7" official touch Screen, local UI enabled and a USB Dac
Since the update to 8.1.0 (and 8.1.1), the Rpi was freezing each 2 or 3 hours (nothing is responding even ssh access is very very slow).

In the log I could see that there was the same behavior as described in that issue: https://github.com/raspberrypi/linux/issues/2810

After several try, i found a solution by enabling the swapfile:

# sudo dphys-swapfile swapoff

As root, edit the file /etc/dphys-swapfile and modify the variable CONF_SWAPSIZE to 1024:

CONF_SWAPSIZE=1024

# sudo dphys-swapfile setup
# sudo dphys-swapfile swapon
# systemctl enable dphys-swapfile.service
# systemctl start dphys-swapfile.service

It seems that the 1Gb of memory of the Rpi 3 is not enough when localUI is used since 8.1. I did not faced that issue before

I hop it will help people in the same case

Max
dude you are ******* legend.

current moode audio still has this issue til this date. no idea why the devs are not fixing it.

this solution still works.
with older pis, you are likely to see extremely laggy UI that almost looks like it works but doesn't. As soon as you change a setting and apply, it'll freeze up for hours. (bad implementers. )
 
Very odd.

Plenty of our users run locally attached displays including myself and there have been no reports in our Forum of the chromium-browser memory leak issue since our 8.1.1 release over a year ago. This release contained an updated version of chromium that fixed the leak. One of my own systems is a old 3B with a Pi 7" Touch running our latest 8.3.3 release and no performance or freeze issues whatsoever.

All our subsequent releases beginning with 8.1.2 are built using pi-gen, the same tooling used to make the official Raspberry Pi OS releases. The package and kernel versions included are the latest from the Raspberry Pi repos at the time the release is generated. In our current 8.3.3 release chromium-browser version is below

Code:
pi@moode:~ $ dpkg -l | grep chromium-browser
hi  chromium-browser                     113.0.5672.95-rpt1               arm64        Chromium web browser, open-source version of Chrome
hi  chromium-browser-l10n                113.0.5672.95-rpt1               all          chromium-browser language packages
 
I've recently shared preliminary rough analyses regarding the impact of shielding on noise levels in an RPI setup. This includes examining noise comparisons when shielding and earth grounding both the RPI and its processors, and how these factors influence the overall noise.

Furthermore, I've conducted comparisons of noise levels between the RPI 3b and 4b models, as well as when utilizing different power supplies. This information might capture your interest.

Please be aware that the presence of noise in any CPU based product is a typical phenomenon. In the video, the noise is significantly amplified, making it detectable. However, under normal circumstances, particularly with effective shielding and quality power supplies, this noise is often imperceptible to the human ear. With the right protective measures and power sources, the RPI proves to be an outstanding choice for audio applications.