Share on other sites

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.

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.

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.

Share this post

Link to post

Share on other sites

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...

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.

Share this post

Link to post

Share on other sites

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.

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.