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) - mstef - 2013-11-26 (2013-11-26, 16:19)Mangoes Wrote: I just tested the new nightly, which includes the commit with lmyllari's fix. I've also tested last build OpenELEC-Generic.x86_64-devel-20131126081257-r16438, xrandr autoexec disabled and blacks are not black, just grey even when 16-235 range is set. But there is strange behavior eather: Please select first Color range 16-235, then below reset settings to default - not the screen are darken and color range is unselected; Then check Colour range 16-235 - the screen are brighter, then unselect this setting - wow, the screen is even brighter There is some bug I suppose. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2013-11-26 (2013-11-26, 19:23)Mangoes Wrote:(2013-11-26, 18:58)gamble Wrote: And i decided that ill stick with the stable Build for now, i´m fed up of running from one problem into another I tried all the Nightlies since page 46 of this Thread and yeah things do get better but im tired of sitting 1-2 hours a day between the forums and the NUC triing to figure out the next step without getting stuck into a random Problem again...maybe on the weekend again when i have more spare time, but now after work i am totally NOT in the right mood (2013-11-26, 19:36)Ravetrancer Wrote:(2013-11-26, 18:58)gamble Wrote: For now i can shut off even while playing a movie and it stays off so i can't try Latest Frodo on OpenElec 3.2.3 Yes, autostart.sh with xandr for full range RGB, no IR cuz i only use my ipad to control it. No advanced settings (2013-11-26, 19:57)IBTB Wrote: I am however still not satisfied with the video. Don't know exactly how to set a word on it, but it's just like the video stutters a little bit (very little) and I have compared the same source (I notice it good on the intro in Disney movies) on other (physical) players I feel the picture is "floating" better than on the NUC. Yeah, i kinda feel the same for micro stuttering, never compared it to another device and in the beginning i thought it would be the 24p look..but i do know what u mean. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - arokh - 2013-11-26 The hit-stop-before-shutdown trick does work, confirmed here also. Have no idea why that would make any difference because XBMC is shutdown anyway. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-11-26 https://www.dropbox.com/s/99thzttxxdm9uoa/OpenELEC-Generic.x86_64-devel-20131125154034-r16441.tar is the build I'm using. It's based on the latest master, and adds my limited 16..235 passthrough hack. Remove any xrandr commands and don't use 16-235 in xbmc settings unless you know exactly what you're doing -> blacks and colors should work fine. I'll upload a 3.2 based build too with the fixes in a few hours. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Ravetrancer - 2013-11-26 (2013-11-26, 20:22)arokh Wrote: The hit-stop-before-shutdown trick does work, confirmed here also. Have no idea why that would make any difference because XBMC is shutdown anyway. So you pressed stop 1 extra time and it shut down like it should do right? Want to know because i sat for hours yesterday starting and shutting down the nucs to see when it worked and when it didnt work. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Mangoes - 2013-11-26 (2013-11-26, 21:29)lmyllari Wrote: https://www.dropbox.com/s/99thzttxxdm9uoa/OpenELEC-Generic.x86_64-devel-20131125154034-r16441.tar is the build I'm using. It's based on the latest master, and adds my limited 16..235 passthrough hack. Remove any xrandr commands and don't use 16-235 in xbmc settings unless you know exactly what you're doing -> blacks and colors should work fine. lmyllari, my hero (2013-11-26, 19:57)IBTB Wrote: My config (Running Frodo 12.2): Unless you have a lousy TV that doesn't support 24p (or 48p), always set: - Adjust display refresh rate to match video: ON There should be no stuttering with this. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2013-11-26 If i set the Adjust display refresh rate to match, Sound doenst work anymore.. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - zag - 2013-11-26 Thats a bug with the latest linux kernals, try a different refresh rate such as 50hz RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Mangoes - 2013-11-26 (2013-11-26, 22:37)gamble Wrote: If i set the Adjust display refresh rate to match, Sound doenst work anymore.. Which build? Stable? I never had this during the 2 years I have been using XBMC. Adjust display refresh rate to match should always be set to match to keep a smooth playback without stuttering. But with the gotham builds the xbmc gui refresh rate should be set to 23.98, otherwise passthrough doesn't work (and keep "Adjust display refresh rate to match", it will switch automatically and the sound passthrough will still work). edit: ah zag was a couple seconds faster, yea so if there's a bug.... but still, works fine for me. edit 2: and keep in mind that if Adjust display refresh rate to match is not ON, it is practically not possible to have smooth playback. This is the only way to avoid lost frames, unless you have a TV with very high refresh rates that can extrapolate to match. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-11-26 (2013-11-26, 22:41)zag Wrote: Thats a bug with the latest linux kernals, try a different refresh rate such as 50hzDo you have any more information on this? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - mstef - 2013-11-26 Using OpenELEC-Generic.x86_64-devel-20131126081257-r16438 NUC is power off every time, from remote and from GUI, S4/S5 disabled in BIOS, something was improved. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - zag - 2013-11-26 (2013-11-26, 22:48)lmyllari Wrote:(2013-11-26, 22:41)zag Wrote: Thats a bug with the latest linux kernals, try a different refresh rate such as 50hzDo you have any more information on this? http://openelec.tv/forum/68-audio/67227-no-sound-on-a-new-haswell-system-at-1080p Read my post #17 RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-11-26 (2013-11-26, 22:54)mstef Wrote: Using OpenELEC-Generic.x86_64-devel-20131126081257-r16438 NUC is power off every time, from remote and from GUI, S4/S5 disabled in BIOS, something was improved.Maybe the update to kernel 3.12.1? (2013-11-26, 23:05)zag Wrote: http://openelec.tv/forum/68-audio/67227-no-sound-on-a-new-haswell-system-at-1080pThanks. Looks like that patch hasn't made it to 3.2 branch. Maybe I should pass on the 3.2 build - there will be issues like this with it. Haswell seems to need recent bits, and more recent patches on top of that. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - mstef - 2013-11-27 You can try, we can test, please. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - ChopD - 2013-11-27 I have the following settings (Win 8.1, i3 NUC, Frodo 12.2): My config: Settings - Videos: - Render method: Auto Detect - Allow hardware acceleration (DXVA2): On - Adjust display refresh rate to match video: On - Sync playback to display: Off Settings - System - Video output: - Display Mode: Full Screen #1 - Resolution: 1920x1080p - Use a fullscreen window rather than true fullscreen: On - Vertical blank sync: Always enabled Seems to work fine. I'll admit I'm more of a casual user though, so don't know if these are considered the 'right' settings....if anyone more knowledgeable than me thinks I should be using something different then I'm happy to change and feedback the results. |