Moode Audio Player for Raspberry Pi

Jump to Latest
#11,202
TheOldPresbyope said:
Hi, Mike.

I'm not a lawyer nor do I play one on TV. However, I do know how to argue like one. It seems to me there is sufficient vagueness in the wording of GPLv3 (specifically in its labored definitions of things like "System Libraries") to be able to argue for and against releasing moOde images without providing access to source code for everything in them.

GNU General Public License - Wikipedia is a fun read (esp. the discussion of Linking and derived works). The line which jumps out at me is:



So it's not an issue unless someone makes it an issue. These shenanigans are the stuff of which lawyers careers are made. It's not for me.

Regards,
Kent
Click to expand...

I think it was the $10 charge that set the MPD dev off on one, he has also made the same request of Euphony Audio who don't seem to have responded.

I get the impression having occasionally browsed the MPD git issues list that once his mind is made up that's it and the power is with how the copywrite interprets the licence or your compliance. As Kent said I too am not lawyer and having spent an hour watching a Linux licensing video I certainly would not be a copywrite lawyer.

The only way round I can see is the Redhat route and have support subscriptions (that would be a nightmare 🙂 ) even then Redhat release all sources which is how Centos exists.

Is MPD in the Red hat repos? 🙂
 
#11,203
Serverbaboon said:
I think it was the $10 charge that set the MPD dev off on one, he has also made the same request of Euphony Audio who don't seem to have responded.

I get the impression having occasionally browsed the MPD git issues list that once his mind is made up that's it and the power is with how the copywrite interprets the licence or your compliance. As Kent said I too am not lawyer and having spent an hour watching a Linux licensing video I certainly would not be a copywrite lawyer.

The only way round I can see is the Redhat route and have support subscriptions (that would be a nightmare 🙂 ) even then Redhat release all sources which is how Centos exists.

Is MPD in the Red hat repos? 🙂
Click to expand...

Nope, not in RHEL/CentOS 7, nor epel.

Phil
 
#11,204
staskuzma said:
Good afternoon. Tell me what needs to change in the MPD settings to see all the folders on the NAS. The drive mounts fine but MPD can not display all folders updating to spin but the folders are not added.
Click to expand...

gabrielrosca said:
Hi!
Most probably the player is not allowed to access all the folders.

Try to browse that folder from SSH like: cd /mnt/NAS/YOUR_NAS
Display folder and attributes: ls -l
Click to expand...

Hi,

Yes, most likely permissions issue. Examine MPD log to see whats going on.

cat /var/log/mpd/log

-Tim
 
#11,205
TimCurtis said:
Hi,

This appears to be a bug in Piano 2.1 driver. Sub 2.0 mode can be set but not the 2.1 and 2.2 modes. See the amixer output below. I've sent a note to Allo.

Kernel 4.9.61

pi@rp3:~ $ amixer -c 0 sget "Subwoofer mode"
Simple mixer control 'Subwoofer mode',0
Capabilities: enum
Items: 'None' '2.0' '2.1' '2.2'
Item0: 'None'

pi@rp3:~ $ amixer -c 0 sset "Subwoofer mode" 2.0
Simple mixer control 'Subwoofer mode',0
Capabilities: enum
Items: 'None' '2.0' '2.1' '2.2'
Item0: '2.0'

pi@rp3:~ $ amixer -c 0 sset "Subwoofer mode" "2.1"
amixer: Invalid command!

pi@rp3:~ $ amixer -c 0 sset "Subwoofer mode" "2.2"
amixer: Invalid command!


-Tim
Click to expand...

jonners said:
I certainly had it working in 2.2 mode some time ago, in an earlier release of Moode - but I'm not sure which one.
Click to expand...

soundcheck said:
Piano2.1

Code: 
root@x ~# amixer -c 0 sget "Subwoofer mode"
Simple mixer control 'Subwoofer mode',0
  Capabilities: enum
  Items: 'None' '2.0' '2.1' '2.2'
  Item0: 'None'
root@x ~# amixer -c 0 sset "Subwoofer mode" "2.2"
Simple mixer control 'Subwoofer mode',0
  Capabilities: enum
  Items: 'None' '2.0' '2.1' '2.2'
  Item0: '2.2'
root@x ~# amixer -c 0 sset "Subwoofer mode" "2.1"
Simple mixer control 'Subwoofer mode',0
  Capabilities: enum
  Items: 'None' '2.0' '2.1' '2.2'
  Item0: '2.1'
root@x ~# amixer -c 0 sset "Dual Mode" "Dual-Mono"
Simple mixer control 'Dual Mode',0
  Capabilities: enum
  Items: 'None' 'Dual-Mono' 'Dual-Stereo'
  Item0: 'Dual-Mono'

