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) - tutu - 2013-12-04 (2013-12-04, 15:59)micoba Wrote: Sorry, I didn't have time until now. Sorry the steps should be more clear. Set fan to min 20%, max 100% in the bios Boot openELEC Play a 1080p movie at 24 fps with no gui open Ssh into the nuc Then run sensors and report fan speed and temp I just want to see if the extra EUs in the i5 require more fan rpms or not over your i3 Thanks RE: Intel NUC - HTPC (Haswell Late 2013 edition) - docpaul - 2013-12-04 (2013-12-04, 17:06)quintixbox Wrote: Hi Guys, Thanks for the update. I think this is the direction I want to go with mine, as well. Quick question: how are the colors within XBMC rendering? Is the graphics driver being used correctly (presume that the changes in OpenELEC have made their way over to XBMC? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - ascl_ - 2013-12-04 (2013-12-04, 18:40)lmyllari Wrote: I cleaned up the obsolete builds. You can use nightlies instead, they have all those fixes and more. So the nightly's are still missing the 16-235 fix? Can you please point me towards that patch? Thanks RE: Intel NUC - HTPC (Haswell Late 2013 edition) - quintixbox - 2013-12-04 Mwaah, the colors are a tad off, a bit washed out compared to the OpenELEC nightlies and the great work lmyllari has been doing. But, still extremely watchable, in some cases less "dark" than the aforementioned tweaked OpenELEC builds I just made the NUC dualboot, so I have the best of both worlds. The changes in the OpenELEC nighlies are mostly system and kernel changes, xbmc itself is not responsible for driver/system/kernel issues, neither in Frodo or Gotham. So, no, the changes have and will never make their way over to xbmc. Give Mint a try, it's a pretty painless install and a nice distro. If you don't like it go for either dualboot or a fresh OpenELEC install. Cheers, Q RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-12-04 (2013-12-04, 22:12)ascl_ Wrote:The 16-235 range fix is in nightlies. It fixes the default output having grey blacks. See https://github.com/OpenELEC/OpenELEC.tv/pull/2776(2013-12-04, 18:40)lmyllari Wrote: I cleaned up the obsolete builds. You can use nightlies instead, they have all those fixes and more.So the nightly's are still missing the 16-235 fix? Can you please point me towards that patch? The only thing missing is my hack that allows you to output full range and tell the display it is a limited range signal. It is only usable with software decoding and Gotham. Consider it an expert setting for now. See https://github.com/laurimyllari/OpenELEC.tv/commit/57c2a927ac3de067d73190cf870d6be8b603144a RE: Intel NUC - HTPC (Haswell Late 2013 edition) - mattchapman - 2013-12-04 I was going to post a new thread but thought I'd just ask in here. What is the general appeal with the Intel NUC? Is it because it's so small? I'm about to build an HTPC and saw the NUC but it seems sort of expensive for what it is so I wondered what's so attractive about it. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - micoba - 2013-12-04 It's small, sexy, fast and energy efficient! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - philbio - 2013-12-04 New BIOS release (0022) https://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=3742&DwnldID=23455&lang=eng&iid=dc_rss RE: Intel NUC - HTPC (Haswell Late 2013 edition) - micoba - 2013-12-04 But not on the official site. Though it seems correct. Thanks from me. https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Desktop+Boards&ProductLine=Intel%C2%AE+NUC+Boards+and+Kits&ProductProduct=Intel%C2%AE+NUC+Kit+D34010WYK&ProdId=3742&LineId=3736&FamilyId=36 RE: Intel NUC - HTPC (Haswell Late 2013 edition) - quintixbox - 2013-12-04 No mention of an IR fix in the release notes: http://downloadmirror.intel.com/23455/eng/WY_0022_ReleaseNotes.pdf RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Peppin - 2013-12-05 What are the optimal video / playback settings for i3 Haswell NUC? I currently use the following, but I experience some skipped frames (not dropped) during playback of high bitrate videos System - Settings - Video output Code: Resolution: 1920x1080p System - Video - Playback Code: Render method: Auto detect Video settings (during playback) Code: Deinterlace video: Auto Any suggestions on settings that are not optimal? Thanks. -edit: I run OE generic r16441 RE: Intel NUC - HTPC (Haswell Late 2013 edition) - furii - 2013-12-05 (2013-12-04, 22:27)lmyllari Wrote:(2013-12-04, 22:12)ascl_ Wrote:The 16-235 range fix is in nightlies. It fixes the default output having grey blacks. See https://github.com/OpenELEC/OpenELEC.tv/pull/2776(2013-12-04, 18:40)lmyllari Wrote: I cleaned up the obsolete builds. You can use nightlies instead, they have all those fixes and more.So the nightly's are still missing the 16-235 fix? Can you please point me towards that patch? can you explain why one would want to output full range but tell the display it is a limited range signal? i'm currently using an nvidia card but am strongly considering switching to haswell and have been following your fixes which i assume translate to haswell in general and is not confined simply to the nuc. i have a vt50 and have yet to have it professionally calibrated (why bother when you aren't getting perfect input?) because of an issue i see with 1-Grayscale Ramp.mp4 where there is banding. from other posts on the forum it seems this is a result of xbmc expanding from limited to full and back or something. the comment in your commit leads me to believe this would be fixed. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Protax - 2013-12-05 Hi Selene, Just bought a Logitech Harmony Touch and followed your advice. Media Center Extender turns my NUC on/off, but the menu doesn't seem to work well... Can't go back out of menu's. For example: I pick TV Shows out of the main menu, but want to watch a movie... Can't come out of the TV Show folder anymore Do you have another device to control it? Gr, Protax (2013-12-04, 20:25)Selene Wrote: My power button doesn't work either. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Selene - 2013-12-05 (2013-12-05, 01:46)Protax Wrote: Hi Selene, Read up on configuration stuff here: http://openelec.tv/forum/12-guides-tips-and-tricks/3218-in-progress-harmony-one-complete-guide You probably just need to set your keys properly in customize buttons. That guide has everything you need. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-12-05 (2013-12-05, 00:51)furii Wrote:I have a professionally calibrated plasma and can recommend it.(2013-12-04, 22:27)lmyllari Wrote: The only thing missing is my hack that allows you to output full range and tell the display it is a limited range signal. It is only usable with software decoding and Gotham. Consider it an expert setting for now. See https://github.com/laurimyllari/OpenELEC.tv/commit/57c2a927ac3de067d73190cf870d6be8b603144a I think you mostly got the idea. It's not really about outputting full range, but rather not modifying the signal. The banding comes from expanding luma from 16-235 to 0-255. This is done for typical PC monitors, which expect a full range signal. New Intel linux drivers by default give TVs a limited range signal, taking the expanded 0-255 and scaling it to 16-235. This does not eliminate the banding that was created by the original expansion, and original information below 16 and above 235 was already lost in that same step. (Why do they do it? It's the right thing according to the standards, and some TVs don't like full range -> crushed blacks.) If the player software (xbmc in this case) decodes to 16-235 (meaning "don't change luminance, keep black at 16 and white at 235"), the video card outputs full range 0-255 (meaning "don't scale the levels, just output what you're given"), and display is set to limited range input (meaning "16 is black, 235 white"), we eliminate the banding in greyscale ramp (because the range is not scaled at any point) and keep blacker-than-black (luma values under 16) and white-than-white (luma values above 235). If your plasma defaults to limited range RGB (and doesn't listen to the infoframes in the HDMI stream) or you can set limited range manually, you don't need anything special. Just set your player software to 16-235 (which you can now do with Gotham and software decoding) and make sure the video card doesn't change the signal (the xrandr broadcast range "Full" setting mentioned a lot in this thread). In my case, the monitor obeys the infoframes (and there are other devices connected to the same input preventing a manual setting), so I need a patch to switch it to limited range without altering the video signal. |