Question / Help 19.0 Webcam No Longer Works [Jim: caused by Avast/AVG - turn on their passive mode]

[unsane]

Updated from 18.0.2 to 19.0.2. Webcam no longer works.

Integrated laptop webcam. Light is on. Closed and reopened OBS. Changed scenes. Added new Video Capture Device. Tried Deactivate and Reactivating. Tried setting Resolution/FPS Type to Custom instead of Device Default. Nothing works.

https://gist.github.com/ee11906e1430ab8bf06f61064b490cca

 

[R1CH]

Does the camera work OK in other applications? Your log doesn't seem to report any errors relating to it.

 

[unsane]

I never use it anywhere else, however i tested it on http://www.testmycam.net/ just now, and it works there.

 

[Activist]

Same issue is still happening with me, only since the 19.0 update. I have updated all my drivers, changed all resolution settings, and deactivated/remade scene.
https://gist.github.com/8eb7bedbd22dff75df3367fbaf84cba1

Update: Tried two separate webcams and still no display. They both work fine on other applications.

 

[Harold]

What antivirus?

 

[Activist]

What antivirus?

AVG

 

[unsane]

Avast, shields turned off, silent mode on.

 

[Lain]

I didn't change the webcam mode. If you guys are using Avast/AVG, could you try "Passive mode" with it and see if it still happens? Maybe they didn't actually fix the bug as I thought they did. Are your definitions up to date?

Reason why I say this is because Avast/AVG started blocking webcams when we released 18.0.2 earlier this month, I thought they'd fixed it.

If you're not using Avast/AVG let me know. I didn't change the video device code at all.

 

[Activist]

Thanks Jim. That was the problem for me, I took AVG into passive mode and the cam worked just fine. Kind of annoying on their end but as long as I am able to get it working I can't complain.

 

[Lain]

Also could you try to see if your definitions are up-to-date? If the issue persists, I'll have to try to contact AVG/Avast again.

 

[unsane]

Updating Avast definitions worked. Thanks.

 

[Lain]

Awesome, I was sure that it was fixed -- glad to hear that it is.