Encoding overload/ cpu to hot?

[meraki]

When you edited the Register to Disable Game DVR, you actually left it enabled but disabled Game Mode. I would undo that & update the settings in Windows Gaming.

12:23:21.817: Game Bar: On
12:23:21.817: Game DVR: On
12:23:21.817: Game DVR Background Recording: Off
12:23:21.818: Game Mode: Off

yeah, im having a real hard time to get rid of this.
i tried to update in windows gaming, game mode i disabled in windows, that was easy, but the bar i had a hell of a time with and its still not fixed. goodled it the whole of yesterday and tried everything that was suggested down to shell commands,.. and its still there.

what would you undo? turn game mode on again? i went into the registry because nothing else worked in regards to turn off the game bar and dvr

 

[rockbottom]

Yep, Game Bar & DVR aren't needed & can be disabled but you should have Game Mode on.

After you get the plugins updated run another test & use a game that you're not having trouble capturing. After the test, close/re-open OBS & then upload the previous file. Need to see where your system is lagging.

Here's a couple more stale plugins I found.
12:23:24.298: [Move Transition] loaded version 2.12.0

Move - History

obsproject.com

12:23:36.513: [Source Clone] loaded version 0.1.4

Source Clone - Updates

obsproject.com

 

[meraki]

Yep, Game Bar & DVR aren't needed & can be disabled but you should have Game Mode on.

After you get the plugins updated run another test & use a game that you're not having trouble capturing. After the test, close/re-open OBS & then upload the previous file. Need to see where your system is lagging.

Here's a couple more stale plugins I found.
12:23:24.298: [Move Transition] loaded version 2.12.0

Move - History

obsproject.com

12:23:36.513: [Source Clone] loaded version 0.1.4

Source Clone - Updates

obsproject.com

all plugins should be ok now.

https://obsproject.com/logs/APXMUxNOodD65QOb

https://obsproject.com/logs/zYOcPSU9S8EBQFf6

you able to read some sense out of that?

something weird happened today, from twitch stream manager it had a warning symbol about streaming at too high bitrate and that the stream was unstable. i stream at 4000 kbps, and have not changed that in a long time, so i dont know why that error was showing there. it stabilised for a few minutes, then going back to show say it was usntable due to too high bitrate

 

[meraki]

as an note to my last post about twitch manager and bitrate- it seems i ahve switched from simple to advanced output settings, and in the advanced one the bitrate was higer- its now set to 4k in both- so i think that dealt with that issue atleast. still the rendering alg and such to deal with:-/

its giving me ulcers

 

[rockbottom]

So your rendering lag was much higher before, making progress. Your system appears to be running good, timings at the bottom of the log look A-OK.

A good troubleshooting step, create a New Scene Collection with just (1) Scene/Source & test. It won't mess with your current Profile but will help determine if something is buggy in the Profile.

Today's log
12:05:33.077: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 22 (0.0%)
12:05:33.077: Video stopped, number of skipped frames due to encoding lag: 22/51837 (0.0%)

Yesterday's log
13:31:48.250: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 7982 (18.1%)

13:35:54.569: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 9513 (64.9%)

 

[meraki]

So your rendering lag was much higher before, making progress. Your system appears to be running good, timings at the bottom of the log look A-OK.

A good troubleshooting step, create a New Scene Collection with just (1) Scene/Source & test. It won't mess with your current Profile but will help determine if something is buggy in the Profile.

Today's log
12:05:33.077: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 22 (0.0%)
12:05:33.077: Video stopped, number of skipped frames due to encoding lag: 22/51837 (0.0%)

Yesterday's log
13:31:48.250: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 7982 (18.1%)

13:35:54.569: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 9513 (64.9%)

ok, so this is my log with just a g ame in the scene- in g ame capture mode/ not window capture mode.
i went for games thats given me issues before, witcher and path of exile 2

https://obsproject.com/logs/v6fg14qf9T0oloWv

https://obsproject.com/logs/rhuyRs3exTqJq5uA

(im not sure why i got two log fiels for the session)
getting audio
rendering and encoder issues here.

with jsut games and nothing else.

again, i feel my system should be more than capable of handling this.
when it dosent, is that sign of hardware error?

it says my mic could be cause of the audio buffering, but its muted and not even in that scene.

i did not create a new profile for this, just a new scene that had only the game capture source in it

 

[rockbottom]

Nothing changed in those logs. Both still have the large Scene Collection, lots of filters in play, PLUS I've been ignoring the SE & Java Script errors that make up most of your logs.

 

[rockbottom]

Here's the mic buffering. This may indicate that the system was overloaded at the time.

11:42:41.594: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: a.shure)

