The USB Device Class Definition for Video Devices, or USB Video Class, defines video streaming functionality on the Universal Serial Bus. Much like nearly all mass storage devices (USB flash disks, external SATA disk enclosures, ...) can be managed by a single driver because they conform to the USB Mass Storage specification, UVC compliant peripherals only need a generic driver.
The Linux UVC projects is currently focussing on kernel support for UVC devices. The driver implements the Video4Linux 2 (V4L2) API. Support for the deprecated V4L1 API will not be added.
Veho Vms 004 Driver
9 This Device ID is known to be used by several different webcams among which at least one is currently not supported by the driver. If you plan to buy this camera make sure it matches the product name.
12 Recent versions of the device use UVC as a façade. They talk a vendor-specific protocol with a vendor-provided Windows driver, and trying to handle them with the UVC protocol results in low frame rate and corrupted frames in most resolutions. Device BCD 1.00 is known to be affected, BCD 0.02 seems to work.
13 Despite being able to work with lower USB bandwidths, this device always requests the maximum possible bandwidth, even for the MJPEG format. Using one of those cameras in conjunction with another USB device (including the camera internal microphone) will likely fail. You can tell the uvcvideo driver to estimate the required bandwidth instead of trusting the camera by setting the FIX_BANDWIDTH quirk. This will only affect uncompressed formats, and even there there's no guarantee of success. See the FAQ for more information.
14 The camera severely underexpose images under low-light conditions when using any frame rate other than the default (which also happens to be the maximum), probably because auto-exposure is only enabled at the default or maximum frame rate. The RESTRICT_FRAME_RATE quirk has been added to the driver to ignore all non-default frame rates.
If you are an end-user the easiest way to retrieve an up-to-date driver is to clone the media build git repository located at _build.git. The code includes support for older kernel versions, but might lag behind the uvcvideo git repository by a few days.
UVC-specific parts of the driver API are documented in the Linux kernel tree starting at version 2.6.38, in Documentation/video4linux/uvcvideo.txt. Older kernel versions implemented a different API that is now deprecated and scheduled for removal in 2.6.39.
However, for the money, I think the VMS-004 has some potential for pseudo educational/fun use. It's definitely fun to use. It installed without problems on Windows 7 (though x64 drivers are, I understand, problematical or unavailable). I'd definitely consider the VMS-004 as a present, and it may even find some use in my own work for photographing small details that could be featured in articles I write. I just wish it was easier to use.
Features- Adjustable LEDs for object illumination- 2 MP Cmos (interpolated)- Measurement function using enclosed software- Snapshot and video recording function- Alloy stand and stand alone capture button- Tacton rubber touch housing- With a base zoom level of 20x, the VMS-004 can be further zoomed in manually to a factor of 400x- Fine slider adjustment for brightness, hue, saturation and sharpness, plus a black and white display mode- VMS-004 USB Microscope is supplied with Windows and Mac drivers. For software for side-loading CD drives just visit the download centre- The 2 megapixel CMOS lens can be adjusted to point in any direction using the movable arm- Simply install the drivers, plug the microscope into your computer via the USB and you''re ready to go
Veho manufactures several types of film, slide and negative scanners for both home and business use. To keep these machines running well and ensure compatibility with the latest programs and operating systems, you have to periodically apply updates to the scanner's drivers. Veho makes up-to-date driver software readily available on its website, and the process of installing the new drivers is simple.
Create a folder for the new drivers when prompted by Windows' extraction program. This should be an easily accessible location, such as C:\VehoDrivers. Windows closes the extractor program once it completes. 2ff7e9595c
Comments