Jump to content

Ubuntu


Luke

Recommended Posts

LeidenSpain

Thanks !

to me???
Thanks to you for emby, and for the support.
 
I am already at home, so in a while install everything (before I'll see how ubuntu).
Link to comment
Share on other sites

LeidenSpain

Hi,

 

I'm installing lubuntu 18.04.1 LTS on my miniPC.

 

for the moment, I've done a test on another computer, using windows.

i7-8650 with UHD Graphics 620

 

IntelQuickSync OFF

5bed804578151_GPUoff.jpg

 

IntelQuickSync ON

5bed805d41aa8_GPUon.jpg

 

 

This is my reference's point.

Link to comment
Share on other sites

LeidenSpain

OK Lubuntu installed, and the system don´t found the graphic card

5beda161155af_01.jpg

 

Intel have not support for 18.04, the I used the repositories again

5beda1ab8404a_repositorios.jpg

Link to comment
Share on other sites

sfatula

In the step where you showed vainfo, you should be installing not from a ppa, but the generic ubuntu package i965-va-driver, then retry the vainfo

 

You can do this command from the command line to see if the UHD 600 is detected:

lspci | grep VGA

It would be unusual since Intel graphics drivers are all built into ubuntu to not detect it. If the above shows your card, try this too:

lshw -C video

  *-display                 
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 07
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:128 memory:de000000-deffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
Edited by sfatula
  • Like 1
Link to comment
Share on other sites

LeidenSpain

 

In the step where you showed vainfo, you should be installing not from a ppa, but the generic ubuntu package i965-va-driver, then retry the vainfo

 

You can do this command from the command line to see if the UHD 600 is detected:

lspci | grep VGA

It would be unusual since Intel graphics drivers are all built into ubuntu to not detect it. If the above shows your card, try this too:

lshw -C video

  *-display                 
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 07
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:128 memory:de000000-deffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
 
indeed, in the capture of vainfo I had only installed vainfo.
When I tried 18.10 yes that I detected the UHD600 directly.

 

home-server@home-server:~$ lspci | grep VGA

00:02.0 VGA compatible controller: Intel Corporation Device 3185 (rev 03)

 

home-server@home-server:~$ sudo lshw -C video

  *-display                 
       descripción: VGA compatible controller
       producto: Intel Corporation
       fabricante: Intel Corporation
       id físico: 2
       información del bus: pci@0000:00:02.0
       versión: 03
       anchura: 64 bits
       reloj: 33MHz
       capacidades: pciexpress msi pm vga_controller bus_master cap_list rom
       configuración: driver=i915 latency=0
       recursos: irq:127 memoria:a0000000-a0ffffff memoria:90000000-9fffffff ioport:f000(size=64) memoria:c0000-dffff

 

 
Now, i install the package  i965-va-driver-shaders from synaptic (This package contains also contains the non-free encode shaders for VP8, VP9, HEVC and AVC for generation 7.5 hardware a newer.)

 

home-server@home-server:~$ vainfo

libva info: VA-API version 1.1.0
libva 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_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel® Gemini Lake - 2.1.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointEncSliceLP
      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
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile0            : VAEntrypointEncSlice
      VAProfileVP9Profile2            : VAEntrypointVLD

 

home-server@home-server:~$ lspci | grep VGA

00:02.0 VGA compatible controller: Intel Corporation Device 3185 (rev 03)

 

home-server@home-server:~$ sudo lshw -C video

  *-display                 
       descripción: VGA compatible controller
       producto: Intel Corporation
       fabricante: Intel Corporation
       id físico: 2
       información del bus: pci@0000:00:02.0
       versión: 03
       anchura: 64 bits
       reloj: 33MHz
       capacidades: pciexpress msi pm vga_controller bus_master cap_list rom
       configuración: driver=i915 latency=0
       recursos: irq:127 memoria:a0000000-a0ffffff memoria:90000000-9fffffff ioport:f000(size=64) memoria:c0000-dffff

 

FINE
 
But.....
some strange happends with the system detect and the intel-gpu-tools
5bedcaa3edde4_01.jpg
 
And now, I see the generic ubuntu package i965-va-driver it's not compatible with N4100 (Gemini Lake)

 

This package contains the video decode and encode driver backend for the

Intel G45 chipsets and Intel HD Graphics for the Intel Core processor family.
The supported platforms include:
 * Cantiga, Intel GMA 4500MHD (GM45)
 * Ironlake, Intel HD Graphics for 2010 Intel Core processor family
 * Sandy Bridge, Intel HD Graphics for 2011 Intel Core processor family
 * Ivy Bridge
 * Haswell
 * Broadwell
 * Skylake
 * Kaby Lake
 * Coffee Lake
 * Cannon Lake
 

 

Link to comment
Share on other sites

sfatula

Aha, so that is going to turn out to be your problem, it isn't supported by the i965. I suspected it wasn't emby. The names always confuse me, I don't always recall which name associates to which processor, yes, can look it up I know. 

 

This might be of some help:

 

https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa

 

It says it's not in generic ubuntu yet (will be), but, the new version of Mesa improves support for Gemini Lake. Worth a shot. If you go down the road of other drivers, you might succeed, but, it's often a hard road. 

 

With the newer updated i965 driver, it says:

 

Add support for Gemini Lake (aka. GLK)

- Decoding: H.264/MPEG-2/VC-1/JPEG/VP8/HEVC/HEVC 10-bit/VP9/VP9 10-bit
- Encoding: H.264/MPEG-2/JPEG/VP8/VP9/HEVC/HEVC 10-bit/AVC low power CQP mode
- VPP: CSC/scaling/NoiseReduction/Deinterlacing{Bob, MotionAdaptive, MotionCompensated}/ColorBalance/STD
 
Note the article is old, newer Mesa is available. Use this ppa to try:
 
 
You would want mesa 18.2.2 While not officially ubuntu supported per se, it's close. Hopefully, this might get you somewhere but the issue is your GPU is not supported at present in stock ubuntu. So, that's why emby was failing to accelerate. 
Edited by sfatula
  • Like 1
Link to comment
Share on other sites

LeidenSpain

 

Aha, so that is going to turn out to be your problem, it isn't supported by the i965. I suspected it wasn't emby. The names always confuse me, I don't always recall which name associates to which processor, yes, can look it up I know. 

 

This might be of some help:

 

https://www.omgubuntu.co.uk/2018/06/mesa-18-1-1-ubuntu-18-04-ppa

 

It says it's not in generic ubuntu yet (will be), but, the new version of Mesa improves support for Gemini Lake. Worth a shot. If you go down the road of other drivers, you might succeed, but, it's often a hard road. 

 

With the newer updated i965 driver, it says:

 

Add support for Gemini Lake (aka. GLK)

- Decoding: H.264/MPEG-2/VC-1/JPEG/VP8/HEVC/HEVC 10-bit/VP9/VP9 10-bit
- Encoding: H.264/MPEG-2/JPEG/VP8/VP9/HEVC/HEVC 10-bit/AVC low power CQP mode
- VPP: CSC/scaling/NoiseReduction/Deinterlacing{Bob, MotionAdaptive, MotionCompensated}/ColorBalance/STD
 
Note the article is old, newer Mesa is available. Use this ppa to try:
 
 
You would want mesa 18.2.2 While not officially ubuntu supported per se, it's close. Hopefully, this might get you somewhere but the issue is your GPU is not supported at present in stock ubuntu. So, that's why emby was failing to accelerate. 

 

 

 

Hi,

I think the problem is not the driver: remember that in my first installation, the lubuntu used the GPU to 

 

 

 

Hi

I'm using emby 3.5.3.0 and Lubuntu 18.04.1 LTS over an Intel N4100 (GPU UHD600). This chip has hardware transcodification-

 

First I used emby with windows and IntelQuickSync and I saw how the use of the GPU increased.

But now I to use ubuntu, and I can not use transcoding with emby (but if it is used in the video player).

 

This is my info

 

 

 

 5beb10430d07b_Sinttulo.jpg

 

 

 

And now playing a film

5beb10b95417d_film.jpg

 

 

I do not think that's the problem: in my first installation, ubuntu used the GPU to play video, using these drivers:

https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

 

I try with the mesa driver

Edited by juancarlos.castro
Link to comment
Share on other sites

LeidenSpain

The same: if I play the video directly on lubuntu, I see that the gnome-mpv player use the GPU.

But the transcoding option on emby is disabled when emby try to do it

 

 

UPS, mesa drivers have a very big problem:

 

home-server@home-server:~$ vainfo

libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
 

 

 

And the same with the Oibaf

 

Really, it's not a easy configuration

Edited by juancarlos.castro
Link to comment
Share on other sites

sfatula

Sounds like it. But the hardware is not fully supported either (I took the notes from the changelog of i965 mentioning Gemini Lake), I may be getting totally confused on all the variants you have tried, but, I thought your first config was with custom drivers?

 

With my Intel 620, it was as simple as install xubuntu, install i965, add video group to emby user, works. 

 

You are comparing an mpv based player though, not the same thing that emby is using, your screen captures showed mpv as working, but the ffmpeg emby transcode as not working if I recall correctly. I wonder if you could run ffmpeg manually with the correct options and see if it will use gpu? That might be a good hint?

 

I don't know if mpv uses the i965 driver or not. Don't know enough about it. 

  • Like 1
Link to comment
Share on other sites

LeidenSpain

Sounds like it. But the hardware is not fully supported either (I took the notes from the changelog of i965 mentioning Gemini Lake), I may be getting totally confused on all the variants you have tried, but, I thought your first config was with custom drivers?

 

With my Intel 620, it was as simple as install xubuntu, install i965, add video group to emby user, works. 

 

You are comparing an mpv based player though, not the same thing that emby is using, your screen captures showed mpv as working, but the ffmpeg emby transcode as not working if I recall correctly. I wonder if you could run ffmpeg manually with the correct options and see if it will use gpu? That might be a good hint?

 

I don't know if mpv uses the i965 driver or not. Don't know enough about it. 

 

 

tell me how I can do the ffmpeg test.

But now, it's too late.

 

But before going to sleep, I found the official drivers from the web of intel

 
I try tomorrow
 
Good night
Link to comment
Share on other sites

sfatula

Yes, those are where Intel does it's thing in the Linux world. Those are the official intel drivers, which are unofficial from an ubuntu point of view. However, I would use them if needed and it sounds like you do! They have some interesting projects they have been working on over there for virtual machines and GPUs that I have been following for some time (GVT).

 

The relevant doc for ffmpeg is here:

 

https://trac.ffmpeg.org/wiki/HWAccelIntro

 

I am not an ffmpeg command line person, someone else might be able to chime in, but from that page, appears that the option you need is -hwaccel. Usually, it's not much of a command, if I get a chance, I'll try and make one for a video later. 

Edited by sfatula
  • Like 1
Link to comment
Share on other sites

LeidenSpain

Yes, those are where Intel does it's thing in the Linux world. Those are the official intel drivers, which are unofficial from an ubuntu point of view. However, I would use them if needed and it sounds like you do! They have some interesting projects they have been working on over there for virtual machines and GPUs that I have been following for some time (GVT).

 

The relevant doc for ffmpeg is here:

 

https://trac.ffmpeg.org/wiki/HWAccelIntro

 

I am not an ffmpeg command line person, someone else might be able to chime in, but from that page, appears that the option you need is -hwaccel. Usually, it's not much of a command, if I get a chance, I'll try and make one for a video later. 

HI

 

someone said that emby does a VA-API test and if it gives an error it is disabled

Is it possible to do that test in some way to see where the fault is?

 

Regards

Link to comment
Share on other sites

sfatula

I'd be curious of that also, but still, you need to do a simple ffmpeg test and see if it uses VAAPI, especially if MPV is working. I believe you don't need much, just input, output, and, the hwaccel flag

 

If ffmpeg does not use vaapi, then, emby sure won't. If ffmpeg does use it on your system, then, it's not more intriguing as to why does emby not

Edited by sfatula
  • Like 1
Link to comment
Share on other sites

LeidenSpain

I'd be curious of that also, but still, you need to do a simple ffmpeg test and see if it uses VAAPI, especially if MPV is working. I believe you don't need much, just input, output, and, the hwaccel flag

 

If ffmpeg does not use vaapi, then, emby sure won't. If ffmpeg does use it on your system, then, it's not more intriguing as to why does emby not

Would you know how I can do this test?

Link to comment
Share on other sites

sfatula
ffmpeg -i 'Manifest S01E05 Connecting Flights.ts' -s 1280x720 -f null -

The above will test without vaapi, monitor by your tool of choice to see how it behaves, replace video name with a correct path to some large video file

ffmpeg -hwaccel vaapi -i 'Manifest S01E05 Connecting Flights.ts' -s 1280x720 -f null -

That should give a different use of cpu/gpu

 

I believe these will work good enough for a test of ffmpeg and vaapi, hopefully! Someone can correct if necessary. 

  • Like 1
Link to comment
Share on other sites

LeidenSpain
ffmpeg -i 'Manifest S01E05 Connecting Flights.ts' -s 1280x720 -f null -

The above will test without vaapi, monitor by your tool of choice to see how it behaves, replace video name with a correct path to some large video file

ffmpeg -hwaccel vaapi -i 'Manifest S01E05 Connecting Flights.ts' -s 1280x720 -f null -

That should give a different use of cpu/gpu

 

I believe these will work good enough for a test of ffmpeg and vaapi, hopefully! Someone can correct if necessary. 

 

 

 

 

OK, I try

 

 

home-server@home-server:~/Vídeos$ ffmpeg -i '001.mkv' -s 1280x720 -f null -

ffmpeg version 4.0.3-1~18.04.york0 Copyright © 2000-2018 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04)
  configuration: --prefix=/usr --extra-version='1~18.04.york0' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  libavutil      56. 14.100 / 56. 14.100
  libavcodec     58. 18.100 / 58. 18.100
  libavformat    58. 12.100 / 58. 12.100
  libavdevice    58.  3.100 / 58.  3.100
  libavfilter     7. 16.100 /  7. 16.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  1.100 /  5.  1.100
  libswresample   3.  1.100 /  3.  1.100
  libpostproc    55.  1.100 / 55.  1.100
Input #0, matroska,webm, from '001.mkv':
  Metadata:
    encoder         : libebml v1.3.6 + libmatroska v1.4.9
    creation_time   : 2018-09-17T19:00:02.000000Z
  Duration: 00:41:10.76, start: 0.000000, bitrate: 2078 kb/s
    Stream #0:0: Video: mpeg4 (Advanced Simple Profile) (XVID / 0x44495658), yuv420p, 704x396 [sAR 1:1 DAR 16:9], 25 fps, 25 tbr, 1k tbn, 23.98 tbc (default)
    Metadata:
      BPS-eng         : 1692668
      DURATION-eng    : 00:41:10.760000000
      NUMBER_OF_FRAMES-eng: 61769
      NUMBER_OF_BYTES-eng: 522772108
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:1(spa): Audio: mp3, 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:2(eng): Audio: mp3, 48000 Hz, stereo, fltp, 192 kb/s
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg4 (native) -> wrapped_avframe (native))
  Stream #0:1 -> #0:1 (mp3 (mp3float) -> pcm_s16le (native))
Press [q] to stop, [?] for help
Output #0, null, to 'pipe:':
  Metadata:
    encoder         : Lavf58.12.100
    Stream #0:0: Video: wrapped_avframe, yuv420p, 1280x720 [sAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc (default)
    Metadata:
      BPS-eng         : 1692668
      DURATION-eng    : 00:41:10.760000000
      NUMBER_OF_FRAMES-eng: 61769
      NUMBER_OF_BYTES-eng: 522772108
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc58.18.100 wrapped_avframe
    Stream #0:1(spa): Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s (default)
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc58.18.100 pcm_s16le
frame=35112 fps=337 q=-0.0 size=N/A time=00:23:24.79 bitrate=N/A speed=13.5x    
 

5bef463ff4183_01.jpg

 

 

And now, using "-hwaccel vaapi"

 

home-server@home-server:~/Vídeos$ ffmpeg -hwaccel vaapi -i '001.mkv' -s 1280x720 -f null -

ffmpeg version 4.0.3-1~18.04.york0 Copyright © 2000-2018 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-27ubuntu1~18.04)
  configuration: --prefix=/usr --extra-version='1~18.04.york0' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  libavutil      56. 14.100 / 56. 14.100
  libavcodec     58. 18.100 / 58. 18.100
  libavformat    58. 12.100 / 58. 12.100
  libavdevice    58.  3.100 / 58.  3.100
  libavfilter     7. 16.100 /  7. 16.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  1.100 /  5.  1.100
  libswresample   3.  1.100 /  3.  1.100
  libpostproc    55.  1.100 / 55.  1.100
Input #0, matroska,webm, from '001.mkv':
  Metadata:
    encoder         : libebml v1.3.6 + libmatroska v1.4.9
    creation_time   : 2018-09-17T19:00:02.000000Z
  Duration: 00:41:10.76, start: 0.000000, bitrate: 2078 kb/s
    Stream #0:0: Video: mpeg4 (Advanced Simple Profile) (XVID / 0x44495658), yuv420p, 704x396 [sAR 1:1 DAR 16:9], 25 fps, 25 tbr, 1k tbn, 23.98 tbc (default)
    Metadata:
      BPS-eng         : 1692668
      DURATION-eng    : 00:41:10.760000000
      NUMBER_OF_FRAMES-eng: 61769
      NUMBER_OF_BYTES-eng: 522772108
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:1(spa): Audio: mp3, 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
    Stream #0:2(eng): Audio: mp3, 48000 Hz, stereo, fltp, 192 kb/s
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg4 (native) -> wrapped_avframe (native))
  Stream #0:1 -> #0:1 (mp3 (mp3float) -> pcm_s16le (native))
Press [q] to stop, [?] for help
[mpeg4 @ 0x55f6e933f600] No support for codec mpeg4 profile 15.
[mpeg4 @ 0x55f6e933f600] Failed setup for format vaapi_vld: hwaccel initialisation returned error.
Output #0, null, to 'pipe:':
  Metadata:
    encoder         : Lavf58.12.100
    Stream #0:0: Video: wrapped_avframe, yuv420p, 1280x720 [sAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc (default)
    Metadata:
      BPS-eng         : 1692668
      DURATION-eng    : 00:41:10.760000000
      NUMBER_OF_FRAMES-eng: 61769
      NUMBER_OF_BYTES-eng: 522772108
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc58.18.100 wrapped_avframe
    Stream #0:1(spa): Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s (default)
    Metadata:
      BPS-eng         : 192000
      DURATION-eng    : 00:41:10.752000000
      NUMBER_OF_FRAMES-eng: 102948
      NUMBER_OF_BYTES-eng: 59298048
      _STATISTICS_WRITING_APP-eng: mkvmerge v26.0.0 ('In The Game') 64-bit
      _STATISTICS_WRITING_DATE_UTC-eng: 2018-09-17 19:00:02
      _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
      encoder         : Lavc58.18.100 pcm_s16le
frame=11584 fps=325 q=-0.0 size=N/A time=00:07:43.58 bitrate=N/A speed=  13x 

5bef4742039de_02.jpg

 

 

PERFECT, now I see the problem is on my system.

Then, I must find the correct driver and configuration until you get to use the GPU in this way

 

THANKS 

Link to comment
Share on other sites

sfatula

I see no difference in the 2 really, so, yep. 142% vs 137% at the moment each was captured, should be way different. About the same fps. It will always vary some. I guess that's "good" news, at least you should know when you get it working so you can retest emby. 

 

I was interested as I did not understand why your machine could be so difficult when mine was so easy. It has to be the CPU/GPU not being fully supported yet, at least by some of the tools, maybe not all. I think there should be a way to get that from the Intel site you located. 

  • Like 1
Link to comment
Share on other sites

LeidenSpain

I see no difference in the 2 really, so, yep. 142% vs 137% at the moment each was captured, should be way different. About the same fps. It will always vary some. I guess that's "good" news, at least you should know when you get it working so you can retest emby. 

 

I was interested as I did not understand why your machine could be so difficult when mine was so easy. It has to be the CPU/GPU not being fully supported yet, at least by some of the tools, maybe not all. I think there should be a way to get that from the Intel site you located. 

I'm going to try installing Lubuntu 18.10 to see what happens.

Link to comment
Share on other sites

sfatula

Be sure and post back! I don't see why Lubuntu should be any different than the other flavors as far as vaapi. 18.10 should have later versions at least of various libraries and drivers. I do want to hear your results. 

  • Like 1
Link to comment
Share on other sites

Since you're mentioning mpv, I'm having a hard time following what you guys are discussing. Emby Server does not use mpv, however, some of our apps do.

 

If you are discussing Emby Server transcoding, then perhaps you might like to get involved with the changes in the beta channel. If so then you can participate here:

 

https://emby.media/community/index.php?/topic/64534-36058-hardware-acceleration-settings/

 

Thanks guys.

  • Like 1
Link to comment
Share on other sites

LeidenSpain

Since you're mentioning mpv, I'm having a hard time following what you guys are discussing. Emby Server does not use mpv, however, some of our apps do.

 

If you are discussing Emby Server transcoding, then perhaps you might like to get involved with the changes in the beta channel. If so then you can participate here:

 

https://emby.media/community/index.php?/topic/64534-36058-hardware-acceleration-settings/

 

Thanks guys.

I will be happy to help in any way I can.
That if I notice that my knowledge is something basic, so I need to be guided.
Link to comment
Share on other sites

sfatula

Since you're mentioning mpv, I'm having a hard time following what you guys are discussing. Emby Server does not use mpv, however, some of our apps do.

 

If you are discussing Emby Server transcoding, then perhaps you might like to get involved with the changes in the beta channel. If so then you can participate here:

 

https://emby.media/community/index.php?/topic/64534-36058-hardware-acceleration-settings/

 

Thanks guys.

 

 

Summary:

 

mpv came up as he was comparing emby not transcoding with another player transcoding, but that player used mpv so it was not the same thing. That lead him to believe that emby was messing up. But we just showed that ffmpeg will not use vaapi on his machine, so, now he's going to try and solve that. 

Link to comment
Share on other sites

LeidenSpain

Summary:

 

mpv came up as he was comparing emby not transcoding with another player transcoding, but that player used mpv so it was not the same thing. That lead him to believe that emby was messing up. But we just showed that ffmpeg will not use vaapi on his machine, so, now he's going to try and solve that. 

correct

The problem is the way used in my system with ffmpeg and VA-API.

Emby works fine (in anothers computers :D )

Link to comment
Share on other sites

LeidenSpain

OK, this is the actual situation:

  • installed Lubuntu 18.10
  • update
  • upgrade
  • dist-upgrade

The system don't recognice the GPU.....

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...