Server Version#:1.15.6.1079
Player Version#:latest
I’m having issues with 10bit H265 files on my synology when using hardware transcoding. When hardware transcoding is enabled clients get a green screen, with hardware transcoding turned off everything is fine (but CPU then suffers with multiple transcodes).
Any ideas?
Hi,
It is a Synology DS916+. The issue only manifests when transcoding X265 or HVEC with hardware acceleration enabled, with that disabled it works fine. Here is what I can see in the logs when I try to play with it enabled:
Jul 26, 2019 14:07:51.142 [0x7f33adcd7700] WARN - Failed to find encoder ‘hevc_qsv’
Jul 26, 2019 14:07:51.150 [0x7f33adcd7700] ERROR - [FFMPEG] - Encoding entrypoint not found (17 / 6).
Jul 26, 2019 14:07:51.152 [0x7f33adcd7700] WARN - avcodec_open2 returned -38 for encoder ‘hevc_vaapi’
Jul 26, 2019 14:07:51.242 [0x7f33ae5a1700] ERROR - ClientProfileExtra: video transcode target already exists for streaming hls
Jul 26, 2019 14:07:52.340 [0x7f33ae5a1700] ERROR - [Transcoder] [hevc @ 0x261c280] Failed setup for format vaapi_vld: hwaccel initialisation returned error.
It is installed natively and my network is fine. Like I say, everything plays fine apart from h265 when hardware transcoding is enabled. H264 is fine with hardware transcoding. I believe the nvidia shield also had the same issue with the Plex sever on there not being able to hardware transcode h265 which has just been resolved in the latest beta for nvidia shield.
I think it may be a limitation on my hardware.
DS916+ will only decode 8bit HEVC.
It would be good if Plex could detect this and failback to non hardware transcoding so It is still available when needed.
Plex does fall back however there is a problem with that. It’s unreliable fallback in all cases and why the transcoder is undergoing a major update to fix it along with other reasons.
The DS916+ utilizes the N3710 CPU
DS916+ Intel Pentium N3710 Quad Core 4 Yes Braswell DDR3 2 / 8 GB
Braswell cannot handle 4K in hardware but can process HEVC SDR (8 bit). The first processor to give us this capability is the KabyLake. (-7xxx series) and its companion the J3455.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
