TV at 1080p 60hz
Does the TV have 23.976/24/50/59.94 modes? .. what happens if you enable "adjust refresh" with whitelist entries for those modes and support for rate doubling (to handle deinterlaced content)?
I'm asking because I only see the pink line with a shitty 10" LCD that I use for testing sometimes which only has 1080p 50/60Hz modes. If using the normal house TV with more modes and adjust-refresh I don't see the line. It would be nice to confirm it's only present with 60Hz.
Pick a different HDMI cable. Pick a different HDMI port?
You already proved the issue is not the NUC or LE by connecting the monitor so next call is Samsung support.
So WOL is no longer supported on LE 20 ?
I replied to the "Any suggestions or alternatives?" .. because regardless of whether LE supports WOL (don't know, never used it) it is a method that always seems to result in frustrated users moaning about how flaky/difficult it is to get working right on their hardware or the app being used (or some other issue) in forums. So I suggested something low-tech that will work.
@chewitt: did you forget to remove the patch 'amlogic-0091-FIXUP-add-adc-gpio-keys-and-led-s-to-dreambox.patch' before merging nigthly? This only causes trouble, because the exit dialog opens with almost every keystroke on the infrared remote control
There are multiple additions in that Fixup! commit so it would be good if you can experiement and tell me which bits work or not. The formula for the adc-keys values can be found in the vendor dts so perhaps validate my maths as it would be good to have the keys working.
There are some users who claim 4.3 is broken and terrible and 4.2 is the only TVH to use. There are also users who claim that 4.2 is old and broken and terrible and 4.3 is the only TVH to use. So .. 
dootsie5times USB rtw88 drivers were merged in 6.2 and were backported to 6.1 in LE, so they are present in current LE11 nightly images.
Probably not for all hardware (e.g. I haven't picked all those changes for AMLGX) and I'm not sure they're present for RPi images either.
Known issue. We need to backport the LE11 fix to LE10 and then build a replacement add-on. That should happen in the next 24-48h.
I have an old build LibreELEC-S912.arm-8.2.5-Chroma.422.10bit.img that works flawlessly.
I cant find out builds anymore, where they all deleted?
Nothing to do with me so can't help.
All media, from 1080P H264 , AVI to DVD VOB files. Audio output is from the mecool analogue out.
And what is the playback resolution? - TV or Monitor?
HDMI output should not have issues. The Analogue audio output is somewhat untested.
crazyazz What resolution and bit-depth is the media being played, and what resolution is the TV when the pink line shows? .. or are you using a monitor? .. and what audio device is connected: HDMI, S/PDIF or Analogue?
IR controllable power socket? https://www.ebay.co.uk/itm/284397741540
[global]
allow insecure wide links = yes
[library]
follow symlinks = yes
wide links = yesAbsorb those bits ^ to the custom samba.conf then reboot and try to connect again. Working?
Nothing changed in Samba or our Samba config for aeons but if this is a removable drive, is it NTFS formatted? .. because we switched from using FUSE to native in-kernel NTFS drivers since LE9.2 and that may explain the difference in behaviour.
Please forgive my ignorance, but what do I need to instal for my Mecool M8S PRO L? Also on another note, is it possible to install these images on the internal storage instead of SDCARD?
Q1 - Read this wiki article https://wiki.libreelec.tv/hardware/amlogic
Q2 - No. Read the statement at the bottom of ^ that article
Just take a backup using the LE settings add-on and move the tar archive file somewhere safe. Clean install using the latest nightly image, and if things like previously watched status are super important to you; then put the file on the new install and manually unpack it somewhere to allow simple restore of things to where they need to be in the filesystem (easy to Google for that info). If you're not bothered with status then just go about setting up sources and scraping media again. I would caution against simply restoring the backup as a) this will restore Python2 add-ons to a system that no longer runs them and this is a frequent cause of update issues, b) most installs will benefit from not restoring the accumulated years of cruft from the old install (spring cleaning).
Any hints and ideas welcome. Would like to get this running asap.
Any difference with LE 10.0.4? .. or this nightly? RE: LE 10.0.1 / Rpi4 / No picture after update from LE 10.0.0
Kodi 20 stable is ready! We will be very happy if you (chewitt and the other LE team members) include all this Amlogic fixes and tweaks in LibreELEC stable release. Thank you for your support and good attitude towards us - the common users.
Current plan is to resume support for GXBB/GXL/GXM devices. Images are not perfect but more than usable for average users with average media media collections that are mostly 1080p based, although S905X/D and S912 do support 4k/HDR playback. The same images can be installed on newer devices but the hardware decode drivers have greater issues on newer hardware so those are really limited to software-only decoding (1080p max) and to set low expectations and keep things sensible we will state those are not supported. All recent changes in my branches are upstreamed to GitHub master branch yesterday. There is still more general stuff to get shipshape before an LE11 release can be announced .. I'd expect another 7-10days is required.
Are these FFMpeg changes already in the last image on test.libreelec.tv or only on chewitt.libreelec.tv? Would you mind writing who is behind these changes, someone has taken it upon themselves to fix it, or maybe it's to your credit?
https://github.com/LibreELEC/LibreELEC.tv/pull/7387 was merged yesterday along with a few other things so the next round of images on the test server should contain the same content as the images on my share. The FFMpeg changes are by John Cox @ Raspberry Pi foundation. He is not working on Amlogic support, but we have common goals for v4l2_m2m support in FFMpeg and care that the current codebase that he is working on supports a range of SoCs and not just RPi boards. To further that I regularly test his experimental changes and provide feedback (especially when regressions are involved). In this case, a change made definitely helps with HEVC seeking. It's not a full fix though; that will almost certainly need changes to the kernel driver (which is lacking developers for aeons) but an improvement is still an improvement.
I have a hunch on the rar archive support add-on?
