Moode Audio Player for Raspberry Pi

Hi,

I have 2 bugs in the 2.6RT3 version :
- Time-line is not working correctly (the indicator is too late compare to the song total duration)
- True random function is not working (no random at all when the option is activated)

Hi,

Time ring graphic can lag if Moode window is not topmost. Don't know why this occurs but it has been an artifact of the Player since version 1.0. Browser refresh updates ring to current song pos.

The setting on System config for True random play functions as below and is described in the (i) help for the setting.

True random play replaces MPD random play as the default method for the 'Random' button on the Playback panel.

True random play waits until the last song in the Playlist has finished playing then it adds a random song from the music library to the end of the Playlist then removes it when it finishes playing. This creates a continuous stream of music without growing the Playlist.

After turning it on in System config, press the 'Random' button on Playback panel. The 'Consume' button will be automatically activated.

If above is not happening then could be a bug.

Regards,
Tim
 
Hi I have currently one bug in current TR3 i think it is the same one i had on stable.

I get massive lags and noticed that CPU is stuck at 99% with www-data taking all the cpu one example of processes taking up 100% cpu https://ibin.co/2gi0Bd6ZhYIy.png

My config.
raspeberry pi b with Hifiberry DAC
Static IP address
and NAS via samba share

Let me know if you need any log or anything and how to get them
 
Hi I have currently one bug in current TR3 i think it is the same one i had on stable.

I get massive lags and noticed that CPU is stuck at 99% with www-data taking all the cpu one example of processes taking up 100% cpu https://ibin.co/2gi0Bd6ZhYIy.png

My config.
raspeberry pi b with Hifiberry DAC
Static IP address
and NAS via samba share

Let me know if you need any log or anything and how to get them

Hi,

Try running ~/mrestart.sh to clear the condition.

Email tim at moodeaudio dot org and I'll help diagnose and troubleshoot :)

-Tim
 
Hi I have currently one bug in current TR3 i think it is the same one i had on stable.

I get massive lags and noticed that CPU is stuck at 99% with www-data taking all the cpu one example of processes taking up 100% cpu https://ibin.co/2gi0Bd6ZhYIy.png

My config.
raspeberry pi b with Hifiberry DAC
Static IP address
and NAS via samba share

Let me know if you need any log or anything and how to get them

This is interesting. I'm running tr3 on an RPi3 with HiFiBerry DAC+, WiF connection, DHCP-assigned IP address, NAS via SMB. Despite my music collection on the NAS, I've been using this lash-up almost exclusively as an Internet Radio for the past several days, trying out the pre-defined stations and adding some new ones of my own.

I just came back from dinner out to find it seemingly locked up ... not responsive to any of the several web browsers I had left open on various local hosts. For some reason, I was thinking it would turn out to be a WiFi problem and hence was surprised to find that an ssh session I had left open was still responsive. Like taiebot65, I found usage of one CPU was at 100 percent (in user space) running php5-fpm as user www-data.

Not having seen Tim's following suggestion yet, I simply rebooted from the command line.

Now, with 3 browsers on 3 hosts tracking the Playback screen and listening to a radio stream, "top" sees very small usage (< 5-7 percent at most) of any of the 4 CPUs and essentially no mention of user www-data or command php5-fpm. If I jump back and forth between several radio stations in my playlist, I'll see 5 such processes pop up momentarily but very little uptick in CPU usage before they quit.

I'll be interested to hear what might have driven my player into a catatonic state in my absence.

Regards,
Kent
 
Now I'm finally looking at log files on the same RPi3 system described in my last message.

1) Probably unrelated to the lock-up I described there, I see a recurring kernel message about pcm512x, reported to syslog and reflected in dmesg. Here are the lines as I grep'ped them from syslog, starting with the last boot at 20:51:31 (note it is currently 00:09:00 so none has occurred in the last hour):

