Your DAC's built in volume control will not be able to change Moode UI knob. moOde only recognizes physical volume controls that are directly connected to the Pi via USB or GPIO.
Just try one of the many USB volume knobs that are available. Plug it into the Pi and then turn on "USB volume knob" in Audio config.
https://www.amazon.com/DROK-Lossless-Com...B01MV411BR
Looks like your DAC is displaying an odd volume scale. My Rev DAC displays volume in dB and if I turn on "Display dB volume" in Audio Config then the dB level displayed in the moOde knob matches the dB level shown in the DAC's OLED display.
[
attachment=2042]
(01-10-2021, 03:08 PM)Tim Curtis Wrote: [ -> ] (01-10-2021, 02:40 PM)TheOldPresbyope Wrote: [ -> ] (01-10-2021, 01:25 PM)Tim Curtis Wrote: [ -> ]@TheOldPresbyope identified a potential problem possibly in the version of chromium-browser that came with RaspiOS 10.6 that apparently causes it to eat memory after many hours idle. I wasn't able to repro the issue on my end but that does not necessarily rule anything out in this case.
Anyway if it is some sort of issue with chromium-browser there aren't many options going forward other than to wait for a new version that may or may not contain a fix or try testing with the particular version that was used in 671 to see if the problem goes away. I don't have the bandwidth ATM to do this testing but maybe someone will volunteer to give it a try.
-Tim
Late breaking news-
A preliminary experiment suggests substituting the current Vivaldi browser (d/l directly from its devs) for Chromium as the local client may keep the system alive. I'm composing a guide for those hard souls who want to follow in my footsteps. More testers make it more likely any flaws in my approach will be uncovered.
It's not a desirable approach because Vivaldi-ARM isn't considered stable yet so isn't in the Raspberry Pi OS repo.
ETA ... but it may help the few affected users and it also may help illuminate the problem.
Regards,
Kent
Maybe more evidence it's a memory leak in chromium-browser
https://bugs.launchpad.net/ubuntu/+sourc...ug/1751137
Hadn't seen that one. If you read to the end of the thread, it appears that an ad-blocker extension was responsible in that particular case. But it was two years ago...lots of opportunities to have introduced new failure modes since. (Not that we'd know anything about that
)
Chromium is an amazing mashup of code. The Vivaldi devs posted a nice
blog entry about why they chose to build on the existing Chromium engine---smart as they are,"[T]here is a reason why no-one has built a new engine from scratch in 20 years."
I've now posted my
guide.
Regards,
Kent
Hi guys!
Yesterday I recognized that all tracks in my queues shows "undefined image" at the thumbnails.
But why?
shouldn't show the embedded artwork of the file there?
Menu, Configure, Library
Thumbnail Generator.
View Status
Also in moode log there are records showing the result of MPD database update and thumbnail generator.
Hi,
Did a fresh install of 7.0.1 (previous was 6.4.2) (system: PI-3B, Allo Boss, NAS NFS, PI is wired, clients are wifi)
I like the new interface and improvements. Thanks!
Do have some issues though;
- at start-up I get 2 times the message "MPD error unexpected end of JSON input"
- if I click on the check (V) of consume, a default image is shown, instead of unchecking the option (which is minor)
- if I click the refresh function in the moode menu, the circles are decreased and out of center, a ctrl-F5 solves this (which is also minor)
- The album view on a PC is very laggy. (about 3000 albums and cover file image) The loading of images (400px) is not smooth but acceptable. The problem is that Chrome is slowing down, e.g. highlighting the menu items takes seconds. If album view is active and static, chrome processor usage is about 25%, while the other pages are about 3%.
Any suggestions?
Many thanks in advance,
Post the Moode startup log.
Hi, not sure if this is a lack of a feature or a bug. When mounting a Samba share, Moode issues the following command:
mount -t cifs "//<NAS_HOST>/volume2/Music" -o username="blah",password="blah",rsize=61440,wsize=65536,iocharset=utf8,vers=1.0,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/MY_NAS_SMBSHARE"
My Synology DS216+II is configured to support a MIN of v2 and max of v3. It took me awhile to figure out that I had to use SSH and commandline to mount the share if I did not want to downgrade to v1.
I found that the moode.log and other logs did not contain any errors... however it definitely does not work.
Assuming I'm correct about this, I would think a lot of users are getting stuck here and abandoning the effort. Ideally moode/linux would automatically figure out the right version OR the UI would ask the user which version to use.
Thanks!
mount -t cifs "//192.168.1.114/volume2/Music" -o username="admin",password="jmm0079",rsize=61440,wsize=65536,iocharset=utf8,vers=1.0,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/MCTBOXSMB"
mount -t cifs "//192.168.1.114/volume2/Music" -o username="admin",password="jmm0079",rsize=61440,wsize=65536,iocharset=utf8,vers=1.0,ro,dir_mode=0777,file_mode=0777 "/mnt/NAS/MCTBOXSMB"