+- 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: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - Rumpelstiltskin - 2018-05-27
(2018-05-27, 10:45)fritsch Wrote:Sure, here we go : https://mega.nz/#!Z5hwFKzI!U3zmtAHAf6K_aSyxmyEzMsoSXdTwewMEZudW6hJNBFs(2018-05-27, 10:28)Rumpelstiltskin Wrote: Hi @fritschGood - we have a bugreport for this EAC3 already ... can you post a 100 MB sample of this file using dd?
I can not try Librelec because my nuc does not go (and I do not understand the reason) with the USB boot.
Today I updated to this release 2:18.0+git20180527.0201-0cc5e0f-0bionic and now it seems to work all well as before except the movies in E-AC3 that are out of sync: my AVR go well in e-AC3 But the audio comes 1 second after
Just a little pleasure, can you confirm that this file is out of sync even in your system?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-05-27
Quote:[ffmpeg/audio] eac3: Multiple frames in a packet.
AO: [pulse] 48000Hz 5.1(side) 6ch float
[ffmpeg/audio] eac3: Dependent substream decoding is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[ffmpeg/audio] eac3: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. ([email protected])
Edit: https://trac.kodi.tv/ticket/17871 <- all new information you can add here.
Edit2: Don't blame ffmpeg guys. They can decode it properly - it's most likely our fault in the EAC3 Syncer as decoding works fine also in kodi ... thx for the sample, please add a link to the report above.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - redbiro - 2018-05-27
(2018-05-26, 03:05)Jester1o1 Wrote: Has anyone done an update from 16.04 to 18.04?I'm also interested in it. Is there any issues?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-05-27
(2018-05-27, 19:50)redbiro Wrote:Basically you are on your own and if something breaks we cannot help you.(2018-05-26, 03:05)Jester1o1 Wrote: Has anyone done an update from 16.04 to 18.04?I'm also interested in it. Is there any issues?
ppa-purge all ppas before your start, after that do the usual upgrade. I did this on two machines and it worked. Though making a kodi backup and afresh installation is preferred.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - Jester1o1 - 2018-05-28
Thanks fritsch, understood. Thank you.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - ezechiel1917 - 2018-05-31
Hi, anyone knows if it is possible to mount removable devices to /media/<LABEL> instead of /media/kodi/<LABEL> ?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-05-31
Second answer: https://askubuntu.com/questions/214646/how-to-configure-the-default-automount-location - only our nightly has udisks2 support
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - Rumpelstiltskin - 2018-05-31
@fritsch
hey fritsch, any news for eac3 "bug"?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-05-31
(2018-05-31, 19:16)Rumpelstiltskin Wrote: @fritschNo - Nobody is working on it. Just disable EAC3 ...
hey fritsch, any news for eac3 "bug"?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - ezechiel1917 - 2018-05-31
(2018-05-31, 13:47)fritsch Wrote: Second answer: https://askubuntu.com/questions/214646/how-to-configure-the-default-automount-location - only our nightly has udisks2 supportThanks for this link, I have followed that + https://github.com/xbmc/xbmc/pull/13897
Unfortunately I can't get it working with latest nightly ppa / ubuntu 18.04 udisks2:
If a removable drive is already plugged when kodi starts, it is automounted to /media/<label> - that's what I would like (but if I unplug it and plug it again it will be mounted to /media/kodi/<label>
So once kodi is running, it automounts removable drives to /media/kodi/<label> for some reason
Any idea what could be wrong?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-05-31
No. On bootup it is auto mounted by the system for you and if plugged in later the mounts are done in kodi user's context.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - ezechiel1917 - 2018-05-31
Just to be more clear:
kodi started , removable drive not connected
sudo service kodi stop
plug in removable drive (no automount at this point)
sudo service kodi start - automount now appears in /media/<label>
unplug removable drive
plug in removable drive - automount now appears in /media/kodi/label>
is this expected behaviour?
My other box is kodibuntu (14.04 lts) with jarvis and removable drives are always automounted to /media/<label>.
Do you know if automount behavior was specific for this distribution or something changed in kodis automount handling code later on?
I'm not sure if I understand it correctly, but should it be possible to automount in 18.04 to /media/<label> when kodi is running and handling automount or not?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-06-01
To my knowledge kodi has nothing to do with the location, it's done by udisks and friends - depending on which user is currently running with appropriate permissions. Please open your own thread about this issue.
Final idea from arch wiki:
Quote:Mount to /media (udisks2)By default, udisks2 mounts removable drives under the ACL controlled directory
. If you wish to mount toCode:/run/media/$USER/
instead, use this rule:/etc/udev/rules.d/99-udisks2.rules# UDISKS_FILESYSTEM_SHAREDCode:/media
# ==1: mount filesystem to a shared directory (/media/VolumeName)
# ==0: mount filesystem to a private directory (/run/media/$USER/VolumeName)
# See udisks(8)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - ezechiel1917 - 2018-06-01
fritsch:
I've double checked all possible logs and found udisks2 can't automount removable device because it gets mounted faster by udevil to /media/kodi/<label>.
Solution:
sudo apt-get remove udevil
Now removable devices are always mounted with udisks2 udev rule from your link to /media/<label>
Thanks for your help.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 18.04 server - fritsch - 2018-06-01
ah! yes of course!!! I will remove udevil from the howto - it's not more needed for v18 or later.