The VideoLAN Forums

Posted: **01 May 2018 18:10**

A week ago I bought Intel barebone: https://ark.intel.com/products/126135/I ... t-NUC7CJYH

I gave it 8GB of RAM, and 120GB of SSD disk (some Kingston).

Instralled Debian stable (debian testing and ubuntu 18.04 didn't start X environment for some reason), installed VLC 2.2 there (vlc 3 is afaik not available for Debian stable), and tried to playback a video - fullhd mp4 in matroska.

The playback was terrible - dropped frames, jumping action. Both cores of the Celeron (J4005) inside pegged at 100%.

What can I do to debug/fix the problem? Playback was over the network (1gbit switched ethernet from samba share, works 100% ok with other computers).

I know that this is not much of a detail, but perhaps you can tell me what to check/where/how so I can give you better information that would allow you to help me?

Posted: **01 May 2018 18:58**

Enabling hardware decoding may be helpful.

Tools -> Preferences -> Input/Codecs -> Hardware-accelerated decoding -> Choose VAAPI

Make sure that your system has installed libva1 and use vainfo to check vaapi status.

https://wiki.videolan.org/VLC_GPU_Decoding/

Posted: **02 May 2018 21:39**

Sorry for lag in responding, bred.sun. Will check it tomorrow, and let you know if it did help.

Posted: **03 May 2018 09:19**

So, I tried.

1st, made sure all is installed:

=# dpkg -l | grep -iE 'libv(a1|dpau)'
ii libva1:amd64 1.7.3-2 amd64 Video Acceleration (VA) API for Linux -- runtime
ii libvdpau-va-gl1:amd64 0.4.2-1 amd64 VDPAU driver with OpenGL/VAAPI backend
ii libvdpau1:amd64 1.1.1-6 amd64 Video Decode and Presentation API for Unix (libraries)

Then I started VLC and tried setting hardware decoding to:

vaapi x11
vaapi drm
vdpau

In all of these cases both cpu cores were 100% pegged, and there was virtually no playback - still frame, and that's all.

File I was testing on, as tested with ffprobe:

=$ ffprobe -hide_banner x.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'x.mp4':
Metadata:
major_brand : isom
minor_version : 1
compatible_brands: isomavc1
creation_time : 2014-06-24T19:04:04.000000Z
Duration: 02:03:15.85, start: 0.000000, bitrate: 2143 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709/bt709/unknown), 1920x1040, 2045 kb/s, 23.98 fps, 23.98 tbr, 24k tbn, 47.95 tbc (default)
Metadata:
creation_time : 2014-06-24T19:04:04.000000Z
handler_name : video.264#trackID=1:fps=23.976 - Imported with GPAC 0.5.0-rev4065
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 93 kb/s (default)
Metadata:
creation_time : 2014-06-24T19:04:14.000000Z
handler_name : GPAC ISO Audio Handler

All the problems could stem from this:

=$ vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit

But I'm not sure how to handle this. I tried looking online for help, created (didn't have before) xorg.conf in /etc/X11, and added there "AccelMethod" glamor, but then X wouldn't even start. Any hints? Suggestions?

Posted: **04 May 2018 15:19**

I found following two links. kernel 4.11+ and libva 1.8.3+ are required to support Gemini Lake.

Your kernel and libva are too old. Maybe you should try another newer distribution or build required driver/library yourself.

https://github.com/intel/intel-vaapi-dr ... /tag/1.8.3
https://www.linux.com/news/linux-kernel ... ake-socs-0

Posted: **07 May 2018 13:27**

The problem is that I was unable to boot even installer on anything newer (tried couple of ubuntus from 17.04 to 18.04 and debian testing) - after grub selection, I ended up with black screen, as if X couldn't create graphics. Will look into it, thanks a lot.

The VideoLAN Forums

Performance problems on barebone from Intel

Performance problems on barebone from Intel

Re: Performance problems on barebone from Intel

Re: Performance problems on barebone from Intel

Re: Performance problems on barebone from Intel

Re: Performance problems on barebone from Intel

Re: Performance problems on barebone from Intel