If videos are on the USB drive the speed of the SD card is rather irrelevant. Just use it.
Posts by chewitt
-
-
Support for 23.976Hz modes is determined by the EDID data presented by the TV/Monitor on the HDMI connection. Most (but not all) TV's will have a 23.976 mode. Most better monitors support it too. Older TVs may not, and cheap monitors often support only 50/60Hz modes.
-
If the remote doesn't work please follow this: https://wiki.libreelec.tv/configuration/…ration-advanced to capture the keys so we can compare to what I've set in the preconfigured keymap.
-
Testing with no dtb name or dtb's for SoC types that don't match yours (S812 aka meson8m2) is pointless. I would not expect them to work so we can ignore those non-results. And if you're going to report an issue (on the correct SoC type) as a minimum you need to share the URL generated by "pastekodi" after accessing via SSH, or dump the systemd journal and pastebin it somewhere.
-
fab233 add "video=HDMI-A-1:1920x1080M@60" to boot params in syslinux.cfg; this should force Linux to 1080p@60 instead of the 4K modes which either driver or TV seems to dislike. Kodi GUI will run best @ 1080p with 4K modes only used for video playback via whitelist and adjust-refresh set to start/stop.
-
As documented in the release notes that nobody reads: Users with an nVidia GPU will need to use the Generic Legacy image as the GBM/V4L2 graphics stack that is now used in the Generic image does not support nVidia cards.
-
Pastebin a debug log somewhere please.
-
What's the actual CPU temp on the box? .. is it running at 85ºC or did the kernel evolve and finally gain support for reporting CPU thermals resulting in some overlooked placeholder value triggering warnings at 50ºC?
-
^ Same SoC so same answer, there is only minor progress since December. Ask again in six months (or look for a different board).
-
Kodi has logic for handling fall-back to software decoding with DRMPRIME hardware decoding enabled. As no hardware supports 10-bit H264 hardware decoding it will always fall-back to software. This normally gives bad results because software decoding 10-bit H264 requires lots of CPU and few users are using high(er)-end Intel chips that are capable of the task.
Subtitles support selection preferences for default selection when there's a collection of subs to choose from, but there's currently no way to say "if english keep subs off, if french turn subs on" .. the on/off decision is always manual and user determined. If you want that to change you need to make a request in the Kodi forum feature-requests section. If you want to submit something to the Kodi main branch it needs to be code because Team Kodi doesn't accept requests via GitHub issues - it's a bug tracker so if you make one it will be closed.
-
https://wiki.libreelec.tv/configuration/edid has instructions on configuring an edid.bin file so Kodi sees the TV as always connected. The wiki needs updating to reflect that the Intel instructions apply to all devices using the kernel DRM architecture; including Amlogic (and Allwinner, Rockchip) boards.
https://chewitt.libreelec.tv/edid.bin was dumped from older (2012-ish?) Samsung 8-series TV, and contains 23.976/24/25/29.97/30/50/59.94/60 modes. You might not be able to use all (or any) of them, but it might work and you can disable the ones that don't in the whitelist.
https://wiki.libreelec.tv/configuration/…ration-advanced has instructions (also needing update) on capturing and creating a custom IR config. The bit that needs updating is that the config file format has changed to "toml" .. but if you look at the wiki instructions and compare to the toml files in /usr/lib/udev/rc_keymaps/ the new format is pretty simple to crib.
-
Kodi only reads mode data once at startup so swaping cables after boot will not change anything. And if the 4K 50/60 modes configured in the mode whitelist are not available (due to 1.4 cables) they will be silently dropped; requiring you to edit the list and reinstate them if you reboot with higher spec 2.0 cables attached again. NB: Lots of users think they have high-speed cables and will swear on their mothers life that their cables are not the issue; but issues often magically go away when a new certified cable is purchased
-
DV files won't play right even if the projector does support HDR. DV media is not supported.
-
Code
video=HDMI-A-1:1920x1080M@60^ remove the current video= string and use that. What happens?
-
sky42 shares images that have all the RAID modules/tools and encrypted disk stuff included. Last time I looked there were ~20 active users of those images and it's been fairly consistent around that number for a few years; so I think we're justified in continuing to release without features that aren't in general demand.
-
You can enable "adjust refresh" in Kodi player settings, but the system will need to have a native 23.976 mode or you'll need to use an edid.bin file to fake a connected TV with more modes. The old method you found is not possible in the modern kernel used now.
Please run "pastekodi" and "modetest | paste" and share the URLs so we can see what modes and timings exist.
-
I’ve done a search and found out that this is a thing with LE, but I’ve never experienced this with Kodi before. Is this a known issue?
I've never seen issues (or similar reports) with H264, so
-
Is the box connected via Ethernet or WiFi? .. some wireless routers isolate devices on the wireless network so e.g. WLAN connected iPad will not be able to reach WLAN connected LE device. Connecting the box to Ethernet would fix that. Or it might be the app having an issue with the SSH certificate algorithm being used (although unlikely I think).
Pls create an SD from https://chewitt.libreelec.tv/testing/LibreE….0.2-box.img.gz and set meson-gxl-s905x-nexbox-a95x.dtb in uEnv.ini. I doubt it will help the SSH issue but hopefully HDMI audio and the IR remote should work out-of-box now? If you're able to access the box via SSH please run "pastekodi" and share the log file URL. The dtb could use some other cleanup/changes but one step at a time.
