Encoding overload/ cpu to hot?

rockbottom

Active Member
10:48:25.228: Output 'simple_stream': Total frames output: 75293
10:48:25.228: Output 'simple_stream': Total drawn frames: 75403
10:48:25.231: ==== Streaming Stop ================================================
10:48:25.341: warning: 2 frames left in the queue on closing

0
10:24:26.488: Output 'simple_stream': Total frames output: 134902
10:24:26.488: Output 'simple_stream': Total drawn frames: 134968
10:24:26.491: ==== Streaming Stop ================================================

Witcher
12:17:54.688: Output 'simple_stream': stopping
12:17:54.688: Output 'simple_stream': Total frames output: 92898
12:17:54.688: Output 'simple_stream': Total drawn frames: 93030 (93031 attempted)
12:17:54.688: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 1 (0.0%)
12:17:54.688: Video stopped, number of skipped frames due to encoding lag: 4/92958 (0.0%)
12:17:54.691: ==== Streaming Stop ================================================
12:17:54.778: warning: 2 frames left in the queue on closing
 

rockbottom

Active Member
Next step, rebuild your Scene Collection slowly, test along the way or go back to the old collection & start troubleshooting it. I won't be helping with either.
 

rockbottom

Active Member
Fire up GPU-Z when you get a chance & confirm your 3070 is running @ x16 4.0 & not x8 4.0.

Video Encode Thread is still on the slow side. It should look more like this.
21:08:11.522: obs_graphics_thread(16.6667 ms): min=0.572 ms, median=16.667 ms, max=373.675 ms, 99.9853% within ±2% of 16.667 ms (0.00756859% lower, 0.00710284% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.174 ms, median=16.671 ms, max=54.188 ms, 95.8738% within ±2% of 16.667 ms (1.94175% lower, 2.18447% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.239 ms, median=16.664 ms, max=52.542 ms, 97.4246% within ±2% of 16.667 ms (1.05248% lower, 1.52287% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.207 ms, median=16.663 ms, max=163.72 ms, 96.3167% within ±2% of 16.667 ms (1.50275% lower, 2.18056% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.287 ms, median=16.664 ms, max=45.766 ms, 96.2005% within ±2% of 16.667 ms (1.66359% lower, 2.13596% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.274 ms, median=16.663 ms, max=65.359 ms, 95.8251% within ±2% of 16.667 ms (1.80549% lower, 2.36939% higher)

Not this:
10:48:27.277: obs_graphics_thread(16.6667 ms): min=6.132 ms, median=16.667 ms, max=1088 ms, 99.7508% within ±2% of 16.667 ms (0.126361% lower, 0.122818% higher)
10:48:27.277: obs_gpu_encode_thread(16.6667 ms): min=5.508 ms, median=16.672 ms, max=28.499 ms, 36.4933% within ±2% of 16.667 ms (31.6411% lower, 31.8656% higher)
 

rockbottom

Active Member
Double check your capture settings, some of the logs it's correct but
09:46:39.110: [game-capture: 'Game Capture'] d3d12_init: device=0x26D9D5386D0
09:46:39.110: [game-capture: 'Game Capture'] DXGI_SWAP_CHAIN_DESC:
09:46:39.110: BufferDesc.Width: 2560
09:46:39.110: BufferDesc.Height: 1369
 

meraki

New Member
Those logs look way better than the slop you were rolling out earlier.

Personally I think your audio routing is lame, using both Global & Source Audio concurrently. Not a good idea. Might be the cause of the audio lag but further testing will be needed on your end.
i dont understand what global and source audio you mean?

in global audio device under settings, i have it disabled and jsut use the mic under source.

Could be forgot when tried a clean profile- but its how i usually have it (just checked- and it wasnt disabled on this profile)


im not sure what to look at in the other logs you posted?

i shall test again later.
 

meraki

New Member
Fire up GPU-Z when you get a chance & confirm your 3070 is running @ x16 4.0 & not x8 4.0.

Video Encode Thread is still on the slow side. It should look more like this.
21:08:11.522: obs_graphics_thread(16.6667 ms): min=0.572 ms, median=16.667 ms, max=373.675 ms, 99.9853% within ±2% of 16.667 ms (0.00756859% lower, 0.00710284% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.174 ms, median=16.671 ms, max=54.188 ms, 95.8738% within ±2% of 16.667 ms (1.94175% lower, 2.18447% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.239 ms, median=16.664 ms, max=52.542 ms, 97.4246% within ±2% of 16.667 ms (1.05248% lower, 1.52287% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.207 ms, median=16.663 ms, max=163.72 ms, 96.3167% within ±2% of 16.667 ms (1.50275% lower, 2.18056% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.287 ms, median=16.664 ms, max=45.766 ms, 96.2005% within ±2% of 16.667 ms (1.66359% lower, 2.13596% higher)
21:08:11.522: obs_gpu_encode_thread(16.6667 ms): min=0.274 ms, median=16.663 ms, max=65.359 ms, 95.8251% within ±2% of 16.667 ms (1.80549% lower, 2.36939% higher)

Not this:
10:48:27.277: obs_graphics_thread(16.6667 ms): min=6.132 ms, median=16.667 ms, max=1088 ms, 99.7508% within ±2% of 16.667 ms (0.126361% lower, 0.122818% higher)
10:48:27.277: obs_gpu_encode_thread(16.6667 ms): min=5.508 ms, median=16.672 ms, max=28.499 ms, 36.4933% within ±2% of 16.667 ms (31.6411% lower, 31.8656% higher)
ive never used it before.
where do i see what its running at?

in my nvidia control panel it says x16 gen 2

so im guessing thats what its suppsoed to be at.
 
Last edited:

rockbottom

Active Member
OK

The stats indicate that there's room for improvement due to slower than expected performance for your set-up. Check the PCI-e buss for proper operation & update the capture resolution prior & let it rip.
 

meraki

New Member
OK

The stats indicate that there's room for improvement due to slower than expected performance for your set-up. Check the PCI-e buss for proper operation & update the capture resolution prior & let it rip.
how do i check the pci bus is its ok?

ill ahve a look at the capture resolution too:)
 

meraki

New Member
OK

The stats indicate that there's room for improvement due to slower than expected performance for your set-up. Check the PCI-e buss for proper operation & update the capture resolution prior & let it rip.
ok so,..im not sure how to do that- but i think its by doing a render test from teh graphics card menu`?
if thats correct in that section it said to look to the bus interface readout, which i think is in the sensors tab?

in that tab, during the render test, the bus interface load went between 6-10%

i dont know how much it should go to? or if i checked it right.

when i used the lookup i got the message graphics devide lookup failed, we could not find your gpu in our database, which may not yet dispay rare or unreleased devices,..which is strenace as i havea envidia geforce rtx 3070, which is neither rare or unreleased
 

rockbottom

Active Member
Lookup just opens up https://www.techpowerup.com/gpu-specs/nvidia-geforce-rtx-3090-founders-edition.b8046

I do have an FE.

1737291832814.png
 

rockbottom

Active Member
Founder's Edition

Cool! If it was running @ x8 4.0, your 3070 would be getting nerfed. I did some benchmark testing with my set-up using both x16 & x8 configurations & the difference was about 25%.

Check that capture res/update if needed & run a test. If there's still some funk, run a second test with the main monitor @ 60HZ instead of 120HZ.
 
Top