It is obvious that people are wasting large amounts of time trying to get this player to work reliably. Fixes are scattered over hundreds of postings. Is there a central, comprehensive, troubleshooting guide anywhere? Or at least a detailed manual explaining the principles of operation -- is any knowledgeable person working on such a document? The cheat sheet offered is simply not adequate for an application this complex.
Doesn't DIY almost always infer an element of wasted time, and is that not part of the attraction?
It can be frustrating, educational and rewarding all at the same time, but if you prefer an almost guaranteed switch on and work solution, there are plenty of companies out there who would gladly take your money.
But where's the fun in that?
Using Kazoo to to browse your dnla server and select music to play is not giving up on Moode, Moode is still used to play the musicOops....I dont want to give up Moode...
The only part of Moode not being used is the web front end, and even then still works as a status.
Wanted to give a bump to my question for Tim or someone knowledgeable about the I2C dac settings. If those settings might need to be different between the ESS9008 and ESS9108 Buffaloes, it would be good to know. I wouldn't mind helping with the footwork in tracking it down, so we can have all 3 generations of Buffalo officially supported.
Hi would be grateful if you could please give me directions on how to proceed about this
Had to reflash Moode more than 4 or 5 times
Hello all!
First, thank you Tim for creating Moode for all to use!
I have been attempting to use it with my Synology NAS hosting my FLAC files and having the RPi 3 connected via USB to the Nuprime DAC 9. The Moode is set up to run Squeezelite that is controlled by the LMS 7.9 running on the NAS.
The problem that I have been having is that it seems to run stable for a few weeks and then it stops responding correctly. I have used a brand new 16 GB SD card and have extended the entire SD card space for Moode to use.
I would pause the LMS player in the morning when I leave for work, shut down my DAC and amp. The Pi is always on.
When I get back from work, I power up my DAC and amp, and access the LMS server to resume playing. That's when it starts to behave strangely and I cannot play music.
What I notice is that when it does decide to stop working, the green LED next to the red power LED is constantly on. The LMS is unable to find Moode as a player even after multiple restarts of the Squeezelite player in Moode. Sometimes, even the Moode interface player stops working and doesn't respond. Restarting MPD doesn't work and neither does restarting the LMS.
I can get it to respond again when I restart the entire Moode OS or power cycle the Pi. But it eventually stops responding again after a day or two.
At this stage I eventually give up and re-flash the SD card and start over. I follow the start up guide diligently during setup and it always works ok for some time.
But the stability doesn't last.
I have tried multiple SD cards but to no avail. How do I get it to remain stable and functional without having to re-flash every few weeks? Has anyone been able to run it continuously with Squeezelite and LMS for say 6 months with no issues?
Any help or pointers appreciated!
Hello all!
First, thank you Tim for creating Moode for all to use!
I have been attempting to use it with my Synology NAS hosting my FLAC files and having the RPi 3 connected via USB to the Nuprime DAC 9. The Moode is set up to run Squeezelite that is controlled by the LMS 7.9 running on the NAS.
The problem that I have been having is that it seems to run stable for a few weeks and then it stops responding correctly. I have used a brand new 16 GB SD card and have extended the entire SD card space for Moode to use.
I would pause the LMS player in the morning when I leave for work, shut down my DAC and amp. The Pi is always on.
When I get back from work, I power up my DAC and amp, and access the LMS server to resume playing. That's when it starts to behave strangely and I cannot play music.
What I notice is that when it does decide to stop working, the green LED next to the red power LED is constantly on. The LMS is unable to find Moode as a player even after multiple restarts of the Squeezelite player in Moode. Sometimes, even the Moode interface player stops working and doesn't respond. Restarting MPD doesn't work and neither does restarting the LMS.
I can get it to respond again when I restart the entire Moode OS or power cycle the Pi. But it eventually stops responding again after a day or two.
At this stage I eventually give up and re-flash the SD card and start over. I follow the start up guide diligently during setup and it always works ok for some time.
But the stability doesn't last.
I have tried multiple SD cards but to no avail. How do I get it to remain stable and functional without having to re-flash every few weeks? Has anyone been able to run it continuously with Squeezelite and LMS for say 6 months with no issues?
Any help or pointers appreciated!
Hi Jon,
Couple questions from me first:
1. Are u using Std or Adv kernel?
2. Buffalo I uses es9008 chip?
Wrt I2S audio, at a high level the audio device manufacturer is responsible for writing a kernel device tree overlay source file for their device and then getting it included in mainline Linux kernel. This file when loaded tells Linux audio subsystem which audio codec to use for I2S interface. The audio codecs I think are provided to Linux kernel by the chip manufacturer.
It works as follows:
I2S audio device (Moode friendly name) --> device tree overlay (/boot/config.txt) --> codec (.ko)
Moode configures Buffalo II/IIIse as below. The configs are based on user feedback as to what has worked since there is no Buffalo-specific device tree overlay from Twisted Pear.
Advanced kernel
Buffalo II/IIIse DAC --> simple-es9023-overlay --> es90323 codec
simple-bclk-64fs-overlay can also be loaded (optional)
Standard kernel
Buffalo II/IIIse DAC --> rpi-dac --> pcm1794a codec
pi@rp3:~ $ cat /boot/config.txt
disable_splash=1
hdmi_drive=2
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=off
dtoverlay=rpi-dac
dtoverlay=pi3-disable-bt
dtoverlay=pi3-disable-wifi
pi@rp3:~ $
There is a description of each overlay in the file README. I've only listed the audio overlays.
pi@rp3:~ $ ls -l /boot/overlays
-rwxr-xr-x 1 root root 583 Feb 17 07:24 adau1977-adc-overlay.dts
-rwxr-xr-x 1 root root 2606 Feb 17 07:24 ads1015-overlay.dts
-rwxr-xr-x 1 root root 1930 Feb 17 07:24 ads7846-overlay.dts
-rwxr-xr-x 1 root root 1253 Feb 17 07:24 akkordion-es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 889 Feb 17 07:24 akkordion-iqdacplus-overlay.dts
-rwxr-xr-x 1 root root 884 Feb 17 07:24 allo-boss-dac-pcm512x-audio-overlay.dts
-rwxr-xr-x 1 root root 1214 Feb 17 07:24 allo-piano-dac-pcm512x-audio-overlay.dts
-rwxr-xr-x 1 root root 602 Feb 17 07:24 audioinjector-wm8731-audio-overlay.dts
-rwxr-xr-x 1 root root 402 Feb 17 07:24 audremap-overlay.dts
-rwxr-xr-x 1 root root 586 Feb 17 07:24 dionaudio-loco-overlay.dts
-rwxr-xr-x 1 root root 1581 Feb 17 07:24 es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 575 Feb 17 07:24 hifiberry-amp-overlay.dts
-rwxr-xr-x 1 root root 573 Feb 17 07:24 hifiberry-dac-overlay.dts
-rwxr-xr-x 1 root root 1251 Feb 17 07:24 hifiberry-dacpluslight-es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 1038 Feb 17 07:24 hifiberry-dacplus-overlay.dts
-rwxr-xr-x 1 root root 631 Feb 17 07:24 hifiberry-digi-overlay.dts
-rwxr-xr-x 1 root root 697 Feb 17 07:24 hifiberry-digi-pro-overlay.dts
-rwxr-xr-x 1 root root 745 Feb 17 07:24 iqaudio-dac-overlay.dts
-rwxr-xr-x 1 root root 908 Feb 17 07:24 iqaudio-dacplus-overlay.dts
-rwxr-xr-x 1 root root 850 Feb 17 07:24 iqaudio-digi-wm8804-audio-overlay.dts
-rwxr-xr-x 1 root root 1235 Feb 17 07:24 i-sabre-dac-es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 749 Feb 17 07:24 justboom-dac-overlay.dts
-rwxr-xr-x 1 root root 628 Feb 17 07:24 justboom-digi-overlay.dts
-rwxr-xr-x 1 root root 1258 Feb 17 07:24 mamboberry-dacplus-es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 665 Feb 17 07:24 raspidac3-overlay.dts
-rwxr-xr-x 1 root root 63892 Feb 17 07:24 README
-rwxr-xr-x 1 root root 472 Feb 17 07:24 rpi-dac-overlay.dts
-rwxr-xr-x 1 root root 1359 Feb 17 07:24 rra-digidac1-wm8741-audio-overlay.dts
-rwxr-xr-x 1 root root 931 Feb 17 07:24 simple-bclk-64fs-overlay.dts
-rwxr-xr-x 1 root root 1897 Feb 17 07:24 simple-bclk-int-div-40-80-overlay.dts
-rwxr-xr-x 1 root root 1901 Feb 17 07:24 simple-bclk-int-div-50-100-overlay.dts
-rwxr-xr-x 1 root root 846 Feb 17 07:24 simple-es9023-audio-overlay.dts
-rwxr-xr-x 1 root root 827 Feb 17 07:24 simple-pcm5102a-audio-overlay.dts
pi@rp3:~ $
You will notice that there are only a handfull of I2S audio codecs.
pi@rp3:~ $ ls -l /lib/modules/4.4.39-rt59-moode2+/kernel/sound/soc/codecs
-rw-r--r-- 1 root root 17668 Feb 17 07:24 snd-soc-adau1701.ko
-rw-r--r-- 1 root root 5152 Feb 17 07:24 snd-soc-adau1977-i2c.ko
-rw-r--r-- 1 root root 17912 Feb 17 07:24 snd-soc-adau1977.ko
-rw-r--r-- 1 root root 6568 Feb 17 07:24 snd-soc-es9023.ko
-rw-r--r-- 1 root root 5268 Feb 17 07:24 snd-soc-pcm1794a.ko
-rw-r--r-- 1 root root 6972 Feb 17 07:24 snd-soc-pcm5102a.ko
-rw-r--r-- 1 root root 6584 Feb 17 07:24 snd-soc-pcm512x-i2c.ko
-rw-r--r-- 1 root root 31860 Feb 17 07:24 snd-soc-pcm512x.ko
-rw-r--r-- 1 root root 4500 Feb 17 07:24 snd-soc-sigmadsp-i2c.ko
-rw-r--r-- 1 root root 11288 Feb 17 07:24 snd-soc-sigmadsp.ko
-rw-r--r-- 1 root root 12180 Feb 17 07:24 snd-soc-tas5713.ko
-rw-r--r-- 1 root root 13376 Feb 17 07:24 snd-soc-tpa6130a2.ko
-rw-r--r-- 1 root root 22964 Feb 17 07:24 snd-soc-wm8731.ko
-rw-r--r-- 1 root root 16004 Feb 17 07:24 snd-soc-wm8741.ko
-rw-r--r-- 1 root root 5436 Feb 17 07:24 snd-soc-wm8804-i2c.ko
-rw-r--r-- 1 root root 17088 Feb 17 07:24 snd-soc-wm8804.ko
pi@rp3:~ $
-Tim
Hi,
Reboot then post output from /var/log/moode.log so i can see what your config looks like.
-Tim
Are you an Iphone or Android user, if you are an Android user then you can also use Bubble UPNP on your Phone.
Configure Moode by enabling the UPNP Renderer option in audio configuration
When you run Bubble you should see Moode appear as a Renderer and you DNLA Library appear as a library.
In Kazoo you should see Moode appear as a 'Room' and the Library as the source, you select you library in the kazoo setup and then your music appears under 'Your Music'.
I am not at home so cannot do screen shots.
Just done a bit of research I think your Seagate Connect works with a phone/Tablet application called the Segate Media App, you maybe able to use this to send your music to Moode.
As I am not sure what if you understand what the components of UPNP playback so see below, apologies if I have misunderstood.
There are basically three parts to a upnp solution, the components can mixed together but for ease of understanding think of them as three separate components.
UPNP Renderer - This plays the Music that it is asked to play in the form of a play list - In this case the Renderer is Moode with UPNP enabled.
UPNP Control Point - Eg Bubble, Kazoo, JRiver, Uplay - This allows you to Browse your music library and the then tell your UPNP Renderer (moode) to play the track or album you select by adding the song to the UPNP Renderer's (moode ) play list. Perhaps also your Seagate Media App can do this.
UPNP Server - This is your Seagate Connect Box and indexes your music that you have stored on it and then presents this information as a resource to browse and select music from. It presents this information in the form the Control point can understand, as a bonus 'should' display Album Art if it exists.
You UPNP control point basically allows you browse the UPNP/DNLA server and see the music there, you can tell Moode to play this music by usually selecting play. In the background the Control point (Bubble/Kazoo) tells Moode to play your track located on your server so then Moode will go to your DNLA server and say stream me this music track at this location you have given to the Control point. ( This is usually in the form of a HTTP address)
Last edited:
Standard, and yes, a Buffalo I is a es9008.
Hmmm, sounds like simple config, but enabling a kernel driver, that hopefully will meet all your needs. I'll see if I can read that file. Wondering how you get the console back from the HDMI port after it finishes booting and goes black. Or is SSH'ing in a better way to go?
Advanced kernel is only usable by later Pi's? I'm running a B+ v1.2 (which I guess is the single core, 700mhz chip)
Side questions: How much more in features do I get if I go to a 2 or 3 and the advanced kernel? CPU power would be different. Not sure if I need it so much, but played with the resampler, and saw CPU hitting the high 90%, maybe even some cutouts, on the B+.
I might just haul off and buy a 2 or 3, to see how the advanced 9023 chip driver performs.... Any need for larger than 8GB microSD with advanced?
After switching back to USB, then to I2C and the Buffalo a second time, I didn't have the problem of the audio info page being total garble. A one time glitch it seems. Will listen to it longer tonight to see if it still has volume glitches, so far, no problem there.
I do have significant clicks and pops when starting and stopping or switching between things, that's still there. Hoping for better muting, it's somewhat annoying on headphones, it would be problematic for the home system.
Hi Jon,
1) Unplug HDMI display (and USB keyboard) and use SSH. In fact turn off the HDMI port and enjoy much faster boot
2) Adv kernel support for armv6l (Pi-1B Pi-Zero) are in upcoming Moode 3.5 release
I have Pi-1B, 2B, 3B and Zero W in continuous use and all work fine with Moode but u just can't beat the 3B or Zero W for performance and ease of use
-Tim
Hi thank you so much for your detailed reply. I am using a Android device. I will do as you explained and will update you on the outcome.
Ah and dont worry , you have been bery clear in explaining the steps. Thanks a ton again.
Okay lets see if the SMB share is supported in SEAGATE CENTRAL
Hi Tim,
Here it is:
20170329 072024 worker: Startup
20170329 072026 worker: Host (moode)
20170329 072026 worker: Hdwr (Pi-3B 1GB)
20170329 072026 worker: Arch (armv7l)
20170329 072026 worker: Kver (4.4.30-v7+)
20170329 072026 worker: Ktyp (Standard)
20170329 072026 worker: Gov (ondemand)
20170329 072026 worker: OS (moodeOS 1.1)
20170329 072026 worker: Rel (Moode 3.1 2016-12-05)
20170329 072026 worker: Upd (None)
20170329 072026 worker: MPD (0.19.19)
20170329 072026 worker: Session loaded
20170329 072026 worker: Debug logging (off)
20170329 072026 worker: File check...
20170329 072027 worker: File check ok
20170329 072027 worker: Auto-shuffle deactivated
20170329 072027 worker: USB sources (none attached)
20170329 072027 worker: MPD scheduler policy (time-share)
20170329 072027 worker: MPD started
20170329 072027 worker: wlan0 does not exist (off)
20170329 072027 worker: DLNA server started
20170329 072027 worker: UPnP renderer started
20170329 072028 worker: Squeezelite renderer started
20170329 072028 worker: HDMI port off
20170329 072028 worker: Audio (USB audio device)
20170329 072028 worker: ALSA outputs unmuted
20170329 072028 worker: ALSA mixer name (NuPrime DAC-9 Output)
20170329 072028 worker: MPD volume control (disabled)
20170329 072028 worker: MPD output 1 ALSA default (enabled)
20170329 072028 worker: MPD output 2 ALSA crossfeed (disabled)
20170329 072028 worker: Hdwr volume controller exists
20170329 072028 worker: Volume level (0) restored
20170329 072028 worker: wlan0 address not assigned
20170329 072028 worker: eth0 exists
20170329 072028 worker: eth0 (192.168.13.200)
20170329 072029 worker: NAS sources (mountall initiated)
20170329 072029 worker: MPD consume reset to off
20170329 072029 worker: MPD crossfade (off)
20170329 072029 worker: Watchdog started
20170329 072029 worker: End startup
20170329 072029 worker: Ready
Problems with setting up wifi dongle
Pi 3 with HiFi Berry DAC+ board and metal case
Very frustrated - I cannot get the internal wifi of the Pi to work properly. In AP mode the SSID appears randomly but I have never been able to connect to it. I have resorted to using an external wifi dongle (Pi official model) but I can't get this to work either.
My questions are as follows -
1. Should be dongle be attached to a powered usb hub in view of the DAC+ board?
2. I have disabled the PI's internal wifi/BT function, so how do I configure the wifi dongle - will this be wlan(1)? I would prefer to use the auto-config file method to set up the Pi to connect to my router's wifi and bypass the need for AP mode if possible. Could you suggest suitable auto-config file settings to do this please?
Pi 3 with HiFi Berry DAC+ board and metal case
Very frustrated - I cannot get the internal wifi of the Pi to work properly. In AP mode the SSID appears randomly but I have never been able to connect to it. I have resorted to using an external wifi dongle (Pi official model) but I can't get this to work either.
My questions are as follows -
1. Should be dongle be attached to a powered usb hub in view of the DAC+ board?
2. I have disabled the PI's internal wifi/BT function, so how do I configure the wifi dongle - will this be wlan(1)? I would prefer to use the auto-config file method to set up the Pi to connect to my router's wifi and bypass the need for AP mode if possible. Could you suggest suitable auto-config file settings to do this please?
I have not used MoOde (still waiting for support for BOSS DAC), but I have experienced a similar problem with WiFi on my RPI 3.Pi 3 with HiFi Berry DAC+ board and metal case
Very frustrated - I cannot get the internal wifi of the Pi to work properly. In AP mode the SSID appears randomly but I have never been able to connect to it. I have resorted to using an external wifi dongle (Pi official model) but I can't get this to work either.
My questions are as follows -
1. Should be dongle be attached to a powered usb hub in view of the DAC+ board?
2. I have disabled the PI's internal wifi/BT function, so how do I configure the wifi dongle - will this be wlan(1)? I would prefer to use the auto-config file method to set up the Pi to connect to my router's wifi and bypass the need for AP mode if possible. Could you suggest suitable auto-config file settings to do this please?
I was using channel 12 on my router, which was something that RPI did not like. I changed the channel and then I could see my WiFi again.
See if it is a channel issue.
Hi,
Log looks ok. I've not had any stability issues. Some of my test systems are on continuously, sometimes for several weeks w/o reboot.
Could be a power supply issue.
If you can still get an ssh session going then check the following:
- dmesg
- cat /var/log/syslog
- pgrep mpd
- pgrep watchdog.sh
- pgrep worker.php
-Tim