Posts by Da Flex

What a crazy fix!

PS: Conclusion: HiFiBerry doesn't test the products they ship. That's bad.

There is a setting at /storage/.kodi/userdata/guisettings.xml:

<setting id="audiooutput.volumesteps" default="true">20</setting>

Reduce 20.

If you really can't get any audio from the card, blame HiFiBerry.They shipped the wrong device, so demand the right one and try again.

PS: If you decide to buy an RPi camera port device, then the add-on "Raspberry Pi Tools" should provide the driver for LE.

You can play around with audio volume / mute by directly editing guisettings.xml (top and bottom of the file).

PS: A little thing you should think about: Usually companies don't upgrade an ordered product without good reason. Maybe they shipped a Pro version, because they know the COAX output is broken, and they hope you only need TOSLINK.

dtoverlay=hifiberry-digi is the right overlay for your device, there is no need for a "Pro" option. Please do a research whether you can use TOSLINK and COAX at the same time (the HiFiBerry company should know). Maybe you can only switch between those two output options.

Have you done a forum search about the projector topic? We already have threads like this.

Quote from FHoevi

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.

Good choice. So it's no LE question anymore. An RPi camera port device will deliver best streaming data to work with. So don't fall in love with your USB camera too much.

Quote from bobacisko

Can you please validate if this command correct/sufficient to enforce full HD?

echo 1080p60hz > /storage/.kodi/userdata/disp_cap | systemctl restart kodi

I only have an RPi, so I don't have a disp_cap file. Maybe blueribb can do the test, because he is an Intel NUC owner.

Quote from bobacisko

LibreELEC:~ # tail /sys/class/drm/*/status

==> /sys/class/drm/card0-DP-1/status <==

connected

==> /sys/class/drm/card0-DP-2/status <==

disconnected

==> /sys/class/drm/card0-HDMI-A-1/status <==

disconnected

==> /sys/class/drm/card0-HDMI-A-2/status <==

disconnected

Display More

Maybe you have some special setting at your TV, and you can switch between HDMI and Display Port mode.

Quote from FHoevi

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.

I'm not familiar with camera drivers on Linux. On a working Linux (like Raspbian) you could use the lsmod command to list all loaded driver modules. Then identify the modules for your camera. On a non-working Linux (like LE) you can try to load those driver modules by insmod <module_name>. If you get a "not found" error while trying to load the modules, then my theory will be proofed.

Unfortunately there is no way to install new drivers modules on LE without compiling from source. Maybe driver modules for the RPi camera port are available by default on LE.

Quote from andz

Have removed almost everything and put tvservice -p im autostart.sh and it keeps working at 1080p.

If it's solved now, you can mark the thread that way.

Quote from bobacisko

Thank you Da Flex, considering cables as potential cause as well but got HDMI 1.4 (=high speed standard) gold cable.

You need an HDMI 2.0 or 2.1 cable to use 4K resolution.

Quote from milan0

I added this line to the route table, but i don`t know how to remove it.

Easy to find answer.

Yes, LE has no package manager, just add-ons.

If you don't find a fitting add-on, install Java or Docker apps on LE. Use our forum search function for details.

Thanks for the info, the RPi 4B is faster than I thought then. Check the loaded camera driver modules on Raspbian, they are probably not available on LE.

Did you already tried config.txt to enforce an HDMI mode for your preferred resolution?

Background: It's possible that your /dev/sdb partition will stay mounted after first use, so it's unable to spin-down from that time on.

Check this theory by using the mount command before and after first partition usage. It shows all mounted partitions.

Please try the partition version anyway. It's about what the system marks as "busy", not what we physicaly see busy.