@TimCurtis, here are the data
moOde release = 8.2.5 2023-01-20
RaspiOS = 11.5
Linux kernel = 5.15.84-v8+ #1613
Platform = Pi-3B+ 1.3 1GB
Architecture = aarch64 (64-bit)
System uptime = up 10 minutes
Timezone = Europe/Athens
Current time = 2023-03-13 16:36:06
SoC identifier = bcm2837
Core count = 4
Kernel timer freq = 250 Hz
SDCard freq = 50 MHz
USB boot = enabled
Warranty = OK
Root size = 117G
Root used = 7%
Root available = 105G
Root expand = expanded
Memory total = 931 MB
Memory free = 362 MB
Memory used = 569 MB
SoC temperature = 35.4°C
Throttled bitmask = 0x0
Throttled text = No throttling has occurred
CPU governor = ondemand
USB auto-mounter = udisks-glue
Onboard WiFi = On
Onboard BT = On
HDMI output = On
LED state = 1,1
IP addr timeout = 90 (secs)
Ethernet check = No
SSH term server = Off
SMB file sharing = On
NFS file sharing = On
NFS access = 192.168.1.4/Volume_2
NFS options = rw,sync,no_subtree_check,no_root_squash
PHP-FPM version = 7.4.30
NGINX version = 1.18.0
SQLite3 version = 3.34.1
Hostapd version = 2.9
RPi.GPIO version = 0.7.
- moOde version 8.2.5 2023-01-20
- Pi model Raspberry Pi 3 Model B+
- Network config check below
- Number of tracks in collection 405000 tracks
moOde release = 8.2.5 2023-01-20
RaspiOS = 11.5
Linux kernel = 5.15.84-v8+ #1613
Platform = Pi-3B+ 1.3 1GB
Architecture = aarch64 (64-bit)
System uptime = up 10 minutes
Timezone = Europe/Athens
Current time = 2023-03-13 16:36:06
SoC identifier = bcm2837
Core count = 4
Kernel timer freq = 250 Hz
SDCard freq = 50 MHz
USB boot = enabled
Warranty = OK
Root size = 117G
Root used = 7%
Root available = 105G
Root expand = expanded
Memory total = 931 MB
Memory free = 362 MB
Memory used = 569 MB
SoC temperature = 35.4°C
Throttled bitmask = 0x0
Throttled text = No throttling has occurred
CPU governor = ondemand
USB auto-mounter = udisks-glue
Onboard WiFi = On
Onboard BT = On
HDMI output = On
LED state = 1,1
IP addr timeout = 90 (secs)
Ethernet check = No
SSH term server = Off
SMB file sharing = On
NFS file sharing = On
NFS access = 192.168.1.4/Volume_2
NFS options = rw,sync,no_subtree_check,no_root_squash
PHP-FPM version = 7.4.30
NGINX version = 1.18.0
SQLite3 version = 3.34.1
Hostapd version = 2.9
RPi.GPIO version = 0.7.
Attachments
Looks Ok although if you are not going to be connecting to SMB shares I'd prolly turn off SMB file sharing.
The way to troubleshoot "empty library" is to regenerate the Music database from scratch while monitoring the MPD log for errors.
1. Open an SSH terminal
2. Enter the following commands
3. Menu, Configure, Library
4. REGENERATE Music database
5. Watch the MPD log for errors
If errors appear in the MPD log, check the moOde log using the command below to see whether MPD has crashed and gets restarted by watchdog.
The most common causes for issues that result from MPD scanning collections are bad file permissions or corrupt files.
Good luck.
The way to troubleshoot "empty library" is to regenerate the Music database from scratch while monitoring the MPD log for errors.
1. Open an SSH terminal
2. Enter the following commands
Code:
sudo truncate /var/log/mpd/log --size 0
tail -f /var/log/mpd/log3. Menu, Configure, Library
4. REGENERATE Music database
5. Watch the MPD log for errors
If errors appear in the MPD log, check the moOde log using the command below to see whether MPD has crashed and gets restarted by watchdog.
Code:
moodeutl -lThe most common causes for issues that result from MPD scanning collections are bad file permissions or corrupt files.
Good luck.
I am sorry. I forgot to mention before that I am able to access the library throught the folder path. However album and tag windows are completely empty and the message nothing found appears.
Thank you
Thank you
@anounaki, For moOde releases prior to upcoming 8.3.0 the Setup Guide contains the default SSH userid and password. Starting with release 8.3.0 there will be no default userid or any passwords on the image but they can easily be setup using the official Raspberry Pi Imager.
Tag/Album views being empty might suggests some sort of resource issue in generating the Library tag cache or transferring it from server (Pi) to client (Browser). The Tag cache is derived from the MPD database and contains tags for the entire collection thus extreme sized collections could be problematic.
You could try increasing the MPD output buffer size in MPD Config. The setting is in the Resource allocation section.
Tag/Album views being empty might suggests some sort of resource issue in generating the Library tag cache or transferring it from server (Pi) to client (Browser). The Tag cache is derived from the MPD database and contains tags for the entire collection thus extreme sized collections could be problematic.
You could try increasing the MPD output buffer size in MPD Config. The setting is in the Resource allocation section.
Hi, moOde 8.3.0 is available for download. Visit the Forum for more information.
https://moodeaudio.org/forum/showthread.php?tid=5430&pid=45686#pid45686
https://moodeaudio.org/forum/showthread.php?tid=5430&pid=45686#pid45686
Hi. I use an rpi4 with a Moode audio player connected via a USB cable to a dac SMSL M500 mk3. I have such a problem that after some time of playback via USB it stops playing with the message "MPD error Failed to open audio output" and I have to select the USB input again with the remote control and it works for a while and so on. Do you know where the error could be?
The symptom "MPD error Failed to open audio output" suggests a possible hardware or power issue in the USB connection.
Your best bet is to post in our Support forum. If you don't already have an id then email tim at moodeaudio dot org with your preferred userid (at least 5 characters) and I'll create an account for you.
Your best bet is to post in our Support forum. If you don't already have an id then email tim at moodeaudio dot org with your preferred userid (at least 5 characters) and I'll create an account for you.
Hi @jaro911 , have the same issue, described in https://www.diyaudio.com/community/threads/moode-audio-player-for-raspberry-pi.271811/post-7277657.
But I have no issue if I disable ALSA loopback (for peppyalsa/peppymeter)! That means standard installation with USB output device and without any changes the moode player is working perfect.
In the log files I could nothing find any note of power/hardware issue.
But: @TimCurtis , thank you so much for your exellent support!
Best regards
I disconnected the usb cable from the rpi4 and connected it to the desktop computer and to the SMSL M500Mk3 dac, and there it stopped playing, so it must be a hardware fault of the SMSL M500Mk3. When I connect the M2tech Hiface adapter to the end of the usb cable and the rca coax cable to the spdif input of the dac, everything works without interruption.
It seems that increasing the MPD output buffer size helped me resolving the library indexing problem. 🙂 Great!
However a have another issue. After updating to the new firmware my local touch 7" screen stacks in Moode login. Though my pc I am able to enter normally.
The official Raspberry Pi 7 inch Touch screen tested with no issues. We can't test with other screens because there are just too many each with their own settings.
Hi, after years I am back to moodeaudio but I need a little support.
First:
I am running moode on a Pi zero and I am not able to login via SSH.
I turned webssh on in the menu but in the browser I can`t login with "pi" and "moodeaudio".
Also with the "ssh" file on the boot partition a login via ssh terminal is not possible.
What must I do to login remotely?
Second:
I want to have a shutdown button to shutdown properly before plug out.
The easiest way I thought is to add the /boot/config.txt with dtoverlay=gpio-shutdown.
A start with shortcut between "GPIO 3 and GND" works. A shutdown does not.
I found that the /etc/systemd/logind.conf could cause this behavior and I uncomment "HandlePowerKey = poweroff".
But this does not help to start the shutdown via button.
Would you please so kind to give me some hints 🙂
Thanky tobbes
First:
I am running moode on a Pi zero and I am not able to login via SSH.
I turned webssh on in the menu but in the browser I can`t login with "pi" and "moodeaudio".
Also with the "ssh" file on the boot partition a login via ssh terminal is not possible.
What must I do to login remotely?
Second:
I want to have a shutdown button to shutdown properly before plug out.
The easiest way I thought is to add the /boot/config.txt with dtoverlay=gpio-shutdown.
A start with shortcut between "GPIO 3 and GND" works. A shutdown does not.
I found that the /etc/systemd/logind.conf could cause this behavior and I uncomment "HandlePowerKey = poweroff".
But this does not help to start the shutdown via button.
Would you please so kind to give me some hints 🙂
Thanky tobbes
Starting with moOde 8.3.0 security has been improved by not including SSH or any default passwords on the image.
It's easy to set them up though. Visit the Download page at http://moodeaudio.org and read the Setup Guide regarding security and using the Raspberry Pi Imager.
It's easy to set them up though. Visit the Download page at http://moodeaudio.org and read the Setup Guide regarding security and using the Raspberry Pi Imager.
Thanks Tim for the quick reply. I was able to install moode with the Imager and ssh working.
Is it recommended to update the OS with "sudo apt update / dist-upgrade" or is this a bad idea?
I have tried moodeaudio now on an old Pi B+ with a hifiberry DAC (marked as: hifiberry R 2.2) on the old P5 header.
Which I2S DAC must I choose for this device?
I tried "hifiberry DAC" / "hifiberry DAC+" / "Generic-1 I2S (hifiberry-dac)" without luck.
There is no sound coming from the DAC. Headphone jack works if choosen.
Is it recommended to update the OS with "sudo apt update / dist-upgrade" or is this a bad idea?
I have tried moodeaudio now on an old Pi B+ with a hifiberry DAC (marked as: hifiberry R 2.2) on the old P5 header.
Which I2S DAC must I choose for this device?
I tried "hifiberry DAC" / "hifiberry DAC+" / "Generic-1 I2S (hifiberry-dac)" without luck.
There is no sound coming from the DAC. Headphone jack works if choosen.
The older DAC board is prolly not compatible with the B+ GPIO
https://support.hifiberry.com/hc/en-us/community/posts/360009586078-DAC-R2-2-compatibility
https://support.hifiberry.com/hc/en-us/community/posts/360009586078-DAC-R2-2-compatibility
Again many thanks for the quick answer.
The DAC was used in the past in the same setup with volumio. Now it is also quit with the old setup.
I think the DAC is dead. Sorry for take your time.
One more question:
Is it recommended to update the moodeaudio OS with "sudo apt update / dist-upgrade" or is this a bad idea?
The DAC was used in the past in the same setup with volumio. Now it is also quit with the old setup.
I think the DAC is dead. Sorry for take your time.
One more question:
Is it recommended to update the moodeaudio OS with "sudo apt update / dist-upgrade" or is this a bad idea?
Prolly a bad idea to upgrade or dist-upgrade and anyway this type of modification to the OS is not supported from a help and troubleshooting perspective in our Forum because we would have no idea what might have changed.
Although our images are built using standard Debian packaging and Pi-Gen they are generally not APT Upgrade Safe due to several dependencies that if updated would cause breakage. For example updating the Linux kernel would break our suite of four custom drivers since drivers are kernel version dependent. Updating PHP would break the config files associated with PHP since PHP embeds the path in is directory name. Etc, etc.
Given that we publish one or more releases each quarter and each release is generally built using the latest versions of the packages and kernel at that time our RaspiOS is almost as current as a rolling release.
Although our images are built using standard Debian packaging and Pi-Gen they are generally not APT Upgrade Safe due to several dependencies that if updated would cause breakage. For example updating the Linux kernel would break our suite of four custom drivers since drivers are kernel version dependent. Updating PHP would break the config files associated with PHP since PHP embeds the path in is directory name. Etc, etc.
Given that we publish one or more releases each quarter and each release is generally built using the latest versions of the packages and kernel at that time our RaspiOS is almost as current as a rolling release.
Still working on this, it's not infuriating, but it's still there intermittently.
I have a cheap USB DAC that I am using to get Toslink out to some QAcoustic BT3.
https://www.amazon.com/gp/product/B00FEDHHKE/
Could it simply be a clock issue, based on the quote below? Emphasis mine.