Posts by FHoevi

Man, a couple of hours later I got it working with Raspberry OS bullseye instead of LE. It is a bit more of rather manual configuration work but it is definitely worth it. LE is history from my perspective now and for my personal use case of Kodi.

The key in the end after all necessary configuring was to start Kodi via kodi --pulse, that did the job of providing me the Pulseaudio sink for snapserver which I set up before and now anything is working again like charm.

And now I can do VNC again on that machine which is really nice as such.

If I deactivate Snapclient addon and start snapclient from command line I am told that while a song or radio station is playing via Snapserver sink (Stream) No chunks available, (Alsa) Failed to get chunk, (Controller) diff to server [ms]: -0.005 and finally (Alsa) No chunk received for 5000ms. Closing ALSA. Bah.

After looking into this thread on GitHub https://github.com/LibreELEC/LibreELEC.tv/issues/6309 I placed this into /storage/.config/autostart.sh:

#!/bin/sh
pactl load-module module-null-sink sink_name="just_a_sink_1"
pactl suspend-sink just_a_sink_1
pactl load-module module-udev-detect
pactl load-module module-allow-passthrough

Now, after activating Snapserver addon, I can select the PULSE: Snapserver sink for audio output via system settings.

So far, so good, but it still does not play any sound. One Snapclient (running on another RPi/Raspbian) is able to detect it and hook on. The other Snapclient which is running on the same machine as addon like Snapserver addon tells me via systemctl status service.snapclient that Started Snapclient. and Starting Raspberry Pi onboard audio. That's it. No usual additional message like Connected to 192.168.xx.xx. What else am I missing? Any hint would be highly appreciated.

All in all it is quite annoying and unnecessarily time-consuming (even -wasting) that LE developers decided to not properly support established addons like Snapserver/client any longer by switching off general pulseaudio support. Why? I think that these addons are extremely useful, unlike many others you could find in various repos.

In principle the Marantz should be able to work with bluetooth devices but the RPi4 is wired to the receiver with an HDMI cable, is properly recognized by it and properly plays audio via ALSA via the device as shown above.

Snapserver/Snapclient are the official addons.

With LibreELEC 9 on an RPi3 anything went fine and after switching on these addons I was able to select the Snapserver sink as audio output (being named "PULSE: Snapserver" or something like that) and the Snapclient running on the same machine was able to hook on and to play audio via a HifiBerry AMP2 HAT.

But now the RPi 4 should only play audio via HDMI.

Dear all,

maybe a problem someone else had already solved: Today I've been putting an RPi4 with LE 10.0.1 into action on a new Marantz NR1711 connected via HDMI0. With Snapclient deactivated on this machine, I can see via Settings -> System -> Audio -> Device the following entry which I picked: "ALSA-vc4-hdmi0 (vc4hdmi0), MJI marantz-AVR on HDMI". So far anything works like charm.

Since this device is in the living room and I do have an additional RPi3 in the kitchen/dining room running a Snapclient, I would like to play sound via Snapserver/Snapclient to both of these machines like I was able to do in the past with an older RPi3 in the living room working as a Snapserver/Snapclient as well. Bluetooth is enabled on the new RPi4. But as soon as I switch on Snapclient as well on the RPi4 I can only see two entries: "PULSE: Default, Bluetooth Audio (PULSEAUDIO)" and "PULSE: Null Output, Null Output (PULSEAUDIO)". I picked the first, but no audio at all. The RPi3 in the kitchen/dining room is able to connect to Snapserver which I can see via Snapcast app on my mobile, but on none of the two machines there is any audio output.

What exactly do I have to do to get this working? I've already spent a couple of hours but now my last idea faded away...

Thanks in advance for hints of any kind!

Dear all, after selecting a radio channel (via radio addon) a popping noise emerges before the radio station starts playing. This behavior is not present when just starting to play an .mp3 file from the SD card.

For audio playback I use a hifiberry Amp2 HAT which is working properly.

Does someone have an idea what the reason could be?

Good news, I just created a fresh install of LibreELEC 10.0.1 on the very same SD card and did the initial bootup with repartitioning of the SD card again. Then I added these two lines at the very end of /flash/config.txt:

dtparam=audio=on
dtoverlay=hifiberry-dacplus

and, tadaa, it's working again.

I even did 3 or 4 additional reboots to see if it "forgets" about my settings and now it seems it doesn't. Just listening to Jimi Hendrix being broadcasted over internet right now.

May it be a good idea to start all over again with a fresh install?

Thanks for your reply, I went ahead as instructed, but it still does not work at all. Omitting dtparam=audio=on leads to an audio output choice being greyed out. Reintroducing it shows the same behavior as above, Amp2 is not recognized by Kodi running on that machine running LibreELEC 10.0.1.

Nope, unfortunately doesn't work either. And I thought that an Amp2 board is essentially a DAC+ board, cf. Amp2 description.

I've just freshly set up a brandnew RPi4 with a Hifiberry Amp2 HAT as well as LibreELEC 10.0.1.

The problem now is that aplay --list-device recognizes this device as card 3 but I cannot choose it via System -> Audio -> Audio Device. There I can only choose from "ALSA:bcm2835 Headphones" or "PULSE:Default".

When trying to play an mp3 file I get the error "aplay: main:830: audio open error: No such device".

What's going wrong?

My /flash/config.txt contains these lines:

dtoverlay=hifiberry-dacplus
dtparam=audio=on
audio_pwm_mode=1

When switching off dtparam=audio=off the choosing option for audio device is greyed out. I already tried some things at this place but this is sort of driving me crazy.

Any hint would be highly appreciated.

Finally I got it working. My setup is like this: RPi4 with plain Raspbian Buster, USB cam attached in webcam mode, TVHeadend, Kodi with TVHeadend client addon. Via the TVHeadend GUI I defined a Mux as a ffmpeg pipe, for which options really need to be set carefully, for such an ffmpeg pipe it should also be possible to stream via command line for which the final pipe:1 should be exchanged with udp://localhost:port?pkt_size=1316. Without this the pipe doesn't work either.

My personal next step is to check whether a higher quality USB device attached to a USB 3.0 port of the RPi4 would lead to a similar result but with higher video quality than this simple webcam device.

I have set up an fresh RPi4 box running Raspbian Buster, installed Kodi as well as TVHeadend and now am experimenting with ffmpeg / vlc on that machine to stream as needed. Basic streams with that USB device do work (which I knew already before) but unfortunately so far not the one I need.

OK, either on my RPi3 running Raspbian with the USB webcam attached or on the RPi4 running LE 9.2.0 lsmod tells me that uvcvideo, videobuf2_v4l2, videobuf2_vmalloc, videodev are present, but only on the Raspbian I do see videobuf2_core, media in addition. I'm absolutely not familiar enough with this stuff to know which one of those is needed and which would be not.

On both machines the camera is present as /dev/video0. On the RPi3, either with vlc or v4l2 test utility I could view the stream coming from that camera.

E.g. insmod uvcvideo does not work on both machines.

Could one perhaps run a docker container under LE 9.2.0 containing anything needed for streaming the camera video? Unfortunately I'm not experienced enough with docker to know instantaneously what needs to be done.

Ah, no, what I've described above runs on an RPi running LE 9.2.0, which could be seen from this file location /storage/.kodi/addons/tools.ffmpeg-tools/bin/ffmpeg. That's the executable location for ffmpeg-tools addon.

The working config is actually an RPi3 but on an RPi4, which I still have to test under plain Raspbian, I hope there will be a quality improvement in speed (USB 3.0) and display quality (higher FPS).

How would I plug Raspbian USB camera drivers (which ones?) into LE without building it from source? I would really be glad if you could provide a hint.

It's an RPi3 running Raspbian Stretch and I'm planning to get t running on an RPi 4 with LE 9.2.0.

Thanks for your valuable hint, but I already have a similar working setup with a second Pi running plain Raspbian and streaming the USB input as is (copy) via cvlc with no further issues except for some inconvenient but constant lag. I have so far not been able to get the same up and running with ffmpeg although I tried really hard.