Hi Kent,
The messages are from an NGINX timeout governing how long to wait for a response from a PHP script being processed by PHP FastCGI Process Manager (PHP-FPM). In this case the script is engine-mpd.php which waits on MPD idle timeout. When one of MPD's subsystems changes, MPD comes out of idle providing metadata and state that is then enhanced by engine-mpd and returned to front-end UI via playerlib.js function engineMPD(). This function then immediately reconnects to engine-mpd.php and the cycle starts anew.
This particular timeout should probably be set to 600000 secs (forever) since there really is no reason to ever timeout engine-mpd script, plus when its timed out from external signal it will probably cause noticable UI refresh.
Look in /etc/nginx/nginx.conf for setting "fastcgi_read_timeout". The default is 60 secs and the current setting is 1 hour. Set to low value like 10 secs and watch what happens.
I'll investigate. Thanks again
-Tim
Yup, that's it. Changing the parameter changes the timing of the error messages. As well, closing browser windows rather than leaving them open and connected to the idle Moode Player causes the messages to cease. Don't know why I didn't notice that before.
All in all, pretty innocuous. I need to get control of my OCD reaction to "error" messages
Thanks.
Regards,
Kent
DAC 8 DSD Pi 3 probs
Hi All,
first of all thank you for the great thread and of course the great player.
I am still amazed by what Tim has put together here.
I switched recently from a Pi 2B to a Pi 3. The periphery around the Pi is the same, except for the WiFi. On the Pi 2 everything is fine, but on the Pi 3 I can't play back my flacs from the USB drive to the DAC 8 via USB. The DAC 8 seems to complain about the timing of the incoming data.
I tried a fresh install of version 2.6 as well as the USB (UAC2) fix option, but so far no success. Working on the shell with linux is fine for me, but I have no experience with the underlying mpd.
Any hint where to dig would be highly appreciated.
Thanx
Christian
Hi All,
first of all thank you for the great thread and of course the great player.
I am still amazed by what Tim has put together here.
I switched recently from a Pi 2B to a Pi 3. The periphery around the Pi is the same, except for the WiFi. On the Pi 2 everything is fine, but on the Pi 3 I can't play back my flacs from the USB drive to the DAC 8 via USB. The DAC 8 seems to complain about the timing of the incoming data.
I tried a fresh install of version 2.6 as well as the USB (UAC2) fix option, but so far no success. Working on the shell with linux is fine for me, but I have no experience with the underlying mpd.
Any hint where to dig would be highly appreciated.
Thanx
Christian
Hi Christian,
Very odd that Pi-3 and Pi-2 would produce different results with same USB DAC. To troubleshoot, copy one of the flac files to the pi-3 sd card and see what happens.
-Tim
Hi,
I'm running a pi3 with a hifiberry DAC+ pro since months without any issue. Now I decided to add another pi with a hifiberry AMP into the same network (for a second room). But I can't find the second AirPlay device. What I'm doing wrong ? I have given different names to both moody audio players.
Thanks
Kai
I'm running a pi3 with a hifiberry DAC+ pro since months without any issue. Now I decided to add another pi with a hifiberry AMP into the same network (for a second room). But I can't find the second AirPlay device. What I'm doing wrong ? I have given different names to both moody audio players.
Thanks
Kai
This is a shot in the dark, but insufficient power often leads to bizarre Raspberry Pi behavior so I recommend you first check your power supply (aka PSU).
I just checked the FAQs on www.raspberrypi.org. The recommended PSU current capacity for the RPi3B is 2.5A, considerably greater than the 1.8A recommended for the RPi2B.
Just my 2 cents worth.
Regards,
Kent
I too have trouble with my USB DAC and i wonder if this a general problem with my DAC or PI 3 specific. Sound clicks every few seconds with every file type and rate except DSD. Only way to avoid is to use the software upsampling which of course doesn't work with Spotify Connect (does not use MPD). Why does upsampling help?
DAC is LH Labs Geek Out v1 (XMOS, ES9018), Power supplies are rated 2.5A/3A (no LPS), external USB power via hub doesn't change anything.
Help appreciated.
____
It would be nice to be able to use upsampling only for PCM, not for DSD.
DAC is LH Labs Geek Out v1 (XMOS, ES9018), Power supplies are rated 2.5A/3A (no LPS), external USB power via hub doesn't change anything.
Help appreciated.
____
It would be nice to be able to use upsampling only for PCM, not for DSD.
Hi Tim,
Running on 2.6, enabled DLNA server from webUI.
when I Rebuild DLNA database, it creates duplicate (recursive?) entries.
Media Controller from WiFi sees several of same entries of a track.
Probably a problem with a script to rebuild DLNA db??
At the initial state, I think it was OK, but its causing a problem after I run Rebuild db.
Running on 2.6, enabled DLNA server from webUI.
when I Rebuild DLNA database, it creates duplicate (recursive?) entries.
Media Controller from WiFi sees several of same entries of a track.
Probably a problem with a script to rebuild DLNA db??
At the initial state, I think it was OK, but its causing a problem after I run Rebuild db.
DAC 8 DSD Pi-3 USB probs -> explained
Thanx for your support.
[power]
The power supply is rated 2.5A, and the DAC does have its own power supply. As far as I understand even the USB port of the DAC is powered from the DAC itself and not by the sender via USB. So that should be ok.
[Onboard WiFi]
I plugged in a Lan cable and switched off the build in wifi of the Pi-3 via ifconfig wlan0 down. Et voila, the problem disappeared! I have not checked if that is fully reproducable but will try to do tomorrow.
-Christian
Thanx for your support.
[power]
The power supply is rated 2.5A, and the DAC does have its own power supply. As far as I understand even the USB port of the DAC is powered from the DAC itself and not by the sender via USB. So that should be ok.
[Onboard WiFi]
I plugged in a Lan cable and switched off the build in wifi of the Pi-3 via ifconfig wlan0 down. Et voila, the problem disappeared! I have not checked if that is fully reproducable but will try to do tomorrow.
-Christian
You are absolutely right about power supplies. I purchased a ifi ipower 5vdc version for my RPi 3, worked good the first day then started flaking out causing all kinds of issues. Plugged the smps that came with the Pi 3 and now no issues at all - running great.
Probably going to send the ipower back and try another one to see if it was a bad one. I'm not ready quite yet to write the ipower off since so many have used the successfully.
eis
Hi Zoot
Thank you, blessed to be in quiet place ! I am soon gonna visit you in NZ, heard it is beautiful
The NAS is connected via ethernet to the router, and the router via ethernet to the RPI.
I did increase the buffer size to 16k and % buffer before playing to 30% but no result. The USB current x2 is set to on (the WaveIO board is USB powered), the USB UAC2 as well. I tried to insert a powered USB Hub... No success, I am lost
KR
Jean-Louis
Hi Jean-Louis,
Thats a strange symptom for an Ethernet-connected system. There certainly shouldn't be a lack of throughput, unless the router has a fault or is extremely underpowered (unlikely with anything better than 802.11g).
There shouldn't be any lack of power on the Pi - I tried 2.6 on an original Pi Model B 512 and while it took a decent amount of time to set up and boot, its operation was fine, as long as you let it finish maintenance tasks like cataloguing the library, etc.
Which points to your NAS as the culprit, or at least, the configuration of some NAS share with the corresponding setting in Moode.
I run a Freenas box running on a Pentium 4 and its flawless with all the share types I have configured, with no configuration tweaks in Moode, apart from the connection parameters.
The easiest file sharing I have found for use with Moode is SMB. I have a majority Apple environment, so prefer to use AFP, but with the new OSX, it seems to prefer SMB shares and the rest of my computers are Linux, so it was easy to standardise on SMB.
I have had problems with NAS dropout with some protocols such as NFS. If you can avoid NFS in favour of SMB, give that a try.
USB current wont make any difference to your DAC, but might be too much draw for your power supply. It really is only needed for connecting USB drives.
If you can detail how you are connecting to your NAS, your NAS share config and any other relevant infor (NAS version?) I will do more digging.
Hi,
Couple of dev things:
1) Radio station updates can now be delivered by Moode 2.6 Updater The first set of updates planned are:
- NEW: AddictedToRadio - Quiet Storm
- NEW: Positivly Baroque
- UPD: Zen FM stream link to mp3
2) Interprocess comms between NGINX and PHP FPM can be improved by converting from using the network stack (127.0.0.1:9000) to UNIX sockets.
3) PHP session storage can be more efficient by using memcached instead of /tmp and disk files.
-Tim
Couple of dev things:
1) Radio station updates can now be delivered by Moode 2.6 Updater
The first set of updates planned are:- NEW: AddictedToRadio - Quiet Storm
- NEW: Positivly Baroque
- UPD: Zen FM stream link to mp3
2) Interprocess comms between NGINX and PHP FPM can be improved by converting from using the network stack (127.0.0.1:9000) to UNIX sockets.
3) PHP session storage can be more efficient by using memcached instead of /tmp and disk files.
-Tim
Attachments
I'm one step further with investigation of the AirPlay problem. If I use WLAN connection of the Pi3 it is working. Can't I operate moode with Ethernet and AirPlay ? And how can I fully deactivate the WLAN of Pi3 if not needed.
Thanks very much for any help
Kai
USB sticks disappear
the problems described below are no problems with Rune or Volumio.
Fresh installation of moode 2.6
A USB hub with 4 ports. inserted 3x USB stick 128GB.
After update MDB all 3 USB sticks visible.
After some time, one USB stick is no longer visible.
Songs on this stick in the DB do not play.
installed auto update. Run auto update
After some time no longer visible an other *USB stick.
Update MDB does not work.
Only one USB stick visible.
All sticks have a label.
the problems described below are no problems with Rune or Volumio.
Fresh installation of moode 2.6
A USB hub with 4 ports. inserted 3x USB stick 128GB.
After update MDB all 3 USB sticks visible.
After some time, one USB stick is no longer visible.
Songs on this stick in the DB do not play.
installed auto update. Run auto update
After some time no longer visible an other *USB stick.
Update MDB does not work.
Only one USB stick visible.
All sticks have a label.
All great observations but don't overlook Jean-Louis's later message http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-354.html#post4750480
He got the same glitches playing music files from SD card and USB key which would seem to eliminate the NAS as a source of his difficulty.
Regards,
Kent
Hello,
please can anybody explain a beginner, where / how (in which file) i can change the font size for the mpd? Moode is running since mounth nearly perfect in my system, but i have to thick fingers to operate Moode on my new 7" touch display
Thank's and greetings from the black forrest
please can anybody explain a beginner, where / how (in which file) i can change the font size for the mpd? Moode is running since mounth nearly perfect in my system, but i have to thick fingers to operate Moode on my new 7" touch display
Thank's and greetings from the black forrest