11:42:55.759: adding 128 milliseconds of audio buffering, total audio buffering is now 170 milliseconds (source: a.shure)
11:42:55.759:
11:42:58.363: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:60091
11:43:00.773: adding 149 milliseconds of audio buffering, total audio buffering is now 320 milliseconds (source: a.shure)
11:43:00.773:

12:27:55.791: Max audio buffering reached!
12:27:55.791: adding 640 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: a.shure)

 

[meraki]

https://obsproject.com/logs/2lopoVp7hfXnUIBO

https://obsproject.com/logs/1NiUvTNiAVQpfW01

ran path of exile 2 and no withcer, game capture only, this time added the mic. not getting anything showing in the analyzer here.

 

[rockbottom]

Better, now your down to 0%. Try running your main monitor @ 60HZ, see if the last of it goes away.

14:15:51.649: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 55 (0.0%)

 

[rockbottom]

13:24:30.851: - source: 'a.shure' (wasapi_input_capture)
13:24:30.851: - monitoring: monitor and output
13:24:30.851: - filter: '1.Gain' (gain_filter)
13:24:30.851: - filter: '2. Noise Suppression(bakgrunnstoy)_ported' (nvidia_audiofx_filter)
13:24:30.851: - filter: '3.Noise Gate' (noise_gate_filter)
13:24:30.851: - filter: '4.3-Band Equalizer' (basic_eq_filter)
13:24:30.851: - filter: '5.Expander' (expander_filter)
13:24:30.851: - filter: '6.Compressor' (compressor_filter)
13:24:30.851: - filter: '7.Limiter' (limiter_filter)

 

[meraki]

Nothing changed in those logs. Both still have the large Scene Collection, lots of filters in play, PLUS I've been ignoring the SE & Java Script errors that make up most of your logs.

would i have to create a new profile then?
cause i can only have one scene active at a time, and i made a new scene- with only the game capture in for the first one.


i dont understand why it pics up from scenes not in use?
like when the mic was buffering the mic wasnt in the scene

in the second test one i added mic, and now in the third test try i added vid

https://obsproject.com/logs/iDqlFestnlt3iSSi

as for SE, the only thing i have from it is a chat overlay, im not sure why it shows as error in the log, because the chat works as inteded, atleast from whats visual on screen. ive not had the chat overlay on at all today as it has its own nest sc ene

 

[rockbottom]

Troubleshooting purposes to see if your Profile is bugged. There is still some rendering lag but your monitor wasn't @ 60HZ.

I don't use SE but see below. Those SE & java script errors may be wasting resources that could be used somewhere else.

 

[rockbottom]

Your video encode thread has been somewhat underwhelming but was showing signs of improvement. 50% within 2% of 16.667 & improving to 80%. Not so in the last log, of the complete logs you posted this is the worst.

14:59:12.891: obs_gpu_encode_thread(16.6667 ms): min=0.299 ms, median=16.672 ms, max=258.134 ms, 26.0603% within ±2% of 16.667 ms (37.0853% lower, 36.8544% higher)

 

[meraki]

Your video encode thread has been somewhat underwhelming but was showing signs of improvement. 50% within 2% of 16.667 & improving to 80%. Not so in the last log, of the complete logs you posted this is the worst.

14:59:12.891: obs_gpu_encode_thread(16.6667 ms): min=0.299 ms, median=16.672 ms, max=258.134 ms, 26.0603% within ±2% of 16.667 ms (37.0853% lower, 36.8544% higher)

yeah, i didnt change the monitor settings yet. i didnt do any more test streams after the last one as i got a horrible headache from stressing with this,...

also, on a side note- when i noticed these encoding overloads (i dont think i ever had them before)
was after i cahnged my twitch username.

before i change it i never had any issues with my stream, but after i got overloading all the time, and often when i would "start streaming" obs wouldnt even send to twitch- it wasnt possible to stop the stream either, i had to shut obs down down completley.

it was because of this i initualliy uninstalled and reinstalled obs, that didnt work either, so i did a completley fresh w11 install, and those start/stop stream issues went away, but the overloading and rendering are still around.

not sure if that info help somehow-

 

[meraki]

Your video encode thread has been somewhat underwhelming but was showing signs of improvement. 50% within 2% of 16.667 & improving to 80%. Not so in the last log, of the complete logs you posted this is the worst.

14:59:12.891: obs_gpu_encode_thread(16.6667 ms): min=0.299 ms, median=16.672 ms, max=258.134 ms, 26.0603% within ±2% of 16.667 ms (37.0853% lower, 36.8544% higher)

so i did a new profile- wiuth just game capture, cam and mic- both without any filters, ran path of exile as its a game thats on the more demaning side apparantly

https://obsproject.com/logs/pcZQ1N9skMLWpRBI

Analyzer | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.

obsproject.com

i letthe wizard choose what settings, so this time isntead of the 4k bit i usually stream in it was in 6k,..but ill try again with 4k and see if it makes any difference,.. but im getting overlaods and rendering lag with nothing else in the profile aswell. it is also in slow quality, and i usually ahve it in faster. i jsut wanted to see what happened when it was all fresh

 

[meraki]

when i look in the log files i feel really confuse-. i see okami mentioned there, and thats a game i didnt even open today.

ill continue on this mission tomorrow,..my head is killing me

 

[meraki]

didnt change monitor hz, so its not at 60, again jsut wanted to see how it would work out on a fresh profile with no filters on cam or mic.
only have game capture cam and mic on.

https://obsproject.com/logs/HipeV6ylpz05fexG

https://obsproject.com/logs/p0TYqsOAFhAW4nWi

the first two with path of exile
the withcer 3 for the last one

https://obsproject.com/logs/yeLOazvd6vz5Aahq

getting audio max buffering on the last one (and thats an error that ive only seen the past couple of days)

should my system not be good enought to play and stream these games with no problem?

i mean, i have this, and while its not superduper good these days, its still decent, no? i feel i shouldnt have an issue streaming and gaming, but still it just never stops- even when the profile has been razed to almost nothing.

Does this indicate hardware error?

• NVIDIA GeForce RTX 3070
• Intel Core i7-12700
• 48 GB DDR4 3200 MHz)
  
  

 

[rockbottom]

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.

 

[rockbottom]

With all the baggage:

14:59:12.891: audio_thread(Audio): min=0.013 ms, median=0.308 ms, max=4298.49 ms, 99th percentile=3.792 ms
14:59:12.891: ┗receive_audio: min=0.006 ms, median=0.192 ms, max=8.243 ms, 99th percentile=2.302 ms, 0.880721 calls per parent call
14:59:12.891: ┣buffer_audio: min=0 ms, median=0.001 ms, max=0.292 ms, 99th percentile=0.004 ms
14:59:12.891: ┗do_encode: min=0.03 ms, median=0.186 ms, max=8.236 ms, 99th percentile=2.297 ms
14:59:12.891: ┣encode(simple_aac): min=0.026 ms, median=0.163 ms, max=8.182 ms, 99th percentile=2.273 ms
14:59:12.891: ┗send_packet: min=0.001 ms, median=0.016 ms, max=0.527 ms, 99th percentile=0.059 ms
14:59:12.891: obs_graphics_thread(16.6667 ms): min=0.086 ms, median=1.035 ms, max=4298.55 ms, 99th percentile=7.31 ms, 99.9258% below 16.667 ms
14:59:12.891: ┣tick_sources: min=0.001 ms, median=0.055 ms, max=1333.11 ms, 99th percentile=0.312 ms
14:59:12.891: ┣output_frame: min=0.076 ms, median=0.828 ms, max=4298.28 ms, 99th percentile=7.017 ms
14:59:12.891: ┃ ┗gs_context(video->graphics): min=0.076 ms, median=0.827 ms, max=4298.28 ms, 99th percentile=7.016 ms
14:59:12.891: ┃ ┣render_video: min=0.007 ms, median=0.766 ms, max=4297.95 ms, 99th percentile=6.872 ms
14:59:12.891: ┃ ┃ ┣render_main_texture: min=0.004 ms, median=0.435 ms, max=4297.95 ms, 99th percentile=6.237 ms
14:59:12.891: ┃ ┃ ┣render_convert_texture: min=0.007 ms, median=0.017 ms, max=22.539 ms, 99th percentile=0.057 ms, 0.884842 calls per parent call
14:59:12.891: ┃ ┃ ┗output_gpu_encoders: min=0 ms, median=0.051 ms, max=38.626 ms, 99th percentile=0.233 ms, 0.884842 calls per parent call
14:59:12.891: ┃ ┗gs_flush: min=0.006 ms, median=0.049 ms, max=40.857 ms, 99th percentile=0.331 ms
14:59:12.891: ┗render_displays: min=0 ms, median=0.111 ms, max=13.031 ms, 99th percentile=0.524 ms
14:59:12.891: obs_gpu_encode_thread(16.6667 ms): min=0.224 ms, median=0.575 ms, max=90.391 ms, 99th percentile=1.734 ms, 99.9875% below 16.667 ms
14:59:12.891: ┣gpu_encode_frame: min=0.22 ms, median=0.552 ms, max=90.341 ms, 99th percentile=1.692 ms
14:59:12.891: ┗send_packet: min=0.002 ms, median=0.012 ms, max=1.942 ms, 99th percentile=0.053 ms
14:59:12.891: =================================================
14:59:12.891: == Profiler Time Between Calls ==================
14:59:12.891: obs_hotkey_thread(25 ms): min=24.166 ms, median=25.34 ms, max=372.239 ms, 67.1716% within ±2% of 25 ms (0.028691% lower, 32.7997% higher)
14:59:12.891: obs_graphics_thread(16.6667 ms): min=1.833 ms, median=16.667 ms, max=4298.56 ms, 98.9187% within ±2% of 16.667 ms (0.534456% lower, 0.546825% higher)
14:59:12.891: obs_gpu_encode_thread(16.6667 ms): min=0.299 ms, median=16.672 ms, max=258.134 ms, 26.0603% within ±2% of 16.667 ms (37.0853% lower, 36.8544% higher)
14:59:12.891: =================================================
14:59:13.188: Number of memory leaks: 30


After New Scene Collection:

12:17:58.303: audio_thread(Audio): min=0.015 ms, median=0.131 ms, max=68.045 ms, 99th percentile=0.899 ms
12:17:58.303: ┗receive_audio: min=0.001 ms, median=0.383 ms, max=1.702 ms, 99th percentile=0.703 ms, 0.296773 calls per parent call
12:17:58.303: ┣buffer_audio: min=0.001 ms, median=0.001 ms, max=0.123 ms, 99th percentile=0.003 ms
12:17:58.303: ┗do_encode: min=0.037 ms, median=0.38 ms, max=1.698 ms, 99th percentile=0.697 ms
12:17:58.303: ┣encode(simple_aac): min=0.032 ms, median=0.365 ms, max=0.992 ms, 99th percentile=0.672 ms
12:17:58.303: ┗send_packet: min=0.002 ms, median=0.013 ms, max=1.255 ms, 99th percentile=0.044 ms
12:17:58.303: obs_graphics_thread(16.6667 ms): min=0.083 ms, median=0.623 ms, max=1026.98 ms, 99th percentile=2.029 ms, 99.9946% below 16.667 ms
12:17:58.303: ┣tick_sources: min=0.001 ms, median=0.02 ms, max=1025.47 ms, 99th percentile=0.278 ms
12:17:58.303: ┣output_frame: min=0.073 ms, median=0.488 ms, max=77.336 ms, 99th percentile=1.772 ms
12:17:58.303: ┃ ┗gs_context(video->graphics): min=0.073 ms, median=0.487 ms, max=77.333 ms, 99th percentile=1.77 ms
12:17:58.303: ┃ ┣render_video: min=0.005 ms, median=0.39 ms, max=24.497 ms, 99th percentile=1.604 ms
12:17:58.303: ┃ ┃ ┣render_main_texture: min=0.003 ms, median=0.279 ms, max=9.062 ms, 99th percentile=1.481 ms
12:17:58.303: ┃ ┃ ┣render_convert_texture: min=0.007 ms, median=0.013 ms, max=1.012 ms, 99th percentile=0.044 ms, 0.296884 calls per parent call
12:17:58.303: ┃ ┃ ┗output_gpu_encoders: min=0 ms, median=0.034 ms, max=23.843 ms, 99th percentile=0.165 ms, 0.296884 calls per parent call
12:17:58.303: ┃ ┗gs_flush: min=0.003 ms, median=0.114 ms, max=77.307 ms, 99th percentile=0.449 ms
12:17:58.303: ┗render_displays: min=0 ms, median=0.089 ms, max=4.287 ms, 99th percentile=0.31 ms
12:17:58.303: OBSBasicSettings::LoadThemeList: 0.091 ms
12:17:58.303: obs_gpu_encode_thread(16.6667 ms): min=0.242 ms, median=0.446 ms, max=196.059 ms, 99th percentile=1.387 ms, 99.9892% below 16.667 ms
12:17:58.303: ┣gpu_encode_frame: min=0.233 ms, median=0.425 ms, max=196.041 ms, 99th percentile=1.356 ms
12:17:58.303: ┗send_packet: min=0.001 ms, median=0.012 ms, max=1.616 ms, 99th percentile=0.043 ms
12:17:58.303: =================================================
12:17:58.303: == Profiler Time Between Calls ==================
12:17:58.303: obs_hotkey_thread(25 ms): min=24.114 ms, median=25.161 ms, max=120.872 ms, 75.5095% within ±2% of 25 ms (0.0518496% lower, 24.4386% higher)
12:17:58.303: obs_graphics_thread(16.6667 ms): min=2.659 ms, median=16.667 ms, max=1026.98 ms, 99.2166% within ±2% of 16.667 ms (0.394104% lower, 0.389314% higher)
12:17:58.303: obs_gpu_encode_thread(16.6667 ms): min=0.404 ms, median=16.672 ms, max=196.065 ms, 43.1092% within ±2% of 16.667 ms (28.0452% lower, 28.8456% higher)
12:17:58.303: =================================================
12:17:58.540: Number of memory leaks: 2