This howto assumes, that you are able to create a file on a linux filesystem. Furthermore it assumes, that you are able to apt-get.
VPP BOB was made working in the meantime on SNB, IVB and HSW. IVB supports MADI (Motion Adaptive Deinterlacing), though there is a little bug in the driver that it produces little artifacts. On HSW even MCDI (Motion Compensation Deinterlacing) and MADI is working now. Though, you need a special driver that wsnipex is packaging in his vaapi ppa (see beneath). Ubuntu Trusty does not ship a new enough version, as a result VAAPI-BOB will produce green artifacts on HSW and MCDI and MADI will jump like hell.
Furthermore the ppa (https://launchpad.net/~wsnipex/+archive/...nta-master) can automatically use a high quality software deinterlacer Yadif or BOB OpenGL Deinterlacer. It can seamlessly use the before mentioned GPU Deinterlacing (VAAPI-BOB, VAAPI-MADI, VAAPI-MCDI). Those methods can be selected when watching a specific movie by changing the relevant options via the movie reel. VAAPI-MCDI is not available on a Baytrail as this is an IVB based chip.
The best quality of the cpu deinterlacers gives the filter called Deinterlace that is the implementation also referred to as Yadif - that costs a lot of CPU cycles (so be warned here). If you have a HSW chip you can use the VAAPI-MCDI deinterlacer which has awesome quality while keeping CPU load low. On Baytrail chips I currently suggest using the OpenGL Bob deinterlacer - cause the GPU is maxed out when using any of the VAAPI methods. I hope we can optimize this in the future when using the new EGL surface sharing API which was introduced in libva 0.3.6.
IVB: VAAPI-BOB (cause of the artifacts mentioned above)
Baytrail / SNB / In general HD2000: BOB (which is done in the renderer and costs nearly nothing, not VPP-BOB).
This ppa provides a helix version of current master. The code will also be used in OpenELEC 5.0 - OpenELEC 4.2 is still Gotham based. The most code was already merged upstream to xbmc, but I suggest keeping the fernetmenta-master ppa for now as most fixes are first actively developed in there.
Some visual comparison:
-1.) Hardware Requirements / Software Requirements
SNB, IVB, HSW Intel Hardware
Ubuntu Trusty mini iso installed x64. Download link for example here: http://archive.ubuntu.com/ubuntu/dists/t...t/mini.iso
If you have a UEFI only system, you need to use the server iso as your basis, as the mini iso won't boot in UEFI mode. Server iso is http://cdimage.ubuntu.com/ubuntu-server/...-amd64.iso
0.) Basic Installation and script tuning
After the mini iso is installed, continue with the following steps:
sudo apt-get update
sudo apt-get install ssh python-software-properties software-properties-common udisks upower xorg alsa-utils mesa-utils git-core librtmp0 lirc libmad0 lm-sensors libmpeg2-4 avahi-daemon libnfs1 consolekit pm-utils libva1 vainfo libva-intel-vaapi-driver linux-firmware
sudo apt-get dist-upgrade
Allow every user (everyone) to start X11
sudo dpkg-reconfigure x11-common
Create the xbmc user and it add it the relevant groups. If you have created the xbmc user during installation only do the usermod part.
sudo adduser xbmc
sudo usermod -a -G cdrom,audio,video,plugdev,users,dialout,dip xbmc
To use the following upstart procedure you need to create /etc/init/xbmc.conf to start xbmc via upstart. That scripts does only wait for your HDMI device, if you want to wait for networking, you have to add that.
# starts XBMC on startup by using xinit.
# by default runs as xbmc, to change edit below.
author "Matt Filetto"
start on (filesystem and stopped udevtrigger)
stop on runlevel 
# tell upstart to respawn the process if abnormal exit
respawn limit 10 5
limit nice 21 21
exec su -c "xinit /usr/bin/kodi --standalone -- /usr/bin/X -nolisten tcp :0" $USER
# the following two are to get an idea, if you want to user a window manager
# sudo apt-get install fluxbox and comment the above exec line
# only one exec line is allowed.
# exec su -c "xinit /usr/bin/fluxbox -- /usr/bin/X -nolisten tcp :0" $USER
# remove all those to set Full rgb range make sure to change HDMI2 to match your device
# starting from the next line, including end script
# post-start script
# sleep 1
# DISPLAY=:0 xrandr --output HDMI2 --set "Broadcast RGB" Full
# end script
edit /etc/security/limits.conf and add before the end. remember xbmc is the username, not the application. This will allow your user to get the audio thread a bit more priority.
xbmc - nice -1
Last thing is missing some permissions to shutdown, suspend the computer, therefore create the file /etc/polkit-1/localauthority/50-local.d/custom-actions.pkla with the following content (don't introduce line breaks, especially the Action= line must be exactly one line (especially no linebreaks or auto ".." in freedesktop.udisks.*), verify this):
[Actions for xbmc user]
1.) Installation of the repository and the new packages
sudo apt-add-repository ppa:wsnipex/xbmc-fernetmenta-master
sudo apt-add-repository ppa:wsnipex/vaapi (see *)
sudo apt-get update
sudo apt-get install kodi kodi-bin
sudo apt-get dist-upgrade
3.) XBMC settings
Vertical Sync: Let Driver decide
Enable HQ Scalers for scaling above: 20%
Allow hardware acceleration (VDPAU): off
Allow hardware acceleration (VAAPI): On
Use Mpeg-2 VAAPI: Yes
Use Mpeg-4 VAAPI: if you like
UseVC-1 VAAPI: off (this causes vc1 interlaced to segfault, when on)
Adjust Refreshrate to match video: On
If you experience kernel hangs (dmesg will tell), you can set Prefer VAAPI Render: Off that will force the swfilter even when progressive / VAAPI BOB is in use.
System -> Video -> Playback
Sync Playback to Display: On
Sync Method: Video Clock (Drop/Dupe)
Adjust display refresh rate to match video: On Start / Stop
When playing some 720p file or lower (do you get why?) open the movie icon and set Deinterlace: Auto and Deinterlace Method to: Deinterlace (if it causes too much cpu load, choose Bob (Celeron Baytrail and Celeron 847 Nucs(!)) - also set Scaling algorithm to Lanczos 3 optimized (also not for Baytrail and Celeron Nucs, only for HD3000 and faster). Save for all files.
If you are running a Baytrail NUC or a 847 Celeron NUC or comparable - choose Scaling: Bilinear and Deinterlace-Method: BOB
advancedsettings.xml in /home/xbmc/.kodi/userdata/advancedsettings.xml should contain (don't create that file / directory as root - use the xbmc user, e.g. mkdir -p /home/xbmc/.kodi/userdata/):
<cputempcommand>sensors|sed -ne "s/Core 0: \+[-+]\([0-9]\+\).*/\1 C/p"</cputempcommand>
<delay>175</delay> <!-- set to zero or adjust if audio seems out of sync with 24p movies -->
Especially the RSS Reader produces high CPU load. You can disable that one under Appearance setting.
Howto update kodi
As kodi is a normal ubuntu package, installed via the ppa, it's as simple as:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get update
sudo apt-get install plymouth-label v86d
wget https://dl.dropboxusercontent.com/u/55728161/plkodi/kodibuntu-plymouth-theme_0.1.0%7Etrusty1_all.deb https://dl.dropboxusercontent.com/u/55728161/plkodi/plymouth-theme-kodibuntu-logo_0.1.0%7Etrusty1_all.deb https://dl.dropboxusercontent.com/u/55728161/plkodi/plymouth-theme-kodibuntu-text_0.1.0%7Etrusty1_all.deb
sudo dpkg -i *kodibuntu*deb
We are now done. A final reboot and everything should work:
In order to get any help, please provide the following logs.
sudo apt-get install pastebinit
dmesg | pastebinit
cat ~/.xbmc/temp/xbmc.log | pastebinit
cat /var/log/Xorg.0.log | pastebinit
DISPLAY=:0 vainfo | pastebinit
dpkg -l |grep mesa | pastebinit
id | pastebinit
aplay -L | pastebinit
Check if you audio device is muted
You can use alsamixer -c0 or alsamixer -c1 to do it manually, or use something like:
amixer set 'IEC958',0 unmute
If you want to run pulseaudio, please see the xbmc wiki before: http://wiki.xbmc.org/index.php?title=PulseAudio
Out of historical reasons, you can join #xbmc-xvba for discussing this howto. The channel name shall make us remember forever, that best hardware is worth nothing, if there are no drivers for it :-)
- As of 14/08/20 MADI and MCDI could be enabled. Intel has fixed the issues Make sure you use the driver in the wsnipex vaapi ppa
- To use VAAPI BOB on HSW, you need to build libva-driver-intel 1.3.2 or higher from source, alternatively you can install that driver from wsnipex vaapi repository
- To use VAAPI MCDI/MADI on HSW, you need to build my ppa or ppa14 branch on my github which has picked the vebox fixes.
- There is an upstream bug in mesa/dri/libva which cause out of a sudden to start tearing. If you press stop xbmc gui will hang and you can see a kernel hang with dmesg. Upstream report is here: https://bugs.freedesktop.org/show_bug.cgi?id=78960 A workaround is to disable "Prefer VAAPI Render method" under Video -> Acceleration (Expert Mode). This will produce a bit more CPU load but will cure that error.
14/01/05: Update to kernel 3.13-rc7
14/01/12: Update to kernel 3.13-rc8
14/01/20: Update to kernel 3.13 final
14/01/30: Update to kernel 3.13.1
14/02/06: Told howto update.
14/02/07: Update to kernel 3.13.2
14/02/14: Update to kernel 3.13.3
16/02/14: Add code to set Display to RGB Full mode
14/02/22: Update to kernel 3.13.4
14/02/24: Update to kernel 3.13.5
14/04/09: Update to Ubuntu trusty
14/04/16: Coming from Saucy? Upgrade: http://forum.xbmc.org/showthread.php?tid...pid1677121
14/06/30: SwFilter Option has been removed. If you want to force a copy to system run disable the new setting: Prefer VAAPI Render in Video -> Acceleration. This is not needed in general, cause when Deinterlace or Bob is active this is automatically bypassed.
*14/08/23: Added wsnipex vaapi ppa to the howto. This will install an experimental intel-driver that can do MCDI and MADI. Beware it will crash roughly every 30 minutes when doing deinterlacing :-)
14/08/30: The crash has been fixed and you should be able to run MCDI without crashing
14/09/11: Rewrite of the indroduction part and settings.
14/10/20: Change The server iso to point to the trusty one.
14/11/18: Added login1 permissions to the pkla file. Replace yours if you don't have suspend / power off options anymore. Thanks to wsnipex.
14/11/02: Workaround for stuttering, mostly on Celeron (1820/1830 and especiallly the chromebox)
A GPU hang appears when VAAPI is used to render. The workaround increases CPU usage a bit, but is currently the only way to get that going:
- Video -> Acceleration: Disable Prefer VAAPI Render Method
- While Playing a Video:
Set Deinterlace: Auto
Deinterlacing-Method: BOB (_not_ the VAAPI BOB) or De-Interlace (More cpu load, high quality).
-> Save for all movies
When watching interlaced Content and MCDI / VAAPI-BOB or MCDI is selected this would implicitely use the VAAPI Render Method, which causes the issues on the chromebox. Don't choose the GPU deinterlacers if you want to workaround those hangs.