Posts by chewitt

Quote from 0ldn3rd

I read in a news, that with Kodi19 and LE10 it will be possibel to get HDR....

On RPi4 and some other ARM devices which now support it. The x86 world is still a bit behind..

Pi Foundation folks are currently focussed on finishing the 10/12-bit video and 4K60 work. This will firm up the kernel/DRM side of the puzzle and allow some ffmpeg cleanup, which needs to happen before more complication (with deinterlace) is added. It's vacation season so all of the above is running about 3/4 speed right now. IMHO the current software deinterlace capability is quite usable (not perfect, but usable).

Content status tracking is done in Library based views (Movies/TV Shows) using content scraped into the Library. Or are you using the non-Library "Videos" view?

Quote from Niceguy

So this is Version is 9.97.1 Beta and not 10.0 Stable ?

RC = Release Candidate. More stable than a beta, but not the 10.0.0 release either (hence not called beta, or stable). Generic is pretty stable though. The remaining WIP bits are related to other platforms (mostly RPi4).

Run "journalctl | paste" and "pastekodi" after booting (and doing whatever is needed with network config) and share the two URLs that are generated. Then reboot and repeat the process, share the URLs again.

Nothing has been explicitly done to fix it, so I doubt it.

Wrappers aren't the right approach because the level of optimisation required for functional 4K pipelines on ARM hardware is high and you'll always end up needing to write efficient native drivers. You can bodge 1080p, but RAM speed and bandwidth become big factors with 4K. The tertiary challenge with V4L2 is that it's all super new and still in a lot of flux; we're still some way from making a serious effort to upstream our current working code to ffmpeg because lots of things are still being experimented on.

Quote from dhymi

Eu gostaria de saber também, no meu caso quero modificar o libreelec pra no lugar de rodar o kodi, rodar outro apk na hora que ligar, isso é possível?

Not possible. Não é possivel.

Practically all 4K content is HEVC (or VP9) encoded and nVidia never added support for either to their Linux drivers, hence the CPU is working overtime to play back 4K content. AMD and Intel have both invested time/effort in their drivers (and both use Kodi as a reference media app) so support is generally good and the main Linux challenge is new chips needing bleeding edge kernels that take a while to stabilise. nVidia continues to be a Linux pariah and future use in LE once we drop X11 support (sooner than later) is not guaranteed. Stats show the number of nVidia users continues to decline and most of them have older cards. These days most people have moved from homebrew boxes to NUC-like devices with a server/NAS for media in the network. Most of those devices are fanless (or quiet enough) and the client/server setup makes it easier and cheaper to upgrade the client device as media tastes evolve over time. Perhaps convert the current box to a server and partner it with an RPi4?

Please retest with a current LE10 nightly. Aside from minor tinkering with widevine support LE9.2 is no longer in development.

Clean install the current nightly from Index of / with no 4K60 configuration and prove things work normally and the RPi4 can see 4K (up to 30) modes - right now it is only seeing 1080p. That suggests bad or inadequate/uncertified HDMI cables (or broken EDID from the TV) or using the wrong HDMI port on the TV. Note that LE defaults to 1080@60 GUI even if the TV supports 4K playback. Rendering the GUI is about CPU performance, it is not hardware accelerated like 4K video, so the GUI will be noticeably slower if you force it to run at 4K. You can still whitelist 4K modes for playback and Kodi will switch to 4K when required. Also note that practically all 4K media is [email protected]/25/30 so in most cases, users do not require 4K60 to be forced.

If vendor boot firmware is present on emmc the box will always boot from it, so to freely experiment with other boot firmware(s) from an SD card or USB stick you will need to completely erase emmc. If the goal is to run the dtech image you should focus on finding a replcement "vendor" u-boot. NB: the u-boot.bin.sd.bin files in my share (in case that's what you found) are mainline u-boot variants and might boot the box but will not greatly help in any mission involving 3.14 vendor kernels. Start by sharing the "strange characters and letters/numbers" seen via UART via pastebin so people can understand what the current boot-state of the device is.

I'm not sure what the issue is (no logs are provided which might give clues) but using autostart.sh should never be preferred over system.d, as the later provides better control over when things are executed.

If you set min SMBv1 and max SMBv3 in Kodi it will default to SMBv2 and you won't connect. Forcing requires min/max SMBv1 to be set.

GitHub shows no commit activity from Thoradia since Jan this year. We have zero contact with him/her/they outside of this forum so we have no way to enquire about future plans. at this point people should assume that this thread (and the repo) is dead.

Quote from dtech

Okay, so far only three people do not understand sarcasm.

Your audience is multinational

For the record .. on LE 9.2.6 on Intel HW we are still rendering via Xorg which means GL not GLES surface (GLES will be in the future once we dump Xorg) but crap add-ons are still crap add-ons

Quote from jimjack12

Now I ask you: is it possible to somehow install LE directly on the nand via aml usb burning, or via usb / sd

Amlogic Burning Tool = No (our .img is not the format used by that tool). USB/SD = You can boot from SD/USB but we provide no tools for internal install (the box has emmc btw, not nand but that doesn't change anything) and you will need working vendor u-boot on the box to boot into LE (or CE, which is probably a better option for clone box). Currently there are no LE releases for this kind of box.