Emby 3.4.1.0 - vaapi problems..

[blj 3]

Hi, i've just reinstalled my openmediavault, and now i'm trying to get emby back up running.

 

I'm having issues with vaapi, which used to work with custom ffmpeg (3.2.10).

 

The new emby-server doesnt seem to have the possibility for custom ffmpeg path, so i've tried to use the included ffmpeg.

 

i get the following error  when trying to transcode, -emby is added to video group:

[AVHWDeviceContext @ 0x1789900] No VA display found for device: /dev/dri/renderD128.
libpostproc 54. 7.100 / 54. 7.100
Input #0, matroska,webm, from 'file:blahblah':
Device creation failed: -22.
Metadata:
Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Invalid argument

Edited May 18, 2018 by blj

[blj 3]

hmm, seems i have fixed it myself now. I added the 'emby' user to my users group, which have read/write/execute in my media folders...

 

Anyone knows why this should be needed.. my 'others' setting is read/execute..

[Luke 42078]

It's normal. The emby user will need to have access to the display.

[mastrmind11 722]

not sure how omv works, but generally you need to add emby to the video group, which allows access to the display.