RuneAudio 0.6-beta for most Raspberry Pi models

RoyB

Hi janui,

In addition to previous post.
I temporarily disconnected the hdd en connected a USB-stick with some music files on it. The same issue: the USB-stick doesn’t mount.
I’m now using 0.5b again, but like to use the upgrade of 0.6b. Is there a way to roll back to build version 2?

Regards,
RoyB

janui

Hi RoyB,

RoyB wroteIn addition to previous post....the USB-stick doesn’t mount....

Thanks for posting this. There was a Linux utility compatibility problem between ARCH and RPiOS. I had tested the last changes in our development environment and on one of the 0.6b versions. However, a parameters was invalid on the other 0.6b version, so one version was failing. I have posted some fixes.

You can get the latest fixes by updating the player (the patch level will remain unchanged):
1. Go to the /dev menu - in the browser url enter http://<playername>.local/dev (e.g. http://runeaudio.local/dev).
2. Switch dev mode on - Scroll down to the 'Dev Mode' button and toggle it to ON, then click on the ‘Save Settings’ button below the toggle button.
3. When the UI comes back, click on the first ‘Save Settings’ button to activate the dev mode options.
4. Perform a git pull - Scroll down to the ‘Update RuneUI’ option and click on the ‘git pull’ button. The update will then be carried out and the player will reboot.

janui

RoyB

Janui wrote:

However, a parameters was invalid on the other 0.6b version, so one version was failing. I have posted some fixes.

Hi Janui, top!!! It works again!
Thanks! I hope you have some time left to enjoy some music yourself.

RoyB

RoyB

Hi janui,

I obtained a SSD to replace my HDD

. RuneAudio 0.6b build3 nicely mounts the SSD (a Crucial X9).
The music files can be seen in the file-explorer of my desktop. Unfortunately transferring files cannot be done. The notification is that the usb-device is protected. In the mean time I learned that this is because of the used exFAT filesystem, which is normally not compatible with version 0.6b.
What is the reason for that, as exFAT is a common and universal filesystem for external SSD’s?

How can I, in an easy way, make RuneAudio accept remote access of an exFAT formatted SSD?

RoyB

RoyB

Hi janui,

In addition to previous post.
I figured out that to enable remote access (via desktop) to an attached SSD with exFAT filesystem udevil.conf has to be changed.
To be more precise:

 default_options_exfat     = ro, nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID

I tried the following changes:
1.

 default_options_exfat     = rw, nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID

 default_options_exfat     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID

Both options seem to be effective. I like to know what is your recommendation.

I made the changes by using Notepad++, directly via desktop access to RuneAudio sys config dir (/etc). So I did not use SSH (PuTTy). Is this a correct way of working?

RoyB

janui

Hi RoyB,

RoyB wrote...Both options seem to be effective. I like to know what is your recommendation....

Both are fine. From a documentation perspective the first is beter since it explicitly specifies r/w but from a consistency perspective the second is more in line with the existing entries. Another option is to format the SSD as NTFS, this is fully r/w accessible on RuneAudio as default. NTFS also has some benefits when using Windows. Here is a discussion over NTFS or sxFAT: https://www.diskpart.com/articles/ntfs-or-exfat-for-ssd-7201.html
janui

janui

Hi There,

While working on the next version, we have run into some problems with Samba file sharing. I have posted some fixes and a couple of improvements.

You can get the latest fixes by updating the player (with this update the patch level will move to 4):
1. Go to the /dev menu - in the browser url enter http://<playername>.local/dev (e.g. http://runeaudio.local/dev).
2. Switch dev mode on - Scroll down to the 'Dev Mode' button and toggle it to ON, then click on the ‘Save Settings’ button below the toggle button.
3. When the UI comes back, click on the first ‘Save Settings’ button to activate the dev mode options.
4. Perform a git pull - Scroll down to the ‘Update RuneUI’ option and click on the ‘git pull’ button. The update will then be carried out and the player will reboot.

janui

RoyB

janui wrote:

Another option is to format the SSD as NTFS, this is fully r/w accessible on RuneAudio as default.

Hi janui,
Indeed using an exFAT formatted SSD as an USB-connected device has its drawback. Transferring (drag-and-drop or copy-past) music files works fine. But renaming folder names is not easily done via Windows. Windows doesn’t accept simple case (upper/lower) changes in this situation (Windows > MPD). A workaround is adding a character and then make your changes and eventually delete the added character. In addition a second issue is that the original folder and the renamed one are displayed in MPD. By deleting and updating the MPD Library this can be solved.
So using an exFAT formatted USB-device causes ‘case-sensitivity’ compatibility problems between Windows and MPD.

I changed the file system of the SSD to NTFS. All works well!

Lesson learned: use NTFS formatted USB-devices.

RoyB

janui

Hello There,
These has been lots of (mis)information on internet this week concerning the 'xz-utils backdoor' security issue. If you are using RuneAudio 0.6b there are no problems unless you have manually upgraded the OS.

If you have manually upgraded the OS, see here: https://lists.debian.org/debian-security-announce/2024/msg00057.html. You should take appropriate action if the package 'xz' (and/or 'xz-utils') have versions matching those listed as compromised.

