Moode Audio Player for Raspberry Pi

[TimCurtis]

Btw, refer to Moode Twitter feed for a fix to an issue with Boss driver not being visible in Adv kernels.

 

https://twitter.com/MoodeAudio

 

-Tim

[macuniverse]

2 hours ago, TimCurtis said:

Hi,

 

Imagine listening with headphones!

 

-Tim

 

That's why I always play the music first and put the headphones on second. Hard learned lesson!

[JoseL]

19 hours ago, Andrea said:

Hi @TimCurtis

 

Thank a lot for the new Moore version!

I've installed now and I have some questions:

 

What is the difference between "Advanced-LL" and "Advanced-RT" Kernel?

What is the difference between MPD scheduler "FIFO" and "RR"?

What is the better setup?

 

Soxr multithread sounds better?

 

Have a nice day!

Andrea

Yes, please Tim (or somebody else) could you give a brief explanation of those settings and what to expect in terms of sound quality?

TIA,

JoseL

[JoseL]

10 hours ago, macuniverse said:

I forgot to mention above, Is it possible to add "Recently added Albums" option?

 

Thanks

Yep, it would be great to have that option, also the ability to import playlists on different formats (m3u/m3u8, xlm, etc).

Please Tim, consider those features for upcomming updates.

TIA,

JoseL

[intermediatic]

Wow yes if it would be possible to have recently added albums that would be fantastic.

[8BitKid]

@TimCurtis: have you thought about offering a Patreon so we can contribute to development on an ongoing basis?

[TimCurtis]

22 hours ago, Andrea said:

Hi @TimCurtis

 

Thank a lot for the new Moore version!

I've installed now and I have some questions:

 

What is the difference between "Advanced-LL" and "Advanced-RT" Kernel?

What is the difference between MPD scheduler "FIFO" and "RR"?

What is the better setup?

 

Soxr multithread sounds better?

 

Have a nice day!

Andrea

Hi Andrea,

 

The Low Latency (LL) and Real-Time (RT) kernels impliment a Task Scheduler strategy that allows the music playing tasks to get higher CPU priority than with Standard kernel.

 

This just means that that music playing tasks will yield the CPU to other tasks less frequently. Tasks configured with FIFO policy are least likely to yield than tasks configured with RR policy.

 

Another feature of the Advanced kernels is that they include a set of enhanced audio capabilities for ES and PCM series I2S DAC chips that were developed by a couple of the Linux Audio kernel devs a while back. Things like 352.8/384k rates, integer bclk divider, etc.

 

Some users feel that these techniques result in improved sound quality but like many things in HiFi YMMV.

 

SoX multithreading is really about efficiency and probably only makes sense when running Standard kernel. It too may not make any audible improvement.

 

-Tim

[tkr001]

On ‎16‎/‎04‎/‎2017 at 2:37 PM, macuniverse said:

Thanks for the update. I don't understand many of the improvements but they sound impressive 

 

So, still no Spotify service support? Pity, this rules me out as I don't want to keep/maintain two sets of players + hardware and keep switching between them. I use Spotify extensively.

 

Tim, is there any docos/links (not necessarily your own) which explain all these advanced tuning options in a humanly possible way?

 

Cheers

I am running spotify connect on the same system as moode 3.5

 

Linux 4.4.39-moode2+ J-Lite Core, armv7l Architecture
                           __    ____  ____
       __ _  ___  ___  ___/ /__ / __ \/ __/
      /  ' \/ _ \/ _ \/ _  / -_) /_/ /\ \
     /_/_/_/\___/\___/\_,_/\__/\____/___/

              moodeOS Version 2.0
                 multi-kernel
              (C) 2016 Tim Curtis

moodeOS is based on Debian GNU/Linux and is custom
factored for Moode Audio Player. The programs included
with moodeOS are free software; the exact distribution
terms for each program are described in the individual
files in /usr/share/doc/*/copyright. moodeOS comes with
absolutely no warranties expressed or implied, or any
other guarantees. Moode Audio Player is covered under
separate license agreement contained in the file
/var/www/LICENSE.moode and displayed in Moode About.

Last login: Thu Apr 20 08:56:51 2017 from 192.168.1.161
pi@moode:~ $ sudo sqlite3 /var/local/www/db/moode-sqlite3.db "update cfg_audiodev set kernel='' where id='1'"
pi@moode:~ $ sudo su
root@moode:/home/pi# systemctl status spotify-connect
● spotify-connect.service - Spotify Connect
   Loaded: loaded (/etc/systemd/system/spotify-connect.service; enabled)
   Active: active (running) since Thu 2017-04-20 08:59:13 NZST; 21min ago
 Main PID: 606 (librespot)
   CGroup: /system.slice/spotify-connect.service
           └─606 /root/librespot --name MoOde --cache /tmp --bitrate 320 --backend alsa --device hw:IQaudIODAC > /dev/null 2>&1

Apr 20 08:59:13 moode systemd[1]: Started Spotify Connect.
Apr 20 08:59:18 moode librespot[606]: INFO:librespot: librespot 871e9e8 (2017-03-26). Built on 2017-04-13.
Apr 20 08:59:18 moode librespot[606]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
root@moode:/home/pi#

[TimCurtis]

1 hour ago, tkr001 said:

I am running spotify connect on the same system as moode 3.5

 

Linux 4.4.39-moode2+ J-Lite Core, armv7l Architecture
                           __    ____  ____
       __ _  ___  ___  ___/ /__ / __ \/ __/
      /  ' \/ _ \/ _ \/ _  / -_) /_/ /\ \
     /_/_/_/\___/\___/\_,_/\__/\____/___/

              moodeOS Version 2.0
                 multi-kernel
              (C) 2016 Tim Curtis

moodeOS is based on Debian GNU/Linux and is custom
factored for Moode Audio Player. The programs included
with moodeOS are free software; the exact distribution
terms for each program are described in the individual
files in /usr/share/doc/*/copyright. moodeOS comes with
absolutely no warranties expressed or implied, or any
other guarantees. Moode Audio Player is covered under
separate license agreement contained in the file
/var/www/LICENSE.moode and displayed in Moode About.

