HandBrake

@Ritsuka please fix this.

Problem solved.

With newer versions of handbrake, up to 1.6.1 I have to do the following:

Enter windows settings, display, graphics and after selecting manually handbrake.worker, change the option to force Intel Xe Graphics.

I have tried again with different options, only intel qsv encoders fails.

Sorry, windows version is 23H2

Description of problem or question: Handbrake 1.7.0 is not working it gives an error and it doesn´t start encoding (no matter the encoder, H265 H264 alone or intel qsv versions). No problems with 1.6.1. Steps to reproduce the problem (If Applicable): Download Handbrake 1.7.0 and start encoding a vi...

Description of problem or question: Handbrake 1.7.0 doesn´t have .NET 8 support Steps to reproduce the problem (If Applicable): HandBrake version (e.g., 1.0.0): 1.7.0 Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update): Windows 11 HandBrake Act...

There are no plans to support .NET 7. .NET 7 is not an in-place upgrade to .NET 6. It runs along side it. Any app compiled for 6, requires 6. .NET 6 is a Long term service release which means it gets maintenance updates through November 2024. This also means there is no real need to uninstall it. I...

Any problem if i leave it to auto? quality or bitrate is decreased versus if i set 4.1 or 5.0 level?

It's an indication that your breaching an attribute of the level. We'd need to see teh full log to say what exactly but you'll probably have to use 5 or 5.1 for this source. If i set it to auto a level 4 file is created. Also with handbrake 1.5.1 and nigthlys before november, i can use level 4.1 wi...

Now the log with codification level set to AUTO, this way it works: HandBrake 1.6.0 (2022122800) OS: Microsoft Windows NT 10.0.22621.0 CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Ram: 16106 MB, GPU Information: Intel(R) Iris(R) Xe Graphics - 31.0.101.4032 NVIDIA GeForce MX350 - 31.0.15.2756 ...

Your out of luck then I'm afraid. 1.6.0 requires a newer driver due to the newer Intel SDK we use. If acer are not providing that and you can't use the Intel one, your next best option is to rollback to 1.5.1 Hi, I also have this problem with a Tigerlake laptop using h.265 intel QSV. And it´s a bug...