Moode Audio Player for Raspberry Pi

Wired and Wireless comms

Not perhaps a query unique to Moode, but as I'm a Moode user, here goes:

Currently my Pi3/IQDAC+ communicates via wired ethernet with my desktop computer. Audio files are stored on this desktop in a shared folder so that Moode can play the tracks. Moode is operated from a browser on this desktop. Everything works beautifully and sounds fantastic.

I currently have NO wireless provision and I also (through choice) don't have or want a smartphone.

I'd like to get a tablet/browser to control the PI/Moode combo wirelessly whilst it remains connected to my desktop computer via wired ethernet. Is this possible? I know next to nothing about wireless networking so don't know whether the PI/Moode Access Point would allow me to control Moode wirelessly from a tablet whist the PI/Moode combo continues to communicate with my desktop computer via wired ethernet.

Perhaps the communication modes are exclusive and I'm going to have to buy a wireless equipped router?

As an aside I've tried loads and loads of music players for the Pi and none of them come close to sounding as dynamic, open and detailed as Moode. It's a mystery to me how this is achieved but I'm a very happy user. Donation has been made!

Tim
 
Not perhaps a query unique to Moode, but as I'm a Moode user, here goes:

Currently my Pi3/IQDAC+ communicates via wired ethernet with my desktop computer. Audio files are stored on this desktop in a shared folder so that Moode can play the tracks. Moode is operated from a browser on this desktop. Everything works beautifully and sounds fantastic.

I currently have NO wireless provision and I also (through choice) don't have or want a smartphone.

I'd like to get a tablet/browser to control the PI/Moode combo wirelessly whilst it remains connected to my desktop computer via wired ethernet. Is this possible? I know next to nothing about wireless networking so don't know whether the PI/Moode Access Point would allow me to control Moode wirelessly from a tablet whist the PI/Moode combo continues to communicate with my desktop computer via wired ethernet.

Perhaps the communication modes are exclusive and I'm going to have to buy a wireless equipped router?

As an aside I've tried loads and loads of music players for the Pi and none of them come close to sounding as dynamic, open and detailed as Moode. It's a mystery to me how this is achieved but I'm a very happy user. Donation has been made!

Tim

Ideally, you'd get a wireless router. Use the tablet to communicate via the new router with the existing setup.

I can't recall enough about networking to know what will or won't work otherwise but... If you connect from a new android tablet to MoOde whilst it's already connected to your wired LAN. You have two networks connected to the Pi. but no way of telling those networks how to move traffic between them.

J.
 
Not perhaps a query unique to Moode, but as I'm a Moode user, here goes:

Currently my Pi3/IQDAC+ communicates via wired ethernet with my desktop computer. Audio files are stored on this desktop in a shared folder so that Moode can play the tracks. Moode is operated from a browser on this desktop. Everything works beautifully and sounds fantastic.

I currently have NO wireless provision and I also (through choice) don't have or want a smartphone.

I'd like to get a tablet/browser to control the PI/Moode combo wirelessly whilst it remains connected to my desktop computer via wired ethernet. Is this possible? I know next to nothing about wireless networking so don't know whether the PI/Moode Access Point would allow me to control Moode wirelessly from a tablet whist the PI/Moode combo continues to communicate with my desktop computer via wired ethernet.

Perhaps the communication modes are exclusive and I'm going to have to buy a wireless equipped router?

As an aside I've tried loads and loads of music players for the Pi and none of them come close to sounding as dynamic, open and detailed as Moode. It's a mystery to me how this is achieved but I'm a very happy user. Donation has been made!

Tim

Hi Tim,

Yes, you can use Access Point mode. Just connect tablet to SSID Moode, pwd=moodeaudio and then from Browser http: //moode.local or http:// 172.24.1.1 and you will get the UI. Follow Moode Setup Guide.

-Tim
 
Hi Tim,

Yes, you can use Access Point mode. Just connect tablet to SSID Moode, pwd=moodeaudio and then from Browser http: //moode.local or http:// 172.24.1.1 and you will get the UI. Follow Moode Setup Guide.

-Tim

Thanks Tim for this answer. And thanks Tim for the question. I had no idea this was possible, and it is exactly what I was looking for to control a Moode Audio box remotely without a wifi signal or ethernet wire.

Just to reiterate for anyone else like me, in Configuration settings, Network, leave SSID blank. Then Moode Audio will send out a wifi signal which you can connect to with the SSID and pwd show above. After wifi connection, direct your browser to either address Tim provided above. My Android phone asked to confirm the wifi connection because there was no internet connectivity. Just accepted that and you have a direct connection between phone (or tablet, laptop, whatever) to Moode Audio.

