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) - voip-ninja - 2014-03-20 (2014-03-20, 07:56)Crssi Wrote: Is this NUC Haswell thread? It is! Although you probably would not know this by last few pages of posts. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - axbmcuser - 2014-03-20 Hey there! i got a D54250WYKH Haswell-i5-NUC and use OpenELEC + DVB-C Live-TV + a "Limited RGB Range only" LCD. Im quiet happy with 3.2.4 (very stable Live-TV!) - but if i understand correctly there is nothing i can do to fix the greyish Blacks on my setup - switching to Full RGB Range is way too dark (and wrong for my Limited RGB Range LCD). I tried out some Nightlies and - yeah - the Black is fine - but in the Nightlies Live-TV is very unsteady/unusable for my setup. What can i do? Is there a mirror of the lmyllari old 3.2 based build with his RGB-Range fixes - or something else? Thank you very much. Greets RE: Intel NUC - HTPC (Haswell Late 2013 edition) - lmyllari - 2014-03-20 (2014-03-20, 15:13)axbmcuser Wrote: Hey there! This should still be available: (2013-11-27, 07:50)lmyllari Wrote: I've uploaded a 3.2 with color/black fixes to https://www.dropbox.com/s/htrw49uctfo1d0k/OpenELEC-Intel.x86_64-devel-20131126123813-r15940.tar RE: Intel NUC - HTPC (Haswell Late 2013 edition) - OllieB - 2014-03-21 (2014-03-19, 06:51)genyus Wrote:(2014-03-15, 17:51)OmBreNoiRe Wrote:(2014-02-22, 06:04)millercentral Wrote: No it is not the same remote codes, or even the same protocol (MCE is RC6, the Xbox One remote is nec1 protocol). Did it work out of the box or did you have to make changes? If so, how did you get it to work? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - genyus - 2014-03-22 This thread has all you need to know really but if you want the exact code I used for the files then send me a private message. http://openelec.tv/forum/103-infared-remotes/67150-how-to-make-your-remote-work-with-oe I found that each Xbox One remote used the same IR codes. I was able to use the same files for each NUC I have and they all work great. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - OllieB - 2014-03-22 (2014-03-22, 05:38)genyus Wrote: This thread has all you need to know really but if you want the exact code I used for the files then send me a private message. Excellent thread. Thank you! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - sat4all - 2014-03-22 Hey there, all was fine, till yesterday when i decided to create mysql database in my synology nas so i did also fresh OE beta2 reinstall. the problem is: xbmc start showing black bars for every single file i try. look at screenshot 1916x1076 > 1920x1027 WTF!!! why is does upscale x and downscale y! tried both hard and soft decoding > same result. last snapshot r17990 > same.. file over mysql database or local file doesn't matter. hard reset > same... Quick shot with ubuntu live stick and latest beta xbmc, the problem is not there. any suggestions? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - sat4all - 2014-03-22 switching off adjust display refresh rate to match video which is not an option for me, fixed the problem. so this is about 24p? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - xbs08 - 2014-03-22 Don't use zoom? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - sat4all - 2014-03-22 being replying to my self for the last few posts but finaly found it!!! it was guisetiings.xml problem: i found almost 1080p refresh rates except 60hz got wrong wrong pixel ration <pixelratio>0.952476</pixelratio> instead of <pixelratio>1.000000</pixelratio> how on earth we have these mess as default? (2014-03-22, 16:27)xbs08 Wrote: Don't use zoom?sure there was no zoom. thx anyway. RE: Intel NUC - HTPC (Haswell Late 2013 edition) - axbmcuser - 2014-03-23 Hey again, lmyllaris 3.2 build worked well for me. Tried it for some days now. Thanks again! Unfortunately i got a new problem today when i upgraded my D54250WYKH from BIOS version 0024 to 0025. With 0025 my DVB-C stick now freezes on the initial scan. I tried multiple installs and it's clearly a issue starting today after the update. So i downgraded to 0024 via removing the jumper. Loaded BIOS default settings (F9) and made the device powerless in between. No chance: My DVB-C stick now also crashes with 0024 as it started with with 0025. So - only way for a TRUE cmos reset is removing battery? RE: Intel NUC - HTPC (Haswell Late 2013 edition) - Peppin - 2014-03-24 (2014-03-20, 11:36)Peppin Wrote: Im currently experiencing troubles with DTS-MA rips.@fritsch, I followed your advice to run with sync vid to display (Video Clock), even with Haswell. Do you know anything about this "bug" with OE4 B1/2? Or is it just me.. Thanks a lot RE: Intel NUC - HTPC (Haswell Late 2013 edition) - fritsch - 2014-03-24 No - but I am already developing for gotham +1 which means ffmpeg bump and other features. Currently only doing PulseAudio backports that are really needed for gotham. Edit: I hope you also combine that with Adjust Refreshrate to match video _and_ you have the relevant modes, if those are missing (see my last lengthy post). RE: Intel NUC - HTPC (Haswell Late 2013 edition) - kouze - 2014-03-24 (2013-12-05, 02:17)lmyllari Wrote:Hi guys,(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'm actually facing this issue with my NUC Haswell I3 with the latest openelec gotham beta 2 with my Panasonic 50VT30 Plasma TV. Using only software rendering is not really an option as I saw some slow rendering issue with 1080p mkv files. I'm thinking using Gotham XBMC under Windows 8.1. Could it be an option to get good RGB signal on my TV? Thanks ! RE: Intel NUC - HTPC (Haswell Late 2013 edition) - noggin - 2014-03-24 lmyllari I follow what you say about losing <16 and >235 levels when 16-235 is scaled to 0-255, and that banding is introduced by spreading the 220 levels in the Limited source across 255 levels of the Full output. However shouldn't the scaling be complimentary, so that if you reverse it, the banding is removed - as the initial scale is across a wider range not a narrower range? Or are you saying that the two scales (LImited->Full and Full->Limited) that in an ideal world we want to avoid - aren't complimentary? I'm thinking of how the signal would fair through a basic LUT approach and how that would work for the mapping (without any dithering - as I don't believe dithering is usually used to mask the level scaling). Each Limited source level will still map to a unique Full output level, so it should be possible to reverse this with zero loss of original data (other than <16 and >235 that is inevitably losses as it is clipped) removing any banding that has been introduced? Or am I missing something - or do "real world" implementations make a mess of this? |