![]() ![]() 13:18:51.825: Info: Main: Highest software API version: 1.9įor those having Intel HD 3000 with NVidia or just Intel HD 3000 - there is no need to apply AMD Catalyst drivers - you just run Leshcat installer to uninstall pack of drivers (AMD Intel) and later just install Intel ones (manually or via setup.exe). 13:18:51.824: Info: Main: Highest Quick Sync hardware API version: 1.4 ![]() 13:18:49.824: Info: Main: Intel HD graphics driver: Intel(R) HD Graphics 3000 capabilities (hardware): vsinfo opt1Ĭ:\Program Files (x86)\q264>q264.exe -info preferred implementation: hardware (any) Intel Media SDK hardware: API 1.4 (minimum: 1.3) OpenCL device # 1: Advanced Micro Devices, Inc. Temp Dir: C:\Users\tskon\AppData\Local\Temp\ĭata Dir: C:\Users\tskon\AppData\Roaming\HandBrake Team\HandBrake\0.0.0.0 Yeah, it was weird that the DLLs got installed fine with the driver but somehow applications couldn’t use them that lead to some googling. Since then QSV encoding in Handbrake and q264 in Windows 10 works like a charm ! HD3000 IGPs have 100 OGL support in W11 and (most likely) W10 systems now hix3r May 9, 2022, 8:09pm 25 boombastik Thank you for testing, that is great news. ![]() "Catalyst UnifL – Catalyst Unified Leshcat Drivers" There are a few guides of how to overcome this Driver issue, just search for Intel HD 3000 Open GL support and you will see its always the same approach. work: average encoding speed for job is 271.954529 fps.įor me the solution was to replace default Windows 10 Intel drivers for HD 3000 (provided by M$ via Windows Update) and replace them with customized ones for HD 3000: below result after applying new drivers): On default W10 Intel drivers for HD 3000 there was no support for Intel QSV (insane fast hardware H264 encoding in short, e.g. GPU: Intel HD Graphics 3000 / AMD Radeon HD 7400M Series
0 Comments
Leave a Reply. |