Dolby Vision Profile, VS10, plus other info on skins

Unsupported/EOL HW/SW Community Projects
314

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.

315

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

316

nor worried, just to clarify

317

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 .

318

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

Currently this is the only one way.

319

“Repetita iuvant” Sorry If I use Latin proverb.

320

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?

321

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
322

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
323

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
324

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
325

will try, I tried yesterday but got stuck at some point, so hopefully will get there with your manual. Thanks a lot.

1 Like
326

What needs to be edited in:

327

PKG_VERSION, PKG_SHA256 and PKG_URL must be edited.

> projects/Amlogic-ce/packages/linux/package.mk

package.mk (12.1 KB)

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

package.mk (18.9 KB)

Try this.

Note, however, that this is only intended for the current changes up to now. If CPM makes a change, these files must be edited again.

If anyone knows a better solution, please let us know.

Edit:
You may get an error in the build because of the json-c.

Change the SHA256 in the package.mk of the json-c to one of the two. (forget which one is the right one)

bca9a584a8da64d8dff50082a06f6cea26fb735f74924afc6d01ae6be7a75885

or

fc1b9ed57f4cda51c52ec9b3b012f6973bd8d80fb70f363c5ca2754342389eb1
3 Likes
328

There’s no better solution, just a different one if you want to base his changes on the latest Kodi from nightly CE (with cherry-picking his commits on the latest upstream Kodi, generating a patch and without the need to modify packages). Cpm described the procedure in one of his posts. That’s what I’m doing. Current branch of cpm’s code is based on a slightly bit older kodi version compared to upstream with a couple of newer changes backported. So using packages.mk you get fully what’s in his repo.

1 Like
329

I don’t know how you get the URL as the cpm-code/xbmc/archive is not reachable… am I missing something ?

330

You must combine PKG_URL and PKG_VERSION:

https://github.com/cpm-code/xbmc/archive/a5d070267e169b7d5dd367fe17c43a2e77e3a90b.tar.gz

Replace the attached file with yours and done.
You don’t need to download it manually.

331

I know but I’m curious about how you get the PKG_VERSION if not from the URL. I mean I’m trying to find out how you get those codes.

332

I use Powershell with git to get the latest PKG_VERSION:

Paste and enter this:

$PKG_VERSION = git ls-remote https://github.com/cpm-code/xbmc.git HEAD | ForEach-Object { $_.Split("`t")[0] }

Then paste and enter this:

$PKG_VERSION

Then you got a result.

For SHA256 you can get a file calculator to get it or when the builds fails because of the wrong SHA256.

1 Like
333

It makes perfect sense to me now. Thank you very much for explanation.