Moode Audio Player for Raspberry Pi

99% certain this will be a problem with a weak Or noisy wifi signal.

Without knowing your setup ie what's wired/what's wireless, it could be your phone, router or pi or simply a noisy channel.

Most likely a weak signal from the pi.. A quality USB wifi dongle should sort it... Don't get a £4 nano style one if signal is an issue it likely will not improve it

LTF


Hi Everyone, I have set up my Raspberry pi 3 with an IQAudio Digi amp +. The sound quality is great, and moode makes it all work really well. I thought I might ask some questions about Airplay to see if anyone has had a similar experience to me.

Basically iPhones can Airplay to the Pi and play music, however after a minute or so the signal seems to cut out and the sound comes through sporadically. (distance is 2-3 meters from Pi)

There are a few things that might be worth considering: When the iPhone is right next to the Pi it seems to work OK. Also if the phone is a couple of meters away from the Pi it starts cutting out when the phone goes goes into screen save mode (is the phone saving power for Airplay signal as well perhaps?).
The RPi3 is close to the speaker, so the speaker magnet might be interfering with the Airplay signal?
Same problem with an Android phone that is using a Airplay compatible app.

I have tried to re-position the Pi away from the speaker. This didn't help at the time, but I might try it again.

If it is a Airplay reception issue, how hard is it to add an after market antenna in Moode OS? Alot of googling has said that the inbuilt Rpi3 Wifi setup is basic, and might be causing the problem.

In any case if anyone has any ideas i would like to give them a go. I am aware that its probably not Moode that is the problem, however this might be the best forum for the problem. Thanks for any help.
 
Hi learntofly. Thanks for the suggestion, sounds like the best idea. i will grab a new wifi dongle and see how it goes. My setup is totally wireless, but the signal percentage is pretty good (in the mid to high 60's for wifi). it plays music from the attached USB really well. The airplay is probably a weaker signal because it comes from a small phone.
 
Dear Tim,
what did you do to make the LH Labs Geek Out v1 play without clicks?
I tried the UAC fix without luck. A self powered Hub didn't make a difference.
(Pi 3, 2.5A supply, Aukey USB3 Hub, 5A)

Hi,

AFAIK audio glitches that occur with USB connected DAC's are generally due to bugs in Linux USB driver. The USB (UAC2) work around has worked for some DAC's but not others.

The glitches are typically white noise, constant clicks/pops or heavily distorted audio. The 13 sec interval glitch that u describe in a subsequent post does not fit this pattern so possibly there is some other cause.

Try running without a USB hub and instead turning on the "Max USB current 2X" setting in System config.

Are all audio formats affected or only 16 bit?

-Tim
 
Thank you for your answer.
I already tried it without hub first, but it was the same.

I just tried a song with 24/44.1, 24/96 and 24/192. My glitches are faint clicks and they seem to happen only with the 44.1KHz file. Again every 13 seconds.

With the radio station "Audiophile Baroque" (input shown as 24/44.1) clicks happen every 13 seconds.
With the radio station "Czech radio classical (FLAC) (imput shown as 16/48) there are smaller and bigger clicks and they seem more random.

No clicks with enabled upsampling (to 32/384) and with DSD files. I don't get it.
 
Hi Tim,
May I reiterate a request ? It concernes the way Shairport-sync handles the arbitration of the Airplay speakers. (-t option).

Could you please include an option in the GUI with two modes and an optional setting :

  1. the standard Airplay mode which doesn't allow others to "barge in" i.e. take over the speaker without the initial source stopping and then waiting for the timeout
  2. a "barge-in" mode where any source can take over the speaker ?and maybe
  3. an optional setting for the speaker time-out when no source is streaming to it.
References to the -t option are in the attachment and here... thank's 🙂

https://github.com/mikebrady/shairport-sync/issues/49#issuecomment-99058942
 

Attachments

Hi Tim,
May I reiterate a request ? It concernes the way Shairport-sync handles the arbitration of the Airplay speakers. (-t option).

Could you please include an option in the GUI with two modes and an optional setting :

  1. the standard Airplay mode which doesn't allow others to "barge in" i.e. take over the speaker without the initial source stopping and then waiting for the timeout
  2. a "barge-in" mode where any source can take over the speaker ?and maybe
  3. an optional setting for the speaker time-out when no source is streaming to it.
References to the -t option are in the attachment and here... thank's 🙂

https://github.com/mikebrady/shairport-sync/issues/49#issuecomment-99058942

Hi,

Already on TODO list but have not gotten to it yet. The -t option on shairport-sync cmd line controls whether the session can be interrupted.

- t N

N = 0 allow session to be interrupted
N = 1 - 120 secs, session timeout (120 is default)

I have not tested it yet but if u want to try this option edit the function startSps() in file /var/www/inc/playerlib.php 🙂

-Tim
 
Hi,

Already on TODO list but have not gotten to it yet. The -t option on shairport-sync cmd line controls whether the session can be interrupted.

- t N

N = 0 allow session to be interrupted
N = 1 - 120 secs, session timeout (120 is default)

I have not tested it yet but if u want to try this option edit the function startSps() in file /var/www/inc/playerlib.php 🙂

-Tim




No worries ;-) ! thank's anyways... I looked at the file but don't know enough php to touch it... will happily wait for the option to implemented sometime in the future...
 
Hi all

This is my first go at anything DIY audio and so far I'm impressed!

After a bit of research I've ended up with Moode on a PI 3 and after a couple of false starts (all of my own making) it's up and running and sounding good.

But I have a few issues and after quite a bit of googling I'm struggling to find answers. If anyone can shed any light it would be much appreciated.

I have Airplay turned on but it's not showing as available on any devices iphone/ipad or mackbook pro. Airport express on same network both wired and wireless are showing as available.

I have Release: 2.6, 2016-06-07 (downloaded a couple of days ago) and it looks like there are updates but how do I get them? I can't seem to find any update options in the web interface or info on other methods.

I can't connect via ssh. I have done this before on other devices but have very limited knowledge. Sudo ssh [ip address] gets me to a password but 'raspberry' doesn't work. sudo ssh -l pi does the same.

I'm sure I'm doing something wrong with these issues but any helpful advice for a major novice would be appreciated.

Thanks! Adrian
 
Hi all

This is my first go at anything DIY audio and so far I'm impressed!

After a bit of research I've ended up with Moode on a PI 3 and after a couple of false starts (all of my own making) it's up and running and sounding good.

But I have a few issues and after quite a bit of googling I'm struggling to find answers. If anyone can shed any light it would be much appreciated.

I have Airplay turned on but it's not showing as available on any devices iphone/ipad or mackbook pro. Airport express on same network both wired and wireless are showing as available.

I have Release: 2.6, 2016-06-07 (downloaded a couple of days ago) and it looks like there are updates but how do I get them? I can't seem to find any update options in the web interface or info on other methods.

I can't connect via ssh. I have done this before on other devices but have very limited knowledge. Sudo ssh [ip address] gets me to a password but 'raspberry' doesn't work. sudo ssh -l pi does the same.

I'm sure I'm doing something wrong with these issues but any helpful advice for a major novice would be appreciated.

Thanks! Adrian

Hi Adrian,

1) Follow Moode Twitter feed and scroll down a bit to the post that links to instructions on how to bootstrap the Updater into Moode 2.6

2) ssh pi@moode (pwd=raspberry), prefix all commands with sudo

3) If Pi-3 connected via ethernet then Airplay service advertisements will not be routed out eth0 (cause unknown). Fix is to disable the integrated BT/WiFi adapter. Procedure below. I may include a setting for this in an upcomming update.

a) ssh...
b) sudo nano /etc/modprobe.d/disable_rpi3_wifi_bt.conf

paste the lines below into the empty file

# wifi
blacklist brcmfmac
blacklist brcmutil
# bt
blacklist btbcm
blacklist hci_uart

c) Ctri-x y <return> to save the file
d) reboot


Regards,
Tim
 
Hi Tim

Thanks for the info, much appreciated. Thanks also for making Moode, the support and continued development, great work!

