OBS x264 12700kf problem

[wildgg]

Hi LTT,

Before people will state this let me just say I can use NVENC just fine instead of x264 so streaming/recording is not an issue with NVENC.

The issue i'm running into:
I'm trying to run x264 medium cpu preset in OBS with a 12700kf(8P/4E cores), I use process lasso to give OBS all 4 E-cores but 4 E-cores is not enough to run the medium preset, so I'm trying to give OBS 2 extra P-cores but when recording starts OBS only uses the 2 assigned P-cores and shuts off the 4 E-cores.. 

I bascially can't get OBS going with a mix of P and E cores for x264 encoding, any ideas?

12700kf P-cores:5.1GHz / E-cores: 4.1GHz
Tried multiple versions of OBS studio
Windows 10
 

[Kilrah]

Win10 scheduler doesn't properly support the P/E architecture, might be due to that. Should be using Win11 with Alder Lake. 

[Bombastinator]

At least if you want to use the e-cores anyway.  Win10 could probably be updated to handle them properly, but then even fewer people would voluntarily go near win11.  I am really annoyed that Microsoft is making its product worse and worse and simply forcing consumers to use it.  It makes me feel like I’m caught in a leg hold trap.

[wildgg]

1 hour ago, Kilrah said:

Win10 scheduler doesn't properly support the P/E architecture, might be due to that. Should be using Win11 with Alder Lake. 

Yeah I guess so, I thought assigning cores manually would just work fine as it works fine for any other propgram I used E and P cores with at the same time.

I used W11 and I have to many issues with it sadly.

11 minutes ago, Bombastinator said:

At least if you want to use the e-cores anyway.  Win10 could probably be updated to handle them properly, but then even fewer people would voluntarily go near win11.  I am really annoyed that Microsoft is making its product worse and worse and simply forcing consumers to use it.  It makes me feel like I’m caught in a leg hold trap.

Totally agree with you, it is what it is I guess..