vcam | DShow Video Capture Filter | Video Utils library

The problem building the project is coming from this:

1. The project source code has a dependency of DirectShow BaseClasses which is no longer a part of Windows SDK
2. The project has too many settings diverged from defaults; with current Visual Studio it becomes a problem

I updated the github repository and changed the project settings to make the project build (Visual Studio 2019 Communitty) and run: most of the C++ project settings are reverted and DirectShow BaseClasses are used in the build configuration from github.

Check out README.md there, follow build steps (which require to pull Windows SDK Samples first, and build DirectShow stuff there), have DLLs registered (regsvr32) and finally you will have the filter generating video with random data:

Filters folder contains source code for the project. .DSP is the project file for old Visual Studio (or was it Visual C++ 6.0 yet?). If current Visual Studio cannot convert the project file you should still be able to create a new DLL project file and add the source code files.

You need DirectShow BaseClasses to build the code. BaseClasses are no longer a part of Windows 10 SDK, so you have to have Windows 10 SDK and you additionally need this:

• Win7Samples/multimedia/directshow/baseclasses

Note that BaseClasses there are fresher than VCam sample itself and Visual Studio solution file is already .SLN and is known to be buildable and acceptable (via conversion) for current Visual Studio.

Also you can find other filter projects in neighboring folders.

Bin folder contains pre-built Win32 binaries of the project. Don't be confused with .AX extension - the files are regular .DLL files and you can use them directly against regsvr32. If you build the code into .DLL files you will have the same effect as with .AX.

To see the project in action you need a 32-bit application that works with cameras via DirectShow, for example:

• Windows 10 SDK GraphEdit
• AMCap sample (among mentioned samples and also documented on MSDN)
• GraphStudioNext

You should see a new camera option once you regsvr32 the built project (from privilege elevated command prompt!)

To have the project working with 64-bit applications, you need to build the project first, then regsvr32 it. Virtual Driver Cam not recognized by browser question clarifies why 32 and 64 builds work separately and target different applications.

Try to disable "Conformance mode" in properties(From Yes(/permissive-) to No).

I can reproduce this issue and then get it compile after disable it.

This compiler option is set by default in Visual Studio 2017 version 15.5 and later, but it is not set by default in earlier versions.

According to the /permissive document:

By default, the /permissive- option is set in new projects created by Visual Studio 2017 version 15.5 and later versions. It's not set by default in earlier versions. When the option is set, the compiler generates diagnostic errors or warnings when non-standard language constructs are detected in your code, including some common bugs in pre-C++11 code.

...Older versions of the SDK may fail to compile under /permissive- for various source code conformance reasons.

Description how to achieve what I described in a question is provided by Unity staff member - Gregoryl.

CM doesn't give you a notification when things go in and out of dead zones.

You can accomplish what you're looking for by polling the position of B relative to the camera and manually calculating whether the angle between CameraPosToB and CameraForward is sufficiently large, and activating the second vcam when it is.

Here is a part of code - doing what he described:

From what I remember, you can define the blend style in the Cinemachine blend options. From the description, it seems that it is set to "Cut" when you probably want something similar to EaseIn/EaseOut. It even allows you to define your own custom blend between cameras if the default options do not work for you.

Take a look at the documentation for more details.

The diagram below explains the applicability of virtual cameras:

You are trying to somehow mount a lower green or blue box so that it reads data from RTSP.

Note that more and more applications like new Skype are Media Foundation based (top right box on the diagram) and your filter based source is less and less applicable.

Creating a virtual camera which is recognized by various software assumes you are supplying a driver (red box). Even though such packages exist, I am not aware of any open source or even free which let you quickly start on this route.

DirectShow filter based sources (and you are yet to implement RTSP client there) will only be see by DirectShow based applications of the same bitness.

I think you'd better use another camera with higher bitmap dimensions (2x-4x) to render those scenes from vector that you feel are too pixelized. In terms of export, just export the character's bitmaps 2x-4x larger, or you can just have it as a vector somewhere in your app, maybe hidden, and do realtime render when needed, or plain have it in your display list as a vector and not a bitmap.

In case you need to have some complex vector form into a bitmap-based engine, you can use realtime bitmap drawing of a single source in various postures/rotations, then use those rendered bitmaps to get performance. Check the game "Enigmata: Stellar War" for this technique, how does it look in the process (hint: when it says "Loading boss" it does all the render behind the scenes).

Getting a vectorized source form bitmaps is a lot more processor consuming than having a ready-made vectorized source stored somewhere. Also you won't get your original vector restored in exact form, as converting a vector to a bitmap is a lossy transformation.

When you build a 64-bit filter, it will work only for 64-bit software which consumes video capture via DirectShow and not otherwise. There is not so much of this software around though.

See Applicability of Virtual DirectShow Sources to get an idea where such 64-bit builds are applicable and what are the other options.

You will also find relative information in these older questions:

• Virtual Driver Cam not recognized by browser
• DirectShow filter is not shown as input capture device

I cross-posted this question to https://gamedev.stackexchange.com and someone responded with a great answer:

https://gamedev.stackexchange.com/a/157021/11212