Upcoming moOde 9.0.0 (Bookworm)

[TheOldPresbyope]

@Tim Curtis 

So I flashed a new copy of ~pre3, then overwrote alsa.php and worker.php with the latest in the repo as of last night.

I still got the non-zero output from my USB-BT Adapter (I keep calling it that but it's just a USB DAC, functionally) on first play. If I get a chance I'll go through the whole rigamarole again later and check this behavior with the I2S DAC selected instead.

It sounds as if you can still smile when you say "a nice challenge". It's all an uphill slog for me these days, but then I'm old enough that I have trouble remembering where I last laid down my glasses, let alone why some function is in the codebase.

Regards,
Kent

[Tim Curtis]

I was working on some Bluetooth improvements and noticed that bluetooth always starts during boot even though its systemd unit (bluetooth.service) is set to "disabled" and it's not turned on in Renderer Config.

I poked around a bit and was not able to find what is starting Bluetooth.

ETA: Here's what shows up in dmesg log

Code:

pi@moode9:~ $ dmesg | grep Bluetooth
[    4.647910] Bluetooth: Core ver 2.22
[    4.647946] Bluetooth: HCI device and connection manager initialized
[    4.647952] Bluetooth: HCI socket layer initialized
[    4.647955] Bluetooth: L2CAP socket layer initialized
[    4.647960] Bluetooth: SCO socket layer initialized
[    4.665974] Bluetooth: HCI UART driver ver 2.3
[    4.665981] Bluetooth: HCI UART protocol H4 registered
[    4.666022] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    4.672749] Bluetooth: HCI UART protocol Broadcom registered
[    5.029576] Bluetooth: hci0: BCM: chip id 107
[    5.029801] Bluetooth: hci0: BCM: features 0x2f
[    5.030954] Bluetooth: hci0: BCM4345C0
[    5.030962] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[    5.036236] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.raspberrypi,5-model-b.hcd' Patch
[    5.480236] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.480245] Bluetooth: BNEP filters: protocol multicast
[    5.480252] Bluetooth: BNEP socket layer initialized
[    5.774026] Bluetooth: hci0: BCM: features 0x2f
[    5.775430] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
[    5.775436] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
[    5.775746] Bluetooth: hci0: BCM: Using default device address (43:45:c0:00:1f:ac)
[    5.797339] Bluetooth: MGMT ver 1.22

[TheOldPresbyope]

I was working on some Bluetooth improvements and noticed that bluetooth always starts during boot even though its systemd unit (bluetooth.service) is set to "disabled" and it's not turned on in Renderer Config.

I poked around a bit and was not able to find what is starting Bluetooth.

ETA: Here's what shows up in dmesg log

Code:

pi@moode9:~ $ dmesg | grep Bluetooth
[    4.647910] Bluetooth: Core ver 2.22
[    4.647946] Bluetooth: HCI device and connection manager initialized
[    4.647952] Bluetooth: HCI socket layer initialized
[    4.647955] Bluetooth: L2CAP socket layer initialized
[    4.647960] Bluetooth: SCO socket layer initialized
[    4.665974] Bluetooth: HCI UART driver ver 2.3
[    4.665981] Bluetooth: HCI UART protocol H4 registered
[    4.666022] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    4.672749] Bluetooth: HCI UART protocol Broadcom registered
[    5.029576] Bluetooth: hci0: BCM: chip id 107
[    5.029801] Bluetooth: hci0: BCM: features 0x2f
[    5.030954] Bluetooth: hci0: BCM4345C0
[    5.030962] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0000
[    5.036236] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.raspberrypi,5-model-b.hcd' Patch
[    5.480236] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.480245] Bluetooth: BNEP filters: protocol multicast
[    5.480252] Bluetooth: BNEP socket layer initialized
[    5.774026] Bluetooth: hci0: BCM: features 0x2f
[    5.775430] Bluetooth: hci0: BCM43455 37.4MHz Raspberry Pi 3+-0190
[    5.775436] Bluetooth: hci0: BCM4345C0 (003.001.025) build 0382
[    5.775746] Bluetooth: hci0: BCM: Using default device address (43:45:c0:00:1f:ac)
[    5.797339] Bluetooth: MGMT ver 1.22

I see what you mean. On the system I just spun up (and mentioned in my last post) I see

Code:

pi@m9pre3pull:~ $ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
    Loaded: loaded (/lib/systemd/system/bluetooth.service; disabled; preset: enabled)
    Active: active (running) since Fri 2024-04-12 07:43:56 EDT; 3h 26min ago
      Docs: man:bluetoothd(8)
  Main PID: 617 (bluetoothd)
    Status: "Running"
     Tasks: 1 (limit: 1596)
       CPU: 121ms
    CGroup: /system.slice/bluetooth.service
            └─617 /usr/libexec/bluetooth/bluetoothd

...

Ah, but I also see bluealsa.service is enabled and running

Code:

pi@m9pre3pull:~ $ systemctl status bluealsa.service
● bluealsa.service - Bluealsa proxy
    Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; preset: enabled)
    Active: active (running) since Fri 2024-04-12 11:24:05 EDT; 31min ago
  Main PID: 627 (bluealsa)
     Tasks: 3 (limit: 1596)
       CPU: 36ms
    CGroup: /system.slice/bluealsa.service
            └─627 /usr/bin/bluealsa -p a2dp-source -p a2dp-sink -c aptx -c aptx-hd -c ldac --sbc-quality=xq+

...

and bluetooth.service is required by bluealsa.service so maybe that's why bluetooth.service is running?

Code:

pi@m9pre3pull:~ $ systemctl cat bluealsa.service
# /etc/systemd/system/bluealsa.service
[Unit]
Description=Bluealsa proxy
Requires=bluetooth.service
After=bluetooth.service

[Service]
Type=simple
ExecStart=/usr/bin/bluealsa -p a2dp-source -p a2dp-sink -c aptx -c aptx-hd -c ldac --sbc-quality=xq+

[Install]
WantedBy=multi-user.target

Mind you, I'm just a dilettante with systemd and dbus related-stuff.

Regards,
Kent

[Tim Curtis]

Good find. bluealsa need to be disabled.

[Tim Curtis]

Just a heads up that I'm planning to upload ~pre4 soon which will contain a new Bluetooth implementation based on @jakste Thread https://moodeaudio.org/forum/showthread....5#pid53465 and the referenced article https://forums.raspberrypi.com/viewtopic.php?t=235519 in the Pi forums. It involves replacing the existing blu_agent.py with the bt-agent program from the blue-tools package.

[Tim Curtis]

Here is a screen shot.

Currently anonymous pair/connect works as usual but PIN code pair/connect does not. I may not have the knowledge to get this part working and if it's still broken when I post ~pre4 maybe someone with Bluetooth expertise can help out. I'll list all the parts involved.

   

There are also two new volume options, one for ALSA and another for CamillaDSP. This is to control overall volume output.

[the_bertrum]

I assume the volume options are relevant only for "outgoing" connections (to headphones et al)?

[Tim Curtis]

I assume the volume options are relevant only for "outgoing" connections (to headphones et al)?

Actually just the opposite. They only affect moode output volume for incoming connections like a smartphone. Its meant to address the issue where for some reason (certain) Bluetooth clients seem to have a very steep volume curve whereby even one volume bump above zero is pretty loud.

[the_bertrum]

I assume the volume options are relevant only for "outgoing" connections (to headphones et al)?

Actually just the opposite. They only affect moode output volume for incoming connections like a smartphone. Its meant to address the issue where for some reason (certain) Bluetooth clients seem to have a very steep volume curve whereby even one volume bump above zero is pretty loud.

Right, I get it.  I'll need to have that at 100% then

[popeye65]

Hi,
small status report, I'm trying image_2024-04-10-moode-r900~pre3-arm64-lite on a Pi4, inside the Stealth V3 enclosure, with the Waveshare 7.9 display. With the appropriate config.txt content (which I will document in a later phase, when everything works), it boots, display the console, starts the local display and even answers to the touch screen beautifully. After setting the appropriate USB output, music plays (some radio). Amazing performance !

Now on issues:

The first issue, I can't start squeezelite renderer. It says started and stopped if I toggle the switch, but there is no process running, and no player appearing in LMS. In the moode.log, I see only `20240418 212416 worker: Job slsvc` when toggling the switch. Specifying the IP of LMS on the option doesn't help. I think it doesn't want to start at all.

Other issue : the "sys-config.php" page, appears fine the first time, but then answer incorrectly, and after a save, is blank. I have to start a new private browser page to continue using it, and my changes aren't saved. I wanted to turn on debugging, but I can't

hints welcome