Moode Audio setup guide readme.txt says "WIFI ADAPTERS THAT SUPPORT ACCESS POINT MODE:

- Raspberry Pi 3 integrated WiFi adapter
- Canakit WiFi Adapter
- Raspberry Pi USB WiFi Dongle
- WiFi adapters based on RTL RT5370 chipset
- Edimax EW-7811Un"

Very helpful.

energyman
 
Hi,

Added Driver options for I2S devices and made a first pass at streamlining Audio config to make it a bit easier to use. Thanks to inmate SC for some nice ideas 🙂 The driver options are only available under the Advanced Audio Kernels and provide Enable/Disable for the two dtoverlay params below.

1) bclk_ratio_int_div

Integer balk divider for ES9023 48/96 kHz rates.

2) slave

Slave mode for Allo Boss DAC enabling it to work with Allo Kali reclocker

-Tim
 

Attachments

  • moode-r35-driveropt.png
    moode-r35-driveropt.png
    142.5 KB · Views: 421
  • moode-r35-config-menu.png
    moode-r35-config-menu.png
    210.7 KB · Views: 410
  • moode-r35-audiocfg-a.png
    moode-r35-audiocfg-a.png
    170.2 KB · Views: 416
  • moode-r35-audiocfg-b.png
    moode-r35-audiocfg-b.png
    171.4 KB · Views: 405
Hi Tim,

Yes, you can use Access Point mode. Just connect tablet to SSID Moode, pwd=moodeaudio and then from Browser http: //moode.local or http:// 172.24.1.1 and you will get the UI. Follow Moode Setup Guide.

-Tim

Can you connect to both AP mode and Ethernet at the same time? I believe that's what he wants to do: his PC and Pi are both connected via Ethernet, the Pi is providing AP and supporting his tablet wirelessly.

If not, I can knock up a quick config to allow that, post initial configuration. However, if your scripts overwrite the config we will need to work out a way to make it work through configuration changes.

EDIT: I guess so 🙂 looks like he's got it working. Enabling routing would give him internet connectivity, at the expense of more general cpu and subsystem activity. NAT can aid general connectivity too.
 
Last edited:
Ideally, you'd get a wireless router. Use the tablet to communicate via the new router with the existing setup.

I can't recall enough about networking to know what will or won't work otherwise but... If you connect from a new android tablet to MoOde whilst it's already connected to your wired LAN. You have two networks connected to the Pi. but no way of telling those networks how to move traffic between them.

J.

Just ensure an appropriate numbering and masking scheme, and enable packet forwarding. On Moode 3.1, if you enable AP mode, it starts dhcp and hostapd, which are the modules supporting network numbering and routing.

If you have a spare SD and a copy of Jessie, this tutorial is still valid, but replace USB wifi with whatever you have: How-To: Turn a Raspberry Pi into a WiFi router | Raspberry Pi HQ

If you have any other Ethernet device as well as your isp router, you can make an Ethernet-to-Ethernet router with any Pi, from the 1 on up, at minimal cost but a little time. It's worth getting to know Pi networking.

The only cross-network routing will be the tablet doing housekeeping or other wireless activity (such as internet access) and the Pi handing out network updates. It can handle those in its sleep. As a router, Jessie and the Pi3 together do a pretty good job.
 
Last edited:
MPD Error

Using Chrome on a PC to configure MPD I get the following error when I click the APPLY button: mpd-config: connection to mpd failed. The URL is: http://moode.local/mpd-config.php

The odd thing is that when I go back to check, my changes were saved. If the change requires that MPD needs to be restarted, I receive the message that MPD has been restarted.

So the only problem here is the error message every time I click the APPLY button. There seems to be no other problem. 😕
 
Just ensure an appropriate numbering and masking scheme, and enable packet forwarding. On Moode 3.1, if you enable AP mode, it starts dhcp and hostapd, which are the modules supporting network numbering and routing.

If you have a spare SD and a copy of Jessie, this tutorial is still valid, but replace USB wifi with whatever you have: How-To: Turn a Raspberry Pi into a WiFi router | Raspberry Pi HQ

If you have any other Ethernet device as well as your isp router, you can make an Ethernet-to-Ethernet router with any Pi, from the 1 on up, at minimal cost but a little time. It's worth getting to know Pi networking.

