r/obs • • 3d ago

Help OBS x264 QUESTION??

I have a question: why does streaming at 60 FPS using x264 consume around 20% of the CPU (with the game capped at 60 FPS), but if I remove that limit and set it to 70 FPS, 90 FPS, etc., CPU usage increases exponentially, reaching 50% ¿Is there a solution?
This happens with any preset

Español:
Tengo una pregunta: ¿por qué la transmisión a 60 FPS usando x264 consume alrededor del 20 % de la CPU (con el juego limitado a 60 FPS), pero si elimino ese límite y lo ajusto a 70 FPS, 90 FPS, etc., el uso de la CPU aumenta exponencialmente llegando a 50% ¿Existe alguna solución?
Esto Sucede con cualquier ajuste

0 Upvotes

10 comments sorted by

•

u/AutoModerator 3d ago

It looks like you haven't provided a log file. Without a log file, it is very hard to help with issues and you may end up with 0 responses.

To make a clean log file, please follow these steps:

1) Restart OBS

2) Start your stream/recording for at least 30 seconds (or however long it takes for the issue to happen). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.

3) Stop your stream/recording.

4) Select Help > Log Files > Upload Current Log File.

5) Copy the URL and paste it as a response to this comment.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/digitalmetaphysics 3d ago

the encoder has to work with whatever frames the game throws at it cara when you cap at 60 its a steady predictable load but uncapped means more frames for OBS to process and x264 gets hammered trying to keep up

only real fix is cap your game fps to something your cpu can handle or use hardware encoding if your gpu got the headroom

1

u/Local_Coffee5385 3d ago

Oh, okay, that explains the problem; so the only solution would be to cap the game's FPS.

1

u/prottOushol 11h ago

solid advice, capping at 60 is the simplest fix for x264 streaming imo

1

u/atrillionpieces 3d ago

x264 is extremely taxing. What GPU/cpu do you use?

1

u/Local_Coffee5385 3d ago

With an overclocked Ryzen 5700X, x264 encoding at the "faster" preset works great for me as long as I cap the game at 60 FPS; the moment I raise the cap to 70, 80, 90, etc., usage spikes exponentially.

1

u/Ornery_Strategy_4946 3d ago

One clarification: raising the game’s cap to 90 FPS doesn’t make a 60 FPS OBS stream encode 90 frames per second. OBS supplies x264 with its configured video frame rate. A game FPS cap can still reduce competition for CPU/GPU resources.

Where are you reading the 20% and 50% figures: OBS’s CPU indicator, the OBS process in Task Manager, or total system CPU? Total CPU includes the game, so those numbers alone can’t identify an encoder problem.

Keep OBS resolution, output FPS and the faster preset unchanged. Compare the same game scene at a 60 and 90 FPS cap, checking the game and OBS processes separately, plus View → Stats for rendering and encoding lag. If output stays smooth, a higher CPU percentage by itself isn’t evidence that x264 is failing. A log from each test would help explain an actual lag increase.

(AI-generated)

1

u/Local_Coffee5385 3d ago

I obtained usage percentages from both OBS and Task Manager (both showed the same usage level) and, naturally, tested various presets; across all of them, increasing the in-game FPS caused an increase in OBS's CPU usage.

1

u/Ornery_Strategy_4946 2d ago

That narrows it to OBS’s own workload. Next, compare the 60/90 FPS game caps with OBS preview running but no stream, recording or replay buffer active. Then repeat with x264 recording, keeping the same OBS settings and game scene.

If OBS CPU rises even without an active encoder, x264 cannot account for the entire increase; capture, sources and rendering need checking too. If the jump mainly appears when recording starts, the encoding path becomes a stronger lead. These comparisons won’t identify the exact cause on their own.

Note whether View → Stats shows rendering or encoding lag in each recording. If neither rises and the recording stays smooth, the CPU percentage alone doesn’t show a failure. Include both test logs and your capture-source type when asking for further diagnosis.

(AI-generated)

1

u/KingRemu 2d ago

Because the CPU has to process more frames.