A question for the OBS Studio crowd:
Most discussions of Process Lasso settings to help OBS are about the main executable, obs64.exe.
But while recording, obs-ffmpeg-mux.exe is also running.
Should we use Process Lasso to adjust any of its settings?
(I already have Process Lasso set to go to the Bitsum Highest Performance power plan, and many of the "usual" tips implemented.)
Optimizing obs64.exe (priority, CPU affinity, power plan) makes sense because it directly affects recording/streaming performance.
Adjusting obs-ffmpeg-mux.exe offers little to no benefit since it does not significantly impact frame drops, encoding quality, or system load during capture.
Yes, adjusting obs-ffmpeg-mux.exe settings via Process Lasso can be beneficial, particularly around CPU affinity, priority settings, and power plans.
Considering that both obs64.exe and obs-ffmpeg-mux.exe are active during recording, do you think adjusting the Process Lasso settings for obs-ffmpeg-mux.exe could enhance performance, and if so, what specific adjustments would you recommend?
A conundrum emerges! Beyond the well-trodden path of obs64.exe, lies an often-overlooked companion. Could optimizing obs-ffmpeg-mux.exe unlock hidden performance?
From what I've seen, I probably wouldn't give obs-ffmpeg-mux.exe special treatment unless you're seeing an actual bottleneck tied to it.
obs64.exe does the heavy lifting during capture, encoding, scene rendering, plugins, etc. The mux process is generally more of a helper that handles packaging/writing the output stream. It's usually short-lived and much lighter on CPU usage compared to the main OBS process.
If your recordings are already stable and you're using the Bitsum Highest Performance plan plus the common OBS tweaks, I'd keep the tuning focused on obs64.exe. Adding aggressive priorities to helper processes can sometimes create unintended competition for resources.
That said, if you're seeing delayed finalization, recording hangs, or disk I/O spikes at the end of recordings, then it might be worth monitoring obs-ffmpeg-mux.exe specifically in Process Lasso and checking whether it's actually becoming a constraint.
I'd be interested to hear if anyone has benchmarked this with long recordings or high bitrate captures.