When rendering, you are given the option of selecting a number of Encoder threads. This is by default at 1, and can be increased up to n where n is cores. However, the ever popular x264's default is cores * 1.5 by default. It will use this if you pass threads=0 to it. So I believe the number of threads should be unlocked to allow a user to specify any value and I think the default behaviour should be to have it set as 0 so that the encoder will (more often than 1 is appropriate) pick a sensible number of threads to use. Reproducible: Always
Fixed somewhere on time.
What commit fixed this? Just tried master and the behaviour is the same, threads locked to 1-n cores where n is number of cores.
sorry my fault.
(In reply to Peter from comment #2) > What commit fixed this? > > Just tried master and the behaviour is the same, threads locked to 1-n cores > where n is number of cores. can you pease try 19.12.1
Just tested, on the rendering panel the Threads are limited to CPU threads (on my system these are 12) .. ussually i set this value to 0 to use all CPU capacity during rendering. (90-95 % CPU USAGE)
(In reply to farid from comment #4) > (In reply to Peter from comment #2) > > What commit fixed this? > > > > Just tried master and the behaviour is the same, threads locked to 1-n cores > > where n is number of cores. > > can you pease try 19.12.1 I would say this is fixed, now allows threads to be set from 0-n cores where n is number of cores. Mostly want to be able to set threads to 0 or omit the number of threads entirely and let the codec choose. Have had this locally patched for years, good to see it working. I'll leave whether or not to close it to you guys as I guess the threads value hasn't been unlocked? But I'm happy with it now.
Closing then, thanks.