Code:
May 10 20:54:49 moode-rpi3 kernel: [  189.957781] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:09 moode-rpi3 kernel: [ 2129.419122] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:30 moode-rpi3 kernel: [ 2150.851872] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:45 moode-rpi3 kernel: [ 2165.927500] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:28:10 moode-rpi3 kernel: [ 2191.278622] pcm512x 1-004d: No SCLK, using BCLK: -2 since I rebooted, 
May 10 21:40:17 moode-rpi3 kernel: [ 2917.931112] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:40:24 moode-rpi3 kernel: [ 2924.633289] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:40:30 moode-rpi3 kernel: [ 2931.021370] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:21 moode-rpi3 kernel: [ 2981.940962] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:34 moode-rpi3 kernel: [ 2995.112739] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:49 moode-rpi3 kernel: [ 3009.994165] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:53 moode-rpi3 kernel: [ 3014.040401] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:46:09 moode-rpi3 kernel: [ 3269.616065] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 22:06:10 moode-rpi3 kernel: [ 4470.455069] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 22:58:30 moode-rpi3 kernel: [ 7611.226584] pcm512x 1-004d: No SCLK, using BCLK: -2

2) Also, I finally noticed that /var/log/samba/log.smbd has a couplet of lines of the following form recurring roughly every 13 minutes:

Code:
[2016/05/10 23:28:12.388894,  0] ../source3/printing/print_cups.c:151(cups_connect)
  Unable to connect to CUPS server localhost:631 - Bad file descriptor
[2016/05/10 23:28:12.389326,  0] ../source3/printing/print_cups.c:528(cups_async_callback)
  failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL

Why is a cups server being sought?

3) There's errors in /var/log/nginx/error.log. Here's the last bunch recorded before I rebooted so perhaps suggestive of what was leading up to catatonia (none since, so far):

Code:
2016/05/10 19:12:49 [error] 849#0: *931 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462918373220 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 19:12:49 [error] 849#0: *931 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462918373220 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 19:12:49 [error] 849#0: *933 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462918369271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 19:12:49 [error] 849#0: *933 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462918369271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 20:12:55 [error] 849#0: *931 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462921979224 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 20:12:55 [error] 849#0: *931 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462921979224 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 20:12:55 [error] 849#0: *933 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462921975255 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 20:12:55 [error] 849#0: *933 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462921975255 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"

FYI, 192.168.1.172 is the IP of a Windows 10 host; 192.168.1.175 is the IP of a Linux host. 192.168.1.24 is the IP of moode-rpi3.

4) Finally, and perhaps most suggestive, I note the following in /var/log/php_errors.log. These are the only lines time-stamped today and they occurred during the 15 minute period just before I returned and found the web interface latched up.

Code:
[10-May-2016 20:36:07 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:36:08 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:36:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:36:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:37:08 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:37:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:38:13 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:38:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:39:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:39:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:40:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:41:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:41:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:42:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:42:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:43:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 93
[10-May-2016 20:44:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:44:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:45:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:46:00 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:46:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:47:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:47:47 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:48:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:48:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:49:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:50:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:50:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:50:52 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:51:22 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91

I wish I knew what I should be looking for. I can only hope this info will help narrow the search.

Regards,
Kent
 
Hi,

Which adapters does this enable to work in AP mode?

-Tim

This works with any Realtek 8188/8192 chipset. The downside is that you are potentially breaking something else that relies on hostapd

I thought I sent you that info ages ago? Sorry if I didn't - I meant to wen we were discussing various wifi chipsets.

And yes, it will work with your Edimax.
 
Last edited:
Hello all

For those of you with a Raspberry Pi 3. I've ordered this from Banggood. It is a small Bluetooth keypad with 5 buttons to control reproduction for Mobile Phones. Hopefully it will work with Raspberry Pi 3 Bluetooth connection and it will make a nice remote for Moode.

BT-005 12M Bluetooth Media Button Support ISO Bluetooth 3.0 Android OS 4.0 Sale - Banggood.com

I'll keep you informed on my progress to make it work.

BR / Fernando

I received it yesterday. I tried it with OSMC and it works by just pairing it. All the buttons and functions work as expected. Nice thing is that it disconnects to save battery and it connects once you press some of the buttons.

I'm on my way to make it work with Moode. So far I've connected via SSH to configure and pair it. Guess I need to install some app that takes the input from the bluetooth device and translates it into mpc orders or maybe I should try to create one with Python.

Let's see how it ends up :)

BR / Fernando
 
This works with any Realtek 8188/8192 chipset. The downside is that you are potentially breaking something else that relies on hostapd

I thought I sent you that info ages ago? Sorry if I didn't - I meant to wen we were discussing various wifi chipsets.

And yes, it will work with your Edimax.

You did send info, i was just being a bit lazy.

What I might be able to do, since the EDIMax adapters are very popular and perform so well, is make a setting in Moode Auto-config that would substitute the custom hostapd binary and conf setting. Something like that.

-Tim
 
Now I'm finally looking at log files on the same RPi3 system described in my last message.

1) Probably unrelated to the lock-up I described there, I see a recurring kernel message about pcm512x, reported to syslog and reflected in dmesg. Here are the lines as I grep'ped them from syslog, starting with the last boot at 20:51:31 (note it is currently 00:09:00 so none has occurred in the last hour):

Code:
May 10 20:54:49 moode-rpi3 kernel: [  189.957781] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:09 moode-rpi3 kernel: [ 2129.419122] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:30 moode-rpi3 kernel: [ 2150.851872] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:27:45 moode-rpi3 kernel: [ 2165.927500] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:28:10 moode-rpi3 kernel: [ 2191.278622] pcm512x 1-004d: No SCLK, using BCLK: -2 since I rebooted, 
May 10 21:40:17 moode-rpi3 kernel: [ 2917.931112] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:40:24 moode-rpi3 kernel: [ 2924.633289] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:40:30 moode-rpi3 kernel: [ 2931.021370] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:21 moode-rpi3 kernel: [ 2981.940962] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:34 moode-rpi3 kernel: [ 2995.112739] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:49 moode-rpi3 kernel: [ 3009.994165] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:41:53 moode-rpi3 kernel: [ 3014.040401] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 21:46:09 moode-rpi3 kernel: [ 3269.616065] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 22:06:10 moode-rpi3 kernel: [ 4470.455069] pcm512x 1-004d: No SCLK, using BCLK: -2
May 10 22:58:30 moode-rpi3 kernel: [ 7611.226584] pcm512x 1-004d: No SCLK, using BCLK: -2

2) Also, I finally noticed that /var/log/samba/log.smbd has a couplet of lines of the following form recurring roughly every 13 minutes:

Code:
[2016/05/10 23:28:12.388894,  0] ../source3/printing/print_cups.c:151(cups_connect)
  Unable to connect to CUPS server localhost:631 - Bad file descriptor
[2016/05/10 23:28:12.389326,  0] ../source3/printing/print_cups.c:528(cups_async_callback)
  failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL

Why is a cups server being sought?

3) There's errors in /var/log/nginx/error.log. Here's the last bunch recorded before I rebooted so perhaps suggestive of what was leading up to catatonia (none since, so far):

Code:
2016/05/10 19:12:49 [error] 849#0: *931 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462918373220 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 19:12:49 [error] 849#0: *931 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462918373220 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 19:12:49 [error] 849#0: *933 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462918369271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 19:12:49 [error] 849#0: *933 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462918369271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 20:12:55 [error] 849#0: *931 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462921979224 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 20:12:55 [error] 849#0: *931 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.172, server: , request: "GET /engine-mpd.php?state=stop&_=1462921979224 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "moode-rpi3", referrer: "http://moode-rpi3/"
2016/05/10 20:12:55 [error] 849#0: *933 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462921975255 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"
2016/05/10 20:12:55 [error] 849#0: *933 open() "/usr/share/nginx/html/50x.html" failed (2: No such file or directory), client: 192.168.1.175, server: , request: "GET /engine-mpd.php?state=stop&_=1462921975255 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.24", referrer: "http://192.168.1.24/"

FYI, 192.168.1.172 is the IP of a Windows 10 host; 192.168.1.175 is the IP of a Linux host. 192.168.1.24 is the IP of moode-rpi3.

4) Finally, and perhaps most suggestive, I note the following in /var/log/php_errors.log. These are the only lines time-stamped today and they occurred during the 15 minute period just before I returned and found the web interface latched up.

