Nashville Number System Conversion
Parse literal Roman roots/qualities/sevenths into explicitly concatenated Nashville number suffix convention (V7→57), preserving accidental and minor/diminished evidence; not numeral text replacement or absolute-key assignment.
Description
Nashville numbers express degree and quality through a declared text convention.
Nashville numbers express degree and quality through a declared text convention. A dominant seventh combines its degree digit with a seventh suffix.1
Enter 1–128 exact Roman tokens I–VII/i–vii, optional b/bb/#/##, optional o/ø/+ and optional7; ø requires 7. Convert minor to m, diminished to dim and preserve other markers. V7 becomes 57.
When to use Nashville Number System Conversion
Use Nashville Number System Conversion when you need to evaluate the supplied records under the calculation and evidence rules below. Concatenation follows this tool’s convention. No absolute key, nested functions or editorial normalization is inferred.
Enter the written notes, explicit grouping, pitch observations or supported chord tokens requested. Keep scientific octaves, accidentals and caller evidence consistent.
How to use Nashville Number System Conversion and understand its results
- Enter the written notes, explicit grouping, pitch observations or supported chord tokens requested. Keep scientific octaves, accidentals and caller evidence consistent.
- Enter romanChordTokens using the field table and calculation rules, then run the tool.
- Read nashvilleChordTokens. 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 |
|---|---|---|---|
| romanChordTokens | Roman chord tokens | list of string | Required |
Enter 1–128 exact Roman tokens I–VII/i–vii, optional b/bb/#/##, optional o/ø/+ and optional7; ø requires 7. Convert minor to m, diminished to dim and preserve other markers. V7 becomes 57.
output=accidental+degree+qualitySuffix+optional7 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| nashvilleChordTokens | Nashville chord tokens | list of string |
{
"input": {
"romanChordTokens": [
"I",
"vi",
"bVII",
"V7"
]
},
"output": {
"nashvilleChordTokens": [
"1",
"6m",
"b7",
"57"
]
}
}Limitations and assumptions
Concatenation follows this tool’s convention. No absolute key, nested functions or editorial normalization is inferred.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Roman Numeral Chord Analysis: Roman analysis preserves a chord root’s written degree and chromatic alteration. Enharmonic sounding equality can conceal different written functions. For a complementary task, use Secondary Dominant Target Lookup: A secondary dominant is spelled a perfect fifth above a declared target. The slash target carries Roman degree and alteration relative to a major tonic.
References
-
Nashville Number System Conversion — tool.io
Similar or alternative tools
- Roman Numeral Chord Analysis
Roman analysis preserves a chord root’s written degree and chromatic alteration. Enharmonic sounding equality can conceal different written functions.
- Secondary Dominant Target Lookup
A secondary dominant is spelled a perfect fifth above a declared target. The slash target carries Roman degree and alteration relative to a major tonic.