You must install CoreELEC ng first/Latest nightly from 08/04.
Then through Network/ssh place Tar file
1 Like
@cpm
Since your build āCoreELEC-Amlogic-ng.arm-21.1-Omega_devel_20240625151500.FC12ā and following (T, T2, T3 and T4), I am having problems playing DTDL (in .m2ts container). The problems can be red screen, heavy judders, black screen, playing in HDR instead of DV. These variables depend on the specific file I try to play. Latest build that works perfectly with these files is āCoreELEC-Amlogic-ng.arm-21.1-Omega_devel_20240621122317.FC11ā. The problems are only affecting DTDL files whilst DTSL are playing just fine. Coreelec setup is your default and the TV is Panasonic Oled LZ1500. This is just to let you been informed. Presently I am using the last working build as I have more than 60 m2ts DTDL movies.
Thanks again for your precious contributions here.
Do the DTDL work ok on the latest ng 21 nightly builds?
I.e. try to isolate is it something I have changed or something it is being based on.
If ok in nightly, then if you have a sample can attempt to track down what is causing the issue.
They work well in the latest ng 21 (08/04) nightly.
I will upload 2 small movie samples in few minutes.
and also I have the āmulticolour UIā when going back to kodi.
LLM generated garbage when it can be explained in a literal haiku lol
2 Likes
This is some serious overkillā¦
Here are two better and faster options.
-
Put the tar on your media files host/server drive, and smb to it in the Kodi File Manager, and copy the tar to the root ā.updateā folder on the Kodi device, reboot.
-
In Windows, if you enabled Samba or NFS and can see the COREELEC, or whatever you have named your device, in the Network section of Explorer, copy/drag the tar to the āUpdateā folder and reboot.
Both take all of 1min to do and then reboot. 
3 Likes
Or just enable SSH on the box, and sftp the file to the update directory (use root as user and the password you created when enabling ssh)
1 Like
Or just download the update to a USB, insert it in the Ugoos and copy it via file manager to the .Update folder then reboot, no network or ssh needed.
1 Like
I have downloaded and tried both, annoyingly they both play what looks to be perfectly for me, also no issue with colours returning to menu.
Cannot see at this point from the code - why it would have changed or be different to the nightly in behaviour for this.
brain storming: long shot - maybe it is something to do with 3D for example played something in 3D and then this and get issue, and in other circumstances had not played any 3D from boot and then it works - something like that.
FYI. The only changes in the media modules aml repo are for the special processing around āATEME Titanā.
Here is a diff with the CE head:
That would be a simple starting point, can fork your own version and merge in that change and then go through a build from your own branch - should pick up quite a bit just stepping through that process all the way to get to it working on your device.
1 Like
Thanks, makes it a bit more simpler, will give it a go later.
@ragico - Do you also have any M2TS DV 7 with HDR10+ on the BL layer can provide a sample?
Works fine for me as well. Do you think you can send screenshots so that I can tell what Iām looking for?
I do not use the Ugoos for 3D contents. I have only tested it. For 3D I use another device an old (X99max+) which works perfectly.
Here i enclose a sample of a DV movie with HDR10+ in the BL layer and it works perfectly.
1 Like
when you get some time can post a kodi log around 15 seconds before and after returning to the menu, just want to see what it is logging when the video closes
I think I found the issue:
When playing software decoded content - it uses CDVDVideoCodecFFmpeg, so I had added logic to switch off DV when that happens as would be āfakeā DV and not true to the content.
But the CDVDVideoCodecFFmpeg is also being involved for reasons other than playing content - looks to be for some thumbnails or maybe something else in the background so is clashing, and turning off the DV when this happens.
Ideally need to see what CDVDVideoCodecFFmpeg is invoked for (though may not be possible) and not touch DV settings if not invoked for playing content.
For now, I can do a build which removes the switching off - hopefully get sometime this weekend, though would then have the potential fake DV issue - but this is a corner case - e.g. DV Mode: On and playing a vc-1 using the software decoding e.g. using CDVDVideoCodecFFmpeg
3 Likes
Thanks @cpm .
Is this problem happening to me only?
I am using Ugoos AM6b plus your CE build and your settings.
Is this due to my TV?
And why this happens from T! build onward?
I beg you pardon for these questions, I am not technically prepared so mine are just out of simple curiosity questions.
Again thank you.
Or, maybe, I am the only one watching DTDL in m2ts container?
Itās not only you. I also sometimes get such garbeld menu colors returning from DV, and others have also reported it with āTā versions.