Posts by chewitt

Quote from jim_p

Can you please show me the AMLGX thread?

libreelec AMLGX - Google Suche

Kodi and its scrapers are designed to work with relatively standardised naming formats and the single best way to avoid naming issues is to use the right formats when you rip original media. You can start by sharing Kodi debug logs showing a library update/scrape so we can see what might be happening.

2023-01-07 11:55:21.524 T:852     debug <general>: OnPlayBackStarted: CApplication::OnPlayBackStarted
2023-01-07 11:55:21.525 T:1231    debug <general>: Thread BackgroundLoader start, auto delete: false
2023-01-07 11:55:21.531 T:1186    debug <general>: Loading settings for /media/ExternData/HDD/Filme/0-Test/4K/Dolby Vision FEL Test Samples/FEL_test_for_AVS.mkv

There is no support for Dolby Vision at this time, and that file doesn't appear to have other (normal HDR) tracks to fall back onto.

I'm not familiar with OpenATV .. so how does it save/record media and what format/location are subs being save to (or embedded in)? - And how are you playing back the recordings? (from a shared, IPTV list, etc.)?

#!/bin/bash
for i in `ls /dev/sd*`; do
  umount -f $i
  sleep 2
  udiskctl power-off --block-device $i
  sleep 2
done

^ That should unmount disks before powering down the drive. Also, you probably want to block the shutdown process while this is done so background the commands like autostart.sh

Quote from NO_ob

Hi i dont suppose you know of any newer more capable devices that can support 480i over component? I have tried searching but have not seen anything only devices supporting composite

Nope. I'd probably search on Amazon or eBay for some kind of component converter so you can use a modern source device.

If using personal keys they are accessible (readable, and thus copyable) by other users on the host. On a multi-user system that would be bad from a security perspective. LE only has one user (root) so it's not really the same security issue, but openvpn doesn't know that so it shows an error. The following command run over SSH probably fixes it:

chmod 600 /storage/.kodi/addons/service.vpn.manager/UserDefined/pass.txt

Then reboot and check again.

History shows that these changes are rarely permanent (where there's a will, there's a way) but since fixing depends on part-time developers giving time for free, things aren't always quick, esp. in early Jan when everyone heads back to their day jobs again. Keep a watch on the Kodi add-on support thread for more info.

Quote from gecko20016

I bought this tuner because it was recommended to work well with LE/Kodi. Can you suggest another model or manufacturer which works well in combination with a RPi4 ? I actually just want a setup that works reliably.

I've always recommended people run the server on a separate device to the player. This allows you to keep the server end on something that works; often a conventional distro where you can (re)compile the kernel with whatever set of shitty hacked-up drivers are needed to make the tuners work reliably, and then never change it while the no-longer-dependent-on-weird-kernels player device runs whatever latest LE/Kodi release you fancy. Linux DVB drivers suck

It looks like it got missed somewhere (we will investigate). You can always download 10.0.2 then do a manual update to 10.0.3 using the regular Generic .tar or .img.gz file (both contain KERNEL/SYSTEM which are the only things updated).

Textures13.db has become corrupted so a query to the DB fails; this is shown in the second and third errors. The DBus error is harmless.

Delete the Textures13.db file and the thumbnails folder. The DB will be recreated on Kodi restart, and thumbnails will be re-downloaded on access to GUI views that require artwork. If you don't remove the thumbs the cache references will be incorrect and you'll have blanks all over the GUI and you'll need to manually refresh everything to repopulate content.

The issue is probably add-on configuration not the content of the script or filesystem perms. You've probably configured a path to a folder not the script so it's trying to execute the folder (which isn't an executable object), hence the error.

To be clear: There is zero support for hyperion under GBM and that's unlikely to change. It's a fundamental "how GBM video pipeline's work" thing and not "development code is a bit rough" (there is no development code). Hence the previous suggestion to look at external grabbers if hyperion is a must-have for you.

I rebased my experimental AMLMX image (for Meson 8 devices) on LE master branch using Martin B's latest Linux 6.2-rc kernel yesterday. It's completely untested as I don't have a spare monitor to use at the moment, and prob. needs some manual fiddling to boot on some devices due to the prehistoric u-boot versions being used (UART cables may be required) but people are welcome to play:

https://chewitt.libreelec.tv/testing/LibreELEC-AMLMX.arm-10.88.0-box.img.gz

NB: I rebased the AMLMX image (for Meson 8 devices) on LE master branch using Martin B's latest Linux 6.2-rc kernel yesterday. It's untested as I don't have a spare monitor at the moment, and prob. needs some manual fiddling to boot on some devices due to the prehistoric u-boot versions being used, but people are welcome to play: https://chewitt.libreelec.tv/testing/LibreE…88.0-box.img.gz

Quote from jim_p

Thank you for all the clarifications. I want to try a le11 nightly image on s905 sometime (= when I will feel better and done with all the medical tests), so does it contain the device tree for my box (mxqpro4k 1gb)? Also, can it boot from a usb stick, because I have no sdcards handy?

There's no specific device tree but there are a number of other GXBB (S905) box devices present and one will probably be close enough to work. The upstream kernel doesn't require RAM specs to be coded in the device-tree which makes experiments a little easier. The box will always boot from emmc (hardcoded boot priorities) but you should be able to use the 'toothpick' method to trigger a recovery mode search for boot.scr and loading the upstream kernel from SD or USB.

If you have further Q's let's take them to a separate thread (or the AMLGX general thread) to keep this one on-topic.

Our settings add-on submits pastes anonymously, so there's no method to delete pastes. The site does purge pastes at some point, but there appears to be no formal policy on when (that we ever found). To ensure pastes are available for as long as possible (sounds like a reasonable goal) I'd expect purge to be FIFO and triggered on disk consumption not paste age.

_emanuel_ We inherit "keep-power-in-suspend;" from the w400 dtsi SDIO node so I'm not sure what's wrong or missing there. I do note that you've told me the sdio-pwrseq node is "GPIO_ACTIVE_LOW" whereas the vendor dts shows "GPIO_ACTIVE_HIGH" .. not sure if that's relevant.

Please also see if https://github.com/chewitt/linux/…e0c5cd69ba1c6f0 gives control over the red power LED, power button, and the Volume up/down/enter keys now?