https://test.coreelec.org/ray/CoreELEC-Amlogic.arm-9.0-devel-1555074085.tar
OK, will try it this one and see how it behaves
This addon here is definitely ahead of itās time lol.
We need to poke @cdu13a to at least push the config changes.
Thatās the problem your /sys/class//sys/class/amhdmitx/amhdmitx0/config returns a different set of values.
You need the latest version dated 2019-04-12 devel-1555074085
This is probably the only version where is works right now
From my S912:
cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 353
VIC: 353 3840x2160p60hz
Colour depth: 8-bit
Colourspace: YUV420
Colour range: limited
EOTF: SDR
YCC colour range: limited
PLL clock: 0xc000027b, Vid clock div 0x000a339c
audio config: on
3D config: off
Lolā¦ yep it relies on the output of amhdmitx0/config using the exact labels.
@Pelican Yep, thatās the format Iām working from
I know I checked your source
Well those changes have not been applied to 4.9 kernel yet. Thats why we rely on Testversions.
Yes, it works now OK on this 12th April version
It works as it should also on my moded Estuary skin.
Well itās a mess with all the Testversions right now but we are moving at a fast development rate.
With this version a completely different output:
CoreELEC (community): devel-1555074085 (Amlogic.arm)
CoreELEC:~ # cat /sys/class/amhdmitx/amhdmitx0/config
cur_VIC: 16
cur_video_param->VIC=16
VIC: 16 1920x1080p60hz
Colour depth: 8-bit
Colourspace: YUV444
Colour range: default
EOTF: SDR
YCC colour range: limited
Colourimetry: BT.709
PLL clock: 0xdb1204f7, Vid clock div 0x000a339c
audio config: on
audio on/off: on
audio source: SPDIF
audio type: L-PCM
audio channel num: 2 channels
audio sample rate: 44.1kHz
audio sample size: MAX
3D config: off
CoreELEC:~ #
Does the script and skin work for you now?
Scratch thatā¦ I see your reply with it working
Here you go Ray as a massive thanks for all the work you put into this project hereās an Estuary MOD V2 version of DialogPlayerProcessInfo.xml for you
DialogPlayerProcessInfo.xml (16.9 KB)
Awesome! This is a nice gesture. Working good!
@roidy If you could fork the xbmc repo from CE github and create a pull request with the Estuary skin changes, that would be great.
Before I do that should I add the addon as a dependency to the skin? If so where do I put it as I have no repo. I have no real clue how this works.
The skin works fine without the addon you just donāt get the extra information.
We want to build your addon into the image, enabling it by default.
That way the changes in the skin should work right out of the box.
Ok, no problem, Iāll put together a pull request first thing tomorrow.
When I do the pull request should I just put the addon into xmbc/addons then?