Posts by Da Flex

Linux drivers for x86 and ARM (RPi) are different.

There is no HCL.

I can test my Behringer UMC22 on RPI, which is an "ASIO 4 All" (default ASIO) device. Stay tuned.

Then it's a driver issue on both devices. Linux driver support is incomplete. It seems like both systems have trouble to create a virtual mixer device, which controls the volume. Probably LE loads the same drivers, but doesn't accept main audio without such mixer.

Because drivers are part of the Linux kernel, we can't do anything. If you have another audio interface (default ASIO), try it. Or buy a HiFiBerry DAC. They are supported by LE.

Thanks. We will discuss that issue among the dev's.

Do you use RPi OS on the working device?

Can you name the used audio driver(s) of the working device?

LE provides the default ASIO driver, but it seems like your audio interface is using a custom ASIO driver from Digidesign.

Which hardware do you use?

In case you are using config files like remote.xml, then please post them.

Use the linked thread to ask questions. AmandaB was active during the last days, so I guess you can PM her.

OK, thanks for testing.

Disable Bluetooth on LE's settings, reboot and try again. (I don't think that it works, it's just to finish that approach)

My next theory is that Blaze TV tries to use volume control or mixing functions. That's not available for Chrome by default. To add those features, use this thread: Click!

The log is fine, and the error is visible:

Sep 06 17:24:28.548234 LibreELEC kernel: logitech-djreceiver 0003:046D:C534.0001: hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
Sep 06 17:24:28.548309 LibreELEC kernel: logitech-djreceiver 0003:046D:C534.0002: hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1
Sep 06 17:24:28.548383 LibreELEC kernel: logitech-djreceiver 0003:046D:C534.0002: device of type eQUAD nano Lite (0x0a) connected on slot 1
Sep 06 17:24:28.548459 LibreELEC kernel: logitech-djreceiver 0003:046D:C534.0002: device of type eQUAD nano Lite (0x0a) connected on slot 2
Sep 06 17:24:28.548468 LibreELEC kernel: input: Logitech Wireless Keyboard PID:4023 as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.1/0003:046D:C534.0002/0003:046D:4023.0003/input/input3
Sep 06 17:24:28.548545 LibreELEC kernel: logitech-hidpp-device 0003:046D:4023.0003: input,hidraw2: USB HID v1.11 Keyboard [Logitech Wireless Keyboard PID:4023] on usb-0000:00:14.0-5/input1:1
Sep 06 17:24:28.548554 LibreELEC kernel: input: Logitech Wireless Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-5/3-5:1.1/0003:046D:C534.0002/0003:046D:4055.0004/input/input4
Sep 06 17:24:28.548630 LibreELEC kernel: logitech-hidpp-device 0003:046D:4055.0004: input,hidraw3: USB HID v1.11 Mouse [Logitech Wireless Mouse] on usb-0000:00:14.0-5/input1:2

It seems like your wireless keyboard is wrongly detected as sound output device (logitech-djreceiver), which kills the default audio. Try with wired input devices to avoid this.

A kodi.log might help to translate the uh's and oh's.

1. activate debug logging at GUI
2. reboot
3. reproduce the error
4. login by SSH
5. run pastekodi
6. post the resulting link

Quote from dippes

What still doesn't work is that the Surroundbar switches on when a signal comes from the Raspi and switches off when the Raspi shuts down.

That's CEC-triggered, so have a look at LE's CEC adapter settings.

Probably the the Google server is occasionally too slow:

2021-09-02 21:47:30.195 T:2585756528   DEBUG: PLEX.subscribers: Sent server notification with parameters: {u'key': u'/library/metadata/74134', u'X-Plex-Token': u'REDACTED', u'X-Plex-Platform': u'Generic', u'X-Plex-Model': '4.19.127', u'X-Plex-Platform-Version': u'1.0.0', u'X-Plex-Client-Identifier': u'a997e10d-9004-4b09-a5ef-7f60825e31a0', u'ratingKey': 74134, u'playQueueItemID': 5706, u'X-Plex-Device': u'Linux', u'state': u'paused', u'X-Plex-Product': u'PlexKodiConnect', u'time': 719168, u'duration': 3271072, u'X-Plex-Device-Name': u'Kodi LibreELEC', u'X-Plex-Version': '2.14.0'} to https://REDACTED.a37ab5a2bb8e4499b9ec6ee03662dda2.plex.direct:32400/:/timeline
2021-09-02 21:47:30.605 T:2126115696 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
2021-09-02 21:47:32.270 T:2585756528 WARNING: Previous line repeats 3 times.

Our research says that the HiFiBerry DAC wasn't made for your board. It's not 100% pin compatible. So there is no software implementation, too.

Sorry, then I don't know the target file. Do you have a /flash/overlays file?

PS: Fortunately we have Radxa Zero user among our dev's. He'll have a look...

Add the line dtoverlay=hifiberry-dacplus to config.txt, reboot and select your new device on LE's audio settings.

Looks like that browser launcher add-on creates Chrome links without the parameters from default.py. Add volume control, and maybe that's the fix for those missing parameters.

Cool, then you can just copy mglae 's default.py to get audio. If you add volume control from my link, it should be perfect.

Maybe this thread can help to activate Chrome audio: Click!

Does that mean you have two Chrome browser add-ons installed? If yes, it should be possible to link to the one with audio.