DTS-HD HRA audio track sample works OK and shows as correct file in Player Process Info.
Using 2x Tox3 S905X4 with differing firmware.
For me, it only works if I set the output on my LG C4 to âAuto or PCMâ instead of Passthrough. As soon as I set it to âPassthrough,â it no longer works. Itâs no big deal. I donât own a single title in HRA. But still, it would have been nice if it had worked with passthrough mode instead using PCM or Auto.
Confirming. DTS-HD HiRes canât be passthrough using a LG 4 series. All others work just fine, but not the HiRes ones. It is not a CE issue but the LG causing this. Connected straight to receiver, sound will come, but I prefer the LG (G4) eARC passthrough option. For me also, no big issue for that one not much used codec 
1 Like
I rolled back to 20260504. But Docker still doesnât work. Reinstalling doesnât help. How do I get it to start?
âCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?â
The same movie , after a reboot not all time ,on the Video Source type
Dolby Vision appear and then after a restart it show SDR .
But the color of the movie are the same.
The issue must be at least partly to do with the addons - which remain the same updated versions after a rollback.
The only way to recover a fully working system is to do a full system restore of a backup - which will restore the older addons as well as the CE system.
UPDATE: Scratch that advice, something weird is going on here as a full restore of a backup doesnât resolve the issue.
Fixed latest docker: https://test.coreelec.org/vpeter/service.system.docker-22.0.10.1.zip
Also uploaded to addons repo.
Please try and report back.
In case it doesnât work install old version manually until proper solution is found.
https://test.coreelec.org/vpeter/service.system.docker-22.0.9.3.zip
3 Likes
Now it works! (22.0.10.1)
Thanks.
1 Like
Things have gotten just to unstable of late so I am jumping ship back to Omega.
When you never follow the guide from the Wiki how to report issues itâs better, yes.
3 Likes
@Portisch Was there any findings regarding this issue (so that I should test a fresh nightly)? I tried looking at the commits but itâs hard to determine from them.
Hello.
After one of the recent updates to nightly build,
my guess https://archive.coreelec.org/Amlogic-no/CE-22/20260508/changelog-20260508.html
the mount on NTFS formatted external USB drive is not possible. Only exFAT or FAT.
If I try to mount manually, the error will come
FUSE exfat 1.2.8
ERROR: exFAT file system is not found.
There were several changes related to NTFS in that build and upwards. Please check / confirm.
Well I have been running three units. One with an old nightly that caused panics before. One with beta3 and one with the latest nighlies. Changing between running a video in a loop and idling.
No crashes occured until now. Unfortunately, no logging showing the issue to examine.
Fingers crossed no more panics from now on 
Confirmed, will be fixed in next nightly.
3 Likes
I have been running on alpha3 for some time, and today, when I booted a box that was working a week ago, the GUI keep freezing rebooting when initializing my HDHomeRun PVR. The only workaround Iâve found so far is to rename or delete the hdhomerun addon directory in /storage/.kodi/addons/ . Reinstalling the HDHomeRun PVR client via addons results in the same lockups, so leaving the addon removed/disabled is the only way Iâve gotten my box responsive again. Kodi logs donât appear to be logging anything useful, as the crash seems to happen before it logs anything.
1 Like
Congratulations on the FEL support - thatâs a fantastic achievement and I look forward to trying it out.
Is there any chance youâll also be looking at the vsync hardware clock work I have seen floating about? Sync/smoothness has always been a weakpoint for Kodi, and these sound like very worthwhile improvements.
I much prefer sticking with the official CE and of course wish such work would flow back as PRs to the main project, but that seems unlikely at this point - so just wondering if youâre thinking about it at all.
Sorry, donât understand the question.
VSYNC is a hardware IRQ, there is nothing to do about it!?
All samples like FPS_test do run smooth in all formats.
Sorry, donât understand the question.
VSYNC is a hardware IRQ, there is nothing to do about it!?
All samples like FPS_test do run smooth in all formats.
All "improv
I am referring to this, in short:
While investigating stuttering issues and PGS subtitle color accuracy, I stumbled upon the frame pacing logic of the VS10 core. We already use the VS10 core for certain format conversions, and it uses a different method for frame pacing, which seemed to work quite well.
An idea was born.
After some finagling the âVS10 HDR10 to HDR10â and âVS10 SDR to SDRâ (existed before, but buggy) pipeline was implemented. We now by default use the excellent frame pacer from the VS10 core, which makes an astounding difference in playback quality. Visually this means less stuttering, better panning shots, and even a better perceived picture quality, probably due to more even frame pacing.
*This also ensures correct colors in PGS subtitles, as the VS10 core, when properly initialized, uses its own color mapping instead of having to rely on BT2020 shaders.
*
(Release Release T3 ¡ pannal/CoreELEC ¡ GitHub)
I donât want to raise any sore points of course. But whilst it is indeed overall smooth (correct rate switching etc) - side by side with other video players Kodiâs frame-pacing is indeed always subtly imperfect (and has been forever, really, at least to my eye - itâs an issue I am sensitive to - right back to the ION330 days when I spent some time testing and attempting to debug this in depth with FernetMenta).
Where are the real samples on what we have this sync/smoothness issues on latest nightly?
And you can ask pannal to send PR. We have some from him that was merged.
And samples please on what we can see problems now on Peers build.
1 Like