Jacob_B 1 Posted December 7, 2020 Posted December 7, 2020 (edited) Scenario: 12/4 Running QTS Version 4.5.1.1480 and Emby 4.5.2 No issues with Converting using 1050 Ti. (logs attached) 12/7 Updated QTS Version 4.5.1.1495 and Emby 4.5.3 Unable to utilize the 1050 Ti for converting (logs attached) Any ideas what "Encoder does not support the minimum required encoding level (HevcLevel3)" means or how to fix? *Edit* Added transcode log showing failure when un-selecting VAAPI (transcoding->advanced) attempting to force 1050 usage. Tried: Downgrading NVIDIA GPU Driver 4.0.2->4.01(Previous Version) - Reboot Downgrading Emby 4.5.3->4.5.2 2020-12-07-Fail.txt 2020-12-04.txt 2020-12-07.txt Edited December 7, 2020 by Jacob_B Add Failure Log And Added Troubleshooting
softworkz 4278 Posted December 9, 2020 Posted December 9, 2020 @Jacob_B I see two different issues in your logs: libx265 encoding profile not recognized (when falling back to CPU-transcoding) => this has been fixed internally Your GeForce Ti's capabilities are probably not detected correctly => Could you please post the hardware detection log? Thanks
Jacob_B 1 Posted December 10, 2020 Author Posted December 10, 2020 6 hours ago, softworkz said: @Jacob_B I see two different issues in your logs: libx265 encoding profile not recognized (when falling back to CPU-transcoding) => this has been fixed internally Your GeForce Ti's capabilities are probably not detected correctly => Could you please post the hardware detection log? Thanks Thanks for looking into this! I have attached the most recent hardware detection log. QNAP TVS-1272XU - i3-8100 Firmware: 4.5.1.1495 NvKernelDriver: 4.5.1.1495 NVIDIA GPU Driver: 4.0.2 Emby Server: 4.5.3.0 Usage: Using the folder sync plugin for these conversions to reduce size before syncing the content across a high latency low bandwidth link. hardware_detection-63742928580.txt
softworkz 4278 Posted December 10, 2020 Posted December 10, 2020 @Jacob_B - Thanks a lot for the detection log. In recent drivers, Nvidia have changed the reporting of HEVC levels to the level numbers that the HEVC spec is using - which is the decimal level multiplied by 30. So, level 6.2 becomes 186. We have adapted Emby to that change, but your version of the Nvidia driver still reports the old way. We have internally fixed this now, so that Emby can deal with both variants. Sorry for the inconvenience!
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