Encoding overload/ cpu to hot?

R

rockbottom

Active Member
Hard to say for sure but system performance is suspect & no doubt part of the issue. You have lots of filters in play, nothing is free.

All there is is rendering lag (GPU overload), so load reduction is in order. Start over if needed & rebuild the Scene slowly again.
 
M

meraki

Member
rockbottom said:
Hard to say for sure but system performance is suspect & no doubt part of the issue. You have lots of filters in play, nothing is free.

All there is is rendering lag (GPU overload), so load reduction is in order. Start over if needed & rebuild the Scene slowly again.
Click to expand...

you think it could be the gpu itself being the problem?
pc is only 2 years old, so warranty is still in place- but i dont really know how to argue for being sure its the gpu thats underperforming if thats the case

uninstalled obs and reinstalled it to make sure if theres anything from the original corrupt profile still lingering- thats its totally gone now, and rebuilt again.
 
R

rockbottom

Active Member
No idea. The only benchmarking/troubleshooting tool you have used is Cinebench.

But if you posted the correct results for your CPU test, your CPU appears to be getting throttled or something else is going on. The 12700F should be scoring over 1,000 on multicore, not 680. Over 30% performance gone....

"cpu multi 30:
(15 min in now and temp is in the 40-50 range on all cores- so far score is around 680,... dont think much will change the next 15 min)"

GPU score is way low too but that may be a result of the above or something else too.

It's under warranty but you changed the cooling so your builder may give you a hard time with warranty.
 
R

rockbottom

Active Member
Not the way I read those logs. It's on the decline/getting worse. Audio lagged again.

Fix your rig.

Figure out what's wrong with your StreamDeck too, websocket errors galore since you updated OBS.

Update Nvidia &

Stroke Glow Shadow - Updates

obsproject.com obsproject.com

I'm out, multiple problem(s) ID'ed, you need to take care of them. Nothing I can do further here.
 
M

meraki

Member
rockbottom said:
Not the way I read those logs. It's on the decline/getting worse. Audio lagged again.

Fix your rig.

Figure out what's wrong with your StreamDeck too, websocket errors galore since you updated OBS.

Update Nvidia &

Stroke Glow Shadow - Updates

obsproject.com obsproject.com

I'm out, multiple problem(s) ID'ed, you need to take care of them. Nothing I can do further here.
Click to expand...
oh, really? here i was thinking everything was finally starting to work out,....
i've just been checking what the analyzer is saying- i dont know how to read the logs manually, thought it was looking fine *cries*

nvidia drivers for the gpu was updated yesterday and should show as installed today?
all the plugins i downloaded fresh and installed when i reinstalled obs a few days ago, so unless glow stroke got updated in the past few days, it should be updated too,..but ill check it out to make sure. (oh, it got updated today, ty for the heads up:)

i shall have a look at the streamdeck, just assumed it was working as it should since things seemes connected there, and the analyzer not writing out any errors.
if by fix your rig you mean my cpu and how its underperforming, i dont know how to do that other than by actually replacing it.
 
R

rockbottom

Active Member
Nvidia plugin has an update available.

Hopefully the driver you have installed is good. I haven't ventured that far, still running the studio driver that was released before the 5000 series hit the scene. There's evidence of performance issues so I'm waiting.

Yep or adjust your expectations.
 
M

meraki

Member
rockbottom said:
Nvidia plugin has an update available.

Hopefully the driver you have installed is good. I haven't ventured that far, still running the studio driver that was released before the 5000 series hit the scene. There's evidence of performance issues so I'm waiting.

Yep or adjust your expectations.
Click to expand...

aha,... cool, ill give it a look too, thought it was the nvidia gpu driver:)

had a look in streamdeck, it could be that the obs plugin there i havent mapped the keyes, asi havent even peeked into the obs plugin after reinstalling (i mainly just use it for easier audio adjustment and twitch plugin)
so all other keys are unmapped. ill give it a whack and see if that fixes all the errors from there.

im not sure what causes the audio to act up again.
yesterday (and i dont know why cause i have set my webcam to not be allowed to take over audio) my webcam had set itself to main input audio for my pc. it was my mic still in obs, so im not sure it had anything to do with it,..but maybe? i think i might have updated its software,..maybe that caused it to try and take over? no clue tho

in obs the shure is the only source, and used as a audio capture source and nothing activated in global audio devices


(im just waiting for a good deal in the secondhand market now i think,.... it's just not woth getting ulcers over this:p )


but the render lag is gone tho,..right,... so it's some progress over how it was before i unistalled and reinstalled.

need to look into what those errors from twitch alerts culd be. that should be just the standard alerts you get when ppl sub etc, and i deactivated alerts for just following. i didnt have it on yesterday, and today i had no events happening that triggered any alerts at all from it, so its weird its giving errors from just being there.
 
R

rockbottom

Active Member
Can't help with StreamDeck.

Audio lag is generally a sign of system overload but as mentioned many times before, it could be the filters. Hard to say for sure since your system is nerfed.

Yeah, it's better but I guess it depends on how much rendering lag you can tolerate. The target is 0.
 
M

meraki

Member
rockbottom said:
Can't help with StreamDeck.

Audio lag is generally a sign of system overload but as mentioned many times before, it could be the filters. Hard to say for sure since your system is nerfed.

Yeah, it's better but I guess it depends on how much rendering lag you can tolerate. The target is 0.
Click to expand...
did you see any render lag in the log files? in the analazer it didnt report any

the log from today
analyzer dosent report any errors
ive tried to look at the files too, but i dont understand much from it


does the error from the sessiongo overlay mean anything, or is it just noise?
its a overlay to keep track of goal followers, bits etc achieved in one session.
ill remove it for the next stream to see what gets fixed then

there is graphql error from the twitch creator studio alerts overlay aswell,... i dont really know what that means.

it seems like the streamdeck issues is gone now, because i assume that was the long list of 4009 websocket something errors from the previous logs

i dont think i saw any audio buffering either, which i assume is what caught your eye in the previous logs?

two weird thigns in obs upon start today, the game capture was cropped when i started up, usually it justs captures the game and has it in the right proportions and streches it to the frame on its own, but it didnt do that today.
it has also disconnected itself from streamerbot, and i ahd to manually connect it again i know streamerbot has an update, but i dont know if its already rolled out- as my interface still looks exactly the same
 
R

rockbottom

Active Member
Yep, not horrible but there is some.
20:00:05.098: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 114 (0.0%)

Mic buffered too, buried in all that SE BS.
13:07:01.803: adding 213 milliseconds of audio buffering, total audio buffering is now 256 milliseconds (source: shure)

Cleared up the Websocket/SD errors, that looks better but added SE/JavaScript errors back.

Your best bet is to just keep things simple & don't build large Scene Collections. Remove crap/plugins that's no longer needed.
 
M

meraki

Member
rockbottom said:
Yep, not horrible but there is some.
20:00:05.098: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 114 (0.0%)

Mic buffered too, buried in all that SE BS.
13:07:01.803: adding 213 milliseconds of audio buffering, total audio buffering is now 256 milliseconds (source: shure)

Cleared up the Websocket/SD errors, that looks better but added SE/JavaScript errors back.

Your best bet is to just keep things simple & don't build large Scene Collections. Remove crap/plugins that's no longer needed.
Click to expand...
yeah, i guess thats how it jsut has to be for now,.. but i dont really have much going on.
my audio filters is kinda just basic modifiser for the mic when i dont have a "seperate soundboard" or a clsoed room with no other background noise in

from yesterday

from today
got a new problem today,..the nvidia noise suppression filter stops working a couple of min into the stream. restarted it 4-5 times and it jsut kept on happening. its been working fine until today (yesterday) with no issues,.. maybe it came after i tried to update the nvidia driver?

also in logs theres this (maybe it has something to do with the filter stopping working?
[NVIDIA Audio Effects: '2NVIDIA Audio Effects'] NVAFX SDK redist path was found here
 
You must log in or register to reply here.
Top