janui

janui

Hi Beelzebassie & RoyB,

Beelzebassie wrote...Encountered some strange behavior: When browsing the library, adding a cue-sheet to the queue does show the album-art on playback; adding the folder the cue-sheet is in instead, does not...

I have looked at this problem and made some changes to the metadata and album art processing. I am not sure that all situations using cue sheets are fixable due to the way MPD processes them. There are also some other related bug fixes included. Looking forward to your feedback...

You can get the latest changes and bug fixes by updating the player (with this update the patch level will remain at 4):
1. Go to the /dev menu - in the browser url enter http://<playername>.local/dev (e.g. http://runeaudio.local/dev).
2. Switch dev mode on - Scroll down to the 'Dev Mode' button and toggle it to ON, then click on the ‘Save Settings’ button below the toggle button.
3. When the UI comes back, click on the first ‘Save Settings’ button to activate the dev mode options.
4. Perform a git pull - Scroll down to the ‘Update RuneUI’ option and click on the ‘git pull’ button. The update will then be carried out and the player will reboot.

janui

Beelzebassie

I'll give it a spin.

Thanks for the heads-up about the xz-utils backdoor too!

tomp

0.6 is working great for me on a pi 4b with a HifiBerry digi2 pro hat.

I really appreciate the continued effort to keep the classic RuneAudio alive! Thank you!!!

Stephane

I am facing a problem with my music collection, the Library tab only displays directories to the letter D!
If I search the database for artists past letter D then no problem, I can see the result on the screen (local or remote).
So maybe it's a limitation of the number of lines that it can display?
I'm running version 0.6b , made a git pull and my my other Rune system (0.5) does not do this.
Anyone with the same behaviour?

janui

Hi Stephane,

Stephane wroteI am facing a problem with my music collection, the Library tab only displays directories to the letter D!
If I search the database for artists past letter D then no problem, I can see the result on the screen (local or remote).

There are no line limitations built in. However, there could be a limit imposed by one of the system settings, or it could be caused by a bug.
Can you tell me how many directories you have starting with the letter a to d?
Have you tried using a different browser?
Do you use modified code in the library UI?

janui

Stephane

There are 54 files and 176 directories displayed. On the local screen (chromium) or on a remote Firefox.
No modifications in the UI except one, the name of the player just before the MENU (top left).

janui

Hi Stephane,

Stephane wroteThere are 54 files and 176 directories displayed. On the local screen (chromium) or on a remote Firefox.
No modifications in the UI except one, the name of the player just before the MENU (top left).

This should not be a problem, I have over 2000 albums displayed. Chrome, Chromium, Firefox all display the same. I suspect that there is an invalid character in the metadata of one of your songs, the latest versions of PHP and nginx are much stricter than their previous versions. Things like backspace and null characters are no longer valid as they can be used in malware. I will put a script together which you can use to check things out, give me a couple of days. In the mean time you could try checking out the metadata of the songs in the first directory not to be displayed (also check that the last displayed directory has all its files), or just try temporally removing these suspect songs from your library. If you modify metadata or remove the songs from your library then you need to run an 'Update MPD library' from the Sources UI before retesting.

janui

Stephane

Thank you for the tips Janui, the culprit is the last album displayed. Once deleted I see all my music collection.
Now I have to analyse the MP3 files.

janui

Hi Stephane,

Stephane wroteThank you for the tips Janui, the culprit is the last album displayed. Once deleted I see all my music collection.
Now I have to analyse the MP3 files.

I have been looking at the code, trying to work out a generic fix without imposing a performance overhead. If you plan to look at the metadata of the suspect file(s), could you check the occurrence of an entry which ends with 'OK' (for example Title: Are you OK) ?
There is a tool in RuneAudio which can be used from the CLI to print all the song metadata, try:

getid3-cli <full-path-and-filename-of-the-music-file>

or, for more information about the tool:

getid3-cli -h

janui

Hi Stephane,

Stephane wroteThank you for the tips Janui, the culprit is the last album displayed. Once deleted I see all my music collection.
Now I have to analyse the MP3 files.

I have posted a couple of fixes which should solve any problems with album metadata. If you could try retesting by replacing the unaltered music files it would be appreciated.

You can get the latest fixes by updating the player (with this update the patch level will remain at 4):
1. Go to the /dev menu - in the browser url enter http://<playername>.local/dev (e.g. http://runeaudio.local/dev).
2. Switch dev mode on - Scroll down to the 'Dev Mode' button and toggle it to ON, then click on the ‘Save Settings’ button below the toggle button.
3. When the UI comes back, click on the first ‘Save Settings’ button to activate the dev mode options.
4. Perform a git pull - Scroll down to the ‘Update RuneUI’ option and click on the ‘git pull’ button. The update will then be carried out and the player will reboot.

janui

Stephane

Anyway, the last directory scanned contains OK at the end so maybe the problem is here.
I removed it, did a DB rebuild, put it back and no problem with the DB rebuild.
Problem solved. Thank you.

PS: I will test your patch during the week.

« Previous Page Next Page »