Moode Audio Player for Raspberry Pi

Jump to Latest
#15,543
zlone said:
I am running the latest version of Moode on Pi with a display and having an issue with Cover View mode. Metadata does not update on the screen for radio stations that I have edited. For example, I changed the streaming URL for Sonic Universe to the higher resolution stream, and now the station graphic, song title, etc. does not update on the screen. It permanently shows the metadata from the last unedited station and song played, and a generic MoOde graphic. Thoughts?
Click to expand...
I realize the question about the Audio Info was regarding another post, but I tried looking at Audio Info when playing one of the problematic streams and nothing happens, I never see the Audio Info screen. Switching to a properly working stream, Audio Info displays correctly.
 
#15,544
zlone said:
I am running the latest version of Moode on Pi with a display and having an issue with Cover View mode. Metadata does not update on the screen for radio stations that I have edited. For example, I changed the streaming URL for Sonic Universe to the higher resolution stream, and now the station graphic, song title, etc. does not update on the screen. It permanently shows the metadata from the last unedited station and song played, and a generic MoOde graphic. Thoughts?
Click to expand...
When you change a station URL it doesn't update any occurrences of the station in the Queue. Just remove the old station from the Queue and re-add the updated one and you should be all set.
 
#15,549
audio stops after ca. 50 minutes
get an error: mpd error

pi@moode79:~ $ cat /var/log/mpd/log Feb 22 18:17 : output: Failed to play on "ALSA Default" (alsa): snd_pcm_writei() failed: Broken pipe Feb 22 18:17 : exception: Failed to open audio output
If i press again "play" then sound goes on again for 50 minutes

Raspi3 with hifiberry = no problems
Raspi4 with usb-audio (3,5 Apple-DAC) = sound stops after ca. 50 minutes
Raspi4 with usb-audio (3,5 no name) = sound stops after ca. 50 minutes

All players with peppyalsa and peppymeter. If I stop/disable peppyservice the issue is present. If I deactivate in settings "ALSA loopback" then are no errors.
At the moment I have no idea how I will find my problem.

removed all unused sounddevices:
pi@moode79:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: A [USB-C to 3.5mm Headphone Jack A], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 7/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7

config.txt
pi@moode79:~ $ cat /boot/config.txt [cm4] otg_mode=1 [pi4] hdmi_force_hotplug:0=1 hdmi_force_hotplug:1=1 [all] disable_splash=1 disable_overscan=1 hdmi_drive=2 hdmi_blanking=1 hdmi_force_edid_audio=1 hdmi_force_hotplug=1 #changed #hdmi_group=0 #add hdmi_group=2 hdmi_mode=87 hdmi_timings=400 0 100 10 140 1280 10 20 20 2 0 0 0 60 0 43000000 3 display_rotate=3 #end dtparam=i2c_arm=on dtparam=i2s=on #dtparam=audio=on dtoverlay=disable-wifi dtoverlay=disable-bt

_sndaloop.conf
i@moode79:~ $ cat /etc/alsa/conf.d/_sndaloop.conf pcm.!_audioout { type plug slave.pcm { type multi slaves { a { channels 2 pcm "plughw:0,0" } b { channels 2 pcm "pippopeppy" } } bindings { 0 { slave a channel 0 } 1 { slave a channel 1 } 2 { slave b channel 0 } 3 { slave b channel 1 } } } ttable [ [ 1 0 1 0 ] # left -> a.left, b.left [ 0 1 0 1 ] # right -> a.right, b.right ] } pcm.pippopeppy { type meter slave.pcm "hw:Loopback,1" scopes.0 peppyalsa } pcm_scope.peppyalsa { type peppyalsa decay_ms 400 meter "/var/tmp/peppyfifo" meter_max 100 meter_show 0 } pcm_scope_type.peppyalsa { lib /usr/local/lib/libpeppyalsa.so }

I found this threat, but it shows an other issue:

https://moodeaudio.org/forum/showthread.php?tid=157&page=2

Does anybody have an idea?
 
#15,552
fdealexa said:
Hi harryup,
It could help in the troubleshooting if you try the following command at the begin of the cycle (first minute) in the middle (25th minute) and at the end (before it stops = 48th minute).
The command is: top.
Best regards,
Francesco
Click to expand...
Hi Francesco,
thank you very much for yout help!
On the results, I can´t find the issue:
Begin:
Bildschirmfoto vom 2023-02-23 17-13-47.png


Middle:
Bildschirmfoto vom 2023-02-23 17-23-56.png


short time bevore break

Bildschirmfoto vom 2023-02-23 17-17-01.png
 
#15,554
fdealexa said:
Hi harryup,
It could help in the troubleshooting if you try the following command at the begin of the cycle (first minute) in the middle (25th minute) and at the end (before it stops = 48th minute).
The command is: top.
Best regards,
Francesco
Click to expand...
Hi Francesco,
found a crazy behavior.
While the music is playing:
pi@moode79:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: A [USB-C to 3.5mm Headphone Jack A], device 0: USB Audio [USB Audio] [B]Subdevices: 0/1[/B] Subdevice #0: subdevice #0 card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 7/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 pi@moode79:~ $ lsusb Bus 002 Device 002: ID 0781:5597 SanDisk Corp. Cruzer Glide 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:110a Apple, Inc. USB-C to 3.5mm Headphone Jack Adapter Bus 001 Device 003: ID 0712:000a WaveShare WaveShare Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

waiting till the issue occours
music stops:
pi@moode79:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: A [USB-C to 3.5mm Headphone Jack A], device 0: USB Audio [USB Audio] [B]Subdevices: 1/1[/B] Subdevice #0: subdevice #0 card 1: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 pi@moode79:~ $ lsusb Bus 002 Device 002: ID 0781:5597 SanDisk Corp. Cruzer Glide 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:110a Apple, Inc. USB-C to 3.5mm Headphone Jack Adapter Bus 001 Device 003: ID 0712:000a WaveShare WaveShare Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Crazy, if I press "play" again:
pi@moode79:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: A [USB-C to 3.5mm Headphone Jack A], device 0: USB Audio [USB Audio] [B]Subdevices: 0/1[/B] Subdevice #0: subdevice #0

Why does the subdevice change to 1 0 ....really crazy.
O.k. if I stop the music manually the audio Divece change from 0/1 to 1/1 again. I will try to verfy this on the Raspberry with Hifiberry
 
#15,555
Sorry for late answer,
I have tryed to replicate the problem and to understand if any problem in memory or CPU lack, but nothing raise.
I Think that if you try to open a thread in the moode Forum, a lot of people should try to help you.
I am very sorry but I have not any other advice.
Best regards,
Francesco
 
#15,556
I am running 8.2.5 on RPi 4B 4GB model and experiencing EXTREMELY long library update times for a USB connected SSD drive. Library is 140GB with 600ish folders and 7k files. It can take longer than an hour after power up to populate music in the library. This drive is lightning fast on other machines. Looking for any help on diagnosing what may be going on here.

Thanks
 
#15,559
Hi,

I have a huge library in NAS (almost 3TB both mp3 and flac) which cannot be seen in Moode. Its loading and loading but when it stops all the library is still empty.
If I upload a folder with less data, for instance an artist discograrphy everything seems ok.
Does Moode works flawless with huge libraries or it doesn't worth to try anymore?
Any help please?
 
You must log in or register to reply here.
Top Bottom