Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to find camera "0" on Windows #39

Open
jeremylcarter opened this issue Mar 7, 2025 · 0 comments
Open

Unable to find camera "0" on Windows #39

jeremylcarter opened this issue Mar 7, 2025 · 0 comments

Comments

@jeremylcarter
Copy link
Contributor

When using CameraK on Windows JVM the grabber is FFmpegFrameGrabber("video=0") which does not map to the first indexed camera, rather the camera name is required. Other grabbers exist such as the VideoInputFrameGrabber which you can set to index 0.

I propose that for Windows we use the VideoInputFrameGrabber(0) by default, but also allow through the builder for the user to specify their own org.bytedeco.javacv.FrameGrabber instance as a sensible override.

I will draft a PR and submit it.
jeremylcarter added a commit to jeremylcarter/CameraK that referenced this issue Mar 7, 2025
@jeremylcarter
Kashif-E#39
9ac8706 
Fixed issue where camera index 0 was not available on Windows systems using FFmpegFrameGrabber.
Added ability to pass in custom FrameGrabber to DesktopCameraControllerBuilder. Added ability to flip the image horizontally to the DesktopCameraControllerBuilder.
@jeremylcarter jeremylcarter mentioned this issue Mar 7, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremylcarter