Dolby Vision Profile, VS10, plus other info on skins

ok, I’ll wait for a bit. But I think he deleted the builds and branches more as a cleanup, as they are might not be ‘relevant’ for him considering latest changes in the CE’s kodi (reintroduction of libdovi, bringing back of P7 conversion to MEL or P8, etc). Though it’s not fully rebased yet, he pulled in some changes separately. So he’s leaving just the current code that he’s maintaining for his own use. That’s my take on it.

From now on, he only fixes/cleanup his code.
He said he will not add any more functions in future.

I think the new commit from today for the PlayerProcessInfo was just the end of it all.

It’s just my guess.

Btw:
Convert from profile 7 to MEL or P8.1 works fine.
Test it already.

good to hear, I expected so (just haven’t managed to test yet), as it was a recent change in official nightly and he adapted it to his work.

the ‘fun part’ would be maintaining these changes if there’s another major surgery in upstream that touches his rework. So far it’s been pretty simple resolving a couple of minor conflicts during cherry-pick, but who knows what future brings, we might end up stuck with some build for a while.
But that’s a story for another day)

Everything is working as expected.
I haven’t noticed anything that causes any problems.

I have tried different media (movies):
Dolby Digital - :white_check_mark:
Dolby Digital Plus (Atmos) - :white_check_mark:
Test this because he doing some code refactoring about it.

The following is also without complaint:
Convert profile 7 to MEL - :white_check_mark:
Convert profile 7 to P8.1 - :white_check_mark:

The problem I had for two weeks that new local media were not automatically detected has also been resolved. :white_check_mark:

So this build is definitely very stable and the VS10 engine runs very very well.

Another positive thing I noticed that some people have criticized on last build is HDR10+.
So the conversion from HDR10+ to Dolby Vision runs well to for me. :white_check_mark:

4 Likes

thx for the testing (my build with today’s commit is in progress).
Hopefully our gurus from CE Team will kick the buffer issue’s behind in the not so distant future,
and with that fixed it would be a good build to stay on for while if adapting changes poses a problem at some point.

3 Likes

@cpm
you are aware that many many people is following your researches and have adopted your builds. I follow this forum from many years and never encountered a similar situation. I do not want to enter the problems between you and CE Team. I only am part of hundreds of people very happy until yesterday and now abandoned . It’s ok if you have decided what you have decided but have you ever considered your followers? I have a great respect for your intelligence and sensibility and am sure that you are still reading this forum. Therefore you know that the vast majority of us does not have the preparation and experience to use your repo for building the .tar. So what? Will continue “ad infinitum” like now or you want to walk a different way? Thank you very much and sorry.

1 Like

The days for NG 21 are counted. There is no longer much movement from the CE team. Soon it will all be snow from yesterday. The only thing we can hope for is that CPM is still working on it. (Code cleanup/fixes) of its VS10 engine to perfect the whole thing and then we will have many years of fun with it.

1 Like

yeap, I don’t have a need for any new functionality. It’s only the sync issue for me that remains and If it’s fixed I can stay content with that for a while. At least as local UHD FEL remux player (for everything else some non-FEL capable box with newer and supported kernel will work just fine in case I need it).

1 Like

Who will enjoy from this “perfect build” of NG 21? only few and lucky people?
Here it seems that the discussion is now among 3/4 people only.

I’m sure it will be shared, no need to worry.

nor worried, just to clarify

I dont know how others but I dont know how to compile the source code to img. Hence for me no other updates are relevant as the sdr to dv is the biggest leap in video encoding for me. It’s really frustrating as the overal skin/encoding/new features was so exciting. So many of us just ended up on latest A5 build without any other tweaks from CE team and @cpm .

The code is public and can be compiled by yourself if you have experience.

Currently this is the only one way.

“Repetita iuvant” Sorry If I use Latin proverb.

Maybe asking a stupid question, but is NG CPM the only CE version that can successfully decode FEL on the Ugoos?
I’ve read somewhere that the Ugoos will be supported in other CE versions, too, but does this mean is does not have all features?

Yes it will. Maybe not here on the CE forum but it will be available. He said it. Just be patient. I guess within 1 or 2 weeks , everybody will be happy again

5 Likes

This is the Guide:
https://wiki.coreelec.org/coreelec:build_ce

Prefered option is to use WSL if you are a windows user.

git clone https://github.com/CoreELEC/CoreELEC.git
cd CoreELEC
git checkout coreelec-21

This needs to be edited to get the sources from CPM:

projects/Amlogic-ce/packages/linux/package.mk
projects/Amlogic-ce/packages/mediacenter/kodi/package.mk

Then build with this command:

DEVICE=Amlogic-ng PROJECT=Amlogic-ce ARCH=ARM make
4 Likes

and media-modules is no longer needed as the changes have been a part of upstream for while.
so only two packages need adjustment.

1 Like

I hope everyone will appreciate work needed even for some small change or feature more after this. By CE team or by any other dev.

8 Likes