Posts by chewitt

4K@60/59.94 with a high-bitrate audio stream might be pushing the limits I guess (not that I'm knowlegeable on what the limits are). Do you have "certified" HDMI cables between the RPi4 and AVR? .. the total HDMI bandwidth required for this will be above average and cable quality does become a factor at some point.

Do you have the correct number of speakers for Atmos? (5.1.2, 5.1.4, 7.1.2, 7.1.4)

Kodi supports pass-through of Atmos/DD+/TrueHD audio on hardware that supports the respective formats. Not all hardware does.

What happens if you select the 5.1 audio surround stream instead of the TrueHD 7.1 stream?

I have a hunch that the {special} filename is incorrect as normally the filename should match the full path to the mount. However I have no clue how to represent a path with folders that start with or contain periods and underscores. Create a more simple path like /storage/xmltv to mount to, and name the file storage-xmltv.mount. If that works you proved the theory and can hit Google for documentation.

cp /usr/lib/udev/rules.d/40-modeswitch.rules /storage/.config/udev.rules.d/40-modeswitch.rules

^ Copy the existing rules file to the udev.rules.d overlay directory and edit (append/add) another rules section with the device IDs for the chip. If you installed usb_modeswitch from one of our tools add-ons it's normally usable without the other files or just have udev eject the /dev/sr0 device like the existing other devices in the rule flle - which works with most WLAN devices.

ConnMan allows you to set persistent preferences for interface type, e.g. prefer Ethernet over WLAN but not which interface; largely because in Linux the interface identifier is dynamic and determined by probe order. It is also possible to reorder the priority of interfaces (move them once probed). So if the devices consistently probe to the same identifiers you can use systemd.d to run a shell script late in the boot process (after network is up, but before Kodi starts) to detect if /dev/wlan1 is present, and if yes, run a connmanctl command to order wlan1 above wlan0 in the interface list. It's fiddly to create, but do-able and normally reliable once done. You'll find some prior art for the reordering commands in wireguard VPN threads.

I can tell from the original report that Kodi is falling back to CPU decoding; hence the suggestion to try a newer kernel which might have more functionality added (as upstreaming codecs takes time). If the situation didn't improve you won't see magic happen - no codec driver means Kodi will CPU decode and this probably requires a high-end i7 or i9 chip to work. If the HEVC driver exists under Windows and you need to play 4K HEVC media .. use Windows.

Download, Yes. Install and run, No.

I'd start with a current nightly image and see if the issue is resolved with newer kernel (and its newer drivers).

If the devices are hidden behind NAT you configured the APX incorrectly. If you configure it as a wireless bridge, everything will be visible.

kszaq retired a long time ago now. Have a look at the image dtech has been releasing (sticky thread).

LMGTFY - Let Me Google That For You

echo "options mxl58x mode=2" > /storage/.config/modprobe.d/mxl58x.conf
reboot

^ this should work

If it's crashing with the default skin then the issue is likely an add-on that's installed. The main approach to that is either disabling all add-ons and then (assuming that stops the crashing) you start reenabling them until you find the culprit; or you stop Kodi and move the current install out of the way (preserving it) so you restart with a clean setup. Now you can stop/copy/restart and progressively copy back stuff from the working install (or reinstall things) until you find the crashy thing. I personally prefer the clean-start approach as that generally exorcises or spring-cleans a pile of other Kodi related cruft that's accumulated over time too.

Find a spare SD card and see what happens when you clean-boot a fresh image. If it boots fine you narrowed the problem to software.

YouTube/Tubed require an API key. Follow guides in the Kodi forum support threads. It's not simple, but once done it's done.

From the description; the .deb package install requires sudo (root/admin) rights to be installed. It's not a backdoor password, but since it can be used to gain root rights on the host it's a credential to protect - hence the security best-practice advice of not using the same password for the admin user in TVH.