• 1
  • 271
  • 272
  • 273(current)
  • 274
  • 275
  • 342
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
Hi there I wa using j1900 pc with kodibuntu and perfectly working vaapi-bob for a while. I decided to check libreelec (latest stable) but when i set the same settings, the moment i choose vaapi-bob the picture freeze and when i try torun the channel again there is rather long buffering(10-15sec) to 100% and just black screen with audio. What do i miss? Thanks!
Reply
You miss your Debug Log. And you are in the wrong thread. LibreELEC stable has nothing to do with this Krypton testing thread.

Please open your own thread.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2016-08-07, 23:19)Jan0sh Wrote:
(2016-08-07, 20:07)fritsch Wrote: Nope - that was @maurer. In your case most likely the "inputstream" addon causes this issue, which no requires a not yet packaged up2date version.

So for now I will downgrade to
17.0~git20160726.0200-2b8e204-0xenial_amd64.deb (lying around in apt cache) which works with current inputstream version.

Now I have to wait on which package to get updated? kodi-inputstream-mpd or kodi itself?
Where could I find more information when I can go upstream again?

thanks in advance


Today I Upgraded to
17.0~git20160926.0200-d51d4ae-0xenial
Which Works fine. Just for Reference

Edit: just to early..
I was able to watch half an episode then the image freezes after a kodi restart I am now unable to play any files. I can here the audio, Kan view the menu but the actual image won't show up. Restarted the system, tried different settings (without pass through) but problem persists. I also downgraded to version mentioned in the quote above which also did no longer work.

Here are the debug logs:

kodi@htpc:~$ dpkg -l |grep mesa | pastebinit
Http://paste.ubuntu.com/23235746/
kodi@htpc:~$ DISPLAY=:0 vainfo | pastebinit
Error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 0.39.0
llibva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/23235747/
kodi@htpc:~$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/23235748/
kodi@htpc:~$ dmesg | pastebinit
http://paste.ubuntu.com/23235749/
kodi@htpc:~$ id | pastebinit
http://paste.ubuntu.com/23235750/
kodi@htpc:~$ amixer | pastebinit
http://paste.ubuntu.com/23235751/
Reply
Please remove the 3dlut. Also there are a lot non working add-ons in there.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
On a fresh install it seems one of the directories has changed. Is it suppose to install native addons to /usr/lib/x86_64-linux-gnu/kodi/addons instead of /usr/lib/kodi/addons?
Reply
(2016-09-28, 22:50)rome Wrote: On a fresh install it seems one of the directories has changed. Is it suppose to install native addons to /usr/lib/x86_64-linux-gnu/kodi/addons instead of /usr/lib/kodi/addons?

yes
Reply
(2015-07-12, 20:06)fritsch Wrote: If your TV is limited range. Go to System -> Video Output and choose "Use Limited Range", disable Dithering.

Didn't this previously say to enable dithering?
Reply
no, only if TV is full range
Reply
(2016-08-09, 10:10)TimoJ Wrote: I just installed Ubuntu server 16.04.1 and Kodi (nightly) with the instructions of the first post, also installed Intel drivers 1.7.1.

But I have a problem: screen goes blank in random times, even when idle in the main screen.

Looks like refresh rate is quicly changed and then changed back again. Same also happens when I go to settings screen of resolution and refresh rate, there screen goes blank and Kodi asks if I want to keep the change even before I do anything,

Cables are OK, I have no problems with earlier install of Ubuntu server 14.04 and Kodi (nightly).
Mainboard has Intel H87 chipset with Haswell processor, using HDMI connection.

So what is going on? Is there some known kernel/driver bug that causes this?
Since my above message, I have been using Ubuntu 14 and now decided to test again 16.04 and Kodi 17. And still the same problem. I did more testing and looks like it's my AV-preamp that is causing this issue, no problems if I connect my Kodi PC directly to my TV. Installed kernel 4.4.21 but it made no difference. Same happens also via Display Port with HDMI adapter. Sad

What has changed in Ubuntu 16.04 that is causing this? Looks like it's a signal timing issue, is there any way to tweak those parameters?
Reply
It's a kernel bug, yes. You can try to install 4.8.1 and if it does not work -> bugs.freedesktop.org it's a really nasty bug since several months sadly.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Looks like the timing problem is "fixed" if I use edid copied from my TV. But then I get only 2 channel audio. Maybe one of those cheap edid emulators from eBay also fixes this. But I'll try first 4.8.1 kernel.
Reply
Try mine: https://dl.dropboxusercontent.com/u/55728161/edid.bin

Edit: That one: https://dl.dropboxusercontent.com/u/5572...-intel.bin
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Thank you! I'll test it later.
I just switched back to my AV-preamp's edid and still no problems. I don't understand this. Sometimes the system blanks screen very often, even right after boot and sometimes it (almost) works perfectly. It's like some background process causes small display timing changes or something...
Reply
(2016-10-09, 13:10)TimoJ Wrote: I just switched back to my AV-preamp's edid and still no problems. I don't understand this
Now it looks like the problem is caused by Darbee Darblet video processor. I had tested so many cable and input combinations that I forgot that I had it removed from the HDMI-line between TV and preamp Blush
So that is why both EDIDs suddenly started to work. When Darbee is connected, the problem appears no matter what edid is used, also Fritsch's.

Still the Darbee works fine with Kodi&Ubuntu 14 and satellite boxes, so it's not a hardware problem. But at least finally something seems to make sense in this and I can test some connection changes to fix this.
Reply
http://www.asrock.com/mb/Intel/J4205-ITX/index.us.asp <- Apollo Lake HEVC 10 bit
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 271
  • 272
  • 273(current)
  • 274
  • 275
  • 342

Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18