+- 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: Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 (/showthread.php?tid=165707)
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
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - AndyFurniss - 2014-12-21
(2014-12-20, 08:06)fritsch Wrote: We all can find out :-)
Here is a testvideo: https://dl.dropboxusercontent.com/u/55728161/fullrgb-video.mp4
fullrgb didn't have any sub/super to speak of - but then still useful.
I tested with that and a really full range ramp using mplayer (as I am used to it's behavior WRT specifying stretch/no stretch) and I was using Limited.
Confusing to test until I remembered that Limited is still full range, so it's somewhat the same if the player is stretching and the black level has been set around that.
Forcing the driver to flip between Automatic, Limited and Full did show that Automatic = Limited.
Handy to know anyway.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-21
:-) good. That I wanted to show.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-21
Code:
wget https://dl.dropboxusercontent.com/u/55728161/linux-headers-3.18.1-ickle75%2B_3.18.1-ickle75%2B-10.00.Custom_amd64.deb https://dl.dropboxusercontent.com/u/55728161/linux-image-3.18.1-ickle75%2B_3.18.1-ickle75%2B-10.00.Custom_amd64.deb
sudo dpkg -i *3.18.1*ickle*debRE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - Ney - 2014-12-22
(2014-12-21, 17:19)fritsch Wrote:Code:wget https://dl.dropboxusercontent.com/u/55728161/linux-headers-3.18.1-ickle75%2B_3.18.1-ickle75%2B-10.00.Custom_amd64.deb https://dl.dropboxusercontent.com/u/55728161/linux-image-3.18.1-ickle75%2B_3.18.1-ickle75%2B-10.00.Custom_amd64.deb
sudo dpkg -i *3.18.1*ickle*deb
And those are for? (yes the kernel 18.1 but what do they do?)
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-22
click: https://github.com/fritsch/linux/commits/ickle75
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - Ney - 2014-12-22
(2014-12-22, 08:06)fritsch Wrote: click: https://github.com/fritsch/linux/commits/ickle75
Interesting, especially the hang one, thx.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - menno - 2014-12-22
I think I got a hang on RC3 openelec
reverting back to the openelec from this thread!
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-22
"You think"?
Post logfiles or nobody can help you.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - d2kx - 2014-12-23
Kodi 14.0 Final is released... does it support AMD Catalyst using VAAPI under Linux?
It works great for me right now with XBMC 13.1 and 13.2, but I read about whitelisting in 14.0 and that it may not work anymore, so I am wondering and won't update for now.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-23
AMD Catalyst does not support multi threaded decoder contexts, it segfaults right over the place.
Keep 13.2 with an ancient kernel and fglrx will run. You won't have any postprocessing, no deinterlacing, nothing as fglrx does not implement VPP with their "in driver" wrapper. I told them howto fix that over at phoronix.com
I already changed xbmc's vaapi so that fglrx with vaapi will run in "theory", see the new advanced vaapi setting in the wiki, but yeah, it won't work - the same driver bug as 3 years ago, but this time without a chance for us to fix it, as their xvba wrapper is not now integrated.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - d2kx - 2014-12-23
(2014-12-23, 19:12)fritsch Wrote: AMD Catalyst does not support multi threaded decoder contexts, it segfaults right over the place.
Keep 13.2 with an ancient kernel and fglrx will run. You won't have any postprocessing, no deinterlacing, nothing as fglrx does not implement VPP with their "in driver" wrapper. I told them howto fix that over at phoronix.com
I already changed xbmc's vaapi so that fglrx with vaapi will run in "theory", see the new advanced vaapi setting in the wiki, but yeah, it won't work - the same driver bug as 3 years ago, but this time without a chance for us to fix it, as their xvba wrapper is not now integrated.
I will look into it, thanks.
Not sure why you mention an ancient kernel. I runs perfectly with Ubuntu 14.10 and Linux 3.16, haven't bothered trying newer kernels because there's no need to. Also not sure why I would care about post-processing etc., I take it this is mainly for watching TV etc.? Twitch.TV (using the Kodi Addon) Livestream (up to 1080p with 60 FPS) and all my 1080p Anime MKVs work perfectly fine with VAAPI on both my old AMD E-350 (HD 6310) notebook and my AMD R9 285 desktop. I am no longer part of AMD's closed beta program or I would have mentioned it to them, but I know that more video improvements are coming until the open source stack takes over completely.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-23
"Perfectly"?
It cannot even vsync. One core is constantly at 100%. Don't you see that with vsync turned on?
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - d2kx - 2014-12-23
Mmh sorry, can't confirm. It runs just fine on my slow, old, low-end notebook. It also runs fine with mpv instead of XBMC/Kodi. I disable compositing when my windows/video players are fullscreen (KDE setting), force Vsync and have Triple Buffering (it's called Tear-Free-Desktop in the AMD Catalyst Control Center, but it's just triple buffering) disabled (it's disabled by default though). I can see why it would not work with compositing enabled or triple buffering, but that's something for people to try who have problems...
Some sysinfo/kernel, driver, vainfo:
http://i.imgur.com/DhgcyQc.png
Kodi with Vsync forced:
http://i.imgur.com/vzqVgub.jpg
Kodi playing a 1080p Anime MKV:
http://i.imgur.com/h1HKp86.jpg
#edit:
Wanted to try 14.0 but the stable XBMC PPA has problems with Ubuntu 14.10 Utopic right now, the new 14.0 build depends on libafpclient0 but that is not avaible in the PPA and got removed in the Ubuntu repositories with Ubuntu 14.10. I guess it would work if I used the trusty .deb for this library but honestly don't feel like messing with it now.
#edit2:
ok, the dependency was in the XBMC Unstable PPA, so got 14.0 running. VAAPI was disabled by default as expected. I forced it through the advancedsettings.xml but, as noted by you, it works but freezes after about 1 second or so. Nevermind, back to 13.x and everything is working again. Will try to poke AMD about this.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2014-12-23
Mmhe, I thought that issues is still there: http://forum.kodi.tv/showthread.php?tid=211605
Oki, you can please link them my phoronix forum posts. I told how to secure their threading issue and also how to implement VPP-BOB.
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - noggin - 2014-12-24
Now that Kodi has officially hit version 14/Helix, is there an official release of OpenElec with the Intel GPU hang fix and VAAPI de-interlacing available, or should we stick to the one linked to in this thread?
(With apologies for slight thread hijack as this isn't strictly related to Ubuntu)
I saw
Code:
linux: Port fixes for gpu hang to 3.17Sorry - ignore me, just seen this : http://forum.kodi.tv/showthread.php?tid=211595&pid=1869160#pid1869160 (So OE 5.0.1 should hopefully see full VAAPI deinterlacing for Haswell and Intel hang fix?)