CPM builds

Unsupported/EOL HW/SW Community Projects
1

Hello guys

here we can discuss the CPM builds.

15 Likes
2

We call this release A6.
This has been agreed and I have received approval for it.

13 Likes
3

Would I need a ‘permission’ from cpm if/when I want to share my build or you got a general green light for posting builds derived from his modifications?

4

I’m not sure about that.
I have now only received approval for this build. But I don’t think it’s a problem ?

5

me too, was asking just in case. I think cpm would have probably indicated somehow if this was not desirable.

6

In general terms no problem with using it. Keep in mind that 99% of that is just CE (that’s already a mesh of a lot of things).

3 Likes
7

Could someone also post a link to a zip for the skin and @Gilgamesh can you add a link to this zip to your first post when it becomes available?

8

So CPM isn’t doing any builds going forward?

9

Special thank for A6. It is working nice on Kinhank G1. Hope for further smaller fixes if necessary, but I think it is quite OK for a daily driver.

10

A6 version fixed an issue I had with a specific P8/HDR10+ file; no player crash anymore.

11

So I was playing around with the A6 community build and I noticed that full blu-ray menus no longer work properly. The menus do load but don’t (or hardly) respond to presses of the arrow keys or the OK button.

I then switched to the official 20241026 nightly and menus started working again.

I did notice that in the A6 build the experimental buffering code is still present (it was removed from the nightlies because it was causing issues apparently). Could that have something to do with it?

And out of curiosity: which nightly build is the community build based on?

12

Are you talking about the cpm.estuary skin?

You can download it from source here:

Press the green “Code” button and choose “Download ZIP”.

Once you have the ZIP file, you need to extract it and re-ZIP it without the top-level directory, so that the skin.cpm.estuary directory becomes the top-level.

13

Just a heads up to everyone, if you find any bug that can be related to the official code and need some help you must always test the latest nightly and present a log from an official build.
Have fun!

7 Likes
14

Does the CPM Estuary skin include the changes that occurred in the A6 release?

15

Yes.Included

2 Likes
16

Thanks to those who are making regular builds of CPM’s changes! Super helpful. I may set up a build bot on my home server to automatically create builds whenever CPM pushes new code. In the meantime, I’ll piggyback off of the great work of the community :slight_smile:

If you are running CoreELEC with PlexKodiConnect and want an easy way to identify Dolby Vision content, including profile and enhancement layer, here is a script that I wrote that will talk to a Plex server, iterate through all of its movies, and attach labels to them in Plex. Labels will be of the format ‘Dolby Vision P7 FEL’, where the profile can be any existing profile number (generally, 5, 7, or 8) and enhancement layer type (MEL, FEL). In addition, it will optionally add a general ‘Dolby Vision’ label.

This is particularly useful in Kodi / CoreELEC, which treats “sets” in a different way than Plex’s “collections.” In Kodi, a video can be in one and only one set, where in Plex, a video can appear in multiple collections. I have my Arctic Fuse 2 skin configured with a Dolby Vision navigation widget, where I can see all DV videos, or videos with a particular profile and EL. This is a great way to check out DV P7 FEL content with your Ugoos.

6 Likes
17

Hi! Does anyone know why, when using the skin mentioned in the quote above (CPM Estuary), on the latest CPM A6 build compiled by Jamal, when playing an SDR video, the info panel is empty and labeled Dolby Vision - HDR? For HDR10/DV materials it works as intended. What am I doing wrong?
Thanks in advance for any assistance!

20241030_135659
20241030_1356591920×1440 103 KB

18

That’s bug. When SDR, the tab must hidden.

1 Like
19

Hey, it looks like there was a small mistake in the skin. If you look at the last commit Small changes on DialogPlayerProcessInfo.xml ¡ cpm-code/cpm.Estuary@e94db5d ¡ GitHub, the visible code should be added under the <control type="button" id="5552"> in the 1154 row as it is the one correlating to the playerprocessinfo button. Currently it is vice-versa :smiley: . I believe cpm of frodo19 will encounter the bug soon and correct it.

2 Likes
20

Yes, corrected, thanks.
cpm need approve.

4 Likes