No issues over here with the 4.9.61 kernel.
I'm running Arch.
And a patched 4.9.61 audio kernel of course. The patches though wouldn't make a difference.
Click to expand...

Hi,

Somehow the Allo firmware files got nuked :-0 Below is from syslog after trying to change setting via alsamixer. Kernel was installed via rpi-update.

ETA: I'm not seeing the firmware/allo directory in the raspberrypi linux source tree.

Nov 21 06:47:26 rp3 kernel: [ 85.813036] pcm512x 1-004c: Dsp Firmware File Name: allo/piano/2.2/allo-piano-dsp-192000-60-0.bin
Nov 21 06:47:26 rp3 kernel: [ 85.813128] pcm512x 1-004c: Direct firmware load for allo/piano/2.2/allo-piano-dsp-192000-60-0.bin failed with error -2
Nov 21 06:47:26 rp3 kernel: [ 85.813135] pcm512x 1-004c: Error: Allo Piano Firmware allo/piano/2.2/allo-piano-dsp-192000-60-0.bin missing. -2
Nov 21 06:47:26 rp3 kernel: [ 86.262270] pcm512x 1-004c: Dsp Firmware File Name: allo/piano/2.2/allo-piano-dsp-192000-60-0.bin
Nov 21 06:47:26 rp3 kernel: [ 86.262318] pcm512x 1-004c: Direct firmware load for allo/piano/2.2/allo-piano-dsp-192000-60-0.bin failed with error -2
Nov 21 06:47:26 rp3 kernel: [ 86.262325] pcm512x 1-004c: Error: Allo Piano Firmware allo/piano/2.2/allo-piano-dsp-192000-60-0.bin missing. -2

pi@rp3:~ $ ls -l /lib/firmware
total 4844
drwxr-xr-x 2 root root 4096 Sep 7 11:13 3com
drwxr-xr-x 2 root root 4096 Sep 7 11:13 advansys
-rw-r--r-- 1 root root 50698 Aug 9 07:10 agere_ap_fw.bin
-rw-r--r-- 1 root root 65046 Aug 9 07:10 agere_sta_fw.bin
drwxr-xr-x 2 root root 4096 Sep 7 11:13 ar3k
-rw-r--r-- 1 root root 153416 Aug 9 07:10 ar5523.bin
.
.
.
 
Last edited:
#11,206
In need of a little help with regard to Qobuz, I have succesfully built several instances of 4 beta9, but none of them will connect to Qobuz; whereas an earlier beta (7?) did.
Beta 9 is running on RPi3 in both cases, one with HiFiBerry Digi Pro Ethernet connection, the other as a USB to DAC with WiFi connection.
I have tried several re-installs of Upmpdcli as per Component 6 of Additional Components Recipe V1.9.
I notice one error message:
upsend_src/upsend.cpp:161:2: warning: #warning "problem with resource value s!" [-Wcpp]
#warning "problem with resource values!"
after command sudo make -j $(nproc --all)
Is this an error?
I use Linn Kazoo on my Windows Laptop as control point as I don't have Android or idevices.

 
#11,207
Serverbaboon said:
You need a UPNP control point app running on your phone and/or tablet/computer.

For Android this means something like one of the two Bubble UPNP applications or Linn Kazoo.

For iOS you need Linn Kazoo or Luminous.

( Skip this if know the apps)
For example in BubbleUnpn if you select the menu Now Playing you get a menu. In that menu you should get a section called Renderer and One called library.

Renderer
This is the bit that plays the music, the first time you run Bubble it will probably have the Renderer set to Local Render, select the down arrow and a list of discovered UPNP output devices. You should be able to see Moode UPNP here.

Library
Again the first time you run Bubble the library will be set to Local and Cloud. In the list of Libraries you should see Moode UPNP-mediaserver, select this.

In the Library screen you should be able to navigate Tidal as a series of folders at the top of the screen. Play from here.

As an aside, for me Bubbleds and Kazoo are my choices on Android as they support the Radio features of the UPNP renderer in Moode. The normal BubbleUnpn is more feature rich with its support for Echo , the features appear in BubbleDS later.

Regards
Click to expand...


Thanks for the answer Serverbaboon! 🙂
 
#11,209
Serverbaboon said:
You need a UPNP control point app running on your phone and/or tablet/computer.

For Android this means something like one of the two Bubble UPNP applications or Linn Kazoo.

For iOS you need Linn Kazoo or Luminous.

( Skip this if know the apps)
For example in BubbleUnpn if you select the menu Now Playing you get a menu. In that menu you should get a section called Renderer and One called library.

