jaedash.blogg.se

1. #AMCAP VERSION 1.10 HOW TO#
2. #AMCAP VERSION 1.10 UPDATE#
3. #AMCAP VERSION 1.10 DRIVER#
4. #AMCAP VERSION 1.10 WINDOWS 10#

IR streams will show up as regular capture streams in DShow. } VIDEO_FORMAT_FRAME, *PVIDEO_FORMAT_FRAME GUID guidFormat // this field should contain the IR subtype GUID Example Format Descriptor for UVC 1.1 frame based format No scaling or conversions of the IR frames are supported by the pipeline for IR streams.Ī stream exposing IR format types must not expose RGB or Depth format types. Applications written with Media Foundation FrameReader API will be able to consume the IR stream. When these format type GUIDs are specified in the guidFormat field of the frame descriptor, the Media Foundation capture pipeline marks the stream as IR stream. Media Foundation converts this into NV12 uncompressed frames and uses only the luma plane. This type maps to MFVideoFormat_L16.Ĭompressed MJPEG frames. The following format type GUIDs should be specified in the stream video format descriptor, as defined in the WDK ksmedia.h header file: Type

#AMCAP VERSION 1.10 DRIVER#

The Windows inbox USB video class (UVC) driver supports cameras that capture the scene in YUV format and transmit the pixel data over USB as uncompressed YUV or as compressed MJPEG frames. If the SensorCameraMode and SkipCameraEnumeration attributes are not specified in the firmware or the INF, the camera will be registered as a color camera and will be visible only to color camera aware applications. HKR, SkipCameraEnumeration, 0x00010001,1 This makes the camera available HKR, SensorCameraMode, 0x00010001,1 places the value under device HW SkipCameraEnumeration: REG_DWORD: 1 (make it available only for IR applications)Īn example of the custom INF section is as follows: SensorCameraMode: REG_DWORD: 1 (to register as a sensor camera)

#AMCAP VERSION 1.10 UPDATE#

If you cannot update the device firmware as described above, you can use a custom INF and specify that your camera need to be registered as a sensor camera by specifying a value for SensorCameraMode and SkipCameraEnumeration as follows:Ī custom INF file (based on the inbox UVC driver) must include the following AddReg entries: Refer to the Example composite device section below for a sample BOS descriptor with a platform specific MS OS 2.0 descriptor. We recommend you specify the above-mentioned registry value using the BOS descriptor. A camera that exposes both sensor camera and color camera media types should use this value. This will make the camera available for applications looking for either sensor and color cameras. A camera that exposes only sensor camera media types should use this value.Ī value of 2 for SensorCameraMode, will register the device under KSCATEGORY_SENSOR_CAMERA & KSCATEGORY_VIDEO_CAMERA. In addition to this specify a value of 1 for SkipCameraEnumeration to make the camera available to applications looking only for sensor cameras. The attribute SensorCameraMode takes a value 1 or 2.Ī value of 1, will register the device under KSCATEGORY_SENSOR_CAMERA.

This categorization helps applications to select the camera that they want to work with.Ī UVC camera can specify its category preference through attributes, SensorCameraMode and SkipCameraEnumeration, in its BOS MS OS 2.0 Descriptor detailed in following sections. A camera that supports both color and non-color format types should be registered under KSCATEGORY_VIDEO_CAMERA and KSCATEGORY_SENSOR_CAMERA.

A camera that supports IR or Depth-only format types should be registered under KSCATEGORY_SENSOR_CAMERA. We recommend the camera firmware specify a value based on which the UVC driver would register the camera under one or both supported categories.Ī camera that supports color only format types should be registered under KSCATEGORY_VIDEO_CAMERA. The UVC driver supports both types of cameras. RGB or YUV cameras are categorized as color cameras and non-color cameras like gray scale, IR and Depth cameras are categorized as sensor cameras. One is a color camera and the other one is a non-color sensor camera. Windows supports two categories of cameras. Microsoft platform specific BOS device capability descriptor The camera that outputs non-color streams (for example, IR or Depth cameras) The camera that outputs color streams (for example, RGB or YUV cameras) USBVideo.sys driver that ships with the OS

#AMCAP VERSION 1.10 HOW TO#

This document outlines how to expose certain capabilities of a UVC compliant camera to the applications through the inbox driver. This driver supports color and sensor type cameras.

#AMCAP VERSION 1.10 WINDOWS 10#

Windows 10 provides an inbox USB Video Class (UVC) driver for devices compliant with USB Video Class specification (versions 1.0 to 1.5).