Intermittent green flickering when streaming

Hi. I have noticed an issue on my stream recently where I see green flickering down the left hand side of the stream. It looks like the following (excuse the sunglasses, that was part of a challenge in stream):

green-blocks.jpg

This flickering can last from a few seconds to half a minute or so. The stream that this most recently happened on is here:


I currently have OBS up and running on my streaming PC next to me and although it is not steaming I just noticed the green flickering again in the preview panel, so this is not purely an online issue. My setup is as follows:

Gaming PC to Streaming PC via AverMedia Lite, GL310
(I mirror my gaming PC dispaly to the AverMedia capture card in display settings of the gaming PC)
OBS is using LGP Lite Stream engine
Canvas is 1280x720 and capture card is outputting 1280x720 at 5.0Mbps
Encoder=QuickSync H.264, Taget Usage=Speed, Profile=High
The processor is constantly running at about 13-14% when the green flickering happens
OBS, graphics driver and windows are up-to-date with latest versions.
I was running TouchPortal during the stream, but when I recently saw the green flickering when I was not streaming I was not running TouchPortal.

The log file is quite long as I streamed for over 3 hours and started OB about 45 mins before the stream began, but examples of the flickering happen at the following time stamps in the stream (I have added the approximate log time that this equates to after them):

44.34-45.02 in stream (around 19:45.18 in log file - stream started at 19:00.44)
36.19, 37.19 and 37.56 (around 19:37.03+ in log file)

The relevant section of the log file for the above is as follows - I've also attached the complete log file to this post:

18:54:58.459: User switched to scene 'In Game'
18:54:58.463: [obs-websocket] GetTransitionData: duration is negative !
18:54:58.977: [obs-websocket] GetTransitionData: duration is negative !
19:38:51.302: [obs-websocket] GetTransitionData: duration is negative !

[**Green flickering starts around here at 36.19, 37.29 and 37.56 in stream]

[** I didn't switch to "Chat" scene here so no idea why the log says that
I did below - in stream time about 19:39.35]


19:38:51.314: User switched to scene 'Chat'
19:38:51.330: warning: Could not update timestamps for skipped samples.
19:38:53.562: [obs-websocket] GetTransitionData: duration is negative !
19:38:54.119: [obs-websocket] GetTransitionData: duration is negative !
19:39:15.734: [obs-websocket] GetTransitionData: duration is negative !

[** I didn't switch to "Game" scene here - in stream time about 19:40]

19:39:15.741: User switched to scene 'In Game'
19:39:15.790: warning: deprecated pixel format used, make sure you did set range correctly
19:39:17.995: [obs-websocket] GetTransitionData: duration is negative !
19:39:18.126: ---------------------------------
19:39:18.126: [DShow Device: 'LGP LITE'] settings updated:
19:39:18.126: video device: LGPLite Stream Engine
19:39:18.126: video path:
19:39:18.126: resolution: 1280x720
19:39:18.126: flip: 0
19:39:18.126: fps: 30.00 (interval: 333333)
19:39:18.126: format: YUY2
19:39:18.126: using video device audio: yes
19:39:18.126: sample rate: 0
19:39:18.126: channels: 0
19:39:18.126: audio type: WaveOut
19:39:18.559: [obs-websocket] GetTransitionData: duration is negative !
19:39:18.576: warning: Could not update timestamps for skipped samples.

[**Green flicker in stream starts about here at 44.34 for about 28 seconds]

19:45:27.772: [obs-websocket] GetTransitionData: duration is negative !
19:45:27.784: User switched to scene 'Chat'
19:45:27.798: warning: Could not update timestamps for skipped samples.
19:45:29.757: [obs-websocket] GetTransitionData: duration is negative !
19:45:29.772: User switched to scene 'In Game'
19:45:29.784: warning: Could not update timestamps for skipped samples.
19:45:30.031: [obs-websocket] GetTransitionData: duration is negative !
19:45:30.605: [obs-websocket] GetTransitionData: duration is negative !

[**Green flicker ends somewhere around here in stream at 45.02]

21:06:52.003: [obs-websocket] GetTransitionData: duration is negative !
21:06:52.015: User switched to scene 'Chat'
21:06:52.030: warning: Could not update timestamps for skipped samples.
21:06:54.262: [obs-websocket] GetTransitionData: duration is negative !
21:06:54.821: [obs-websocket] GetTransitionData: duration is negative !
21:07:46.043: [obs-websocket] GetTransitionData: duration is negative !
21:07:46.049: User switched to scene 'In Game'


[**The deprecated pixel format below seems to be caused by a Nerd or Die webcam border]

21:07:46.089: warning: deprecated pixel format used, make sure you did set range correctly
21:07:48.294: [obs-websocket] GetTransitionData: duration is negative !
21:07:48.412: ---------------------------------


Does anyone have any suggestions as to what may be causing this? Thanks
 

Attachments

  • 2020-08-17 17-29-58.txt
    151 KB · Views: 24

FerretBomb

Active Member
Chances are good that you're looking at the wrong logfile, if the scene changes are wrong. OBS finalizes the logfile when OBS is closed, NOT when the stream/recording is stopped.

But yeah, that green flicker looks to be either a dying HDMI cable or a poor connection. I'd unplug and firmly replug each end of the cable as the first step; I had the same issue with a console at one point, and turned out that I'd just soft-plugged the console end.

Additionally, you'll want to go into Settings->Advanced and change the Color Range back to PARTIAL. OBS is hard-coded to only stream in Partial for a bunch of reasons, and setting it to Full (as you have it) will just screw up your colors.
Full is for recording in a Full-range RGB end-to-end workflow only.
If you want an improvement, you can swap from 601 colorspace to 709 without issue, though it isn't necessary.
 
Top