Code:
[10-May-2016 20:36:07 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:36:08 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:36:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:36:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:37:08 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:37:38 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:38:13 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:38:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:39:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:39:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:40:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:41:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:41:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:42:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:42:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:43:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 93
[10-May-2016 20:44:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:44:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:45:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:46:00 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:46:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:47:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:47:47 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:48:23 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:48:59 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 94
[10-May-2016 20:49:35 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 92
[10-May-2016 20:50:11 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:50:48 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91
[10-May-2016 20:50:52 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 97
[10-May-2016 20:51:22 America/New_York] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/inc/playerlib.php on line 91

I wish I knew what I should be looking for. I can only hope this info will help narrow the search.

Regards,
Kent

Hi Kent,

I need to add couple more lines to samba conf to get rid of cups messages. Thanks for pointing this out.

The "php hogs cpu" issue is rare in my experience and based on user reports rare in the field although it does happen. Root cause unknown at this time. The log messages "...execution time exceeded..." are usually present when the issue occurs and reflect php timing out on a socket read to MPD. It could be bug in MPD or maybe an MPD resource setting needs to be bumped.

-Tim
 
I received it yesterday. I tried it with OSMC and it works by just pairing it. All the buttons and functions work as expected. Nice thing is that it disconnects to save battery and it connects once you press some of the buttons.

I'm on my way to make it work with Moode. So far I've connected via SSH to configure and pair it. Guess I need to install some app that takes the input from the bluetooth device and translates it into mpc orders or maybe I should try to create one with Python.

Let's see how it ends up :)

BR / Fernando

This is very cool, Fernando. I've been toying with boxing up an RPi3 and an old tablet to make a self-contained tabletop player but I would get much of the functionality I need for casual use with just this button. I hope to see you report success with Moode!

Regards,
Kent
 
Hi Kent,

I need to add couple more lines to samba conf to get rid of cups messages. Thanks for pointing this out.

The "php hogs cpu" issue is rare in my experience and based on user reports rare in the field although it does happen. Root cause unknown at this time. The log messages "...execution time exceeded..." are usually present when the issue occurs and reflect php timing out on a socket read to MPD. It could be bug in MPD or maybe an MPD resource setting needs to be bumped.

-Tim

Hi, Tim.

It's the first time it's happened to me and taiebot65's message was just in time. Will be interesting to see what the root cause is. If you need testing, just shout.

Regards,
Kent
 
nginx 50x.html

Tim,

Regarding my item 3), error messages about a missing file 50x.html, I don't know yet what circumstances were triggering nginx to look for it, but I readily found a copy on github and downloaded it to /usr/share/nginx/html to avoid the problem. In MoodeOS 1.0 distro, only the file index.html is present in this directory (and I screwed up my search for 50x.html elsewhere; turns out a copy is in /etc/nginx/html/. I guess a config file just needs to be tweaked.

Comcast aka Xfinity has failed massively here today and I'm stuck using my cellphone as a Wireless Access Point. Can't get a lot done now that I'm so dependent on the internet. Sigh.

Regards,
Kent
 
Last edited:
What device did you select in the setup? Seems 'HifiBerry DAC' should be working for this device and then you should be able to set the volume in the mixer.

Found this:
https://www.hifiberry.com/guides/mixer-settings/

There must be some way... MoOde doesn't amplify the volume by itself, so if the DAC clips the signal, the problem should be somewhere in the DAC's hardware (=on-chip) volume control setting.

If really no solution to get to hw volume control, use the resample function to force 24 bit output, any damage done by the software volume control is very small when using 24 bits.

Would not worry about quality loss too much as most Pi DAC's are clock slave to the Rapsberry PI and this clock has some jitter which limits the maximum sound quality. For ultimate sound quality, use an USB DAC.
Good advice!
I've set resampling to 24/192, because the rpi isn't capable of resampling to 32 bit, aparently...

Poslano z mojega LG-D855 z uporabo Tapatalk
 
Tim,

Regarding my item 3), error messages about a missing file 50x.html, I don't know yet what circumstances were triggering nginx to look for it, but I readily found a copy on github and downloaded it to /usr/share/nginx/html to avoid the problem. In MoodeOS 1.0 distro, only the file index.html is present in this directory (and I screwed up my search for 50x.html elsewhere; turns out a copy is in /etc/nginx/html/. I guess a config file just needs to be tweaked.

Comcast aka Xfinity has failed massively here today and I'm stuck using my cellphone as a Wireless Access Point. Can't get a lot done now that I'm so dependent on the internet. Sigh.

Regards,
Kent

Hi Kent,

Thanks. The file should have been in /usr/share/nginx and not /etc/nginx so I'll make that change for TR4.

-Tim
 
Etcher - New SD Card Flashing Tool

For everyone that has done numerous .img sd card flashes you can understand how much of a pain it can be. (especially on a Mac) I came across this amazing new app recently and it works great for flashing those moOde TR images. Quick and easy. I've used both Mac and Windows versions numerous times already without a single issue.

Etcher by resin.io
Windows, Mac, Linux

Enjoy!