Hi Siegbert,
In earlier post you said that "normal Raspbian" image did not have any issues. Current release is dated 2016-05-27. Moode uses an earlier release, 2016-03-18.
https://www.raspberrypi.org/downloads/raspbian/
What is the release date of the version of Raspbian that you had success with?
I can troubleshoot Pi3/DAC+Pro issue and possibly determine root cause and make a fix if I have the following:
1) Success case that I can reproduce
2) Failure case that I can reproduce
3) A donated DAC+Pro
Without #3 I can't do anything. #1 is not required but without it troubleshooting becomes much more difficult.
-Tim
It depends on what you expect or what you need. If you feel comfortabel with a device, that just works - fine. For me, the sound is most important. And a well-designed psu definetely makes a difference. In electronics it`s always current - no matter if the signal is "digital" or "analogue". And you get out, what you get in: therefore it´s so important for a pure sound to have a pure current. It´s that simple.
Luki
I guess I am confused as to how a 'psu' can deliver cleaner power than a basic ac:dc transformer.
Not my area of expertise, but I've always preferred the simplest approach and you can't get much more basic than a transformer.
Off-topic, though. I will head off to the more electronically esoteric parts of the forum
just did the update. All running fine! 
I've finally (I wanted to do this so long) made a script that when mpd is stopped/paused, it turns off my amp after 2 minutes and it turn it back on when I resume playing.
(gpio, a transistor, pulling from 5v not from gpio, to amp's remote-in jack)
Found a nice light, handy, small remote from a car stereo I had, mapped the keys with lirc.
So good, top experience!
Nearly perfect. I just need a display of some kind, enclose it all in a good looking hi-fi case with proper power supply, and then it would be perfect
Congrats, Moode rocks
I've finally (I wanted to do this so long) made a script that when mpd is stopped/paused, it turns off my amp after 2 minutes and it turn it back on when I resume playing.
(gpio, a transistor, pulling from 5v not from gpio, to amp's remote-in jack)
Found a nice light, handy, small remote from a car stereo I had, mapped the keys with lirc.
So good, top experience!
Nearly perfect. I just need a display of some kind, enclose it all in a good looking hi-fi case with proper power supply, and then it would be perfect
Congrats, Moode rocks
Hello Tim,
I was running 2.6 with the r26 updates done a few weeks ago. Now I read this but I can't find how to apply this update. Any info I missed ?
TIA,
Charles
Hi Mike,
I think it can also be done using UPnP renderer but needs the Linn Songcast component.
https://www.lesbonscomptes.com/upmpdcli/sc2mpd.html
https://www.lesbonscomptes.com/upmpdcli
There is a another component named Snapcast that could also provide multiroom using MPD but it looks like it would take a substantial work effort.
-Tim
Thanks. I found this: https://volumio.org/forum/multiroom-audio-output-from-volumio-with-snapcast-t3217.html
I guess it's straightforward enough to set up with 'dumb' (non Moode) clients, leaving a central Moode server, with the others just acting as slaves alone.
If you are looking for more features to add to your worklist
it would be great to have a 'kiosk' mode, where you can lock down any config and just allow access to play, library and source.
Last edited:
Tim,
I'm having problems configuring using moodecfg.txt.
Created the file, booted up, but even 20 mins later, nothing.
I popped the SD and put it back in my Linux laptop and moodecfg.txt is still there.
Anywhere I can look on the SD to find a log to show where it stopped when it's out of the Pi?
Here's the moodecfg.txt - I have tried with the apd--- params commented out and filled in, it doesn't work either way. Using a Pi2 with an 8188 chip NIC, so no AP mode and I am trying to make it work headless, so no fiddling via ethernet while it's sitting there.
I'm trying to 'productionise' the build, so I don't need to connect each Pi to my laptop to configure.
Brand new burn of 2.6 on a good SD. I'm stumped.
I'm having problems configuring using moodecfg.txt.
Created the file, booted up, but even 20 mins later, nothing.
I popped the SD and put it back in my Linux laptop and moodecfg.txt is still there.
Anywhere I can look on the SD to find a log to show where it stopped when it's out of the Pi?
Here's the moodecfg.txt - I have tried with the apd--- params commented out and filled in, it doesn't work either way. Using a Pi2 with an 8188 chip NIC, so no AP mode and I am trying to make it work headless, so no fiddling via ethernet while it's sitting there.
I'm trying to 'productionise' the build, so I don't need to connect each Pi to my laptop to configure.
Brand new burn of 2.6 on a good SD. I'm stumped.
Code:
#########################################
# Copy this file to /boot/moodecfg.txt
# worker will process it at startup then
# delete it and automatically reboot.
#########################################
[names]
hostname=moode
browsertitle=MoOde Player
airplayname=Moode Airplay
upnpname=Moode UPNP
dlnaname=Moode DLNA
mpdzeroconf=moode
[services]
airplaysvc=0
upnpsvc=0
dlnasvc=0
[network]
wlanssid=XXXXXXX
wlansec=wpa
wlanpwd=XXXXXXX
#apdssid=
#apdchan=
#apdpwd=
[other]
timezone=America/Detroit
themecolor=EmeraldThanks. I found this: https://volumio.org/forum/multiroom-audio-output-from-volumio-with-snapcast-t3217.html
I guess it's straightforward enough to set up with 'dumb' (non Moode) clients, leaving a central Moode server, with the others just acting as slaves alone.
If you are looking for more features to add to your worklist
Hi Mike,
I think Snapcast needs a bit more time to mature before I want to try to integrate it. Kiosk mode is something I leave up to the user to implement since it is a very specific factoring of the Player.
-TIm
Hi Mike,
Remove # from the params and just leave them at the defaults. The autoconfig code ignores lines with # and is blowing up with your config file.
apdssid=Moode
apdchan=6
apdpwd=moodeaudio
-Tim
excellent, thanks.
For 'kiosk mode', I guess I just need to add some sort of pw for the config pages. I am crap at html, but persistent
Hi Mike,
Look in /var/www/header.php and comment out the "Configure" line from the menu.
under
<ul class="dropdown-menu"...
change
<li><a href="#configure-modal" data-toggle="modal"><i class="icon-cogs sx"></i> Configure</a></li>
to
<!--li><a href="#configure-modal" data-toggle="modal"><i class="icon-cogs sx"></i> Configure</a></li-->
Something like that
-Tim
Hi Tim, I'm on a fresh install of moode with all the updates installed. I'm getting the following error message beneath my Wifi WLAN option: "Unable to activate AP mode". I'm using an Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS], and the RPI is showing it as connected.
Any ideas?
Any ideas?
I was thinking about radios the other day.
- Tim, what about using a central radio url repository like Radio Browser
It's not mine BTW, just found it randomly. AGPL, all code on github
It has its own api Radio Browser API , so it would offload all the "fixing radio urls" work from you and allow others to simply add radios/fix urls?
It already filters by clicks, vote, country, language, tags(genre), codec, etc and you can expose via JSON/XML
You could also host it on your own server, since is freely licensed.
It's missing some european radios, but as soon as you add them on the website they will show immediately in your application. I'd add my fair share of radio urls
Easy enough to add them via website
It's already being used by some apps like Gradio for Ubuntu and a few other ones.
- Tim, what about using a central radio url repository like Radio Browser
It's not mine BTW, just found it randomly. AGPL, all code on github
It has its own api Radio Browser API , so it would offload all the "fixing radio urls" work from you and allow others to simply add radios/fix urls?
It already filters by clicks, vote, country, language, tags(genre), codec, etc and you can expose via JSON/XML
You could also host it on your own server, since is freely licensed.
It's missing some european radios, but as soon as you add them on the website they will show immediately in your application. I'd add my fair share of radio urls
Easy enough to add them via website
It's already being used by some apps like Gradio for Ubuntu and a few other ones.