Logs confirm the kernel side never switches over, though kodi is asking for it to switch, next will try and force the issue from kodi to the kernel via another route.
Next time you see the issue try running the following on ssh:
echo now > /sys/class/amhdmitx/amhdmitx0/attr
Can be installed over the current one, then reboot.
Enjoy! 
great work, thanks! couple of questions:
Hey 
I can enable scrolling for this. Truncate is not possible.
I’m not sure if there is such a thing for this. I’ll see if I can find anything about it.
do you mean automatic or manual scrolling? if auto, I don’t think it makes sense for dynamic value like this. I would then leave as is.
If it is possible I would probably move CPU usage to the bottom of the section and minimize the distance between label and value. It will not look out of place as above elements (progress bars) already take the whole width.
As an alternative: combine CPU speed and temp into one value “1800 / 36” so we have one free line and use it for the CPU load value like this (with more spacing between cores fore better readability:
System CPU Usage:
#0: 1% #1: 5% #2: 1% #3: 5% #4: 1% #5: 5%
[====-----------------------------------------------------------]
yeap, tweaked the skin a bit (removed the build as it’s unnecessary for me on this specific screen) and moved the full cpu usage values to the new line, much better.
Hey, nice work again 
hopefully some more to come soon!
If you don’t mind - we should use the other topic and let this one close out as the initial HDR10+ to DV P8 is done.
@chuckster
Good idea!
I’ll see what I can do later.
@cpm 
Yes, of course. I can post new releases of the skin to the another topic. Can you send me a link where the new location is?
I hope the video/audio bitrate feature will work in future. That’s pretty much the only thing missing except for a few exceptions.
A lot here and in the other skin/player process thread. Did you ever get this working? I’m using Plexuary too.
No, I even switched to an estuary skin that someone made here.
But in PM4K it always shows the default PlayerProcessInfo, not sure why.
I´m also using PM4K, currently with “skin.cpm.estuary.A4” on the latest CPM build (A4.1) and the improved PlayerProcessInfo is working. It was working for previous builds also.
I just upgraded to A4.1 and the A4 skin, I still can’t get the improved PlayerProcessInfo to work.
In PM4K, I go to open menu, then Settings → Show Stream Info while content is playing, no change with default.
Am I navigating to the wrong place?
I think that´s it. If you do it from the Settings → Show Stream Info, it shows the default PlayerProcessInfo. I don´t use that method anymore since I remapped one of the color buttons on my LG remote control to show the PlayerProcessInfo.
I use the “Keymap Editor” addon with the following setting. Edit/Global/Other/PlayerProcessInfo and then select the button on your remote.
I also did the same for the Information and Player Debug Options.
Thanks, that worked
there a new version a5, anyone knows the changelog?
For the HDR10+, you can now prefer this over any original Dolby Vision in the content.
Also see this post as to any changelog:
can we expect any profile 7 playback improvements ?, it playes fine until you pause or ff rw, the the audio gets messed up, and most times the entire screen goes red or pink
apparently all the releases are gone, i guess that answers my question
Audio sync issues are not related to cpm build specifically. CE team is working on a potential solution for this issue, so just have to wait, no ETAs.
I must have missed that post, could I trouble you for a link?
About | FAQ | Terms of Service | Privacy Policy | Legal Notice