Skip to content

Main content

Public Tuning Pitch Name Variant Tool

Preserve an explicit public tuning pitch-name variant and source without equating tuning systems or deriving frequency.

Loading tool…

Description

Record a public tuning source's pitch-name variant.

Musical field records distinguish performer/community attribution, transcription and naming sources, cyclic beat coordinates and recorded permission. A public-access label is different from a reuse license, and a numerical timing residual is different from performance interpretation. Cultural context and actual consent remain tied to original sources.

Record a public tuning source's pitch-name variant.

When to use this tool

Use Public Tuning Pitch Name Variant when checking the stated public-record, timing, attribution or permission convention.

How to use the tool and how it works

  1. Enter recordingId, suppliedPitchName, namingSource. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read token. Use the output convention below.

Require nonempty recording ID, supplied pitch name and naming source. Encode the ordered triple as JSON text.1

Input fieldMeaning and unitsAccepted input
recordingIdRecording IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
suppliedPitchNameSupplied Pitch NameRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
namingSourceNaming SourceRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenJSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "recordingId": "R17",
    "suppliedPitchName": "Sa",
    "namingSource": "source S4"
  },
  "output": {
    "token": "[\"R17\",\"Sa\",\"source S4\"]"
  }
}

Limitations and assumptions

  • No pitch, frequency, tuning, spelling equivalence or culturally appropriate naming convention is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use original recordings and community/source conventions, with appropriate verified consent and rights review for actual interpretation, reproduction or sharing.

References

  1. Calculation and input contract: ethnomusicology/public-tuning-pitch-name-variant — tool.io

Similar or alternative tools