+- 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 - Ivy Bridge (3rd Generation CPU) (/showthread.php?tid=140534)
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
RE: Intel NUC - HTPC possibilities - Roby77 - 2013-06-11
(2013-06-11, 11:24)jammyb Wrote: OpenELEC v3.0.5 is out.
Cured the blacks?
Anyone ?
RE: Intel NUC - HTPC possibilities - DrowningApe - 2013-06-12
Nope...
Intel NUC - HTPC possibilities - Cypher64 - 2013-06-13
(2013-06-11, 21:42)Roby77 Wrote:(2013-06-11, 11:24)jammyb Wrote: OpenELEC v3.0.5 is out.
Cured the blacks?
Anyone ?
I guess I got lucky. The blacks on my setup (i3 nuc, denon avr, lg lm8600 isf calibrated TV) are deep and clear.
This is without a doubt the best setup I've ever had. Openelec 3.0.5 hasn't changed the quality of the blacks for me, still deep and clear
RE: Intel NUC - HTPC possibilities - Kiruya - 2013-06-13
no worth
RE: Intel NUC - HTPC possibilities - Crssi - 2013-06-13
@Cypher64: Don't know about OE 3.0.5, but the problem with intel HD was (or still is), that blacks were too deep. And this is not the problem on OE side, but on Intel linux drivers side.
RE: Intel NUC - HTPC possibilities - bnevets27 - 2013-06-13
I looks like you can run a patched unofficial version that fixes the blacks without any autostart.sh or xrandr: http://www.openelec.tv/forum/67-display/62342-dark-picture-with-intel-ivy-bridge-system?start=90#75364
I've installed it but haven't had time to play with it yet
RE: Intel NUC - HTPC possibilities - Cypher64 - 2013-06-13
(2013-06-13, 08:57)Crssi Wrote: @Cypher64: Don't know about OE 3.0.5, but the problem with intel HD was (or still is), that blacks were too deep. And this is not the problem on OE side, but on Intel linux drivers side.
OH! I understand now, sorry I was thinking by Black Crush was another name Macroblocking during dark scenes.
Intel NUC - HTPC possibilities - DrowningApe - 2013-06-13
(2013-06-13, 17:04)Cypher64 Wrote:(2013-06-13, 08:57)Crssi Wrote: @Cypher64: Don't know about OE 3.0.5, but the problem with intel HD was (or still is), that blacks were too deep. And this is not the problem on OE side, but on Intel linux drivers side.
OH! I understand now, sorry I was thinking by Black Crush was another name Macroblocking during dark scenes.
I thought Black Crush was a Norwegian Black Metal band.
RE: Intel NUC - HTPC possibilities - Crssi - 2013-06-14
(2013-06-13, 17:18)DrowningApe Wrote:(2013-06-13, 17:04)Cypher64 Wrote:(2013-06-13, 08:57)Crssi Wrote: @Cypher64: Don't know about OE 3.0.5, but the problem with intel HD was (or still is), that blacks were too deep. And this is not the problem on OE side, but on Intel linux drivers side.
OH! I understand now, sorry I was thinking by Black Crush was another name Macroblocking during dark scenes.
I thought Black Crush was a Norwegian Black Metal band.
As usual your comment has no resolution value to users with problems.
RE: Intel NUC - HTPC possibilities - Ned Scott - 2013-06-14
(2013-06-14, 09:15)Crssi Wrote:(2013-06-13, 17:18)DrowningApe Wrote:(2013-06-13, 17:04)Cypher64 Wrote: OH! I understand now, sorry I was thinking by Black Crush was another name Macroblocking during dark scenes.
I thought Black Crush was a Norwegian Black Metal band.
As usual your comment has no resolution value to users with problems.
Thank god that's not a requirement, amirite? Now here's a funny youtube video that helps no one:
RE: Intel NUC - HTPC possibilities - z31fanatic - 2013-06-14
*update*
I replaced the RAM again with a single 8GB stick of Corsair Vengeance 1600 MHz and haven't had any crashes since I installed it (5 days now).
The memory I used before was 1333 MHz. Maybe the NUC doesn't like it even though it says that it supports it?
Anyway, all is good now.I am enjoying my XBMC NUC.
RE: Intel NUC - HTPC possibilities - ElJimador - 2013-06-14
(2013-05-30, 10:39)Geekzilla Wrote:(2013-05-29, 23:26)ElJimador Wrote: Well this is strange. Per crssi's links above I ran the xrandr --verbose command through SSH and it's reading my gamma settings as 0.84:0.84:0.84 despite the command in the autostart.sh setting to 1.20:1.20:1.20, plus I don't see any brightness setting at all. Still not sure what that gamma setting actually controls but looks like I'll have to do more testing to figure out what's going on w/this. PQ is still passable to me in the meantime but it would be nice to be able to do some fine tuning, and to know that whatever changes I'm making to these settings in the autostart.sh are actually sticking and that it's not just my imagination if I see a difference in PQ one way or another.
Make sure your autostart.sh is executable:
chmod +x /storage/.config/autostart.sh
Thanks but the xrandr --verbose command is still not returning the same values I've entered in the autostart.sh. When I tried changing the brightness to 1.05 and gamma to 1.15:1.15:1.15 it came back with brightness 1.0 and gamma 0.80:0.80:0.80; and then when I changed brightness to 1.10 and gamma to 1.20:1.20:1.20 it came back with brightness 1.0 and gamma 0.71:0.71:0.71. And as far as the actual picture, I can't tell any difference between any of them. I'm thinking when I thought I noticed a difference before it must have just been a placebo effect. Because this is just screwy. Nothing I do changes the brightness, and gamma goes in the opposite direction I'm trying to change it (whatever gamma even is).
Oh well. If it was really a problem I'd just try the test build that supposedly deals with this. I just didn't want to risk it messing anything else up when I finally got OE working for me just fine otherwise. It's just annoying to know there is the potential for tweaking through the autostart.sh but that I can't actually get it do what I tell it to.
RE: Intel NUC - HTPC possibilities - arokh - 2013-06-15
(2013-06-14, 15:23)z31fanatic Wrote: *update*
I replaced the RAM again with a single 8GB stick of Corsair Vengeance 1600 MHz and haven't had any crashes since I installed it (5 days now).
The memory I used before was 1333 MHz. Maybe the NUC doesn't like it even though it says that it supports it?
Anyway, all is good now.I am enjoying my XBMC NUC.
Keep in mind that you should use two sticks to get dual-channel memory. Not a big deal but you want the most out of your NUC right
RE: Intel NUC - HTPC possibilities - Raytestrak - 2013-06-15
(2013-06-14, 22:19)ElJimador Wrote: Oh well. If it was really a problem I'd just try the test build that supposedly deals with this. I just didn't want to risk it messing anything else up when I finally got OE working for me just fine otherwise. It's just annoying to know there is the potential for tweaking through the autostart.sh but that I can't actually get it do what I tell it to.
Do you see a difference when running the command from ssh? Changing the setting is instant, so it's easy to test what value works for you.
RE: Intel NUC - HTPC possibilities - Bjur - 2013-06-15
Does anyone know if you can run 1 of the HDMI ports to tv and 1 HDMI ports through receiver and get stereo and surround to work in xbmc?