Kodi Community Forum
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)



RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - teeedubb - 2017-02-20

(2017-02-19, 20:55)gurabli Wrote: fritsch, maybe you can help me, ot is somewhat off here, but still. If avr is in standby passtrough mode, so audio is sent from Kodi to TV speakers, can I still use my TV remote to controll Kodi with CEC? I plan to buy a new AVR that has hdmi standby passtrough, but not sure if it passes the CEC commands to Kodi if AVR is not turned on.

Sent from Tapatalk from my Z5 Compact

CEC works with my yamaha rx-v473 when it is off.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-02-20

Driver: has zero to do with Kodi. Was added for wsnipex ppa and 16.04, 16.10. Kodi is an application, not a os with drivers.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - gurabli - 2017-02-20

(2017-02-19, 21:03)fritsch Wrote: I don't know - never did something with CEC.

Sorry, I somewhat remembered you were using CEC, I was wrong then.

(2017-02-20, 03:35)teeedubb Wrote: CEC works with my yamaha rx-v473 when it is off.

Thanks teedubb, this is great to hear. The Denon should work then too!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Axman - 2017-02-27

Question: On the PPA page of Wolfgang Schupp's "xbmc-fernetmenta-master", it states:

Quote:Current highlight:
play HEVC 4k@60p videos on intel braswell and skylake CPUs

Does that mean it is no longer necessary to build Kodi-agile from source, and use mesa drivers from Padoka PPA to achieve this?
What about proper HD pass-through support, it too is supported in this Ppa?

Thanks!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - wsnipex - 2017-02-27

xbmc-fernetmenta-master is not updated anymore, everything is in mainline.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Axman - 2017-02-27

OK thanks. But is it true that "HEVC 4k@60p" is supported then, in mainline (unstable?) ?


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-02-27

No - it's not there. It's currently living in kodi-agile - inclusion of that work started yesterday with AudioEngine bits.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Axman - 2017-02-28

(2017-02-27, 12:14)fritsch Wrote: No - it's not there. It's currently living in kodi-agile - inclusion of that work started yesterday with AudioEngine bits.

Thanks for the clarification.
I've now installed latest mesa using Padoka PPA and built kodi-agile from scratch.. But, now I'm no longer able to reach Xserver. What is the correct forum to troubleshoot the use of these unofficial drivers, do you know?


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-02-28

www.ubuntuforums.org - a simple Xorg.0.log is required and you are allowed to take part in the party :-)


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Axman - 2017-02-28

Good call, I'll try thanks!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - barthand - 2017-02-28

(2017-02-27, 10:55)Axman Wrote: OK thanks. But is it true that "HEVC 4k@60p" is supported then, in mainline (unstable?) ?

(2017-02-27, 12:14)fritsch Wrote: No - it's not there. It's currently living in kodi-agile - inclusion of that work started yesterday with AudioEngine bits.

Sorry for (possibly) lame question, but what about support for hardware decoding of HEVC 10-bit @ 24-30 FPS?

Changelog for Krypton, at Linux-specific section clearly states:
Quote:Added support for HEVC Main 10 profile (10-bit) hardware video decoding via VAAPI if hardware support it

The reason I ask is exactly related to this - I have a HEVC 10-bit sample, rated at 24 FPS and Krypton 17.1 RC on Ubuntu doesn't use H/W acceleration in this case, while my vainfo would suggest it should be able to do so (see profile VAProfileHEVCMain10):

Code:
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :    VAEntrypointVLD
      VAProfileMPEG2Main              :    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointEncSlice
      VAProfileH264Main               :    VAEntrypointVLD
      VAProfileH264Main               :    VAEntrypointEncSlice
      VAProfileH264High               :    VAEntrypointVLD
      VAProfileH264High               :    VAEntrypointEncSlice
      VAProfileH264MultiviewHigh      :    VAEntrypointVLD
      VAProfileH264MultiviewHigh      :    VAEntrypointEncSlice
      VAProfileH264StereoHigh         :    VAEntrypointVLD
      VAProfileH264StereoHigh         :    VAEntrypointEncSlice
      VAProfileVC1Simple              :    VAEntrypointVLD
      VAProfileVC1Main                :    VAEntrypointVLD
      VAProfileVC1Advanced            :    VAEntrypointVLD
      VAProfileNone                   :    VAEntrypointVideoProc
      VAProfileJPEGBaseline           :    VAEntrypointVLD
      VAProfileJPEGBaseline           :    VAEntrypointEncPicture
      VAProfileVP8Version0_3          :    VAEntrypointVLD
      VAProfileVP8Version0_3          :    VAEntrypointEncSlice
      VAProfileHEVCMain               :    VAEntrypointVLD
      VAProfileHEVCMain               :    VAEntrypointEncSlice
      VAProfileHEVCMain10             :    VAEntrypointVLD
      VAProfileVP9Profile0            :    VAEntrypointVLD

H/W acceleration works for me on H264 FHD sources. Hardware: Asrock J3455-ITX.

Many thanks for clarification.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-02-28

Changelog is wrong. It was 8bit at that time.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Blechmann - 2017-03-01

Hello,

i want to use Kodi V17 with Ubuntu Server 16.04.2 but after install i see only gray-screen with cursor.
First start from kodi was ok and i could set the settings (Step2)

My hardware: http://geizhals.de/?cat=WL-220627

Log:
kodi@homeserver:~/.kodi/temp$ dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/24089074/
kodi@homeserver:~/.kodi/temp$ DISPLAY=:0 vainfo | pastebinit
http://paste.ubuntu.com/24089075/
kodi@homeserver:~/.kodi/temp$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/24089081/
kodi@homeserver:~/.kodi/temp$ dmesg | pastebinit
http://paste.ubuntu.com/24089083/
kodi@homeserver:~/.kodi/temp$ id | pastebinit
http://paste.ubuntu.com/24089084/
kodi@homeserver:~/.kodi/temp$ amixer | pastebinit
http://paste.ubuntu.com/24089085/

Can someone help me ?


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Axman - 2017-03-01

(2017-03-01, 11:36)Blechmann Wrote: Can someone help me ?

How did you install Kodi? Does `sudo systemctl start kodi` work for you from command line on TV?
Pls show output of `which kodi` and `cat <kodi-user-home-dir>/.config/openbox/autostart`


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Blechmann - 2017-03-01

[i]How did you install Kodi? : According to the instructions of fritsch (Post 1)

Does `sudo systemctl start kodi` work for you from command line on TV? : No - remote from other terminal

Log:
kodi@homeserver:~/.kodi/temp$ which kodi
/usr/bin/kodi
kodi@homeserver:~/.kodi/temp$ cat /home/kodi/.config/openbox/autostart
OUTPUT=`xrandr -display :0 -q | sed '/ connected/!d;s/ .*//;q'`
xrandr -display :0 --output $OUTPUT --set "Broadcast RGB" "Full"
xsetroot #000000
devmon &
MALLOC_MMAP_THRESHOLD_=131072 /usr/bin/kodi --standalone
while [ $? -ne 0 ]; do
MALLOC_MMAP_THRESHOLD_=131072 /usr/bin/kodi --standalone
done
openbox --exit[/i]

Update: I have found my mistake /home/dir was encrypted.
Sorry