I still can't get anywhere with the ssh as the password 'raspberry' is rejected. tried ssh with ip address and moode and pi, -l, but when I get to a password raspberry doesn't work. Any ideas what i may be doing wrong (I've sucessfuly managed ssh with my tv recoder and NAS previously)?

Adrians-MBP:~ Adrian$ sudo ssh pi@moode
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
Sorry, try again.
sudo: 3 incorrect password attempts

Thanks again, Adrian
 
Hi Tim

Thanks for the info, much appreciated. Thanks also for making Moode, the support and continued development, great work!

I still can't get anywhere with the ssh as the password 'raspberry' is rejected. tried ssh with ip address and moode and pi, -l, but when I get to a password raspberry doesn't work. Any ideas what i may be doing wrong (I've sucessfuly managed ssh with my tv recoder and NAS previously)?

Adrians-MBP:~ Adrian$ sudo ssh pi@moode
Password:
Sorry, try again.
Password:
Sorry, try again.
Password:
Sorry, try again.
sudo: 3 incorrect password attempts

Thanks again, Adrian

Hi, Adrian. You don't need to run "ssh" in "sudo" mode. What you are seeing is "sudo" asking for your password on whatever machine you're executing it on. "raspberry" is unlikely to be it.

Here's an example of what I get logging into one of my Moode Players from one of my Linux boxes (*** instead of my user name):

Code:
****@krypton ~ $ ssh -l pi moode-rpi2b
pi@moode-rpi2b's password: 
Linux 4.4.8-v7+ J-Lite Core, armv7l Architecture
                           __    ____  ____
       __ _  ___  ___  ___/ /__ / __ \/ __/
      /  ' \/ _ \/ _ \/ _  / -_) /_/ /\ \  
     /_/_/_/\___/\___/\_,_/\__/\____/___/  
                                          
              moodeOS Version 1.0
              (C) 2016 Tim Curtis
 
moodeOS is based on Debian GNU/Linux and is custom
factored for Moode Audio Player. moodeOS and Moode
Audio Player are provided for free by the copyright
holders and contributors and come with no expressed
or implied warranties or any other guarantees.

Last login: Fri Jul 15 13:05:34 2016 from krypton
 
Hi Tim.
To begin, thanks a lot for Moode Audio. This is powerful, useful and provides excellent sound quality. Congratulations for your work!

I have two problems to expose :

1 : I can't find WEP in the list of WiFi connection security, only WPA. Is it normal ? My wifi is configured in WEP security for reasons of compatibility with other devices.

2: I have a rapsberry pi2 and a 3. On the pi2, i can mount SAMBA with any problem. On the pi3, i can't. I obtain the following message :
"Last mount error
Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)".

I specify that I tried with the same micro SD and also with a new installation. The problem is the same with the same issues
I find strange that Samba works with pi2 and not with pi3.I'm dissapointed.
Have you an idea of the problem? thank you very much

Guillaume
 
Hi Tim.
To begin, thanks a lot for Moode Audio. This is powerful, useful and provides excellent sound quality. Congratulations for your work!

I have two problems to expose :

1 : I can't find WEP in the list of WiFi connection security, only WPA. Is it normal ? My wifi is configured in WEP security for reasons of compatibility with other devices.

2: I have a rapsberry pi2 and a 3. On the pi2, i can mount SAMBA with any problem. On the pi3, i can't. I obtain the following message :
"Last mount error
Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)".

I specify that I tried with the same micro SD and also with a new installation. The problem is the same with the same issues
I find strange that Samba works with pi2 and not with pi3.I'm dissapointed.
Have you an idea of the problem? thank you very much

Guillaume

Hi Guillaume,

WEP is not supported in Moode because 1) its rarely used, 2) its insecure and 3) it required too much time to troubleshoot when issues came up since I don't run WEP in my network.

You could probably configure WEP manually by editing /etc/net/interfaces file but the file would be overridden anytime Network config screen APPLY were clicked.

I've not seen the mount issue you are describing where same SMB share can be mounted on Pi2 but not on Pi3. I have Pi1,2,3B systems in my test environment and no issues mounting the same SMB share thats located on my file server.

-Tim
 
Today I've got my cheap USB CM6206LX soundcard working as a source and output from my pi.

Using
Code:
mpc add alsa://hw:1,0
.... though I had to select the correct capture device through alsamixer. ("line" in this case).

I appreciate that this isn't the usual MoOde use case. I guess I can save it as a playlist. 🙂

Currently listening to Chvrches via......
Chromecast Audio -> CM6206LX -> MoOde on pi -> CM6206LX -> TPA3116 -> speakers

Controlled from Bubbleupnp on Android.