Fixed: 14.04.5 Failed at make, result in /tmp/logbuildCore**

Started by Jan Gruuthuse, October 16, 2016, 09:24:54 am

Previous topic - Next topic

eumagga0x2a

Quote from: Jan Gruuthuse on October 16, 2016, 05:25:30 pm
vainfo
libva info: VA-API version 0.37.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_0_32
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.37 (libva 1.5.0)


Okay, I think I can deduct the only plausible answer: you have libva and libva-dev 1.5.0-1 from Ubuntu 15.04 (Vivid Vervet) installed on 14.04.5. It provides VA-API version 0.37 and supports HEVC but not yet VP9.

The main thing is that it is now clear that the detection of libva features on behalf of Avidemux works fine.

Jan Gruuthuse

October 17, 2016, 11:38:07 am #16 Last Edit: October 17, 2016, 11:41:50 am by Jan Gruuthuse
grep -nR VAProfileHEVCMain /usr/include/va/
Quote/usr/include/va/va.h:296:    VAProfileHEVCMain                   = 17,
/usr/include/va/va.h:297:    VAProfileHEVCMain10                 = 18

dpkg -S /usr/include/va/va.h
Quotelibva-dev:amd64: /usr/include/va/va.h



libva-dev
Video Acceleration (VA) API for Linux -- development files
Libraries - Development (universe)
1.5.0-1~xedgers~trusty
maintainer: pkg-multimedia-maintainers @ lists.alioth.debian.org

eumagga0x2a

October 17, 2016, 11:46:41 am #17 Last Edit: October 17, 2016, 11:56:18 am by eumagga0x2a
Quote from: Jan Gruuthuse on October 17, 2016, 11:38:07 am
libva-dev
Video Acceleration (VA) API for Linux -- development files
Libraries - Development (universe)
1.5.0-1~xedgers~trusty
maintainer: pkg-multimedia-maintainers @ lists.alioth.debian.org



Thank you for the confirmation. This is not an official Ubuntu Trusty package, it originates from the xorg-edgers PPA which backports (mostly just rebuilds on Ubuntu Trusty) more recent version from Debian.

Edit: This means that packages built on your 14.04.5 system but installed on a regular Ubuntu 14.04.5 (without working VDPAU decoding) would try to play HEVC content via libva and fail, instead of skipping straight to the software decoding via internal ffmpeg. I don't know if they fail gracefully, i.e. automatically falling back to the software decoding or hard, unable to decode HEVC unless hardware accel in Avidemux gets disabled.

Jan Gruuthuse

As it stands now, it looks like hevc is now processed by the the CPU and not by hardware accelerated GPU. It take now minutes to encode 3sat test clip on 14.04.5 versus seconds on 16.04.1 accelerated GPU for the same test clip.
3sat test clip 69 MB download @ dropbox

Jan Gruuthuse

False alarm: avidemux did reset all settings (preferences). From time to time you need to check this, installing a newer avidemux does this.

Jan Gruuthuse

October 18, 2016, 07:18:01 am #20 Last Edit: October 18, 2016, 07:33:27 am by Jan Gruuthuse
14.04.5 x265 encoding seems slower:
x265 [info]: frame I:     14, Avg QP:20,27  kb/s: 18312,09
x265 [info]: frame P:    913, Avg QP:24,08  kb/s: 4086,61
x265 [info]: frame B:    965, Avg QP:29,11  kb/s: 279,65 
x265 [info]: Weighted P-Frames: Y:0,2% UV:0,1%
x265 [info]: Weighted B-Frames: Y:0,0% UV:0,0%
x265 [info]: consecutive B-frames: 53,1% 13,9% 8,8% 24,2%

encoded 1892 frames in 70,51s (26,83 fps), 2250,16 kb/s, Avg QP:26,62


more detailed info from terminal output attached:

Jan Gruuthuse

16.04.1 x265
x265 [info]: frame I:     14, Avg QP:20,25  kb/s: 18283,77
x265 [info]: frame P:    913, Avg QP:24,09  kb/s: 4078,13
x265 [info]: frame B:    965, Avg QP:29,10  kb/s: 277,56 
x265 [info]: Weighted P-Frames: Y:0,2% UV:0,1%
x265 [info]: Weighted B-Frames: Y:0,0% UV:0,0%
x265 [info]: consecutive B-frames: 53,1% 13,9% 8,8% 24,2%

encoded 1892 frames in 64,54s (29,32 fps), 2244,79 kb/s, Avg QP:26,62

more detailed info from terminal output attached:

eumagga0x2a

Quote from: Jan Gruuthuse on October 18, 2016, 07:05:31 am
False alarm: avidemux did reset all settings (preferences).


This happend probably due to [UI] Add a preference to select between reload default encoder setting or keep using current (euma). The way how Avidemux currently reacts encounting a new setting is surely a bug, maybe it will be fixed at some time in the future.

Why are you testing HEVC encoding? The libva features which were initially misdetected are decoding only.

To check if building Avidemux on 14.04.5 with a less outdated and thus HEVC capable libva than available via official repositories poses a problem for users of a regular 14.04.5 installation, one should use a target PC with a pretty recent Intel CPU but without a dedicated graphics card, running Ubuntu 14.04.5 without any PPAs or foreign packages apart from Avidemux added and try to decode (to play or to re-encode) a HEVC video in Avidemux.