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

Setting UVCC autoWhiteBalance to 0 Getting LIBUSB_ERROR_IO #2

Closed
mesalagagan opened this issue Jul 24, 2019 · 1 comment
Closed

Setting UVCC autoWhiteBalance to 0 Getting LIBUSB_ERROR_IO #2

mesalagagan opened this issue Jul 24, 2019 · 1 comment

Comments

@mesalagagan
Copy link

sudo uvcc devices

Optical Mouse [ vId: 0x458  / pId: 0x3a  ]
USB Keyboard [ vId: 0x4d9  / pId: 0x1702  ]
EHCI Host Controller [ vId: 0x1d6b  / pId: 0x2  ]
EHCI Host Controller [ vId: 0x1d6b  / pId: 0x2  ]
USB 2.0 Camera [ vId: 0xc45  / pId: 0x6366  ]

sudo uvcc --vendor 0xc45 --product 0x6366 set autoWhiteBalance 0

Error: LIBUSB_ERROR_IO
Screenshot from 2019-07-24 17-18-41
@joelpurra
Copy link
Owner

@GaganMeesala: I can confirm the problem -- am also getting LIBUSB_ERROR_IO on ubuntu. The same webcam works on macOS without any issue. Looks like the problem isn't in uvcc though, but in upstream code.

Noticed that you opened the same issue in uvc-control; closing in favor of that issue.

joelpurra added a commit to joelpurra/node-uvc-control that referenced this issue Oct 10, 2019
@joelpurra
Target control transfer to device
4ad8a62 
- Currently, each `controlTransfer` by setting `bmRequestType` targets
the camera _interface_ rather than _device_.
- Using an interface would require claiming it, which is not performed.
- Claiming an interface would kill access for any other process
which may be using the camera (including the kernel?).
- This commit targets `controlTransfer` to the _device_ instead.
- There might be better ways to transfer control commands.

See

- makenai#58
- joelpurra/uvcc#2
joelpurra added a commit to joelpurra/node-uvc-control that referenced this issue Sep 1, 2020
@joelpurra
Target control transfer to device
13f31e5 
- Currently, each `controlTransfer` by setting `bmRequestType` targets the camera _interface_ rather than _device_.
- Using an interface would require claiming it, which is not performed.
- Claiming an interface would kill access for any other process which may be using the camera (including the kernel?).
- This commit targets `controlTransfer` to the _device_ instead.
- There might be better ways to transfer control commands.
- Ported from `uvc-control` v1 to v2.

Fixes makenai#58
Fixes joelpurra/uvcc#2

See

- makenai#58
- joelpurra/uvcc#2
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
2 participants
@joelpurra @mesalagagan