tjmc1134 0 Posted May 28, 2020 Posted May 28, 2020 Hello, Preferred Hardware Decoders / Encoder are missing on my DS218+. I've attached my server log, transcoding log, and hardware detection logs. I've read through Hardware Acceleration Overview but nothing helped. I am a premiere member. Running ffdetect vadec and vaenc is successful. Running ffdetect qsvenc fails with "Error initializing an MFX session: MFX_ERR_UNSUPPORTED". Running ffmpeg manually with vaapi does work. # ffmpeg \ > -hwaccel vaapi -hwaccel_output_format vaapi \ > -i http://distribution.bbb3d.renderfarming.net/video/mp4/bbb_sunflower_1080p_30fps_normal.mp4 \ > -c:v h264_vaapi \ > /tmp/example.mp4 ... Output #0, mp4, to '/tmp/example.mp4': Metadata: major_brand : isom minor_version : 1 compatible_brands: isomavc1 composer : Sacha Goedegebure title : Big Buck Bunny, Sunflower version artist : Blender Foundation 2008, Janus Bager Kristensen 2013 comment : Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net genre : Animation encoder : Lavf58.35.100 Stream #0:0(und): Video: h264 (h264_vaapi) (High) (avc1 / 0x31637661), vaapi_vld(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 30 fps, 15360 tbn, 30 tbc (default) Metadata: creation_time : 2013-12-16T17:44:39.000000Z handler_name : GPAC ISO Video Handler encoder : Lavc58.62.100 h264_vaapi Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1(side), fltp, 394 kb/s (default) Metadata: creation_time : 2013-12-16T17:44:42.000000Z handler_name : GPAC ISO Audio Handler encoder : Lavc58.62.100 aac Side data: audio service type: main frame= 302 fps= 41 q=-0.0 size= 4608kB time=00:00:09.96 bitrate=4059.0kbits/s dup=2 drop=0 throttle=off speed=1.26x Any thoughts on what I could do to help debug further? hardware_detection-63726301199.txt ffmpeg-transcode-7b66414b-9a29-40b9-bead-387c44f6b5c4_1.txt embyserver.txt
Luke 40067 Posted June 2, 2020 Posted June 2, 2020 Hi there, VAAPI is what we're currently supporting on Synology. Can you use that?
tjmc1134 0 Posted June 6, 2020 Author Posted June 6, 2020 I moved back to using the Synology package instead of emby/embyserver docker image and that fixed the problem. I'd prefer to use docker so if there is anything else I can do to help debug let me know.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now