Skip to content

Fix malformed ratio in sparschuh-stanhope.scl - #2003

Open
float3 wants to merge 1 commit into
cuthbertLab:masterfrom
float3:fix-sparschuh-stanhope-ratio
Open

Fix malformed ratio in sparschuh-stanhope.scl#2003
float3 wants to merge 1 commit into
cuthbertLab:masterfrom
float3:fix-sparschuh-stanhope-ratio

Conversation

@float3

@float3 float3 commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Degree 8 is written 697//441, with a doubled slash. No Scala parser can read it: the file is unparseable from that line on.

This changes one character and preserves the column alignment of the surrounding degrees. No other file in the archive contains a doubled slash.

Note that music21 still cannot parse this file after the fix, for an unrelated reason: ScalaData.parse only skips lines that start with ! and does not strip trailing inline ! comments.

Degree 8 is written `697//441`, with a doubled slash. No Scala parser can
read it: the file is unparseable from that line on.

The intended value is unambiguous. The comment on the same line documents
the degree as (128/81) * (6273/6272), and that product is exactly 697/441:

    128 * 6273 = 802944
     81 * 6272 = 508032
    802944 / 508032 = 697/441   (both divide by 1152)

It is also consistent with the file's own arithmetic — 6273/6272 is
+0.276 cents, as the comment states — and it sits correctly between its
neighbours 3/2 (1.5) and 82/49 (1.6735) at 1.5805.

This changes one character and preserves the column alignment of the
surrounding degrees. No other file in the archive contains a doubled
slash.

Note that music21 still cannot parse this file after the fix, for an
unrelated reason: ScalaData.parse only skips lines that *start* with `!`
and does not strip trailing inline `!` comments, which every degree line
here carries. That is a separate parser issue, not a data one.
@coveralls

Copy link
Copy Markdown

Coverage Status

coverage: 93.33%. remained the same — float3:fix-sparschuh-stanhope-ratio into cuthbertLab:master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants