I’m very new to this. I’ve only tried recording about two times in game, but both times obs says it’s recording over an hour and then I click stop recording and the video is only the first 10mins. I also went into obs periodically to check and it said it was recording and showed the screen I was on. I tried both record display and record game and then selecting my game, but it did it both times. I have no hot keys (that I know of) listed to stop recordings. I checked the timers and I have no timers on. I checked obs multiple times while recording and it had the red icon beside it. I’m using a laptop with the most up to date windows if that’s relevant.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
OBS says it’s recording for an hour, but the video is only 10-20mins long
- Thread starter lizardd06
- Start date
Tomasz Góral
Active Member
It’s not a recording or streaming session.
But looked on this logs i see, ultravoltage processor (bad news), 4K resolution, 60 fps and intel graphics, is not possible to save correct records video because this machine is too slow for this quality.
But looked on this logs i see, ultravoltage processor (bad news), 4K resolution, 60 fps and intel graphics, is not possible to save correct records video because this machine is too slow for this quality.
Lawrence_SoCal
Active Member
To clarify Tomasz' comment
That is an older U series (ie ultra-low voltage) CPU, optimized for battery life, not the computationally demanding task of real-time video encoding.
I recommend monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization [for ex. using Task manager’s Performance tab and/or Resource Monitor] to see if your system is being maxed out with your settings [which it more than likely us]. The increasing time delay Audio Processing is a common indicator of an overwhelmed system. https://obsproject.com/wiki/General-Performance-and-Encoding-Issues and https://obsproject.com/wiki/GPU-overload-issues
With Intel GPU, you'll want to read up on using QuickSync. To avoid (or minimize) thermal throttling, you'll want to make sure plenty of cooling (like cold air being directed at air intake, etc). Then optimize the Operating System (turning off unnecessary processes, eye candy, etc).. really streamline the system. Learn how your system responds to overheating/throttling
Oh, Do you have Win10 Game DVR=On for a reason?
Do yourself a favor, drop to 1080p30 and learn to use OBS, and don't drive blind, so to speak. Use Hardware Resource monitoring, and plan to leave plenty of headroom. That is target maybe something like a sustained 80% CPU (if your system can handle even that, it may overheat and throttle even then). You want to leave 10-20% spare headroom for the occasional/un-expected so system doesn't crash or fail to record as you are experiencing.
That is an older U series (ie ultra-low voltage) CPU, optimized for battery life, not the computationally demanding task of real-time video encoding.
I recommend monitoring hardware resource (CPU, GPU, RAM, Disk I/O, etc) utilization [for ex. using Task manager’s Performance tab and/or Resource Monitor] to see if your system is being maxed out with your settings [which it more than likely us]. The increasing time delay Audio Processing is a common indicator of an overwhelmed system. https://obsproject.com/wiki/General-Performance-and-Encoding-Issues and https://obsproject.com/wiki/GPU-overload-issues
With Intel GPU, you'll want to read up on using QuickSync. To avoid (or minimize) thermal throttling, you'll want to make sure plenty of cooling (like cold air being directed at air intake, etc). Then optimize the Operating System (turning off unnecessary processes, eye candy, etc).. really streamline the system. Learn how your system responds to overheating/throttling
Oh, Do you have Win10 Game DVR=On for a reason?
Do yourself a favor, drop to 1080p30 and learn to use OBS, and don't drive blind, so to speak. Use Hardware Resource monitoring, and plan to leave plenty of headroom. That is target maybe something like a sustained 80% CPU (if your system can handle even that, it may overheat and throttle even then). You want to leave 10-20% spare headroom for the occasional/un-expected so system doesn't crash or fail to record as you are experiencing.