Intel NUC - Haswell (4th Generation CPU) - Printable Version +- 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 NUC - Haswell (4th Generation CPU) (/showthread.php?tid=176718) 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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
|
RE: Intel NUC - HTPC (Haswell Late 2013 edition) - pigr8 - 2014-12-25 anyone expecting IR Remote lag on OpenElec latest builds? it's the only thing that is driving me crazy, on XBMCbuntu or the new Kodibuntu everything is working fine RE: Intel NUC - HTPC (Haswell Late 2013 edition) - sat4all - 2014-12-25 (2014-12-25, 07:58)pigr8 Wrote: anyone expecting IR Remote lag on OpenElec latest builds? it's the only thing that is driving me crazy, on XBMCbuntu or the new Kodibuntu everything is working fine no problem here using RC3 build. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - a5ian300zx - 2015-01-03 Hi, I am getting the gui error and kodi refuses to launch. OS is Widows 8.1 on Intel nuc i5 Haswell. I was rdp to the nuc using my pc if that makes any difference? I recently installed bonjour services for zeroconf to work. Any ideas as I have removed and reinstalled kodi from fresh with same issue? Thanks RE: Intel NUC - HTPC (Haswell Late 2013 edition) - a5ian300zx - 2015-01-04 I fixed it by deleting the guisettings file in app data - > roaming. Thanks RE: Intel NUC - HTPC (Haswell Late 2013 edition) - myst4ry - 2015-01-17 Sometimes my NUC doesn't respond to my Logitech Harmony Smart Control remote, and I need to reboot the NUC, and then it works. Anyone know how to fix this bug? It only appears like 1/10 times I turn it on. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - noggin - 2015-01-17 This may be of interest to many here : https://communities.intel.com/thread/59216 Looks like new Windows Intel drivers will support H265/HEVC hardware decoding (I believe using shaders for GPU compute as well as the existing hardware acceleration engine used for H264/MPEG2/VC-1?) for 8 bit content on the i3 and i5 Core CPUs in Haswell NUCs? That's quite a bonus. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - rasmu - 2015-01-20 Hi, I have the D34010WYK with Windows 7.1 and it often powers up itself just after a shutdown. The solution is to disable Wake on Lan or to enable Deep s4/s5 (last one disable the wake with IR remote). Has someone find a solution which keep WOL and IR wake working ? Thanks. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - kuro9381 - 2015-01-21 Going back to the discussion about getting optimum black levels and the 16-235 limited range setting in combination with with full or limited RGB output... (2014-07-21, 17:23)lmyllari Wrote: It is possible to patch the driver to allow untouched output with infoframes telling it is limited range. This should work on all TVs and matches what a standalone player typically does. Is this patch available and can I apply it to my linux build of kodi? Passing through the original 16-235 values without expanding to full range and then scaling down again seems like a very worthwhile feature that should be part of the standard build? My setup:
I get good results on the projector by enabling the 16-235 limited range setting in Kodi, setting "Enhanced Range" on the projector HDMI input settings, and setting full range output in xrandr: Code: xrandr --output HDMI1 --set "Broadcast RGB" "Full" -d :0 Playing "1-Black Clipping.mp4", the '17' bar flashes very faintly but is still distinguishable from reference black (16). If I don't set Enhanced Range on the projector, blacks in the 1-Black Clipping.mp4 test file are badly crushed. On the plasma, using all 4 possible combinations of xrandr range setting and the Kodi 16-235 limited range setting, I'm not quite happy with the results and am seeing some black crush - Even if I turn up the brightness on the plasma, 16-20 or so are basically still black and almost indistinguishable. Apart from lmyllari's patch, is there anything I can try changing apart from the xrandr full/limited and kodi limited range on/off settings? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Diapason - 2015-01-21 Are you setting your Kuro to colour space 3 setting when doing the tests? I know I had to manually set that on mine or else it wouldn't be detected properly. (In fairness, it sounds like you know what you're doing, so you probably are.) I know that I had to turn brightness up a single notch to be happy that I wasn't crushing blacks, but I've been delighted with it ever since. I don't know where it falls on the 16-20 range, but a 2% black test is clearly visible above reference black. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - kuro9381 - 2015-01-21 (2015-01-21, 16:33)Diapason Wrote: Are you setting your Kuro to colour space 3 setting when doing the tests? I actually hadn't tried changing the Colour Space setting on the TV, thanks. What HDMI output setting (auto/full/limited) and Kodi limited range setting (enabled/disabled) are you using in combination with Colour Space 3? With my current xrandr output setting = Full and enabling 16-235 limited range in Kodi, Colour Space 4 (RGB 0-255) gives better results than 3 (16-235) playing 1-Black Clipping.mp4. With brightness +2 on the TV I can just make out level 17, with +1 it's too close to call. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Diapason - 2015-01-21 That's odd. I've xrandr set to output full, I have limited range enabled in Kodi, and colour space 3 (16-235) set on the TV, brightness is set to +2 on the TV and that seems just about right... This is with a KRP-500M. I assume 1-Black Clipping.mp4 is on the AVS HD 709 thingummy? I downloaded it once but never actually tried it, so maybe I should give it a go. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Matt Devo - 2015-01-21 (2015-01-21, 18:28)Diapason Wrote: That's odd. I've xrandr set to output full, I have limited range enabled in Kodi, and colour space 3 (16-235) set on the TV, brightness is set to +2 on the TV and that seems just about right... This is with a KRP-500M. if you're using xrandr to set full range (0-255) output, then your TV needs to be set to match (so, color space 0). If you're a limited range on your TV, then you wouldn't need to use xrandr and you should leave the Kodi setting at default (non-limited range) RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2015-01-21 (2015-01-21, 18:18)kuro9381 Wrote:With my KRP-500m, I use xrandr to set GPU to full range (only way to get untouched signal out, although infoframes will now confuse the display), Kodi set to limited range and the display set to limited range RGB input (otherwise it will obey the infoframes and expect full range input, giving a washed out picture).(2015-01-21, 16:33)Diapason Wrote: Are you setting your Kuro to colour space 3 setting when doing the tests? I need to slightly raise the brightness too to get the lowest levels to show (+1 or +2 I think). It doesn't raise the black level yet, and the same setting is needed with other devices too. edit: did you remember to enable swfilter (if you're using Gotham) / disable prefer VAAPI rendering (if you're using Helix)? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Diapason - 2015-01-21 That's exactly what I'm doing, lmyllari, and I'm doing it because you suggested exactly this a while ago! While there are various ways of ensuring correct black levels, this was the best picture I could get in terms of banding. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2015-01-21 (2015-01-21, 18:41)Matt Devo Wrote:When using xrandr to set full range output, the TV needs to be set to match the Kodi setting. If Kodi is set to limited range, then the TV needs to be set to limited range too (although some TVs like Panasonic plasmas ignore the infoframes and always expect a limited range signal).(2015-01-21, 18:28)Diapason Wrote: That's odd. I've xrandr set to output full, I have limited range enabled in Kodi, and colour space 3 (16-235) set on the TV, brightness is set to +2 on the TV and that seems just about right... This is with a KRP-500M. Everything at default (the same as setting limited range with xrandr and full range in Kodi) provides properly tagged limited range signal, but the levels are scaled twice (first by Kodi limited->full range, then by GPU full->limited range), causing banding and clipping BtB and WtW. (PC monitors will get a full range signal, but that is still scaled once and has the same problems.) |