Bug Report Strange issue after updating OBS

DeathWhitch

Member
Know I know the "fix" for me is to just rollback to the previous version I had before the latest update, But I wanted to share this strange glitch I now have on stream after this latest version update which I only did yesterday (I know I wait to install my updates til I remember to do it before I start streaming lol)

So in this video you will see every few seconds my stream pixelates or gets random artifacts on screen. Doesn't seem to effect audio. The effect happens every few seconds while I stream no matter what the pc is doing or what is being displayed on stream. In this clip I have my BRB screen up. Which is scene that contains only a single image file and nothing is running on the pc except OBS and spotify for music at this time. The pixelation seems random too but does consistently happen every few seconds. No matter what scene I am on for what is being displayed on stream. Might be a bug in the update as you can see my past streams from only a few days ago are flawless and the only change made to machine in this time was finally doing the update to obs

My Specs:

CPU- i7-6700k @ 4.0ghz
Ram - 16gb
GPU - GTX 1070 8gb
Bitrate - 3500
Resolution - 1080p @ 30fps
Encoder used - Happens on both x264 and Nvec
OBS version used - 24.0.3 (64 bit)

1min clip of issue - https://www.twitch.tv/videos/565636593
 

DeathWhitch

Member
No its deff not that. Im at the same 2 keyframe and bitrate (3500) ive always used on twitch. It looks different oo, like not normal pixilation, but more the kind you get on a sat TV when its too cloudy to get a clear signal kind of thing, its odd and deff a bug.

I have taken my channel off of sub only mode so you should be able to see the example video now.

Here is the log as requested - https://pastebin.com/uSVbH2hy
 

DeathWhitch

Member
No recording or streaming attempt in the OBS log.
My mistake on the log I got the one after the stream. Here is the correct one - https://pastebin.com/VB83S0Jr

No idea what your on about with the mp4 thing, I didn't do any recordings and the default (which is what its on cause I never record I only stream) is set to mkv, Listen I know the solution for me is to just rollback to the version that didn't have the issue so if your going to have a attitude about helping then please refrain from replying and keep your many fingers and hands for typing somewhere else.

I'm sharing my experience as a bug to help the devs as I believe it to be just that, a bug. My obs worked fine before I updated and now it does this, nothing changed on my end. I downgraded back to a previous version and low and behold its fine again. Thats my story you guys can troubleshoot from there. Cheers
 

BluePeer

Member
~70% of your logfile are error reports
first fix errors then look again

if you upgrade systems with tons of settings its default that one some places "personal" settings are overwritten with new defaults or new defaults implemented with effects before not exist so many places where this can from like "brb video playback issue" or a filter or or or its no need that the "artefact came from your encoding" it can be happen that the "playback" had the artefacts and the encoder only capture it ^^
 

DeathWhitch

Member
~70% of your logfile are error reports
first fix errors then look again

if you upgrade systems with tons of settings its default that one some places "personal" settings are overwritten with new defaults or new defaults implemented with effects before not exist so many places where this can from like "brb video playback issue" or a filter or or or its no need that the "artefact came from your encoding" it can be happen that the "playback" had the artefacts and the encoder only capture it ^^
My brb screen is a jpeg not a video lol the errors are only related to boom replay app. it always does that when first starting if I forget to launch that app before launching obs. Its a nothing error that just basically tells me obs couldnt hook into boom replay because I forgot to open that app and its not running to hook into. Same with my capture card software. Neither of which where even in use during this test and the issue occurs with or without them even being used as sources in obs.

The issue is not something being captured as even when I did use my capture card and boom replay app and had the issue, neither the game i was playing or the replays captured with boom showed that issue on my screen, it only showed up on stream for the viewers and I noticed it when watching my own past broadcast. the issue only happens when the video is streamed through obs and only started happening after the latest update. I have since rolled my obs version back to the one before this latest update and its working fine again, even with the boom and avermedia errors.

hope that clarifies things a bit more. I'm trying to help the issue get resolved before updating obs again and provide some feedback for others who might be having the same weird glitch as me.
 

R1CH

Forum Admin
Developer
Try streaming directly to Twitch, likely Restream is breaking your stream due to FTL protocol.
 

DeathWhitch

Member
Try streaming directly to Twitch, likely Restream is breaking your stream due to FTL protocol.
Again and I cannot stress this enough, Everything works fine after I downgraded back to the previous version of OBS. The ONLY thing I changed to get the issue was that I updated OBS and the ONLY thing I did to resolve the issue was revert back to an older version of OBS.

The issue is 100% related to the latest update of OBS and I am sharing the issue here (even though it is resolved) so that devs may look into that update.

The issue is OBS, not where I am streaming, not any apps It is hooking into or hardware inside my machine but the latest version of OBS itself.
 
Top