+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222)
+--- Forum: Hardware (https://forum.kodi.tv/forumdisplay.php?fid=112)
+--- Thread: Intel Apollo Lake (/showthread.php?tid=270298)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
RE: Intel Apollo Lake - movie78 - 2017-04-05
@piotrasd is HDR working on your build? I am using windows, for now, thinks of a dual boot with LE.
RE: Intel Apollo Lake - HDGMA - 2017-04-05
https://downloadcenter.intel.com/download/26669/
Intel 21.20.16.4627 graphics driver for Apollo Lake.
RE: Intel Apollo Lake - piotrasd - 2017-04-05
HDR for sure no ... Thy just implementing full support HDMI 2.0 and mostly for next gen Gemini Lake. I don't think if that even work before on Linux. On Windows working HDR ?
RE: Intel Apollo Lake - Nekromantik - 2017-04-05
(2017-04-05, 16:49)piotrasd Wrote: Here build Kodi agile with inputstream.adaptive (default disable - so you must enable manual in addons)This build include 10bit hevc?
https://www.sendspace.com/file/w6ggc8
Other changes
- Fixed by peak3d issue with crash when you stopped video in Netflix addon
- Mesa 17.0.3, libva vaapi 1.8.0. Ffmpeg 3.3
- kernel 4.11rc5 (drm-nighlty-intel) + patch for all 4k CEA modes
http://nmacleod.com/public/libreelec/getwidevine.sh here script for install libwidevine what need Netflix
(just execute from ssh)
https://github.com/asciidisco/plugin.video.netflix here addon
(in Nextflix addon settings put your email and pass, also in inputstream.adaptive settings change resolution to MAX if you want get 1080p from netflix
and enable Dolby sound)
Sent from my Nexus 6P
RE: Intel Apollo Lake - piotrasd - 2017-04-05
Yes
RE: Intel Apollo Lake - Nekromantik - 2017-04-05
(2017-04-05, 19:15)piotrasd Wrote: Yes
thanks
RE: Intel Apollo Lake - movie78 - 2017-04-05
(2017-04-05, 17:57)piotrasd Wrote: HDR for sure no ... Thy just implementing full support HDMI 2.0 and mostly for next gen Gemini Lake. I don't think if that even work before on Linux. On Windows working HDR?
The Kaby lake and Apollo lake can play 4K 10bit HDR file, the only issue the metadata in HDR file is outputting.
RE: Intel Apollo Lake - fritsch - 2017-04-05
(2017-04-05, 20:45)movie78 Wrote:(2017-04-05, 17:57)piotrasd Wrote: HDR for sure no ... Thy just implementing full support HDMI 2.0 and mostly for next gen Gemini Lake. I don't think if that even work before on Linux. On Windows working HDR?
The Kaby lake and Apollo lake can play 4K 10bit HDR file, the only issue the metadata in HDR file is outputting.
Could you show me this metadata, that is ignored? Or are you talking about the missing 10 or 16 bit precision visuals?
RE: Intel Apollo Lake - movie78 - 2017-04-05
(2017-04-05, 21:25)fritsch Wrote:Width : 3 840 pixels(2017-04-05, 20:45)movie78 Wrote:(2017-04-05, 17:57)piotrasd Wrote: HDR for sure no ... Thy just implementing full support HDMI 2.0 and mostly for next gen Gemini Lake. I don't think if that even work before on Linux. On Windows working HDR?
The Kaby lake and Apollo lake can play 4K 10bit HDR file, the only issue the metadata in HDR file is outputting.
Could you show me this metadata, that is ignored? Or are you talking about the missing 10 or 16 bit precision visuals?
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (23976/1000) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Writing library : x265 1.9+96-b09998b1256ed8e6:[Windows][GCC 5.3.0][64 bit] 10bit
Encoding settings : wpp / ctu=64 / min-cu-size=8 / max-tu-size=32 / tu-intra-depth=4 / tu-inter-depth=4 / me=3 / subme=5 / merange=92 / rect / amp / max-merge=5 / temporal-mvp / no-early-skip / rdpenalty=0 / tskip / no-tskip-fast / no-strong-intra-smoothing / no-lossless / cu-lossless / no-constrained-intra / no-fast-intra / no-open-gop / no-temporal-layers / interlace=0 / keyint=24 / min-keyint=2 / scenecut=40 / rc-lookahead=60 / lookahead-slices=0 / bframes=0 / bframe-bias=0 / b-adapt=2 / ref=5 / limit-refs=0 / limit-modes / no-weightp / weightb / aq-mode=1 / qg-size=32 / aq-strength=1.00 / cbqpoffs=0 / crqpoffs=0 / rd=6 / psy-rd=1.00 / rdoq-level=2 / psy-rdoq=1.00 / no-rd-refine / signhide / no-deblock / no-sao / no-sao-non-deblock / no-b-pyramid / cutree / no-intra-refresh / rc=crf / crf=0.0 / qcomp=0.60 / qpmin=0 / qpmax=51 / qpstep=1 / vbv-maxrate=100000 / vbv-bufsize=30000 / crf-max=0.0 / ipratio=1.00
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : SMPTE ST 2084
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312680 y=0.329000
Mastering display luminance : min: 0.0005 cd/m2, max: 1000.0000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 400 cd/m2
RE: Intel Apollo Lake - piotrasd - 2017-04-05
@movie78 i know it can play but that dosent mean it will displayed in HDR mode on TV
@fritsch here is nice docu. about HDR on linux https://www.x.org/wiki/Events/XDC2016/Program/xdc-2016-hdr.pdf
RE: Intel Apollo Lake - fritsch - 2017-04-06
That's what I meant. Sending metadata is sth. completely different than outputting > 8 bit. Even on Windows Kodi does nothing to send this metadata explicitly.
RE: Intel Apollo Lake - fritsch - 2017-04-06
To be more precise: if the decoder does not handle it for us, nothing will reach the display at all. On the other hand if the decoder evaluates that info for us, like ffmpeg ac3 metadata handling, no need to send the metadata, cause interpreting has already happened. In that case 16 bit visuals and forced > 8 bit output would be enough.
I can think of shaders doing such transforms prior to rendering but that's it.
RE: Intel Apollo Lake - Nekromantik - 2017-04-06
@fritsch would it help seeing how they done it for Kodi on Android?
Or are the differences between Android and Linux too far that it wont help at all.
RE: Intel Apollo Lake - fritsch - 2017-04-06
Lol :-). Nothing is done there in Kodi at all. It's the decoder decoding to a Blackbox surface and from here it is rendered without any influence by Kodi.
RE: Intel Apollo Lake - fritsch - 2017-04-06
(2017-04-06, 10:28)fritsch Wrote: Lol :-). Nothing is done there in Kodi at all. It's the decoder decoding to a Blackbox surface and from here it is rendered without any influence by Kodi.To add: the TV indicates 10 bit, but it does the very same for non HDR output on Modeswitch. That's what I said above: fully transmitting metadata works exactly nowhere.
Btw. On linux the Intel drivers do depending on the mode 12 bit with back and force dithering..
Long story short: don't trust the TV :-), but make sure the decoder does incorporate the metadata handling and output surface has enough precision and visuals also have and driver does not dither around :-).
So. What of the mentioned points works correctly on android? Or why does the TV indicates HDR even if you don't play that material?