No HEVC (H.265) encoder VAAPi

[Keltere 0]

Like the title i can seem to get the hevc encoder to appear on the list.

I use the last version of arch linux (4.19.8-arch1-1-ARCH) with the last beta of emby (3.6.0.81)

I've already installed intel-media-driver but it just won't appear

[Charlie117 58]

Emby does not support transcoding to HEVC/H.265 yet, but there is a feature request happening here for it: https://emby.media/community/index.php?/topic/48529-transcode-in-h265

[Keltere 0]

Emby does not support transcoding to HEVC/H.265 yet, but there is a feature request happening here for it: https://emby.media/community/index.php?/topic/48529-transcode-in-h265

thanks

Edited December 30, 2018 by Keltere

[Charlie117 58]

I did saw it on this thread

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

 

No, that is for decoding HEVC/H.265 and not for encoding. Notice the text Preferred Hardware Decoders.

 

Decoding is used to decompress the HEVC/H.265 video so that it can be encoded to H.264 faster. 

 

Mine looks the same as you and anyone else that has hardware support for HEVC/H.265 but can't use it yet for encoding:

 

Edited December 30, 2018 by Charlie117

[Keltere 0]

No, that is for decoding HEVC/H.265 and not for encoding. Notice the text Preferred Hardware Decoders.

 

Decoding is used to decompress the HEVC/H.265 video so that it can be encoded to H.264 faster. 

Yes, after linking i saw my mistake. Anyway do you know why i can't decide the hardware decoders?

[Charlie117 58]

What do you mean you can't decide hardware decoders? Do you not get the same checkboxes like I do in the screenshot? 

[Keltere 0]

What do you mean you can't decide hardware decoders? Do you not get the same checkboxes like I do in the screenshot?

I mean i can't choose the hardware decoders. If you check my first snapshoot you will see i can choose just the encoder for h264

Edited December 30, 2018 by Keltere

[Luke 38823]

Can you please attach the emby server log as well as the hardware detection log? Thanks.

[Keltere 0]

Can you please attach the emby server log as well as the hardware detection log? Thanks.

 

Emby server log

 

Hardware detection log

[Luke 38823]

@@softworkz

[softworkz 4280]

@@Luke - there's no ffdetect and ffmpeg version is 4.1 which is not supported by Emby

 

@@Keltere - if you are flexible, you may try another Linux distribution (just my private opinion, though)

[Luke 38823]

Ok, so alucryd hasn't gotten these changes in yet. We should have this resolved on the beta channel soon. Thanks.

[Keltere 0]

@@Luke - there's no ffdetect and ffmpeg version is 4.1 which is not supported by Emby

 

@@Keltere - if you are flexible, you may try another Linux distribution (just my private opinion, though)

Thanks, it's a remote server, i don't have the possibility to change it right now. In future i will migrate to another distribution. Arch is really unreliable even without using AUR. I think i will go with the good old debian.

Sorry if i ask but do you heave any suggestion?

 

Ok, so alucryd hasn't gotten these changes in yet. We should have this resolved on the beta channel soon. Thanks.

Thanks, i will hope that this changes will enhance the performance.

[Luke 38823]

OK regarding betas on arch linux, what you are installing is a package that is being put together by a community member, and as a result it does not have some of our customized components.

 

This week we will start producing our own official beta downloads for arch linux. It won't be in the official AUR repository, just the stable release.

 

Once we make this available I would recommend switching. If you want to continue using what you're using, then you'll need to roll back to ffmpeg 4.0.2, and you'll also need to be aware that these kinds of dependency problems may continue to happen in the future.

 

Thanks !

[Keltere 0]

OK regarding betas on arch linux, what you are installing is a package that is being put together by a community member, and as a result it does not have some of our customized components.

 

This week we will start producing our own official beta downloads for arch linux. It won't be in the official AUR repository, just the stable release.

 

Once we make this available I would recommend switching. If you want to continue using what you're using, then you'll need to roll back to ffmpeg 4.0.2, and you'll also need to be aware that these kinds of dependency problems may continue to happen in the future.

 

Thanks !

 

Thanks, sorry but i didn't understand. I've downgraded the ffmpeg to 4.0.2 but i still can't choose the decoder hardware. Is that related to the missing customized components?

 

PS: Happy new year.

Edited January 1, 2019 by Keltere

[Luke 38823]

Yes exactly, you're not going to get all of our new features using this community package.

[Keltere 0]

Sorry to bother but where it will be released? I mean where should i check for the release? The official archlinux thread?

Edited January 7, 2019 by Keltere

[Luke 38823]

It will be for download on our website. The new stable release is coming very soon though. Thanks.

[Keltere 0]

@@Luke any news on the arch version?

[Luke 38823]

Yes it should be available by the weekend. Thanks.

[Keltere 0]

The package was updated but now i can't even choose the x264

 

 

Emby server log

Hardware detect log

 

@@Luke please give it a look. Maybe some incompatibility?

 

EDIT: here is the vaainfo output

vainfo
error: can't connect to X server!
vainfo: VA-API version: 1.3 (libva 2.3.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.3.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      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

The driver path should be 

/usr/lib/dri/XXX_drv_video.so

in my case is 

/usr/lib/dri/iHD_drv_video.so

Edited January 20, 2019 by Keltere

[Keltere 0]

I've resolved by adding

LIBVA_DRIVERS_PATH=/usr/lib/dri
LIBVA_DRIVER_NAME=iHD

to the file 

/etc/conf.d/emby-server

Thanks to @@alfons27 for the solution wrote here

[Luke 38823]

Thanks for the info !