Renderer
This is the bit that plays the music, the first time you run Bubble it will probably have the Renderer set to Local Render, select the down arrow and a list of discovered UPNP output devices. You should be able to see Moode UPNP here.

Library
Again the first time you run Bubble the library will be set to Local and Cloud. In the list of Libraries you should see Moode UPNP-mediaserver, select this.

In the Library screen you should be able to navigate Tidal as a series of folders at the top of the screen. Play from here.

As an aside, for me Bubbleds and Kazoo are my choices on Android as they support the Radio features of the UPNP renderer in Moode. The normal BubbleUnpn is more feature rich with its support for Echo , the features appear in BubbleDS later.

Regards
Click to expand...

@ Serverbaboon

Hi,

Have you succeeded in getting cover art to show on the MoOde screen when using upnp with either Kazoo or Bubble DS on MoOde 4.0b9. I have not.

Thanks
 
#11,210
For whoever is interested in Tidal streaming, there is also the option to install (and configure) BubbleUPnPserver, providing the additional OpenHome features which are required - in my understanding - to make full usage of controllers such as Lumin App or Linn Kazoo.
I have been doing that for quite some time (2 years o more) and always worked from earlier versions of Moode up to Beta9.
 
#11,212
hui13 said:
I should point out that I am getting artwork for radio stations, so I am probably experiencing an issue with how my music library cover art interacts with upnp.
Click to expand...

Hi,

1. Verify that upexplorer is installed

pi@rp3:~ $ which upexplorer
/usr/local/bin/upexplorer

2. Run a test to see whether it returns the url to cover art image.

upexplorer --album-art "Moode UPNP"

You can also turn on debug logging in System config and then look for the line below in moode log.

cat /var/log/moode.log
enhanceMetadata(): coverurl: (...)

-Tim
 
#11,215
TimCurtis said:
Hi,

1. Verify that upexplorer is installed

pi@rp3:~ $ which upexplorer
/usr/local/bin/upexplorer

2. Run a test to see whether it returns the url to cover art image.

upexplorer --album-art "Moode UPNP"

You can also turn on debug logging in System config and then look for the line below in moode log.

cat /var/log/moode.log
enhanceMetadata(): coverurl: (...)

-Tim
Click to expand...

Thanks for the prompt reply. I checked and upexplorer was not installed. I am afraid that I do not know what it is. Googled it without any luck.

How would I go about installing it?
 
#11,216
franz159 said:
For whoever is interested in Tidal streaming, there is also the option to install (and configure) BubbleUPnPserver, providing the additional OpenHome features which are required - in my understanding - to make full usage of controllers such as Lumin App or Linn Kazoo.
I have been doing that for quite some time (2 years o more) and always worked from earlier versions of Moode up to Beta9.
Click to expand...
The upnp feature in Moode is is already ohome enabled and supports more ohome features than the BubbleUnpn server such as ohradio.

There was an issue with a version of Kazoo that did not work but that was fixed some time ago.

The Bubble server is useful if you want the Chromecast transcoding or internet access, you do not need it for Renderer controlled playlists.
 
#11,217
hui13 said:
Thanks for the prompt reply. I checked and upexplorer was not installed. I am afraid that I do not know what it is. Googled it without any luck.

How would I go about installing it?
Click to expand...
I am not near a computer to tell you which step but I think you just have missed out the one that installs this it utility. I think it is in the upmpdcli section, it's the libupnpp-samples build step.
 
#11,218
BackinBlack said:
In need of a little help with regard to Qobuz, I have succesfully built several instances of 4 beta9, but none of them will connect to Qobuz; whereas an earlier beta (7?) did.
Beta 9 is running on RPi3 in both cases, one with HiFiBerry Digi Pro Ethernet connection, the other as a USB to DAC with WiFi connection.
I have tried several re-installs of Upmpdcli as per Component 6 of Additional Components Recipe V1.9.
I notice one error message:
upsend_src/upsend.cpp:161:2: warning: #warning "problem with resource value s!" [-Wcpp]
#warning "problem with resource values!"
after command sudo make -j $(nproc --all)
Is this an error?
I use Linn Kazoo on my Windows Laptop as control point as I don't have Android or idevices.
Click to expand...

I think you need to try just the 'make' command with out the options for upmpdcli. I think some one posted something about this , however there is a lot of activity on the thread and I could not find it.
 
#11,220
Hi,

Thanks to Gordon at IQaudIO for providing a nice 7" Touch display for testing 🙂

-Tim
 

Attachments

  • pi-touch-display.png
    pi-touch-display.png
    826.3 KB · Views: 321
You must log in or register to reply here.
Top Bottom