How would one go about updating the jellyfin server to the latest version?
Someone submits a pull request to the libreelec-12.0 branch in GitHub bumping the version and updating the SHA256 hash, then the request is merged and gets automatically built overnight and pushed to our repo.
Mostly bumping gets done by staff, but anyone can submit the change.
Have 2 movies in 1080i@25 resolution
Then Kodi playing at 50fps is correct, because Kodi only outputs progressive, so it must render each interlaced (half) frame as a full progressive frame and you need 50 frames to account for 25 interlaced frames.
I lose frames at 50 refresh rate
I normally recommend people re-rip from the original media when the encoding is bad, but you've stolen a movie off the internet that's been ripped into a lossy interlaced format. I guess that made sense to the original pirate that created and shared it.
The only issue I can see is that you're expecting a lossy pirate rip to be high quality 
It should have been built/distributed for all architectures.
Pi4 doesn't want to switch to 25fps. 1920x1080@25 movies play in 1920x1080@50.
And what is wrong with this? - See https://wiki.libreelec.tv/configuration/4k-hdr - Unless you are never going to play interlaced media rate doubling should be enabled, and a side effect of this is 25fps media playing at 50fps, which is harmless.
I'm forgetting that this exists: https://github.com/rudihorn/drm-vc4-grabber
If you want to experiment, the /usr/bin/drm-vc4-grabber binary is embedded in this image:
https://chewitt.libreelec.tv/testing/LibreE…-12.80.2.img.gz (and the .tar)
Note that I've only compiled the package, I have no means of testing it. The 'drm-capture' service should run on boot.
Package changes are here: https://github.com/chewitt/LibreELEC.tv/commits/rpi-13.0
If it works well it could be repackaged as an add-on, although an in-kernel solution would still be nicer.
No idea what the issue is, but it's not a LibreELEC issue, so the correct place to report it (with complete debug log not the snippet posted above) is the inpustream.adaptive support thread in the Kodi forum, or the inputstream.adaptive GitHub repo.
Nothing specific to test, just interested in overall success (or otherwise) reports.
Will that work on a Wetek Core?
No. It will work on other S812 boxes, but WeTek Core locks up on boot and currently the only known workaround is forcing the box to run on a single CPU. So far nobody figured out what magic is required.
LE is not Debian based so that's all completely irrelevant. Who cares if it works under Windows.
Read this: https://wiki.libreelec.tv/configuration/4k-hdr .. even if you are not using 4K or HDR the config suggestions are relevant.
If no change, share Kodi debug logs via "pastekodi" else we are blind guessing at the issue.
All I did was enable SMB (as normally I have it disabled) and either clicking on the now-visible device in Finder>Network or doing the command+k to give an explicit address using <name> (not <name>.local) worked fine.
NB: The default SMB password is libreelec/libreelec not root/libreelec
Just do "command + k" in Finder and provide the smb://NAME/SHARE you want to access, or at least smb://NAME and it will then prompt for credentials and list the available shares.
Changes are merged and should appear in nightlies in the next 24h. You will need to manually update to a fixed nightly before the update process will start working again.
This change should fix the update process in nightlies https://github.com/LibreELEC/serv…ttings/pull/330
There is no need to chainload u-boot as Armbian does. Just use the AMGLX "box" image which includes s905_autoscript and boot.scr on the SD card and vendor u-boot will read one of them and reconfigure the boot environment to look for LE boot files first (and if not found, fall back to default boot into OSMC). It will be the same for Vero 4K and 4K+ boxes (and pretty much anything else with vendor u-boot on internal storage).
I'd suggest you submit the idea to the Raspberry Pi kernel developers via their GitHub repo as this is not something that will be developed by LE staff.
Please provide the URL's from:
lspci -vnn | paste
lsmod | sort | paste
Enabling deep colour changes HDMI properties advertised by the TV on the HDMI port to include 12-bit 4:2:2 and I'd guess that the display chain cannot handle the additional bandwidth required for 4K60 and thus sync is lost. Disabling deep colour forces 8/10-bit 4:2:0 output and allows things to work. The most common issue with 4K60 video is the HDMI cable not being able to sustain higher bandwidths required (esp. when combined with HD audio). Do you have 4K60 certified cables?
There is very little real-world media in 4K60 format (most is under 4K30) and almost nothing in 12-bit (only 10-bit) so if the cable is not the issue, disabling deep colour on the TV or leaving the video= change in syslinux.cfg and never using 4k50/59.94/60 modes (where the issue will probably reappear) are both options. The video= change only forces the initial connector state to 1080@60, it does not prevent Kodi from detecting and using 4K modes with the whitelist later.
