Devices in a Muse ecosystem contain a file that describes the unique capabilities of the device. This file is called the DESCRIPTOR and is a JSON representation of control capabilities available to the device and the command path needed to trigger the action. Prior to launch, AMX duet modules in InConcert do not yet contain a descriptor file needed by the Muse controller. Following the beta period, InConcert will be updated and AMX Duet modules will include needed descriptor file. This Descriptor Generator tool is intended to give beta program members an ability to generate a descriptor file for duet modules you may be interested in working with as part of your test environment. The assembly process for a descriptor file is subtractive. Once an AMX Duet module is imported into the tool, the .jar file is interrogated for the manifest and other contextual information like components.xml and runtimedata.xml. This will establish a framework of Duet SDK components that are implemented, and the specific feature set enabled within each for that module. By default, all functionality is enabled at the selected component with the tool allowing for removing features that are not implemented in the module to offer a more accurate descriptor file.

The Descriptor Visualizer tool is needed by Muse developers to mine the descriptor file in a human readable format to identify the control path information and command options for each control command. This tool will provide scripting language specific syntax guidance for a driver control command.

During the beta period, if you find an issue to report with any of the provided tools, please send an email to itg@harman.com and include the detail on which tool, and what files were being utilized. Thank you