When I update 30.0.2 to 30.1.2 I am no longer able to "Start Virtual Camera". I am downloading the update from within the app. When I click on "Start Virtual Camera" I get a message stating the virtual camera plugin could not be found. I am running macOS Sonoma 14.4.1. I keep having to reinstall 30.0.2 - which works flawlessly. Any help? Thanks!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
No virtual camera plugin when I upgrade to 30.1.2
- Thread starter jazzthis
- Start date
robertrbsn
New Member
I am on Ventura 13.5.2 and virtual camera is not working for me either.
Note to Mac users: DO NOT UPDATE TO 30.1.2 - it is buggy on mac systems
Note to Mac users: DO NOT UPDATE TO 30.1.2 - it is buggy on mac systems
robertrbsn
New Member
I tried to completely reinstall OBS and it worked for me. So if you have any issues according to virtual camera on macOS try to uninstall and reinstall again. Latest version now works fine for me.I am on Ventura 13.5.2 and virtual camera is not working for me either.
Note to Mac users: DO NOT UPDATE TO 30.1.2 - it is buggy on mac systems
Digitalhero
New Member
This has happened to me a couple of times, too.
Throwing the app in the trash (and accepting the dialogue that says the extension will also be trashed) and then re-installing from the disk image and re-allowing the extension after launching fixes it for me, too.
Throwing the app in the trash (and accepting the dialogue that says the extension will also be trashed) and then re-installing from the disk image and re-allowing the extension after launching fixes it for me, too.
thatonepianoplayer
New Member
*raises hand* same thing here. "Could not find virtual camera. Please try again."
OBS 30.1.2
Mac Ventura 13.2
OBS 30.1.2
Mac Ventura 13.2
thatonepianoplayer
New Member
Thanks.... this worked. You're my ...hero, Digitalhero.This has happened to me a couple of times, too.
Throwing the app in the trash (and accepting the dialogue that says the extension will also be trashed) and then re-installing from the disk image and re-allowing the extension after launching fixes it for me, too.