Question / Help Frames Are Skipping

[Blackflags]

So I have assessed all possible aspects I know of. I'm running an i7 7700k clocked to 4.9 and stable. Myu GPU is an AMD R9 390. Not the newest card, but it's still a strong card. I'm attempting to stream Black Ops 4. I even tried the same settings on Stream Labs OBS. Before today, I could run the Veryfast, and even the Faster setting, NO problems. I would feel it on my game a little, but I was fine with that. Now, all of a sudden, I'm getting skipped frames detected, with ZERO dropped frames. I watch my frames drop from 60, down to 17, up to 40, down to 1, up to 60. Up down up down. I was streaming this no problem, and I should be able to no problem with my machine. I even turned off my cam, as I know they can increase CPU usage. Disabled my stream preview and everything. Lowered my bitrate, which shouldn't matter, because I'm not getting dropped frames. It's not a cooling issue. I set priority, and still having issues. My CPU is nearing 90% usage when I stream. For the life of me, I have NO IDEA what's going on. Before, it was fine. Now, it's crappy. Please help!

Log File:

https://obsproject.com/logs/Kw8hdE3JTnp9op7J

 

[mRKK2k]

So what you are saying is that you got 0% dropped frames in OBS but the preview is laggy or skipping frames?
The last time i had issues like that my gpu was overloaded. Streamlabs said 0% lost frames but the FPS-counter in the bottom left dropped down to 40 then back to 60 and so on . I switched my graphics-card into another PCIe-Lane and the issues where gone.

Try to monitor your GPU-Usage while Streaming. Even if youre using X.264 (CPU) to encode in OBS your GPU is still needed to for your sceenes aso.

 

[Blackflags]

So what you are saying is that you got 0% dropped frames in OBS but the preview is laggy or skipping frames?
The last time i had issues like that my gpu was overloaded. Streamlabs said 0% lost frames but the FPS-counter in the bottom left dropped down to 40 then back to 60 and so on . I switched my graphics-card into another PCIe-Lane and the issues where gone.

Try to monitor your GPU-Usage while Streaming. Even if youre using X.264 (CPU) to encode in OBS your GPU is still needed to for your sceenes aso.

My GPU when I play that game is usually 99-100%. I set the server manually last night, and was streaming world of warcraft with NO problem. It makes sense it would be the GPU, because WoW is more CPU intensive than Black Ops. WoW was streaming with a solid 60 frames, no drops. As soon as I went to CoD, it plummeted. I'm going to try and switch it, and see what happens. Thanks for the advice. I will keep you posted.

 

[Stream Advisor]

Obs is telling u the "game" is dropping frames. My gpu is a 100% when streaming some bigger games like COD or Fortnite.
Lowering the in-game graphics might help. Or get a better gpu / cpu. You could also try to switch the process priority to Higher in the Advanced Tab of OBS. This might lagg your game. If you lower the process priorty then it might lagg your obs. In that case better equiptment is recommended.

 

[DEDRICK]

Hit Windows+i, go to Gaming. Disable everything Game DVR and Game Bar related.

Do not have your stream playing on your second monitor in Firefox, you can have chat open but do not have the stream playing, it takes GPU away from OBS. OBS preview is fine on second monitor, anything else hardware accelerated is not because Windows 10 sucks balls at allocating GPU usage between programs.

Avoid running a Window capture of a game and a game capture in the same scene, use one or the other, not both. Game Capture should work for almost every game.

One of your USB devices is misbehaving, I forget how to troubleshoot this so I am going to shotgun a bunch of ideas.

Do you have your Webcam and Audiobox running on the same USB Hub? Can you separate them? Some systems have USB 2.0 and 3.0 ports, you could also try completely unplugging the webcam to see if it still overloads the USB bus. You can also try enabling "Use Device Timestamps" on your Audiobox sources in the mixer.

Basically this mess isn't normal no matter if the end result is invisible to the stream.

17:15:14.385: [WASAPISource::TryInitialize]:[Speakers (2- AudioBox USB)] Failed to activate client context: 88890004
17:15:14.385: [WASAPISource::WASAPISource] Device '{0.0.0.00000000}.{a63ee760-40e5-4ae7-86c5-38232e9f95f5}' not found.  Waiting for device
17:15:14.410: WASAPI: Device 'Line (3- AudioBox USB)' initialized
17:15:14.449: adding 21 milliseconds of audio buffering, total audio buffering is now 21 milliseconds
17:15:14.449: adding 21 milliseconds of audio buffering, total audio buffering is now 42 milliseconds
17:15:14.464: [window-capture: 'Window Capture 3'] update settings:
17:15:14.464:     executable: BlackOps4.exe
17:15:14.470: adding 21 milliseconds of audio buffering, total audio buffering is now 64 milliseconds
17:15:14.492: adding 21 milliseconds of audio buffering, total audio buffering is now 85 milliseconds
17:15:14.517: ---------------------------------
17:15:14.517: [DShow Device: 'Cammm'] settings updated:
17:15:14.517:     video device: Logitech HD Pro Webcam C920
17:15:14.517:     video path: \\?\usb#vid_046d&pid_082d&mi_00#6&1534b302&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\{bbefb6c7-2fc4-4139-bb8b-a58bba724083}
17:15:14.517:     resolution: 1280x720
17:15:14.517:     fps: 30.00 (interval: 333333)
17:15:14.517:     format: I420
17:15:14.536: adding 21 milliseconds of audio buffering, total audio buffering is now 106 milliseconds
17:15:14.536: adding 21 milliseconds of audio buffering, total audio buffering is now 128 milliseconds
17:15:14.557: adding 21 milliseconds of audio buffering, total audio buffering is now 149 milliseconds
17:15:14.580: adding 21 milliseconds of audio buffering, total audio buffering is now 170 milliseconds
17:15:14.597: warning: Stream #0: not enough frames to estimate rate; consider increasing probesize
17:15:14.600: adding 21 milliseconds of audio buffering, total audio buffering is now 192 milliseconds
17:15:14.624: adding 21 milliseconds of audio buffering, total audio buffering is now 213 milliseconds
17:15:14.645: adding 21 milliseconds of audio buffering, total audio buffering is now 234 milliseconds
17:15:14.675: adding 21 milliseconds of audio buffering, total audio buffering is now 256 milliseconds
17:15:14.699: adding 21 milliseconds of audio buffering, total audio buffering is now 277 milliseconds
17:15:14.719: adding 21 milliseconds of audio buffering, total audio buffering is now 298 milliseconds
17:15:14.743: adding 21 milliseconds of audio buffering, total audio buffering is now 320 milliseconds
17:15:14.766: adding 21 milliseconds of audio buffering, total audio buffering is now 341 milliseconds
17:15:14.767: adding 21 milliseconds of audio buffering, total audio buffering is now 362 milliseconds
17:15:14.793: adding 21 milliseconds of audio buffering, total audio buffering is now 384 milliseconds
17:15:14.825: adding 21 milliseconds of audio buffering, total audio buffering is now 405 milliseconds
17:15:14.897: adding 21 milliseconds of audio buffering, total audio buffering is now 426 milliseconds
17:15:14.897: adding 21 milliseconds of audio buffering, total audio buffering is now 448 milliseconds
17:15:14.897: adding 21 milliseconds of audio buffering, total audio buffering is now 469 milliseconds
17:15:14.897: adding 21 milliseconds of audio buffering, total audio buffering is now 490 milliseconds
17:15:14.925: adding 21 milliseconds of audio buffering, total audio buffering is now 512 milliseconds
17:15:14.968: adding 21 milliseconds of audio buffering, total audio buffering is now 533 milliseconds
17:15:14.968: adding 21 milliseconds of audio buffering, total audio buffering is now 554 milliseconds
17:15:14.990: adding 21 milliseconds of audio buffering, total audio buffering is now 576 milliseconds
17:15:15.013: adding 21 milliseconds of audio buffering, total audio buffering is now 597 milliseconds
17:15:15.039: adding 21 milliseconds of audio buffering, total audio buffering is now 618 milliseconds
17:15:15.069: adding 21 milliseconds of audio buffering, total audio buffering is now 640 milliseconds
17:15:15.097: adding 21 milliseconds of audio buffering, total audio buffering is now 661 milliseconds
17:15:15.097: adding 21 milliseconds of audio buffering, total audio buffering is now 682 milliseconds
17:15:15.119: adding 21 milliseconds of audio buffering, total audio buffering is now 704 milliseconds
17:15:15.141: adding 21 milliseconds of audio buffering, total audio buffering is now 725 milliseconds
17:15:15.163: adding 21 milliseconds of audio buffering, total audio buffering is now 746 milliseconds
17:15:15.184: adding 21 milliseconds of audio buffering, total audio buffering is now 768 milliseconds
17:15:15.205: adding 21 milliseconds of audio buffering, total audio buffering is now 789 milliseconds
17:15:15.225: adding 21 milliseconds of audio buffering, total audio buffering is now 810 milliseconds
17:15:15.247: adding 21 milliseconds of audio buffering, total audio buffering is now 832 milliseconds
17:15:15.382: Last log entry repeated for 5 more lines
17:15:15.382: Max audio buffering reached!
17:15:15.382: adding 21 milliseconds of audio buffering, total audio buffering is now 960 milliseconds