Question / Help Sudently can't record without STUTTER, why???

Vingji

New Member
Hi guys, i have been recordin on my PC just fine but when i installed the FORAZA HORIZON 4 Demo and began playing , at the end i found out that the video is unwatchable. I have tried all dhe combination of settings i can on OBS and it does not work. So i thought maybe its the game that its to heavy so i loaded another crappy game and its the same thing. If you see my log file i loose more then 30% of the frames, if the video is long i loose even more.

Can anyone give me some suggestion.

MY PC: i7 4770, 16GB ddr3, RX 470 4GB, 525GB SSD

ps. i have tried every combination in the settings area but nothing has worked, it begins smooth and then just keeps on loosing frames.

Problem is that now i can not use it in any game, and i just found out that i can use AMD Relive, but the audio is bad there, so i want to get back to OBS
 

Attachments

Stop using monitor capture as a source for your game. Use game capture and by the way, disable Windows GameDVR,
Thnx for the response, by the way it has worked fine for over a year now like this so thats why i said suddently. Anyway going to try right away and let you know. Hope it works.
 
Yes, game capture is like 3x as fast as display. I couldn't record 720p45 without stutter with Display capture, now I get 1080p60 easily with game capture.
 
New log file?

The first log file shows, that you have not disabled Windows 10 Game DVR (which I recommend to turn off).
It also shows GPU overload (rendering lag) and massive CPU overload (x264 encoding lag) when using x264 very fast and only GPU overload, when using AMF GPU encoder.
Stick to the AMF encoder, because the CPU is not fast enough for your games+OBS encoding and make sure, your GPU load is not reaching over 95% (so you need an FPS limit and you may have to reduce some ingame details).
 
New log file?

The first log file shows, that you have not disabled Windows 10 Game DVR (which I recommend to turn off).
It also shows GPU overload (rendering lag) and massive CPU overload (x264 encoding lag) when using x264 very fast and only GPU overload, when using AMF GPU encoder.
Stick to the AMF encoder, because the CPU is not fast enough for your games+OBS encoding and make sure, your GPU load is not reaching over 95% (so you need an FPS limit and you may have to reduce some ingame details).
He could try using ultrafast. It really doesn't look that bad. And yeah, an FPS limit could be quite helpful depending on the game.
 
Ultrafast looks worse than NVENC, so I'm not sure, how AMF compares to x264 Ultrafast, but sure, Ultrafast will produce less CPU load, while compression quality suffers.
 
Ultrafast looks worse than NVENC, so I'm not sure, how AMF compares to x264 Ultrafast, but sure, Ultrafast will produce less CPU load, while compression quality suffers.
I suppose it depends on the game, I used to record in ultrafast when I had an iGPU and it looks perfectly fine. I use QuickSync with my GT 1030 now, though.
 
Sure, there are games, that are easy to compress and games that are horrible to compress. At relatively low bitrates, that are common for streaming (for example 3000 - 6000kbit/s), the difference between Ultrafast and Very Fast is quite noticeable. From my own tests, I would even say, that the quality increase from switching from ultrafast to very fast is way bigger, than switching from very fast to medium (that's why very fast is the default setting...it has the best balance between CPU load and compression quality).
 
the strange thing guys is that all was working great and when i tried to record with Forza 4, i got this issue and the problem is that this problem now is with all other games, and part of what you have said, i have tried all the possible combinations of settings, like bitrate, like encoder, CPU at ultra to all others, lower framerate, lower resolution, lower the ingame settings and so on. With the AMD Relive i can record just fine with 1080 at 60 FPS with 30Mbs but i have only one problem with Relive that the audio is a bit noisy sometimes.
 
Then maybe something has changed, that increased your CPU load..could be a new driver for a device or a browser source in OBS, that is demanding.
You could create a new scene collection (not just a scene) in OBS and only add the game_capture source to it. Then test with that.
 
Back
Top