K2TrackingDevice Samples (Amethyst API v20)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

BTW: If you prefer C# to C++ for your device/plugin, please check out this branch.
(You'll need to replace the Amethyst API files with the latest ones yourself, though)

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • SkeletonBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that SkeletonBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (Amethyst API v18)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

BTW: If you prefer C# to C++ for your device/plugin, please check out this branch.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • SkeletonBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that SkeletonBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (Amethyst API v13)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

BTW: If you prefer C# to C++ for your device/plugin, please check out this branch.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (Amethyst API v11)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

BTW: If you prefer C# to C++ for your device/plugin, please check out this branch.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (Amethyst API v10)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (Amethyst API v8)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.
As for a real-world example, please check out this. (JointsBasis w/ custom settings)

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (K2API v7.3)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (K2API v7.2)

Note: Some functions/elements may still not be available as of Amethyst v1.0.1.3
They will work again in Amethyst v1.0.1.5 and later. Consider this a preview release.

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (K2API v7.1)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.

K2TrackingDevice Samples (K2API v7)

Deployment

Both build and deployment instructions are available here.

Overview (K2API Devices Docs)

This repository contains sample projects of devices / plugins in terms of Amethyst project.
Each project in the solution is an example of a different possible implementation
of a tracking device (Later referred to as K2TrackingDevice), and an additional one with settings.

You can find a detailed description about every single plugin and device type here.

Briefly, currently supported device types are:

• Tracking providers:
  • JointsBasis - Provide a vector of named, tracked joints
  • KinectBasis - Provide a fixed array of enumerated, tracked joints
    • Full Character - Provide Joint_Total joints (as many as Kinect V2 does)
    • Simple Character - Provide [ Head, Elbows, Waist, Knees, Ankles, Foot Tips ]
    • Basic Character - Provide [ Head, Waist, Ankles ]
• Spectator - Only poll data from the app

Please note that KinectBasis types can use automatic calibration, whereas JointsBasis cannot.

Additionally, plugins (devices) can provide their own settings, as described here and shown here.