Skip to content

Latest commit

 

History

History
42 lines (34 loc) · 3.09 KB

README.md

File metadata and controls

42 lines (34 loc) · 3.09 KB

uvcc output examples

A small sample of uvcc camera control output. See individual subdirectories for specific cameras. Note that cameras with the same "marketing name" may have several USB hardware implementations with different vendor/product ids, so there may be more than one subdirectory.

How to add or update the output from your camera

  • Open the terminal.
  • Create and/or enter the correct camera product marketing name subdirectory.
    • The "marketing name" is the product name (usually including a short codename) you would see on the box when you buy a camera.
    • Use kebab-case naming, with vendor name and product code/name.
    • Do not use the full "marketing name", such as "Logitech HD Pro Webcam C920".
    • Correct examples:
      • logitech-c920 from Logitech HD Pro Webcam C920 (name in uvcc devices).
      • logitech-c922 from the vendor name and C922 Pro Stream Webcam (name in uvcc devices).
      • microsoft-1425 from the vendor name and the model number 1425 found on the label on the camera cable as well as the box the camera was delivered in.
  • Create and/or enter the correct vendor/product id subdirectory.
  • Reset the camera to default values.
    • Unplug all cameras.
    • Reconnect only the camera you want to test.
    • This done to get "fresh" (hopefully default) values for uvcc export.
  • Run ../../update-example.sh
  • Verify that the *.json files were created/updated.
  • Commit your changes and submit a pull request.

Is it not working?

Not all cameras are UVC-compatible. If you can confirm that your camera model supports UVC, perhaps uvcc needs some fixes to support it.


uvcc Copyright © 2018, 2019, 2020, 2021, 2022 Joel Purra. Released under GNU General Public License version 3.0 (GPL-3.0). Your donations are appreciated!