For some reason I cannot run the virtual cam at 60fps, it always runs at 30fps.
My OBS settings are 1080p 60fps, and i am running the virtual cam as a filter.

It does not show up in any windows camera apps, but works fine for Bluestacks Android emulator.
I checked that nothing else was running at startup which had access to any cameras such as Nvidia Broadcast, but I feel a windows element might be trying to load it before OBS.

Im using this awesome virtual camera app to stream to Google Lens Translate and translate anything I throw at it on the fly like real hardware console gaming.
https://youtu.be/3JDS4SW0LxQ?si=i-JqAxBAfdXnl2GU

The version 2.1.0 exists under "releases", but the attached asset has the filename "obs-virtualcam-2.0.12-windows-x64-Installer.exe", although the timestamps of the contained files indicate that this is version 2.1.0. Can you fix this and upload the final 2.1.0 version to avoid version confusion? Thanks.

From what I was told and what I learned, current output is hardcapped by full-hd aka 1920x1080.
How much effort potentially would it take to move that cap to 4k aka 3840x2160?

I guess I am at that stage where I am probably ready to finance that feature.

so the latest release finally has it showing in the latest obs 30.2

but now it shows and can be started but the output is empty for any cameras....when i rollback to obs virtualcam prelease 3.1.1 everything shows fine and works fine but

theres an error when exiting obs

so seems like almost there?

• win11 x64
• obs 30.1.2 portable
• python 3.12.2
• obs-websocket 5.1.0

I wanna open more than one virtual camera using obs-websocket, eg:

from obswebsocket import obsws, requests

...

virtual_cam_status = self.client.call(requests.GetVirtualCamStatus())
if virtual_cam_status.datain["outputActive"] is False:
    self.client.call(requests.StartVirtualCam())
    time.sleep(1)

...

there is an error:

if virtual_cam_status.datain["outputActive"] is False:
       ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 'outputActive'

Portable version does not support obs-websocket after installing obs-virtualcam.
However, the full install version works fine without obs-virtualcam.

https://github.com/obsproject/obs-websocket/blob/master/docs/generated/protocol.md#getvirtualcamstatus

Hi I'm not sure if you are getting the same issue after upgrading OBS to 30.2:

12:00:31.072: LoadLibrary failed for '../../obs-plugins/64bit/obs-virtualcam.dll': The specified module could not be found.
12:00:31.072: (126)
12:00:31.072: Module '../../obs-plugins/64bit/obs-virtualcam.dll' not loaded

thanks for a great tool

please provided 32 bit version of this application because our x86 application not supported your x64 release
32bit dll have in folder but its not register error occurred missing dependency on windows 10

This is so awesome that you are continuing this for the latest OBS. Thank you!

Do you happen to know if it is possible to change what is being sent to each virtual cam? I'm not sure this is even possible as I can see the additional virtual cams are most likely additional signed drivers and only mirror the one without being able to be unique in that manner.
When I go to the virtual cam settings I only have the one main one to change for the output settings.
Is this possible to implement?
Thank you so much again!

OBS Version: 30.0 BETA 2
OS: Windows 11 Pro 22H2-22621.1702

its gone

Seems exactly the same, virtualcam as a filter doesn't give any option when you go over it on sources where I had already put it on, and I can't put the filter on any new source because it doesn't show up.
Here's the Log: https://obsproject.com/logs/bZFYV50RRuvrieUD hope this helps!

No matter what I do if I change the width of the video output in settings, or I check/uncheck the "Keep aspect ratio" setting, the camera width always stays same. It always stretches to some width which I don't know, the only way to somehow fix it is stretch the app in the viewport vertically so it is something like this, changing width of the video output does nothing to mitigate this.

This does not happen with the official built-in virtual cam