Question / Help Capture card flicker w/ webcam

Boildown

Active Member
Mostly looks good, a little bit of ISP problems but that would be unrelated to the problem description, which I assume is still valid.
02:48:27.211: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 3977 (0.4%)

One thing that confuses me is why you have these custom x264 settings:
21:45:27.131: [x264 encoder: 'streaming_h264'] custom settings: direct=temporal ipratio=1 pbratio=1 keyint-min=30 scenecut=20 scenecut=0

And
21:45:27.131: [x264 encoder: 'streaming_h264'] tune: film

Can you get rid of those, change it to Faster preset, and try again? Can go back to Medium after you verify that it works on Faster if you want.
 

Scotch

Member
Mostly looks good, a little bit of ISP problems but that would be unrelated to the problem description, which I assume is still valid.


One thing that confuses me is why you have these custom x264 settings:


And


Can you get rid of those, change it to Faster preset, and try again? Can go back to Medium after you verify that it works on Faster if you want.
Yeah the frame drops happened at the start of the stream, just usual charter stuff, went another 3+ hours without any more dropped frames.

I honestly don't remember why I have the custom x264 settings...I set that up a while ago and just haven't changed it. I'll look into it again.

The thing about the flicker is that it exists before I even start streaming or recording, obviously it shows up on them when I start. But for the sake of testing I verified that the problem exists even without the custom settings and on the Faster preset.
 

Scotch

Member
I may have fixed the issue.

Not sure how or why this fixed it but I switched the what my capture card was capturing. Instead of just duplicating my main PC monitor twice, one for my monitor and one for my capture card, I set up a second "fake" display for my capture card, used OBS on gaming PC to capture the gameplay and then set preview on the second fake monitor. And some how this fixed OBS...
 
Top