Then use the Edit the path manually and use the ip-address and share name, so 192.168.xxx.xx/music and complete the username(ID) Password and give it a (any) unique name. save and see if it gives the green tick.
ah reread your post.. perhaps you need to register an account on the moOde forums where Tim or Kent will be able to troubleshoot.
Auto-registrations are closed so just email tim at moodeaudio dot org and he'll create an account for you.
ah reread your post.. perhaps you need to register an account on the moOde forums where Tim or Kent will be able to troubleshoot.
Auto-registrations are closed so just email tim at moodeaudio dot org and he'll create an account for you.
Hi, moOde 8.2.3 is available for download. Visit the Forum for more information. https://moodeaudio.org/forum/showthread.php?tid=5237&pid=44140#pid44140
Hi, moOde 8.2.4 bugfix release is available for download. Visit the Forum for more information https://moodeaudio.org/forum/showthread.php?tid=5266&pid=44342#pid44342
Is there a way to get Moode to play a https url which has an untrusted cert?
The error is Failed to decode https://stream.wortfm.org:8443/high.mp3; CURL failed: server certificate verification failed. CAfile: none CRLfile: none.
I think the curl option is --insecure to ignore bad certs.
The error is Failed to decode https://stream.wortfm.org:8443/high.mp3; CURL failed: server certificate verification failed. CAfile: none CRLfile: none.
I think the curl option is --insecure to ignore bad certs.
Thats a question for the MPD project since its MPD that is accessing the URL to play the stream.
https://github.com/MusicPlayerDaemon/MPD/issues
https://github.com/MusicPlayerDaemon/MPD/issues
Hi,
please try with the following url:
http://stream.wort-fm.org:8000/high.mp3
Best regards,
Francesco
hmm i wanna report a strange discovery i made with moode 8.2.2
increasing the nice level of the mpd systemd service with adding
"Nice=-1" to /lib/systemd/system/mpd.service
increased sound quality quite a lot, so much that i actually think something is wrong in the stock configuration of either Moode`s MPD fork or Moode itself
Could someone try this and report back?
increasing the nice level of the mpd systemd service with adding
"Nice=-1" to /lib/systemd/system/mpd.service
increased sound quality quite a lot, so much that i actually think something is wrong in the stock configuration of either Moode`s MPD fork or Moode itself
Could someone try this and report back?
Last edited:
I haven't tried it yet in 8.2.2, but I looked back at 6.6.0 and there is Nice=-10 under [Service]
# scheduling priority adjustment
# applies only to static scheduling policies
# 0 = default, -20 = highest, 19 = lowest
Nice=-10
# scheduling priority adjustment
# applies only to static scheduling policies
# 0 = default, -20 = highest, 19 = lowest
Nice=-10
Was/is this the default for 6.6.0 ?
im really not sure whats going on, specially because it sounds fluid without, but straight up better with increased priority (and the change is not small imo, for me its nothing you would argue about if it sounds better or not, it just does)
im wondering if this is actually the change in sound people hear when they compare moode to other OS`s
one thing that i also noticed is that this reduces the "pop-kind of noise" you get when you listen to a song and switch in the middle of the song to another song the "pop" sound is reduced by 3 times or so
im not entirely sure if this has something todo with camillaDSP, since i use it in the chain but i havent modified camilladsp`s priority, just the pipeline config
Yes, Nice=-10 was the default setting for 6.6.0 with MPD 0.22~git test.
I'll give it a try in 8.2.2. In my setup, 8.2.2 sounds better than 6.6.0 ( MPD 0.22~git test setting), which I thought was due to the updated MPD. Maybe Tim will comment.
I'll give it a try in 8.2.2. In my setup, 8.2.2 sounds better than 6.6.0 ( MPD 0.22~git test setting), which I thought was due to the updated MPD. Maybe Tim will comment.
Last edited:
Hi!
I have been running Moode on a R-pi 3+ with a (non-raspi) HDMI touch screen (https://www.amazon.com/gp/product/B07VNX4ZWY/).
After the last update, I had a couple new things and I can't figure out if it is something that I have mis-configured (or need to re-configure):
-- 1 -- Something changed on how the local display screen is handled. I had set the screen to never time out as the touch screen and it would go into a RGB cycling mode with no input. Now the started timing out and I can't seem to set it to never turn off. It did prompt me to change the screen hardware settings to time out in 10 min, so I don't get the color cycling, but still something isn't working right in my set-up.
-- 2 -- The annoying thing - The local radio station now skips periodically, where it never used to. Other than not seeing the skips in a web-browser, I don't know how to trouble shoot that. I tried to run TOP but I didn't see anything spiking, just the chromium running the top two entries, the first one is usually ~57%. I can't get to the stream url at work (on my lunch break), but this is where I pulled it from. https://mediaplayer.whro.org/station/wfos
-- 3 -- Now that I am messing with things, it seems this version is hugely slower than the previous ones.
-- 4 -- And I have a USB HHD attached, but I don't use it as much as I thought I would (probably because I have all the wrong music loaded on it), but the little lightning thing comes up a lot when I haven't played music off the HHD in at least four re-boots and a couple weeks (prior to when I updated it).
-- Looking at DMESG, I did notice several "undervoltage" warnings. I am using the same Canakit adapter and switch as before when there were no skips (https://www.amazon.com/gp/product/B00MARDJZ4/ plus a trimmed version of a switch (https://www.amazon.com/gp/product/B018BFWLRU/).
Is there any immediate action drill I should be performing (when I get home), or should I just re-download and re-flash?
I have been running Moode on a R-pi 3+ with a (non-raspi) HDMI touch screen (https://www.amazon.com/gp/product/B07VNX4ZWY/).
After the last update, I had a couple new things and I can't figure out if it is something that I have mis-configured (or need to re-configure):
-- 1 -- Something changed on how the local display screen is handled. I had set the screen to never time out as the touch screen and it would go into a RGB cycling mode with no input. Now the started timing out and I can't seem to set it to never turn off. It did prompt me to change the screen hardware settings to time out in 10 min, so I don't get the color cycling, but still something isn't working right in my set-up.
-- 2 -- The annoying thing - The local radio station now skips periodically, where it never used to. Other than not seeing the skips in a web-browser, I don't know how to trouble shoot that. I tried to run TOP but I didn't see anything spiking, just the chromium running the top two entries, the first one is usually ~57%. I can't get to the stream url at work (on my lunch break), but this is where I pulled it from. https://mediaplayer.whro.org/station/wfos
-- 3 -- Now that I am messing with things, it seems this version is hugely slower than the previous ones.
-- 4 -- And I have a USB HHD attached, but I don't use it as much as I thought I would (probably because I have all the wrong music loaded on it), but the little lightning thing comes up a lot when I haven't played music off the HHD in at least four re-boots and a couple weeks (prior to when I updated it).
-- Looking at DMESG, I did notice several "undervoltage" warnings. I am using the same Canakit adapter and switch as before when there were no skips (https://www.amazon.com/gp/product/B00MARDJZ4/ plus a trimmed version of a switch (https://www.amazon.com/gp/product/B018BFWLRU/).
Is there any immediate action drill I should be performing (when I get home), or should I just re-download and re-flash?
i would probably try without usb HDD, to try if the undervoltage messages dissapear (you probably have to use a powered usb hub for the HD now since the display draws too much current)
if this doesnt fix the issue with radio stations skipping (but i expect it to work) you could try my MPD priority tweak "just for fun"
I did try mpd.service Nice=-1 with 8.2.2, and did not hear any difference. Updated to 8.2.4, because of the updated MPD 0.23.11, default and Nice=-1, and did not hear a difference. My setup is RPi2 Allo Kali and DIY NOS I2S DAC HAT, and no digital processing. I now have Nice=-20. Shouldn't I want MPD to have high priority? I will go back to default (Nice=0), and see if there is a difference.
We use stock MPD, typically a recent release, plus our custom Selective Resampling patch. The MPD systemd control file is stock as well.
Visit our package build repo if you want to examine how we build MPD or other components for moOde.
https://github.com/moode-player/pkgbuild
Below is from our 8.2.4 release which uses MPD 0.23.11
Code:
# Playing a radio station
pi@moode:~ $ ps H -q `pidof -s mpd` -o 'pid,tid,cls,rtprio,nice,comm,pcpu'
PID TID CLS RTPRIO NI COMMAND %CPU
1029 1029 TS - 0 mpd 0.0
1029 1030 TS - 0 io 0.0
1029 1031 FF 40 - rtio 0.0
1029 63547 TS - 0 player 0.0
1029 63548 TS - 0 decoder:faad 0.3
1029 63550 FF 40 - output:ALSA Def 0.0
# MPD systemd unit
pi@moode:~ $ cat /lib/systemd/system/mpd.service
[Unit]
Description=Music Player Daemon
Documentation=man:mpd(1) man:mpd.conf(5)
Documentation=file:///usr/share/doc/mpd/html/user.html
After=network.target sound.target
[Service]
Type=notify
EnvironmentFile=/etc/default/mpd
ExecStart=/usr/bin/mpd --systemd $MPDCONF
# Enable this setting to ask systemd to watch over MPD, see
# systemd.service(5). This is disabled by default because it causes
# periodic wakeups which are unnecessary if MPD is not playing.
#WatchdogSec=120
# allow MPD to use real-time priority 40
LimitRTPRIO=40
LimitRTTIME=infinity
# for io_uring
LimitMEMLOCK=64M
# disallow writing to /usr, /bin, /sbin, ...
ProtectSystem=yes
# more paranoid security settings
NoNewPrivileges=yes
ProtectKernelTunables=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
# AF_NETLINK is required by libsmbclient, or it will exit() .. *sigh*
RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK
RestrictNamespaces=yes
[Install]
WantedBy=multi-user.target
Also=mpd.socket
pi@moode:~ $thanks for trying it out, i probably should try a stock moode setup myself
i let MPD run on just one core with camillaDSP together, there was problem i had where MPD would randomly use 100% CPU (and get basicly stuck) while streaming over DLNA (specially if the CPU is underclocked under 1000mhz for some reason, which i find very strange, underclocking shouldnt bring up such problems beside the system getting unstable itself)
the increased priority also fixed this
maybe i actually introduced a problem where i missed the sound quality decrease and increasing priority fixed this again
or maybe this just shows in conjunction with camillaDSP (maybe specially if both run on just one core)
i will try a stock moode setup the following days and report back
Thanks. I'll try that tonight, just seems like since it worked fine with both the HHD and LCD before, why would a software update change the power consumption enough to cause it to be a problem now?