Problem adding new camera using VirtualCamera_installer.exe
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems
Research direction
Reproduce with VirtualCamera_Installer.exe from an elevated command prompt using the reported registration path and options. Check the installer output and the Device Manager, Camera App, TestVCam, and TestCustomControl results. Done means registering Vcam-SimpleMediaSource creates a camera that is visible and detected by those checks.
Written by the indexing model from the issue text.
Description
I followed the instructions and was able to build everything in the solution using the Release | x64 Target. I did upgrade the projects to use 2022 c++ runtime and the 10.0.22621.0 SDK. VirtualCamera_MSI_x64 installed without any errors and I'm running C:\Program Files\Contoso\VirtualCamera_MSI\VirtualCamera_Installer.exe from an elevated command prompt. I'm selecting (1)register -> (1)Vcam-SimpleMediaSource -> (2)Session -> (1) Current User. I get the following output
Register virtual camera...
device string: {7B89B92E-FE71-42D0-8A41-E137D06EA184}
friendly name: SWVCamMediaSource
Lifetime: 0
Access: 0
Succeeded (00000184461CBE00)!
(null)(0):(null), hr=0x80073D57, msg=
(null)(0):(null), hr=0x80073D57, msg=
not running in app package
Start camera
Succeeded!
The 2 (null) lines and not running in app package are printing in yellow. Even though it claims things succeeded no new camera is being created - I've checked the following places
- Device manger / Imaging Devices
- Camera App
- remove, TestVCam and TestCustomControl all print
No Virtual camera found
- Dominant language
- C#
- Stars
- 261
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/Windows-Camera
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/Windows-Camera#69 ·
-
COM reference leak? Open
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
microsoft/Windows-Camera#58 · 1 comment · 1 reaction ·
All issues in microsoft/Windows-Camera
Similar issues
-
effort:S P3 refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1532 ·
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
C#/.NET Roslyn LSP Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DotNetNext/SqlSugar#1458 ·