Keyboard-Patch Coverage

Audit keyboard patch coverage.

Description

Keyboard patch planning connects musical requirements to programmed sounds.

Keyboard patch planning connects musical requirements to programmed sounds. A coverage audit compares patch labels without checking whether their sound and switching behavior fit the score.^[1]

Audit keyboard patch coverage.

When to use Keyboard-Patch Coverage

Use this tool to audit keyboard patch coverage.

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.

How to use Keyboard-Patch Coverage and understand its results

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
Enter requiredPatches, programmedPatches using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredPatches	Required keyboard patches	list of string	Required
programmedPatches	Programmed patches	list of string	Required

Enter requiredPatches and programmedPatches label lists. Trim labels, reject blank entries and match case-insensitively with en-US lowercase. Deduplicate each list, requiring at least one distinct required item; an empty observed list is allowed. Return matched, missing, unexpected labels and coverage. Duplicate normalized labels keep their last trimmed spelling at the first key position.

coverage%=100 matchedDistinctRequirements/distinctRequirements

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredPatches": [
      "alpha",
      "beta",
      "gamma",
      "delta"
    ],
    "programmedPatches": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 50,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma",
      "delta"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No synthesizer data, MIDI routing, audio content or cue timing is examined. Spelling differences beyond case and outer whitespace remain distinct.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Show-Control Trigger Coverage: Audit show-control trigger mappings. For a complementary task, use Dante Latency Budget: Budget Dante audio latency across devices and network hops.

References

Keyboard-Patch Coverage — tool.io

Similar or alternative tools

Show-Control Trigger Coverage
Audit show-control trigger mappings.
Dante Latency Budget
Budget Dante audio latency across devices and network hops.