Just drop it to update folder with samba share…
https://wiki.coreelec.org/coreelec:updates
1 Like
Would there be a way to blacklist by refresh rate? UK TV is 25 or 50hz, most Movies are 24 or 23.967hz?
How can I flash the CoreELEC-Amlogic-ng.arm-21.1-Omega_devel_20240505032916.tar file to my SD card for testing ? Thank you!
Use the CoreELEC image first and then drop this into the update folder.
1 Like
THANKS ! 
[quote=“rome1931, post:149, topic:51323, full:true”]
Use the CoreELEC image first and then drop this into the update folder.
[/quote]
v6.
- Fix lockup with MPEG-2 SDR → DV
- Rebased on latest CoreELEC 21
Edit: Version removed - please see new version in later post.
@anon62335196 Let me know if you see any more lockups your side.
2 Likes
Wonderful job, it’s almost time to retire my z9x pro, just one problem so far, when I reproduce a movie and then stop it most of the times the whole menu/skin is having some kind of background garbaje and wrong colors, restarting kodi do not solve it, it’s anoying but all works anyway, using TV-LED with default skin.
can we this release use next to with the “normal” one?
meaning…having VS10 and full dv support in one device installed on internal storage?
You can but you shouldn’t. It’s not without issues, biggest one being the one mentioned above you.
Just another suggestion if it makes sense, can we have the option to not use VS10 for Dolby Vision content, again don’t know if the VS10 does anything with DV content but if it does, then it may makes sense to have the option
VS10 is just the Dolby Labs name for the Dolby Vision Engine implementation done in partnership in these SoC with AMLogic, Realtek, MediaTek etc.
For original Dolby Vision content there is no change it is processing like it always did for DV → DV
VS10 can map down to HDR10, SDR10 and SDR8 (not withstanding there is a bug somewhere in at least the HDR10 mapping) so made sense to me to just put under one control.
From chatting with the CE team they want to simplify this all down to a much smaller set of parameters - so not sure what they will do eventually, for me I will keep my personal build with the options I like.
Thanks for the quick, makes sense, the lack of fine tuning VS10 was anoying when moving from the zidoo z9x to the z9x pro, in the pro (if you have a DV tv) is just VS10 for all tyoe of video or none.
@cpm would it be possible to ask for a one off special build with the code from v1 , to not change resolution after live tv playback ? So we stay in lldv 50hz /1080 until a play something else
. ( all this to avoid long blackscreen on channel change )
Unfortunately not so simple, I add the VS10 features on top of the CE latest code, I think the change in behaviour you saw between 1 and the later version was something in that underlying CE codebase, not something I was doing.
I think your best bet is to open a new thread detailing your situation, there may well be settings you can change already that could help (of which I don’t have knowledge), and if not maybe the CE team can look to implement something - I think there is plenty of appetite to have minimal changes where possible when moving between shows etc.
Can’t wait to test!
Out of curiosity, what was the issue and how did you fix it? I’m sure it’ll go over my head, but I’m always interested in fixes like this.
First, big thanks to all dev ! What a great device Ugoos am6b with CE has become 
Request :
A option to have always lldv with v10 engine
for live tv ( gui set to 1080@50 lldv)
@cpm needs some help to make this possible
@Portisch do you have some idea how to make this work
My usecase is am6b with ls12000 projector.
Ls 12000 is calibrated for lldv with Ezcoo and Apple TV 4k so my hope is for always lldv/vs10 for CE and Ugoos am6b . The biggest issue without always lldv is that on every channel change my projector goes black for a long time when vs10 changes back to non lldv between every channel . If it is not possible to have always lldv maybe a option to only change resolution when needed, like going from different resolution/ fps . Thanks !
Lots of trial and error, I knew it could work by changing the parameters later as posted about before.
So cut back the code in small chunks until could isolate the line(s) of code causing the lockup.
Turns out it was switching on DV and that was being done two different ways.
Next have some educated guesses what the lockup maybe about - for me I postulated it was going to be around the codec setup,
So one of the enablements of DV I just cut out for the VS10 mapping (probably not needed at all for any flow but left in for the standard DV → DV flow anyway just incase as was not breaking that.)
The 2nd DV enablement I moved to after all the other codec setup and before the playing started, which sorted the lockup.
lol ends up back here anyway!
I hope you get some resolution to this longer term having always on DV and limiting the graphic luminance seems the most appropriate.
1 Like
v7.
- Fix wrong colours returning to UI from DV.
Working for me, but not the prettiest code so not sure if will break for others, let me know.
5 Likes
Working for me too. tested quite extensively and never wrong colours returning to UI from DV. Excellent job @cpm.
Thank you