As far as I know, only Kodi addons can use executeJSONRPC. To use it you’d either have to modify the keymap editor addon, or create your own addon to use with the unmodified keymap editor addon.
There may be a cleaner, simpler way to do this, but I don’t know how.
Hum. Not that easy as the VS10 addon would need to ask for a mapping, store it, append the remote.xml, and check continuously if the remote.xml has changed to reapply the modification.
I guess the easiest and dirtiest way would be to overwrite the keymap editor.
The current settings can be queried with JSON-RPC API, for example:
curl -X POST -H "Content-Type: application/json" -d '[
{"jsonrpc":"2.0","method":"Settings.GetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr8"},"id":1},
{"jsonrpc":"2.0","method":"Settings.GetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr10"},"id":2}
]' http://127.0.0.1:8080/jsonrpc
This would return the value for coreelec.amlogic.dolbyvision.vs10.sdr8 & coreelec.amlogic.dolbyvision.vs10.sdr10. Based on that, a script could issue
DV conversion off
curl -X POST -H "Content-Type: application/json" -d '[
{"jsonrpc":"2.0","method":"Settings.SetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr8","value":5},"id":1},
{"jsonrpc":"2.0","method":"Settings.SetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr10","value":5},"id":2}
]' http://127.0.0.1:8080/jsonrpc
DV conversion on
curl -X POST -H "Content-Type: application/json" -d '[
{"jsonrpc":"2.0","method":"Settings.SetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr8","value":0},"id":1},
{"jsonrpc":"2.0","method":"Settings.SetSettingValue","params":{"setting":"coreelec.amlogic.dolbyvision.vs10.sdr10","value":0},"id":2}
]' http://127.0.0.1:8080/jsonrpc
The above should also be possible through executeJSONRPC
If you’ve not checked it out yet, may I suggest looking at Dovi_Scripts and investing time in proper DV conversion via the 3-1 workflow. It takes time but only has to be done once per film and I’ve found the results to be well worth it.
For the time being I’ve ended up with your curl solution. I use a script launcher, a menu with the settings I want to CURL, and a xml keymap. Quite simple if not elegant, as it still need HTTP remote control. Thank you for your help.
@cpm
Thank you for the lossy atmos indication, and for the cm4 cm2 type.
Great work again. 
Yes, thank you too, it’s really good.
@cpm Thanks for the new A5 build.
I did spot two typo’s in the new “Prefer conversion over original Dolby Vision” 
(it says “Perfer convertion”).
Gotta say thank you to CPM
Thank you @cpm for everything you do. I would like to understand what the letters/numbers after the cm2,9/cm4.0 mean.
Appreciate adding this toggle. There are several static DV/HDR10+ hybrids that I can snatch now.
Happy to see what is apparently in the A5 build, from the comments here, but is there somewhere I should be looking to see what is in any particular update?
I can’t seem to find a way to message you and the guide topic for AM6B+ is closed now, but in this point:
5. Copy the appropriate dtb file, e.g. g12b_s922x_ugoos_am6b.dtb file to the root of your COREELEC flash drive rename it dtb.img
I humbly suggest to make an extra point for the renaming portion. It wasn’t even my first go but I completely missed it while following the guide.
@cpm could you please look at mediainfo for ‘Eizan Electric Railway’ or 4K Night View (2016)? I believe you have both.
I noticed there is very few content that is considered “PQ10” HDR by MediaInfo. It is somewhere between SDR and HDR10/DV, maybe adjacent to HLG and a precursor format to HDR10/DV. VS10 identifies PQ10 HDR files as HDR format and converts to DV. They also trigger HDR on my TV.
Do you know much about this? Does it have similar bug in Amlogic as HLG and should be left alone from VS10 conversion instead?
A few MediaInfo files. First is 4K SDR:
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 44 min
Bit rate : 65.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.327
Stream size : 47.7 GiB (92%)
Writing library : ATEME Titan File 3.9.12 (4.9.12.4)
Language : English
Default : Yes
Forced : No
Color range : Limited
**Color primaries : BT.709**
**Transfer characteristics : BT.709**
Matrix coefficients : BT.709
Source : Pathe Blu-ray
Next is PQ10 HDR:
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 42 min 35 s
Bit rate : 85.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.428
Time code of first frame : 01:00:00:00
Stream size : 25.3 GiB (98%)
Default : Yes
Forced : No
Color range : Limited
**Color primaries : BT.2020**
**Transfer characteristics : PQ**
Matrix coefficients : BT.2020 non-constant
Last is standard 4K HDR10:
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
**HDR format : SMPTE ST 2086, HDR10 compatible**
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 44 min
Bit rate : 35.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.176
Stream size : 25.6 GiB (87%)
Writing library : ATEME Titan File 3.7.8 (4.7.8.0)
Default : Yes
Forced : No
Color range : Limited
**Color primaries : BT.2020**
**Transfer characteristics : PQ**
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0000 cd/m2, max: 1000 cd/m2
Note the difference between PQ HDR and HDR10 on HDR format. I think PQ HDR is using the older ‘SMPTE ST 2084’ transfer function vs HDR10 (ST 2086). I found this article explaining PQ HDR (and derivative formats) and HLG, maybe interesting:
Ctrl+F ‘PQ10’ in above. Discussion starts on page 26
I found a file that worked on previous versions, but seems to be crashing the player on A5 version.
You may have it already, it is “Timescapes” which is DV P8 / HDR10+. I do not have the new setting, prefer conversion over original DV turned on. I do have HDR10 → DV activated.
One question for cpm , its about system led light
I got Homatics R 4K Plus , A5 build installed , no problem with that configuration
Led light on box is allways ON , cant find anywhere in settings to turn em OFF , in NE build that is easy , is it possible to add that possibility in Your build ?
Thanks for this build
Use CoreElec homatics Led addon
Tnx
Completly forgot that addon
Is it possible to install cpm’s current build over the latest nightliy build to get advantage of the new buffering code (since october 17th) which seems to fix the dv seeking / stutterin issues or will the be intergrated into cpm’s builds?
Its integrated in the A5.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice