+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: moOde 6.4.0 bug reports (/showthread.php?tid=1930)
RE: moOde 6.4.0 bug reports - Tim Curtis - 12-14-2019
Here is latest on bug fixes and updates.
Note the fix to the Squeezelite -S option. The option shows up in the config screen but is not actually in the .conf file until the config screen is saved.
Code:
########################################################
//
// 6.4.1 2019-MM-DD
//
########################################################
Updates
- UPD: Add features availability to moodeutl
- UPD: Improve volume knob step limiter
- UPD: Improve mixer name parsing for USB DAC's
- UPD: Improve message after changing Device type
- UPD: Use mixer name 'Channels' for HiFiBerry Amp(Amp+)
- UPD: Comment out Info logging from watchdog
- UPD: Edit Setup guide to reflect changes
Bug fixes
- FIX: 64-bit kernel not listed in dropdown if USBridge SIG
- FIX: Partial fix for Autofocus not working on modal popups
- FIX: Logic to parse /etc/resolv.conf for Moode log
- FIX: Minor bugs in various HTML template files
- FIX: Spurious HTML tags in header.php and footer.php
- FIX: Auto-config fails if moodecfg.txt contains CRLF
- FIX: Revision number parsing when 64-bit kernel
- FIX: Minor bugs in certain Audio info var names
- FIX: Missing -S option in stock squeezelite.confRE: moOde 6.4.0 bug reports - soundof-ferns - 12-14-2019
I've got an odd one. skimming the current bug reports, I don't see my issue, so I'll post. I have moode running on a raspberry pi 4b, using vanilla usb to connect to my benchmark DAC. I use chrome on android as a controller. My music repository is quite large, and is NFS mounted from another pi4 dedicated as a fileserver. The fileserver and moode are on a hardwired (cat 6) ethernet.
I did the upgrade using the moode interface rather than a fresh install. I monitored the upgrade as suggested using moodeutl and saw no errors. Rebooted from the ssh command line. On reboot, my web browser moode sources panel shows my playlists and the SDCard, but no NAS. Yet under configuration/library, both NFS NAS shares show as mounted properly, and I can ssh into the moode and browse the mounted NAS. From the sources panel with the missing NAS entry, I can even select a playlist and browse it from the moode user interface (but it doesn't show up if I try to play it). So the question is why the missing NAS entry on the sources panel. Also, if I try to play one of my NAS playlists, the play screen shows no music.
to emphasize, I have made no changes to my network or NFS, which have been working fine with moode for over a year. The files in question are properly mounted and can be browsed via ssh. Yet there is no NAS entry in my sources.
I suppose the obvious thing is to do a fresh install, though it takes a day to reindex the NAS shares. I'll do the reinstall, but wanted to report this and see if there is any insight first. possibly relevant sysinfo follows....
moOde release = 6.4.0 2019-11-24
Raspbian OS = 10.2
Linux kernel = 4.19.83-v7l+ #1277
Platform = Pi-4B 4GB
Architecture = armv7l (32-bit)
System uptime = up 45 minutes
Timezone = America/Los_Angeles
Current time = 2019-12-14 11:09:32
Host name = moode
Ethernet address = 172.18.1.254
Ethernet MAC = dc:a6:32:5e:28:14
WLAN address = unassigned
WLAN MAC = dc:a6:32:5e:28:16
WLAN country = US
SoC identifier = bcm2711
Core count = 4
Kernel timer freq = 100 Hz
SDCard freq = 50 MHz
USB boot = not available
Warranty = OK
Root size = 29G
Root used = 10%
Root available = 26G
Root expand = expanded
Memory free = 3480 MB
Memory used = 141 MB
SoC temperature = 42.4°C
CPU governor = ondemand
Onboard WiFi = Off
Onboard BT = Off
HDMI output = Off
Eth addr wait = On
Max USB current = Off
USB (UAC2) fix = On
Pi-3B+ eth fix = Off
SSH term server = On
PHP-FPM version = 7.3.11
NGINX version = 1.14.2
SQLite3 version = 3.27.2
Hostapd version = 2.8-devel
WiringPi version = 2.50
RPi.GPIO version = 0.7.0
A U D I O P A R A M E T E R S
Audio device = USB audio device
Interface = USB
Mixer name = Benchmark DAC2 Audio 2.0 Output Playback Sw
Hardware volume = Controller detected
Max ALSA volume = 100
Audio source = Local
Output device = Local
Resume MPD = No
Volume knob = 0
Volume mute = Unmuted
Saved MPD vol = 0
Preamp volume = 0
ALSA version = 1.1.8-1+rpt1
SoX version = 0.1.2-3
RE: moOde 6.4.0 bug reports - Tim Curtis - 12-14-2019
If u were running 0.20.23 MPD b4 the update, the update installs 0.21.16 MPD as the default and this should have triggered a database rebuild after rebooting due to changes in the 0.21.y database structure.
If not then I'd suggest deleting the two music source configs and then re-adding them which should automatically start a database rebuild.
RE: moOde 6.4.0 bug reports - soundof-ferns - 12-14-2019
thanks, should have tried reindexing before posting, but was hoping for a config fix without rebuilding the big indices....
but, following your advice I went ahead and deleted/re-added the shares. NAS now shows up on the sources panel, and things look like they will be normal once the indexing completes.
Maybe the upgrade instructions should clarify that a re-index is likely needed, since the upgrade will incur the mpd upgrade for most.
I don't post often but thanks for such a great product.
this problem is closed....
RE: moOde 6.4.0 bug reports - feh123 - 12-16-2019
Hi
I am running a RPI 3B on Buster with a Hifiberry digi pro HAT. This supplies a digital signal to my Naim amp that does the rest. My RPI is wired to my network, the Naim connects via wifi. I have a trial Premium Spotify account that was working fine with 6.3 and always connected to Moode Spotify at 320k.
On 6.4 I cannot get the Moode Spotify to run. My Moode browser says that Spotify is active but I get no sound. If I choose the Naim from my list of available devices on Spotify that plays okay - but I do prefer the Moode connection.
I cannot find a thread that mentions this for 6.4 so I have added this report.
I cannot say for sure it's something specific to 6.4 but I believe I have exactly the same installation settings as for 6.3. I could, of course be making some mistake in the set up!
As anyone else seen this behaviour?
Thanks.
RE: moOde 6.4.0 bug reports - Tim Curtis - 12-16-2019
Try the commands below while playing a Spotify track.
Code:
# Show whether librespot has crashed (it will print a number of its running)
pgrep librespot
# Show ALSA volume level (It should be 100%)
alsamixer
# Show what's being sent to the audio device
cat /proc/asound/card0/pcm0p/sub0/hw_paramsRE: moOde 6.4.0 bug reports - bobfa - 12-16-2019
(12-12-2019, 04:24 AM)bobfa Wrote:(12-10-2019, 01:16 AM)bobfa Wrote: I think I FOUND the problem. I have two devices running MoOde. I had “renamed” them. But the main rename does not change the other protocol names. So I had two devices with the same name on Squeezelite.
I am testing tonight and it seems to have fixed the problem.
It is not fixed I can reproduce it at will. We can move this to another thread if you want. Way too complex.
I will see If I can pull up a 6.3 on one of my devices to see if it happens there also.
Some more follow-up. I am have built a fresh 5.3.1 sd card from the Allo site. Running with Roon 1.7 server I have found that fast switching tracks from Tidal the system stops playing tracks (they sit at 0 in the Roon UI but the little playback bars next to the track move. A percentage of the time the track playing is garbled. Also, note that starting a new album seems to skip the first track regularly. This also happens on Qobuz but not as often. I do not see it as often the local library.
NOTE on 6.4 MoOde to my Hugo 2 DAC I am regularly getting little pops in the music. More prevalent on streaming. On 5.3.1 that is not as often but it is still there.
NOTE I checked the CPU governor and on this build, it was set to performance.
RE: moOde 6.4.0 bug reports - Tim Curtis - 12-17-2019
Audio glitches are not normal. I don't experience them on any of my 6 systems but I'm using only I2S DAC's, MPD, and the renderers: Bluetooth, Airplay, Spotify, Squeezelite/LMS.
The challenge in troubleshooting an issue like the one your are describing is that the moOde crew would need to be able to reproduce it. We don't have Roon, Hugo or other pieces in your system.
Generally though you would want to first isolate the issue. This is accomplished by first creating the simplest configuration that plays your files perfectly, then make changes to the configuration, one at a time and re-test until your reach a configuration where the issue occurs.
-Tim
RE: moOde 6.4.0 bug reports - alanthebat - 12-17-2019
(12-17-2019, 12:10 AM)Tim Curtis Wrote: The challenge in troubleshooting an issue like the one your are describing is that the moOde crew would need to be able to reproduce it. We don't have Roon, Hugo or other pieces in your system.
-Tim
I have a similar system to Bob's and I don't think this is a Moode issue.
It isn't anything to do with the Hugo either - I have similar skips through the DigiOne Sig SPDIF output on my USBridge Signature. I don't think it's anything to do with the version of Squeezelite in Moode as I get the same skips as well if I load a.n.other distro with only the very latest version of Squeezelite.
The implication then is that the problem is actually Roon's less than perfect implementation of the Squeeze server, and they've made it very clear that they aren't interested in investigating any issues between that and Squeezelite. That leaves four options:
- Run the RoonBridge software - either in a system that directly supports it or by loading it manually under Moode;
- Run Moode with MPD and live without Roon
- Run alternative server software, LMS into Squeezelite of something like Audirvana via DLNA into Moode; or
- Live with the glitches.
RE: moOde 6.4.0 bug reports - bobfa - 12-19-2019
(12-17-2019, 12:10 AM)Tim Curtis Wrote: Audio glitches are not normal. I don't experience them on any of my 6 systems but I'm using only I2S DAC's, MPD, and the renderers: Bluetooth, Airplay, Spotify, Squeezelite/LMS.
The challenge in troubleshooting an issue like the one your are describing is that the moOde crew would need to be able to reproduce it. We don't have Roon, Hugo or other pieces in your system.
Generally though you would want to first isolate the issue. This is accomplished by first creating the simplest configuration that plays your files perfectly, then make changes to the configuration, one at a time and re-test until your reach a configuration where the issue occurs.
-Tim
I "think" I have found it. Roon sends FLAC files with compression. In the advanced settings of the endpoint I turned that off and it seems to have fixed the problem.
Bob