RuneAudio 0.6-beta for most Raspberry Pi models

Beelzebassie

With the new version, it looks like empty folders on the drive are added to the database as ghost folders:

(Trying to open them will just lead back to the 'Browse your library'-screen.)

Attachments

: Untitled-1.png (233.7 KiB) Viewed 99796 times

janui

Hi Beelzebassie,

Beelzebassie wroteWith the new version, it looks like empty folders on the drive are added to the database as ghost folders...

Thanks for this. I had seen it myself and I am working on a fix. I think I can publish the change tomorrow.

janui

janui

Hi Beelzebassie (& Stephane),

Beelzebassie wroteWith the new version, it looks like empty folders on the drive are added to the database as ghost folders...

I have posted a fix for this.

You can get the latest fixes by updating the player (with this update the patch level will move to 5):
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

janui

Hi All,
Spotify have modified their authentication mechanism. This was causing spotifyd, which is our Spotify Connect client, to fail. For the technically minded there is an explanation here: https://github.com/Spotifyd/spotifyd/issues/1293
Spotify also modified their metadata structure, which was also causing some problems.
The advised fix for spotifyd authentication and some changes to the RuneAudio metadata routines have been implemented.

You can get the latest fixes by updating the player (with this update the patch level will move to 6):
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

Hi,

Today I tried to use my player as a Bluetooth receiver. Pairing done with pain, I can now connect and send a stream but I get no sound.
I can see the time growing but I get silence.
What am I doing wrong? When I play a file or radio stream I have sound.
I have a HifiBerry Digi+ card.

janui

Hi Stephane,

Stephane wroteToday I tried to use my player as a Bluetooth receiver. Pairing done with pain, I can now connect and send a stream but I get no sound.

Do you get a Bluetooth logo in the main player after connecting?
If you do, it should be connected and ready to play. Bluetooth receiver mode will time out after about 20 seconds if nothing is playing, if the Bluetooth logo remains after this time it is actively receiving the signal. The volume is controlled by your Bluetooth source, it will automatically be set low after a connection is made. Did you try turning up the volume on your smartphone or PC?
I have found that Bluetooth performs poorly when on-board Wi-Fi is active, its better to switch Wi-Fi off.
If you still have problems please run the following from the CLI after connecting and post the output:

grep -iE 'blue|bt' /boot/firmware/config.txt
systemctl status blue* bt* | grep -iE 'loaded|active'
journalctl | grep -iE 'blue|bt' | grep -iE 'fail|error|warn'
redis-cli hgetall bluetooth

In the meantime I will check to see if any Bluetooth improvements have been included in our development code.
janui

Stephane

When the stream is "playing", the local volume is set at 100 and the phone volume is at max
Here are the results of the commands:

grep -iE 'blue|bt' /boot/firmware/config.txt
#   krnbt                   Set to "on" to enable autoprobing of Bluetooth
#                           driver without need of hciattach/btattach
#   krnbt_baudrate          Set the baudrate of the PL011 UART when used
#                           with krnbt=on
##  Bluetooth settings ##
#   Bluetooth on/off
#dtoverlay=disable-bt
#   Autoprobing onboard Bluetooth if available
dtparam=krnbt=on

redis-cli hgetall bluetooth
 1) "quality"
 2) "default"
 3) "local_volume_control"
 4) "0"
 5) "FastStream_codec"
 6) "0"
 7) "def_volume_in"
 8) "-1"
 9) "quality_options"
10) "[\"default\",\"all_better\",\"all_best\",\"SBC_better\",\"SBC_best\",\"MP3_better\",\"MP3_best\",\"AAC_best_VBR\",\"AAC_best\"]"
11) "aptX_HD_codec"
12) "0"
13) "native_volume_control"
14) "a"
15) "LDAC_codec"
16) "0"
17) "timeout"
18) "20"
19) "remember_last_volume"
20) "0"
21) "samplerate"
22) "44100"
23) "source_dev"
24) "88:46:04:F3:E9:87"
25) "initialising"
26) "0"
27) "IO_toggle"
28) "input"

 systemctl status blue* bt* | grep -iE 'loaded|active'
     Loaded: loaded (/etc/systemd/system/bluealsa-aplay.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-10-15 18:42:33 CEST; 3min 55s ago
     Loaded: loaded (/etc/systemd/system/bt_mon_switch.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2024-10-13 17:35:46 CEST; 2 days ago
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2024-10-13 17:35:46 CEST; 2 days ago
     Loaded: loaded (/lib/systemd/system/bluetooth.target; static)
     Active: active since Sun 2024-10-13 15:42:52 CEST; 2 days ago
     Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2024-10-13 17:35:46 CEST; 2 days ago

 journalctl | grep -iE 'blue|bt' | grep -iE 'fail|error|warn'
Oct 15 18:42:28 garage systemd[1]: bluealsa-aplay.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 18:42:28 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:29 garage systemd[1]: bluealsa-aplay.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 18:42:29 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:30 garage systemd[1]: bluealsa-aplay.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 18:42:30 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:31 garage systemd[1]: bluealsa-aplay.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 18:42:31 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:32 garage systemd[1]: bluealsa-aplay.service: Main process exited, code=exited, status=1/FAILURE
Oct 15 18:42:32 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:33 garage systemd[1]: bluealsa-aplay.service: Failed with result 'exit-code'.
Oct 15 18:42:33 garage systemd[1]: Failed to start BlueALSA player service.
Oct 15 18:42:33 garage systemd[1]: Dependency failed for Bluetooth connection agent service.
Oct 15 18:42:33 garage systemd[1]: bluetooth-agent.service: Job bluetooth-agent.service/start failed with result 'dependency'.
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)
Oct 15 18:43:02 garage kernel: Bluetooth: hci0: Frame reassembly failed (-84)

Stephane

I found a bug (or at least a weird behaviour): when the bluetooth stream stops playing and the system returns to local playing then the online volume stops working on the touch screen (it works fine on the phone). I have to go to the MPD setup to enable the knob again.

janui

Hi Stephane,

Stephane wrote...When the stream is "playing", the local volume is set at 100 and the phone volume is at max...

Thanks for the information, I see that the bluealsa-aplay.service is failing. This may be related to this (still open) issue: https://github.com/raspberrypi/firmware/issues/1150
There is also a fix described, but I would prefer to try it myself before recommending to use it. I need some more information about your setup in order to try to recreate the problem. Could you post the lines from the debug after:
'###### System info ######'
To:
'###### CPU temperature, throttling & power supply voltage status ######'.

Then something to try... From the CLI run:

/srv/http/command/bt_off.sh
/srv/http/command/bt_on.sh
systemctl status bluealsa

The last command should report the status of bluealsa (running or failed). If running, try reconnecting. Then check the status of bluealsa again:

systemctl status bluealsa

Try playing something if bluealsa is still running. Then check the status of bluealsa again.
If not, navigate to the Bluetooth UI and change the 'Bluetooth Input/Output Audio Sample Rate', there are only two options. Then retry:

/srv/http/command/bt_off.sh
/srv/http/command/bt_on.sh
systemctl status bluealsa

If the last command reports that bluealsa is playing try again to connect and play. This should demonstrate when bluealsa fails: on startup, connection or start play. And that the problem is not related to a specific sample rate.

janui

janui

Hi Stephane,

Stephane wroteI found a bug (or at least a weird behaviour): when the bluetooth stream stops playing and the system returns to local playing then the online volume stops working on the touch screen (it works fine on the phone). I have to go to the MPD setup to enable the knob again.

Thanks for this. It's expected behaviour when bluealsa fails. I think it will be fine when the bluealsa problem is fixed, but I will check it.

janui

« Previous Page