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) - Crssi - 2013-11-21 (2013-11-21, 07:45)lmyllari Wrote:(2013-11-20, 19:56)Alchete Wrote: I assume you're trying to build the driver/shader assembly directly in OpenELEC? Can you give a link to the source code and the steps you've taken to build it?https://github.com/laurimyllari/OpenELEC.tv/commit/1b4e60383167b62caacc48a39686d350008bf0f2 You are TZAR and true Wizard. This is really cool. Its "almost" perfect. Why "almost"... because it is a little too bright. But dont take this 100% sure, because I have tried this on uncalibrated monitor and will test again, perhaps this evening, on calibrated TV. Thank you man, i am sure you will change the future of NUC used for XBMC/OE. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Alchete - 2013-11-21 (2013-11-21, 15:58)Ravetrancer Wrote: There is nu such thing in my settings.The software multithreading option only has to do with two things: 1. The Nov. 20th (or later) OpenELEC build 2. Enabling "Expert" settings in that menu. Once you install the Nov. 20 build and enable Expert settings, it will appear in the menu as I showed in the screenshot. It has nothing to do with autostart.sh. If you have "Expert" settings enabled, I can only guess that you do not have the Nov. 20 build installed correctly. You can try that part again. Here's the software tank. Pick the Generic_x86_64 for the NUC: http://sources.openelec.tv/tmp/image/ RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Platypus2 - 2013-11-21 (2013-11-21, 15:52)Platypus2 Wrote: New windows 7 drivers? So far so good for me ! Fixed 4:3 and other random video green bars Hopefully no other problems arise RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Alchete - 2013-11-21 (2013-11-21, 07:45)lmyllari Wrote:Outstanding work! So, it sounds like all that's needed for a full solution is to detect whether the content is SD or HD and switch the coefficients appropriately...(2013-11-20, 19:56)Alchete Wrote: I assume you're trying to build the driver/shader assembly directly in OpenELEC? Can you give a link to the source code and the steps you've taken to build it?https://github.com/laurimyllari/OpenELEC.tv/commit/1b4e60383167b62caacc48a39686d350008bf0f2 Does the Intel driver detect content-type elsewhere? Maybe this is a question to post in your bug report. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2013-11-21 @lmyllari Just tried ur tweaked Version but it doesn't work for me, if i enable va-api i get a way too dark picture as usual with Full RGB Enabled and nothing else.. :/ RE: Intel NUC - HTPC (Haswell Late 2013 edition) - DeCaF76 - 2013-11-21 Hi folks. I'm a noob to this forum. I've had XBMC running on a Revo (win7) off and on for five years. I've skimmed through this thread, seen a few things that concern me, hoping I didn't jump the gun/bandwagon on these things. I received today: Intel NUC D34010WYK Intel 525 Series Lincoln Crest SSDMCEAC120B301 mSATA 120GB SATA III MLC Internal Solid State 2x Crucial CT102464BF160B PC3-12800 8GB DDR3-1600 CL11 SODIMM 204PIN Single Memory Module I have a 43' Samsung plasma, and a Yamaha soundbar. I need to go HDMI to TV, optical to bar. So I guess I need this I"m looking at getting new cables. I haven't used RedMere yet. Any reason why I shouldn't? Based on what I've read in this thread, my head is kind of spinney, and I honestly have no idea where to go with OS here. I don't have a non-OEM windows license right now. I'm not totally opposed to acquiring one, but I'd rather avoid it if I could. I think based on what's in this thread I can sort myself out, but I just have a few questions. As of right now, is there a Linux distro/XMBC combo that is working with the new gen NUC and any Intel driver version? If not, is it realistic to expect this will be resolved by the end of the year? Should I just say screw it and run Win 8.1? What remote should I be looking at? I'd like to use the on-board IR and not spend a lot of $, I'll break it inside a year. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Crssi - 2013-11-21 Which Yamaha soundbar do you have? I have on mine audio pass-trough over HDMI and dont need any optical cord. (2013-11-21, 16:42)gamble Wrote: @lmyllari True. Just tried with RGB Full. There is no change. But the change is visible on RGB Limited. I dont know, but think that the aim should be RGB Full I am wrong here? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - DeCaF76 - 2013-11-21 YS-101, no HDMI unfortunately RE: Intel NUC - HTPC (Haswell Late 2013 edition) - joelbaby - 2013-11-21 (2013-11-21, 16:49)DeCaF76 Wrote: I have a 43' Samsung plasma, and a Yamaha soundbar. I need to go HDMI to TV, optical to bar. So I guess I need this Why not just do NUC->TV via HDMI. TV->Soundbar via optical cable (like you probably already do)? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-11-21 (2013-11-21, 16:40)Alchete Wrote: Outstanding work! So, it sounds like all that's needed for a full solution is to detect whether the content is SD or HD and switch the coefficients appropriately...The Intel driver is already told the colorspace, it just doesn't use that information. It's all in the bug. Only tricky part is to figure out how to change the shader to have parameters to receive the correct coefficients - and that's because I haven't written Intel shaders before. For the Intel devs that should be easy. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - DeCaF76 - 2013-11-21 (2013-11-21, 17:09)joelbaby Wrote:(2013-11-21, 16:49)DeCaF76 Wrote: I have a 43' Samsung plasma, and a Yamaha soundbar. I need to go HDMI to TV, optical to bar. So I guess I need this I don't want my TV on when I'm just listening to music, I assumed it wouldn't pass through when off, I may be wrong, never tried. My Revo has optical and HDMI so it's never been an issue. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Selene - 2013-11-21 (2013-11-21, 16:36)Platypus2 Wrote:(2013-11-21, 15:52)Platypus2 Wrote: New windows 7 drivers? Sweet. Downloading later when I get home. That's the only thing that was wrong RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Ravetrancer - 2013-11-21 (2013-11-21, 16:35)Alchete Wrote:I did follow thedownload link in ur sucess post.(2013-11-21, 15:58)Ravetrancer Wrote: There is nu such thing in my settings.The software multithreading option only has to do with two things: Installed it, but i think it still said it was from 20131112 or 20131114. When i created the livestick it behaved very strange compared to all other times ive created livesticks My livestick was created in 2 seconds time. Usually the format takes some time and then the install some time. To create a livestick usually adds upp to 2-3 minutes but now its ready in 2 seconds, something maybe s wrong with the livestick? (2013-11-21, 08:01)lmyllari Wrote:Im also up for testing on both my i5 nucs.(2013-11-21, 06:22)Dropbear67 Wrote: if the driver is open sourced and should be fixed soon, why hasn't it been fixed with the previous gen nucs??Apparently only a few people noticed it at all. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - gamble - 2013-11-21 He already posted the link to his built, but sadly it doesn't work for me https://www.dropbox.com/s/fy6n5tz6y4jr5xm/OpenELEC-Intel.x86_64-devel-20131120202622-r15931.tar @lmyllari If u plan on doing another version for us to try could u base it on a Nightly ? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2013-11-21 (2013-11-21, 16:42)gamble Wrote: @lmyllari (2013-11-21, 17:00)Crssi Wrote: True. Just tried with RGB Full. There is no change. Black levels shouldn't have changed with this as they seemed correct before. Maybe your screens are set to display blacker-than-black (levels under 16)? [another edit: actually if the picture is too dark, it sounds like your screen expects limited range] To troubleshoot your problems: 1) Figure out which RGB range your TV expects. Use a bluray player or any other media source that you can use to play calibration patterns and set to RGB output. I suggest using AVSHD709 for patterns. Check with the basic tests that you have working settings either in full range or limited range. Make sure your source is set for neutral brightness/contrast. Take note of the lowest and highest visible values. 2) Use xrandr to select full or limited range, same as you used above. 3) Check black levels on xbmc using the same patterns. They should match. If your black levels don't match between steps 1 and 3, please report your reference device and the highest/lowest visible with each device. At the moment, it is not possible to get blacker-than-black (under 16) or whiter-than-white (over 235) with VA-API decoding. They are clipped by the colorspace conversion. If you need those, you will have to use software decoding for now. edit: Crssi: it doesn't matter if you aim for full or limited range at the moment. Use whichever your display defaults to. If you can set it to either, use full. |