Last login: Thu Apr 20 08:56:51 2017 from 192.168.1.161
pi@moode:~ $ sudo sqlite3 /var/local/www/db/moode-sqlite3.db "update cfg_audiodev set kernel='' where id='1'"
pi@moode:~ $ sudo su
root@moode:/home/pi# systemctl status spotify-connect
● spotify-connect.service - Spotify Connect
   Loaded: loaded (/etc/systemd/system/spotify-connect.service; enabled)
   Active: active (running) since Thu 2017-04-20 08:59:13 NZST; 21min ago
 Main PID: 606 (librespot)
   CGroup: /system.slice/spotify-connect.service
           └─606 /root/librespot --name MoOde --cache /tmp --bitrate 320 --backend alsa --device hw:IQaudIODAC > /dev/null 2>&1

Apr 20 08:59:13 moode systemd[1]: Started Spotify Connect.
Apr 20 08:59:18 moode librespot[606]: INFO:librespot: librespot 871e9e8 (2017-03-26). Built on 2017-04-13.
Apr 20 08:59:18 moode librespot[606]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
root@moode:/home/pi#

 

Does the 04-13 build still set client volume to 100% initially?

[tkr001]

yes it does

[serialdie]

@TimCurtis Is the 3.6 update OTA?

[TimCurtis]

Hi,

 

Yes, there is an in-place update to go from Moode 3.5 to 3.6

 

On System config, Click CHECK for software update, then VIEW/INSTALL

 

-Tim

[michelemezza]

I just updated to 3.6 using inplace "mode".

Everything is fine. Only there is no massage of rebooting.

After 6-7 minutes I rebooted the system 

[Mark-JPN]

Hi!

 

I'v just purchased 3.6, and enjoy it.

It is great improvement!

Thanks!

 

However, I have two problems.

 

One is that moodeOS 3.6 does not recognize meta data of AIFF at all.

A file name of AIFF is displayed only.

Please see attached images.

In case of other sources, for example m4a, flac, mp3, etc., meta data is recognized and displayed on UI correctly.

 

It is confirmed that an artwork named "folder.jpg" placed on the same level as AIFF was recognized and displayed on UI.

After deleting it, no artwork is displayed when playing AIFF sources.

 

I know that meta data of AIFF is recognized and displayed until 3.1.

I hope that this problem will be solved in next version.

 

Another one will be posted as a new one in order to avoid confusion.

[Mark-JPN]

Another one is concerning AirPlay.

 

When an I2S DAC board attached on RPi, AirPlay works with no problem.

 

However, when using USB-DAC with MoodeOS 3.6, RPi is not recognized as AirPlay receiver by both of iOS and macOS.

Of course, "none" is selected at "I2S audio device", "USB" is selected at "Audio output" in "MPD Configuration", and "Airplay receiver" is turned on at "Renderers".

 

Is it available to avoid this problem?

Or is it a specified working by MoodeOS?

[Mark-JPN]

5 hours ago, Mark-JPN said:

Another one is concerning AirPlay.

 

When an I2S DAC board attached on RPi, AirPlay works with no problem.

 

However, when using USB-DAC with MoodeOS 3.6, RPi is not recognized as AirPlay receiver by both of iOS and macOS.

Of course, "none" is selected at "I2S audio device", "USB" is selected at "Audio output" in "MPD Configuration", and "Airplay receiver" is turned on at "Renderers".

 

Is it available to avoid this problem?

Or is it a specified working by MoodeOS?

 

Concerning AirPlay problem posted above...

 

Regardless of whether the kernel is advanced or standard, this problem is occurring.

[rappo69]

Hi Tim,

 

I have the release 3.1 installed on RPi3 and I would like to update to 3.6 but when I "CHECK  for software update" it say "Moode software is up to date". It means that I'm forced to download manually from server the 3.6 and install via SD? In this case I will have to rebuild the library...

Thanks for ur help

[astropuppy]

Upgrade 3.5 -> 3.6 on a PI Zero and PI 3

 

"That was Easy" ... MoOde is my number one choice for lossless listening.

Chromecast Audio for whole house MP3 listening.

 

Great job Tim.

 

 

[TimCurtis]

On 4/26/2017 at 4:10 PM, michelemezza said:

I just updated to 3.6 using inplace "mode".

Everything is fine. Only there is no massage of rebooting.

After 6-7 minutes I rebooted the system 

Hi,

 

Completion message is only displayed for short time. This will be fixed in next update.

 

-Tim

[TimCurtis]

7 hours ago, Mark-JPN said:

Hi!

 

I'v just purchased 3.6, and enjoy it.

It is great improvement!

Thanks!

 

However, I have two problems.

 

One is that moodeOS 3.6 does not recognize meta data of AIFF at all.

A file name of AIFF is displayed only.

Please see attached images.

In case of other sources, for example m4a, flac, mp3, etc., meta data is recognized and displayed on UI correctly.

 

It is confirmed that an artwork named "folder.jpg" placed on the same level as AIFF was recognized and displayed on UI.

After deleting it, no artwork is displayed when playing AIFF sources.

 

I know that meta data of AIFF is recognized and displayed until 3.1.

I hope that this problem will be solved in next version.

 

Another one will be posted as a new one in order to avoid confusion.

Hi,

 

I posted AIFF issue in MPD forum a while back and Max (the main dev) partial analysis indicated file corruption but I'm thinking that possibly the 0.20.x series of MPD is either a lot more strict about AIFF format or its a bug.

https://forum.musicpd.org/viewtopic.php?f=7&t=4326&sid=8f189ac04d10285e6fb13a8f5a6cb93b

 

I'd suggest making your own post in MPD forum along with link to sample files and see if Max can reproduce the issue. You can link to my post for all the MPD config information that Max usually needs.

 

-Tim

[TimCurtis]

7 hours ago, Mark-JPN said:

Another one is concerning AirPlay.

 

When an I2S DAC board attached on RPi, AirPlay works with no problem.

 

However, when using USB-DAC with MoodeOS 3.6, RPi is not recognized as AirPlay receiver by both of iOS and macOS.

Of course, "none" is selected at "I2S audio device", "USB" is selected at "Audio output" in "MPD Configuration", and "Airplay receiver" is turned on at "Renderers".

 

Is it available to avoid this problem?

Or is it a specified working by MoodeOS?

Hi Mark,

 

What USB DAC are u using?

 

Try setting Airplay to use 24 or 32 bit depth. Configure -> Audio -> CONFIGURE Airplay,

 

-Tim 

[TimCurtis]

1 hour ago, rappo69 said:

Hi Tim,

 

I have the release 3.1 installed on RPi3 and I would like to update to 3.6 but when I "CHECK  for software update" it say "Moode software is up to date". It means that I'm forced to download manually from server the 3.6 and install via SD? In this case I will have to rebuild the library...

Thanks for ur help

Hi,

 

Yes, release 3.6 is either whole image or in-place update if you are already running release 3.5.

 

-Tim

[TimCurtis]

39 minutes ago, astropuppy said:

Upgrade 3.5 -> 3.6 on a PI Zero and PI 3

 

"That was Easy" ... MoOde is my number one choice for lossless listening.

Chromecast Audio for whole house MP3 listening.

 

Great job Tim.

 

 

Hi,

 

Thanks!

 

-Tim

[Mark-JPN]

14 minutes ago, TimCurtis said:

Hi Mark,

 

What USB DAC are u using?

 

Try setting Airplay to use 24 or 32 bit depth. Configure -> Audio -> CONFIGURE Airplay,

 

-Tim 

 

Thanks for quick response!

 

I tried setting Airplay configuration to use 24, 24 3LE, 24 3LB, 36bit depth.

 

But, Moode AirPlay is still not available in any bit depth.

 

Using USB DAC is FOSTEX HP-A8.

 

Regards

[TimCurtis]

10 minutes ago, Mark-JPN said:

 

Thanks for quick response!

 

I tried setting Airplay configuration to use 24, 24 3LE, 24 3LB, 36bit depth.

 

But, Moode AirPlay is still not available in any bit depth.

 

Using USB DAC is FOSTEX HP-A8.

 

Regards

Hi,

 

Another setting to try is to force Airplay to use software volume. Change Auto to Software in Airplay config.

 

You might also want to try turning on Moode debug logging in System config then turn OFF/ON Airplay and examine moode log for the shairport-sync launch string. Verify that its set to use hw:1 which is the card num assigned to USB audio devices.

 

cat /var/log/moode.log from ssh terminal - OR -

click System info from the main menu and scroll to the end for moode log.

 

If still no audio then send me an email and I'll walk you through capturing a shairport-sync verbose log  that can be posted to the issue list at shairport-sync GitHub.

 

-Tim