You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the code, there are various comments about replacing keyToDegree2 by keyToDegree (and removing performKeyToDegree2).
The comment says:
// TODO won't be required in next SC release see pull request #1164
So I was thinking about making a PR on this repo to remove this (six years have passed ;-), but as far as I can tell, nothing has changed in SC related to this...your SC submissions from 2014 (1163 and 1164) were unfortunately never integrated into SC.
I know it's related to using offsets of 0.1 vs 0.5 for flattened and sharpened degrees:
Maybe the comments should just be updated to state why keyToDegree2 is needed, and no longer suggest that it will be replaced by keyToDegree imminently (it seems it won't be!).
The text was updated successfully, but these errors were encountered:
In the code, there are various comments about replacing
keyToDegree2
bykeyToDegree
(and removingperformKeyToDegree2
).The comment says:
So I was thinking about making a PR on this repo to remove this (six years have passed ;-), but as far as I can tell, nothing has changed in SC related to this...your SC submissions from 2014 (1163 and 1164) were unfortunately never integrated into SC.
I know it's related to using offsets of 0.1 vs 0.5 for flattened and sharpened degrees:
And if we were to use the existing
keyToDegree
, then the resolution of those degrees (by the note Event) would return bad notes...Maybe the comments should just be updated to state why
keyToDegree2
is needed, and no longer suggest that it will be replaced bykeyToDegree
imminently (it seems it won't be!).The text was updated successfully, but these errors were encountered: