Handbrake ignores the set affinity ex: 2 of 8 threads before the encode has begun. When the encode is started I can then go in and lower the thread usage to <8 but each item queued will reset the thread usage back to 8 when it moves onto the next
Steps to reproduce the problem (If Applicable):
Open Handbrake and set the affinity via task manager
Start an encode and it begins using all available threads on the system rather than what was specified previously
Change affinity again, with the process scaling down appropriately
Next item in queue starts, same issue and steps to solve.
HandBrake version (e.g., 1.0.0):
v1.1.2 64bit
Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):
Since we don't set affinity, only priority, it's something outside of HandBrake that is affecting this.
So once set, HandBrake can't choose to ignore it. It's down to Windows to properly schedule the applications threads.
Note, setting affinity doesn't mean HandBrake will use 2 threads. It'll still probably spawn a dozen or more. This is the correct behaviour. It's up to the operating system to schedule those threads on the defined cores.