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.)
by Beelzebassie » 16 Jul 2024, 10:26
by janui » 17 Jul 2024, 09:53
Thanks for this. I had seen it myself and I am working on a fix. I think I can publish the change tomorrow.Beelzebassie wrote:With the new version, it looks like empty folders on the drive are added to the database as ghost folders...
by janui » 18 Jul 2024, 09:27
I have posted a fix for this.Beelzebassie wrote:With the new version, it looks like empty folders on the drive are added to the database as ghost folders...
by janui » 19 Aug 2024, 15:48
by Stephane » 13 Oct 2024, 16:41
by janui » 14 Oct 2024, 14:30
Do you get a Bluetooth logo in the main player after connecting?Stephane wrote: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.
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
by Stephane » 15 Oct 2024, 17:51
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)
by Stephane » 16 Oct 2024, 10:29
by janui » Yesterday, 15:26
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/1150Stephane wrote:...When the stream is "playing", the local volume is set at 100 and the phone volume is at max...
/srv/http/command/bt_off.sh
/srv/http/command/bt_on.sh
systemctl status bluealsa
systemctl status bluealsa
/srv/http/command/bt_off.sh
/srv/http/command/bt_on.sh
systemctl status bluealsa
by janui » Yesterday, 15:33
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.Stephane wrote: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.
support RuneAudio