+- 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 - noggin - 2016-02-17
(2016-02-16, 09:03)scf2k Wrote:(2016-02-16, 00:02)fritsch Wrote: mediainfo or I am not interested
(2016-02-16, 00:56)noggin Wrote: Are they 8 or 10 bit? Are they 4:2:2 ? Are they interlaced ?
ProRes will rely entirely on CPU for decoding (there isn't a VAAPI ProRes implementation), though not sure if VAAPI rendering will deinterlace.
one http://pastebin.com/HiUiFi1r
two http://pastebin.com/VwqqzEYi
three http://pastebin.com/zecZ9s6Z
log http://pastebin.com/ssa629c4
Two may be a bit hopeful - it's 330Mbs 4:4:4, but one and three are 4:2:2 at sensible bitrates for ProRes 4:2:2.
As fritsch says, and as I suspect you realise, these will only be played back with CPU decode, and if the fffmpeg implementation is single-threaded it will require a pretty high spec CPU. From memory the ffmbc implementation of ProRes was a bit better than ffmpeg at one point, but I suspect the ffmbc stuff has been folded back into ffmpeg now. (Same is true for w3fdif and frame rate conversion code I hope. There's a not-terrible frame rate converter in ffmbc based on BBC work in the 80s. It's not Alchemist, but it is a lot better than frame drop/dupe)
I use ProRes 4:2:2 HQ 1080/50i a lot for my 'day job' and have no major issues with it in Quicktime player on a Quad Core i7 Macbook Pro (though no deinterlacing) and it plays back fine over a Thunderbolt HD-SDI/HDMI output device.
Not sure I've ever had much success with 'pro' codecs (ProRes, DNXHD, AVC Intra or DVC Pro HD) in Kodi though - I tend to transcode everything to 4:2:0 H264 if I want to play it in 'consumer' devices.
RE: New Era: VAAPI with EGL interoperation - fritsch - 2016-02-17
(2016-02-17, 15:54)movi Wrote: Hi
Just a simple question for those of us not using openelec and ubuntu, has all of this found it's way into upstream?
Yes - everything is in kodi v17 git repo. The drivers you need to search yourself. kernel (with the non upstream color range patch) you need to build yourself of course.
RE: New Era: VAAPI with EGL interoperation - incubus - 2016-02-17
(2016-02-17, 16:43)fritsch Wrote: Yes - everything is in kodi v17 git repo.
For ubuntu on braswell machines, is it still required to use FernetMenta ppa or xbmc-nightly ppa should be ok?
My guess would be yes for H.265 hw decoding...
RE: New Era: VAAPI with EGL interoperation - fritsch - 2016-02-17
No. All that code is pushed into kodi v17 branch.
You need the updated vaapi drivers / intel xorg drivers / modern kernel separately.
RE: New Era: VAAPI with EGL interoperation - incubus - 2016-02-17
In the case it was already working with FernetMenta ppa (as per the 1st post) a switch to xbmc-nightly ppa should not break it, right ?
RE: New Era: VAAPI with EGL interoperation - fritsch - 2016-02-17
(2016-02-17, 18:43)incubus Wrote: In the case it was already working with FernetMenta ppa (as per the 1st post) a switch to xbmc-nightly ppa should not break it, right ?
Yes.
New Era: VAAPI with EGL interoperation - VirtualRain - 2016-02-17
(2016-02-17, 10:44)scf2k Wrote:(2016-02-17, 09:51)VirtualRain Wrote: Refresh rate changes are not handshaking properly between my Mac Mini and AVR, (I need to unplug-replug the HDMI cable on every refresh rate change to get a signal)
You have this in EVERY change? There is a bug in intel driver which is not fixed yet. It makes handshakes to fail, but not always in my case.
I don't know. My workaround of running the GUI at 23.98 eliminates the need to change refresh rate on 99% of my content. It fails to Handshake on the odd video that's not 23.98.
Is there anything I can do to force Kodi GUI to 23.98 after booting without diving into the settings menu?
RE: New Era: VAAPI with EGL interoperation - incubus - 2016-02-17
Good! Many thanks fritsch!
RE: New Era: VAAPI with EGL interoperation - fritsch - 2016-02-17
(2016-02-17, 18:46)VirtualRain Wrote:(2016-02-17, 10:44)scf2k Wrote:(2016-02-17, 09:51)VirtualRain Wrote: Refresh rate changes are not handshaking properly between my Mac Mini and AVR, (I need to unplug-replug the HDMI cable on every refresh rate change to get a signal)
You have this in EVERY change? There is a bug in intel driver which is not fixed yet. It makes handshakes to fail, but not always in my case.
I don't know. My workaround of running the GUI at 23.98 eliminates the need to change refresh rate on 99% of my content. It fails to Handshake on the odd video that's not 23.98.
Is there anything I can do to force Kodi GUI to 23.98 after booting without diving into the settings menu?
DISPLAY=:0 /usr/lib/kodi/kodi-xrandr --mode 0xWTF <- whatever your 23.98 mode is ...
New Era: VAAPI with EGL interoperation - VirtualRain - 2016-02-17
(2016-02-17, 18:48)fritsch Wrote:(2016-02-17, 18:46)VirtualRain Wrote:(2016-02-17, 10:44)scf2k Wrote: You have this in EVERY change? There is a bug in intel driver which is not fixed yet. It makes handshakes to fail, but not always in my case.
I don't know. My workaround of running the GUI at 23.98 eliminates the need to change refresh rate on 99% of my content. It fails to Handshake on the odd video that's not 23.98.
Is there anything I can do to force Kodi GUI to 23.98 after booting without diving into the settings menu?
DISPLAY=:0 /usr/lib/kodi/kodi-xrandr --mode 0xWTF <- whatever your 23.98 mode is ...
Hmmm... Thanks, but I'm guessing this is going to cause a failed refresh rate change/handshake on boot. Currently, after a restart I go into settings, select 23.98 for GUI which causes a failed refresh rate change. I then pull/replug the HDMI to get a signal and I'm good to go until a restart. I gather this is still going to require an HDMI cord pull. I'm trying to find a solution that doesn't require my lazy ass to get off the couch
RE: New Era: VAAPI with EGL interoperation - fritsch - 2016-02-17
Fix the cause of the problem ... not its symptomes -> bugs.freedesktop.org
RE: New Era: VAAPI with EGL interoperation - jjslegacy - 2016-02-17
Why do you have to change refresh rate each boot? It's a saved setting. What am I missing?
RE: New Era: VAAPI with EGL interoperation - scf2k - 2016-02-17
(2016-02-17, 18:57)VirtualRain Wrote: Hmmm... Thanks, but I'm guessing this is going to cause a failed refresh rate change/handshake on boot. Currently, after a restart I go into settings, select 23.98 for GUI which causes a failed refresh rate change. I then pull/replug the HDMI to get a signal and I'm good to go until a restart. I gather this is still going to require an HDMI cord pull. I'm trying to find a solution that doesn't require my lazy ass to get off the couch
In my case switching source on AVR to something else and back helps restoring the signal.
RE: New Era: VAAPI with EGL interoperation - scf2k - 2016-02-17
(2016-02-17, 16:41)noggin Wrote: Two may be a bit hopeful - it's 330Mbs 4:4:4, but one and three are 4:2:2 at sensible bitrates for ProRes 4:2:2.
As fritsch says, and as I suspect you realise, these will only be played back with CPU decode, and if the fffmpeg implementation is single-threaded it will require a pretty high spec CPU. From memory the ffmbc implementation of ProRes was a bit better than ffmpeg at one point, but I suspect the ffmbc stuff has been folded back into ffmpeg now. (Same is true for w3fdif and frame rate conversion code I hope. There's a not-terrible frame rate converter in ffmbc based on BBC work in the 80s. It's not Alchemist, but it is a lot better than frame drop/dupe)
I use ProRes 4:2:2 HQ 1080/50i a lot for my 'day job' and have no major issues with it in Quicktime player on a Quad Core i7 Macbook Pro (though no deinterlacing) and it plays back fine over a Thunderbolt HD-SDI/HDMI output device.
Not sure I've ever had much success with 'pro' codecs (ProRes, DNXHD, AVC Intra or DVC Pro HD) in Kodi though - I tend to transcode everything to 4:2:0 H264 if I want to play it in 'consumer' devices.
Thanks for your detailed reply. Is the main problem with apple codecs is that implementation is not optimised? Or codec itself is that advanced that requires powerful hardware? I guess I'll just encode with H264/H265 high bitrate and it will play flawlessly then.
New Era: VAAPI with EGL interoperation - VirtualRain - 2016-02-17
(2016-02-17, 18:58)fritsch Wrote: Fix the cause of the problem ... not its symptomes -> bugs.freedesktop.org
Filed a bug months ago.
(2016-02-17, 19:18)jjslegacy Wrote: Why do you have to change refresh rate each boot? It's a saved setting. What am I missing?
It's not saving this setting for me.
Resets to 60Hz on a reboot.