Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server (/showthread.php?tid=231955) 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
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
|
RE: New Era: VAAPI with EGL interoperation - Sunflux - 2015-10-09 (2015-10-09, 17:58)briancl Wrote: I am using a video test pattern to count bars. It's pretty easy to see the different because they are either flashing or not. Assuming your PC is outputting on HDMI1, you need to add Code: xrandr --output HDMI1 --off; xrandr --output HDMI1 --auto to your autostart.sh for passthrough to work correctly. This won't harm other settings. Incidentally... you state you have nothing in your autostart.sh... are you setting your xrandr setting via SSH or something? Because that does NOT work correctly for passthrough mode. It's doesn't reset the display correctly, and thus doesn't take effect until you change refresh rates. Otherwise, your color range setting should ALWAYS be in autostart.sh, for example Code: xrandr --output HDMI1 --set "Broadcast RGB" "Video 16:235 pass-through" RE: New Era: VAAPI with EGL interoperation - briancl - 2015-10-09 (2015-10-09, 18:06)Sunflux Wrote:(2015-10-09, 17:58)briancl Wrote: I am using a video test pattern to count bars. It's pretty easy to see the different because they are either flashing or not. I am setting via SSH... I will go back and try the testing again with setting color range in autostart.sh. Thanks! RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-10-09 The workaround also is in my Jarvis builds ... nothing to do. RE: New Era: VAAPI with EGL interoperation - briancl - 2015-10-09 Okay.. so this time I used the following syntax between each color range setting and ensured the refresh rate changed by stopping/starting black bar video. Code: xrandr --output HDMI1 --off; xrandr --output HDMI1 --auto The results are slightly different. It is still not making sense to me and no clear winner of a setting. The big question I have is why do I see black bars flashing below 16 when the driver is set to limited or passthrough? That is odd. Code: xrandr kodi lowest banding comments RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-10-09 Driver limited: all content no matter what range is rescaled. Driver pasdthrough: limited is signalled and video colors are untouched when! kodi is set to limited range. RE: New Era: VAAPI with EGL interoperation - Sunflux - 2015-10-09 (2015-10-09, 18:34)fritsch Wrote: The workaround also is in my Jarvis builds ... nothing to do. You said the exact opposite a few days ago... hard to keep track when nothing's announced! :-) (2015-10-09, 18:50)briancl Wrote: Okay.. so this time I used the following syntax between each color range setting and ensured the refresh rate changed by stopping/starting black bar video. Okay... any banding you see in passthrough mode is going to be from your projector (or the test pattern), and not Kodi. However, I am still mystified as to why the Kodi internal "Use Limited" setting is affecting the range of video output. Can you answer that one, Fritsch? I would take Passthrough and Limited and adjust your projector's contrast/brightness until the values show as correct. When in "Full" mode (which is what Passthrough is using) all data below 16 is being sent, and it's up to your display device to only show the correct ones. It's normal for adjusting the contrast/brightness to reveal "blacker than black".or "super white". That's a part of proper calibration. RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-10-09 (2015-10-09, 19:00)Sunflux Wrote:As the workaround worked I added it to Jarvis, too. See my post from a week ago.(2015-10-09, 18:34)fritsch Wrote: The workaround also is in my Jarvis builds ... nothing to do. Answer: when limited in kodi is not ticked the display shader upscales to full range when doing nv12 to rgb. No need to touch it twice. RE: New Era: VAAPI with EGL interoperation - briancl - 2015-10-09 Okay.. sounds reasonable... I'll go with Passthrough with Limited. Thanks for the help.. I appreciate it. RE: New Era: VAAPI with EGL interoperation - Sunflux - 2015-10-09 Okay, I thought I had read somewhere that the in-kodi setting didn't affect video rendering, but now I'm thinking that's only if VAAPI is disabled. In which case, I would definitely suggest that briancl work at calibrating the passthrough/limited option to see if it can be made acceptable. As for the workaround, I was still going off this! (2015-10-04, 22:00)fritsch Wrote: I added sunflux workaround to the Isengard build only .... for Jarvis you need autostart.sh workarounds. RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-10-09 (2015-10-09, 19:14)Sunflux Wrote: Okay, I thought I had read somewhere that the in-kodi setting didn't affect video rendering, but now I'm thinking that's only if VAAPI is disabled. Everything you read before this thread's code is most likely wrong. See my suggested settings some pages ago :-) This setting is a critical one. Directly hooks in after decode. Without it ticked everything is upscaled for vaapi and sw decode. Even vdpau uses it under a different name. Valid for this code in this thread. RE: New Era: VAAPI with EGL interoperation - lexi81 - 2015-10-10 (2015-10-02, 22:45)lexi81 Wrote:(2015-10-02, 22:14)fritsch Wrote:(2015-10-02, 11:45)Sunflux Wrote: Just in case you were wondering, here's a stress test log with VAAPI render disabled. Certainly not problem-free, but the system didn't crash and video was still playing fine when I rebooted. Fritsch, did that debug log give you any info. Or do you need a new one with a new build? RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-10-10 Limited Range just replaces the shader. It's even less it uses the same shader but with other coefficients. As you run the old nightmare sandybridge based Celeron 847 which gets hot like hell - check the temperatures, please. RE: New Era: VAAPI with EGL interoperation - Oshan Ruiz - 2015-10-10 I'm running the older fritsch OpenElec build: r21263 Am I missing anything with this latest test build? should I update? RE: New Era: VAAPI with EGL interoperation - mattlach - 2015-10-10 Starting to have some issues with my install from the old 14.04 thread. Considering doing a reinstall using this new method Is the OP post still pretty reasonable to follow, or do I need to read through over a hundred forum pages of incremental changes to get to the latest best practice? Thanks, Matt RE: New Era: VAAPI with EGL interoperation - mattlach - 2015-10-10 Starting to have some issues with my install from the old 14.04 thread. Considering doing a reinstall using this new method Is the OP post still pretty reasonable to follow, or do I need to read through over a hundred forum pages of incremental changes to get to the latest best practice? Thanks, Matt |