What's your old username?
Posts by Da Flex
-
-
I think your PC has a hardware defect, which results in no audio:
CodeAug 27 07:07:41.913375 LibreELEC kernel: Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Aug 27 07:07:41.913479 LibreELEC kernel: ALSA device list: Aug 27 07:07:41.913584 LibreELEC kernel: No soundcards found. -
Don't have it. The only USB thing I had was a Logitech keyboard combo, with the USB dongle plugged in and the keyboard possibly was out of range (in another room).
This USB dongle works, and it's a different USB device:
CodeAug 27 07:07:41.909466 LibreELEC kernel: usb 6-2: new full-speed USB device number 2 using xhci_hcd Aug 27 07:07:41.910568 LibreELEC kernel: logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:01:00.0-2/input2 Aug 27 07:07:41.910732 LibreELEC kernel: input: Logitech K400 as /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb6/6-2/6-2:1.2/0003:046D:C52B.0003/0003:046D:400E.0004/input/input5 Aug 27 07:07:41.911690 LibreELEC kernel: logitech-hidpp-device 0003:046D:400E.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-0000:01:00.0-2/input2:1 Aug 27 07:07:41.911847 LibreELEC kernel: input: Logitech M570 as /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/usb6/6-2/6-2:1.2/0003:046D:C52B.0003/0003:046D:1028.0005/input/input6 Aug 27 07:07:41.912801 LibreELEC kernel: logitech-hidpp-device 0003:046D:1028.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech M570] on usb-0000:01:00.0-2/input2:2 -
-
We have similar case here: Click! In short: Very few TV's produce a very long CEC initialization time since LE 10+. No solution so far.
-
-
If you want to build your own LE, open a new thread at Development section. We also have basic Wiki instructions.
-
No idea, and nobody will do this for you. Easiest workaround: Install Raspberry Pi OS, and autostart Kodi on it. So you'll get JACK.
-
Hm, why would I need JACK if the thing works fine in ALSA?
The audio interface provides a ton of ins and out, without any standard, how to route them to a speaker system. I guess that's why the ALSA driver only provides an API for JACK. JACK is the expert for connection management.
"aplay" makes an assumption about connections, and that worked. Kodi wants to do it right, and asks the driver for input channels. The answer is NULL (see post #8), because JACK should answer instead.
My Behringer UMC22 has two ins, and two outs. In that case stereo routing is obvious, and that works for Kodi.
-
-
We support it, we just have other things to do sometimes.

-
Code
Display More2023-02-16 18:11:52.194 T:1375 info <general>: Device 1 2023-02-16 18:11:52.194 T:1375 info <general>: m_deviceName : @:CARD=UMC1820,DEV=0 2023-02-16 18:11:52.194 T:1375 info <general>: m_displayName : UMC1820 2023-02-16 18:11:52.194 T:1375 info <general>: m_displayNameExtra: Analog 2023-02-16 18:11:52.194 T:1375 info <general>: m_deviceType : AE_DEVTYPE_PCM 2023-02-16 18:11:52.194 T:1375 info <general>: m_channels : NULL 2023-02-16 18:11:52.194 T:1375 info <general>: m_sampleRates : 48000 2023-02-16 18:11:52.194 T:1375 info <general>: m_dataFormats : AE_FMT_S24NE3 2023-02-16 18:11:52.194 T:1375 info <general>: m_streamTypes : No passthrough capabilities 2023-02-16 18:11:52.194 T:1375 info <general>: Device 2 2023-02-16 18:11:52.194 T:1375 info <general>: m_deviceName : iec958:CARD=UMC1820,DEV=0 2023-02-16 18:11:52.194 T:1375 info <general>: m_displayName : UMC1820 2023-02-16 18:11:52.194 T:1375 info <general>: m_displayNameExtra: S/PDIF 2023-02-16 18:11:52.194 T:1375 info <general>: m_deviceType : AE_DEVTYPE_IEC958 2023-02-16 18:11:52.194 T:1375 info <general>: m_channels : NULL 2023-02-16 18:11:52.194 T:1375 info <general>: m_sampleRates : 44100,48000,88200,96000 2023-02-16 18:11:52.195 T:1375 info <general>: m_dataFormats : AE_FMT_RAW,AE_FMT_S24NE3 2023-02-16 18:11:52.195 T:1375 info <general>: m_streamTypes : STREAM_TYPE_AC3,STREAM_TYPE_DTSHD_CORE,STREAM_TYPE_DTS_1024,STREAM_TYPE_DTS_2048,STREAM_TYPE_DTS_512Channels are "NULL" for both output options. I think the "aplay" creates two stereo channels, but Kodi tries to use the channels, provided by the audio interface.
"Device 2" has passthrough capabilities. Please try the passthrough option in LE's audio settings.
-
Tomorrow. But probably everything is exactly the same.
chewitt has just informed me that he found his C2 board. So the log is not necessary anymore.
With that extra C2 board I'm optimistic.

-
Nothing changed in sound playing - "crack" then no data when passthough enabled, stereo when disabled.
Your version has broken my GPIO script started from autostart.sh (power on speakers when TV is on etc.), so I've turned back to official one.
Can you please go back to chewitt build, activate debug logging, replicate the issue, and post a link to the log?
I'm curious whether the missing data formats are available on that build:
- AE_FMT_S24NE3
- AE_FMT_S32NE
- AE_FMT_S16BE
- AE_FMT_U8
-
-
-
Behringer UMC22 (ASIO conform) works fine here (RPi3B+). Which driver do you use at your music production OS? I bet it's not ASIO.
-
I got feedback from a dev. It seems like the Samsung UE40H6470 has an issue. Read this:
Samsung TV not reacting on CEC command - Ubuntu Mate 16.04 Raspberry Pi 2 · Issue #366 · Pulse-Eight/libcecSetup: Samsung TV UE40H6470 Raspberry Pi 2 Model B connected via HDMI cable Installed libcec by the instructions from here: So a work-around that worked for me…github.com