in "settings / display / framerate" the framerate is set to 50fps. When i Play a Video with 24fps after pausing the Video i have micro stuttering for a while. I don't have that Problem when the Video has 25fps. Is there a Solution for that Problem?
Don't force 24Hz content to play at 50Hz?
Use the mode whitelist to enable 1080 @ 60/50.94/50/24/23.976, allow double rates, and enable adjust-refresh.
That makes no sense to me because the default u-boot behaviour (without the patch) is to search for dtb files in /amlogic/ and that's where the files exist (image below shows the layout on the SD card). In older LE images the files are placed in the root folder, hence needing the patch.
I'm wondering if the paths are being appended. If you create /amlogic/amlogic/meson-g12b-odroid-n2-plus.dtb on the default image (without the patch) does the board boot?
Have you enabled "disable password auth" in the SSH server settings (in LE settings)?
Kodi in LE has been compiled with an internal SMB client (libsmbclient) which is independent and separately configurable to the 'smbclient' binary derived from Samba which is also embedded in the OS. Both follow the default 'Samba' behaviour of SMBv2 min and SMBv3 max, meaning clients connect at SMBv2 and (re)negotiate to SMBv3 if the server supports it, unless manually forced to use min/max SMBv3 or min/max SMBv1 only. If users set min SMBv1 and max SMBv3 the client still tries to connect at SMBv2, and this has been the Samba default for at least a decade now (as SMBv1 has long been considered wildly insecure).
The Kodi smb client can be configured with different read/write cache sizes. LE uses the Kodi defaults which can be overriden (with mostly negative effects). In older Kodi versions this is done from advancedsettings.xml. From Kodi 21 (LE12) the default SMB read chunk size was changed and can now be configured from the Kodi GUI which helps with some scenarios. Are all the Kodi clients running the same Kodi version?
I have zero knowledge on Jellyfin clients, but they may work in a similar fashion to Kodi with different caching and protocol support in different OS and app versions. If you want to test for SMBv1 or SMBv2/v3 use, you should be able to disable SMBv1 support on the Lubuntu server (and you should do this anyway) and if things break, it was using SMBv1 (which is slower) to connect.
The only other thing which normally impacts SMB transfer speeds is the filesystem driver on the server; the main problem being that users have NTFS drives which are poorly supported in the host OS. These days LE uses in-kernel NTFSv3 drivers. In the past we used NTFS-3G which are userspace (and thus much slower) drivers - and this is still the default in most distros. However that's a server side restriction so it would limit transfter speeds to all SMB clients, so that's unlikely to be the reason.
Offline DV media is generally encoded with a fall-back to HDR10 so devices like RPi5 which do not support DV itself can still play HDR with correct colours. Online streaming media from DV enabled services (and rips of those services) are generally encoded without the HDR fall-back so will show wrong colours.
Now repeat the curl -vvv from the LE device.
curl -vvv https://addons.libreelec.tv/12.0.0/ARMv8/aarch64/addons.xml.gz.sha256 | pasteRun that ^ and share the URL
Note that you MUST run this from the LE device as we filter/drop requests from non-LE devices.
NB: Unrelated, but it's best to connect HDMI to the socket nearest the PSU connector.
How old is the version of PuTTY?
I can get to skins now - that must have been about getting all my regional stuff set correctly
NB: It has nothing to do with regional settings in Kodi, but might have something to do with geo-region as Team Kodi serves content through a network of third-party mirror servers. LE does too, and although our list of mirrors is smaller and less sophisticated than Kodi's, most of our mirrors are also in their list so an issue with a particular mirror (nearest to you is the logic used) may impact LE and Kodi at the same time. Looking in the debug log should show which is being used.
I'd ask popcornmix to comment. Any ideas?
Hopefully someone also starts work on audio. Silent movies went out of fashion with Mr Chaplin.
Disable sync playback to display. This forces Kodi to use the media for clocking. It's normally more stable.
for i in $(git rev-list --ancestry-path 353213e..968e285); do git show $i; doneThat ^ diffed the commits between the good/bad change and I don't see anything major in the list, but there are a load of u-boot and boot config changes. I know the bulk of them are good and really the single difference between N2 and other boards is the use of FDTDIR instead of normal FDT in extlinux.conf. So on a hunch, if you remove the trailing / from the FDTDIR line so it reads "FDTDIR /amlogic" not "FDTDIR /amlogic/" does it boot properly now?
Not seen anything like it. Have you followed the general setup recommendations in https://wiki.libreelec.tv/configuration/4k-hdr ?
Probably best to ask in the add-on support thread in the Kodi forums (where the add-on developer usually hangs-out).
Feb 28 03:26:06.168165 LibreELEC kernel: dvb-usb: found a 'Sony PlayTV' in cold state, will try to load a firmware
Feb 28 03:26:06.221403 LibreELEC kernel: dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
Feb 28 03:26:06.854691 LibreELEC kernel: dvb-usb: found a 'Sony PlayTV' in warm state.
Feb 28 03:26:06.854918 LibreELEC kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Feb 28 03:26:06.858193 LibreELEC kernel: dvbdev: DVB: registering new adapter (Sony PlayTV)
Feb 28 03:26:06.859088 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Feb 28 03:26:07.192154 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
Feb 28 03:26:07.240171 LibreELEC tvheadend[436]: linuxdvb: adapter added /dev/dvb/adapter0
Feb 28 03:26:07.477923 LibreELEC kernel: dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Feb 28 03:26:07.481703 LibreELEC kernel: dvbdev: DVB: registering new adapter (Sony PlayTV)
Feb 28 03:26:07.484807 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Feb 28 03:26:07.648585 LibreELEC kernel: dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
Feb 28 03:26:07.696182 LibreELEC tvheadend[436]: linuxdvb: adapter added /dev/dvb/adapter1
Feb 28 03:26:07.925450 LibreELEC kernel: dvb-usb: schedule remote query interval to 50 msecs.
Feb 28 03:26:07.925475 LibreELEC kernel: dvb-usb: Sony PlayTV successfully initialized and connected.
Feb 28 03:26:07.925502 LibreELEC kernel: usbcore: registered new interface driver dvb_usb_dib0700It seems to be working ^
Feb 27 17:26:09.585022 LibreELEC udevil[447]: mount: /var/media/MadMax: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Feb 27 17:26:09.585022 LibreELEC udevil[447]: dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:09.585809 LibreELEC kernel: ntfs3: sda1: failed to replay log file. Can't mount rw!The NTFS filesystem on the drive has issues so the kernel refuses to mount the drive. You'll need to fix the issue with chkdsk.exe from a Windows PC as there are no Linux utilities for doing that.