krislemke 1 Posted January 29, 2024 Posted January 29, 2024 The issue seems clear to me, from hardware detection: Failed to initialize VA /dev/dri/render D128 Just not sure how to correct. Direction would be awesome. Thanks! hardware_detection-63842135605.txt ffmpeg-transcode-583b9ab7-2450-4b48-b571-cdc3a027c503_1.txt embyserver.txt
Luke 42077 Posted January 29, 2024 Posted January 29, 2024 Hi, are you able to try the 4.8 beta server and see how it compares?
krislemke 1 Posted January 30, 2024 Author Posted January 30, 2024 Yup. Seems to work now. Thanks!! 1
antcilli 3 Posted February 1, 2024 Posted February 1, 2024 @krislemke, what does your transcoding page look like now that it's working? I made the jump to the latest beta version as well and now I can see two software encoders showing up - are you seeing the N100 register as a hardware decoder or encoder? I tried transcoding a few different videos too and never saw it leverage the hardware acceleration during playback. 1
antcilli 3 Posted February 1, 2024 Posted February 1, 2024 @krislemkeignore me. I found a typo in the GIDLIST on my docker-compose file for the render option. After correcting that (as well as updating to the latest beta), all of the hardware decoder/encoder options showed up and it's working flawlessly now. Transcoding a 4K H265 stream down to a 720p H264 stream used to push the CPU to around 80% of its capacity and now it's < 5% utilization. Quality is still really good even on the high speed settings, so I'm super happy with the performance of this little N100 processor. 2
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