The only cross-network routing will be the tablet doing housekeeping or other wireless activity (such as internet access) and the Pi handing out network updates. It can handle those in its sleep. As a router, Jessie and the Pi3 together do a pretty good job.

Good to know. I wasn't prepared to rehack my config to prove it.

J.
 
I hope someone can help.


I've messed up adding a NAS source so now the the Moode UI hangs when I try to remove it. How can I remove this source via the CLI through SSH? I'd rather not reinstall from scratch again.

Hi,

View contents of table
sudo sqlite3 /var/www/db/player.db "select * from cfg_source"

Delete contents
sudo sqlite3 /var/www/db/player.db "delete * from cfg_source"

Btw, what do you mean "messed up adding a NAS source"? Maybe I can add or modify code to handle this scenario.

-Tim
 
Hi,

View contents of table
sudo sqlite3 /var/www/db/player.db "select * from cfg_source"

Delete contents
sudo sqlite3 /var/www/db/player.db "delete * from cfg_source"

Btw, what do you mean "messed up adding a NAS source"? Maybe I can add or modify code to handle this scenario.

-Tim

Hi Tim,


I'm afraid you're going to have to walk me through. Do I just type in those commands?
 
Okay, that's the output from the first command:

1|Moode|cifs|10.0.0.69||||utf8|61440|65536|cache=strict,ro,dir_mode=0777,file_mode=0777|username specified with no parameter


From the second I get this:


Error: near "*": syntax error

Hi,

My mistake... try it without the splat (*)

sudo sqlite3 /var/www/db/player.db "delete from cfg_source"

I think issue is blank username param. I'll have to look at the code to see whether it handles this condition.

If your CIFS share is not password protected try just specifying a bogus userid and password when you create the NAS source. I use "admin" and "password".

-Tim
 
Hi,

My mistake... try it without the splat (*)

sudo sqlite3 /var/www/db/player.db "delete from cfg_source"

I think issue is blank username param. I'll have to look at the code to see whether it handles this condition.

If your CIFS share is not password protected try just specifying a bogus userid and password when you create the NAS source. I use "admin" and "password".

-Tim

Thanks for your prompt help Tim. That's done the trick.


I have two moode boxes, and I was trying to share the files on USB sticks in each of them, between them. (If that makes sense!).


I've always found setting up NAS sources a trial and error process using that config tool. It's my lack of understanding how it works. I would rather it searched for samba/NFS shares on the network, but I know that would require lots more coding on your part.


In the meantime I'm happy just to listen to music off my usb stick.
 
Thanks for your prompt help Tim. That's done the trick.


I have two moode boxes, and I was trying to share the files on USB sticks in each of them, between them. (If that makes sense!).


I've always found setting up NAS sources a trial and error process using that config tool. It's my lack of understanding how it works. I would rather it searched for samba/NFS shares on the network, but I know that would require lots more coding on your part.


In the meantime I'm happy just to listen to music off my usb stick.

Hi,

I use a Pi3 that runs my moode reference image as a Samba NAS. It has a USB SSD attached and works just fine.

When u set up your NAS source enter a dummy userid and password and it should work.

-Tim
 

Attachments

  • moode-r35-nas-source.png
    moode-r35-nas-source.png
    116.6 KB · Views: 420
Well it is sort of two steps forward and one step back.

Your instructions were perfect. Everything was updated and compiled perfectly.
I do have version 1.1.6 and when I use Kazoo from iOS or Windows I can see all of the files on the Moode DLNA server. The DLNA server no longer crashes!

Not everything is quite how I expected it but that is a nit compared to the problem I am having now. I can add songs to the playlist in Kazoo, and the playlist in Moode does get updated. When I try to play one of the songs that was added from Kazoo the play icon blinks, but that is it. If the songs were added to the playlist from the Moode UI everything works perfectly.

Since the debug log was still configured, I took a look in it. It looks like all of the items that were on the default playlist (radio stations) have been removed as they were not found in the db. Did the update to sqlite clear the data I wonder?

The reason the music won't play is that I apparently don't have access to the flac files any more. I can provide examples from the log if required.

HTML:
<HEAD><TITLE>403 Forbidden</TITLE></HEAD><BODY><H1>Forbidden</H1>You don't have permission to access this resource.</BODY>

Cheers, Bryce.


Hi Bryce,

I have the same problem as you have. Could you find a solution? I have tried to add a user in the minidlna configs -> this was not the answer.

Thanks, Thomas