davidnalesnik
commented
8 years ago (This is perhaps related to #1)
Sam writes: You state that alterations are only available before figures. However, the following markup compiles correctly: \markup \rN { V 5 s }
Sam writes: it fails, as you state, with the following code: \markup \rN { V s }
I should revise the documentation to reflect this. I've been hesitant to do this, because I'd like to fix the underlying problem first. Right now the appearance of the unadorned alteration in the column is a happy coincidence, not a "feature".
The code relies on an internal separation of quality markers and inversion numbers. Figures are parsed in the entry list based on the presence of a number in the first figure given. So \markup \rN { V 5 s } works, but \markup \rN { V s } does not. "s" in this case would be taken as a quality marker, and "s" is not an option--the simple string will be returned.
Is "#" commonly used as a marker for augmented chords? (I can't imagine that V# would ever mean a V with a raised third...) If it is, I can add it to the list of recognized qualities. (You'll note that I removed "f" from the list of recognized qualities -- "V f:" makes no sense. If you need a Mmm7 chord, write "V f9".)
In general, I am having great difficulties deciding what constitutes a quality and what constitutes a figure. I think that the Roman numeral system is rather fuzzy about the distinction. For example, take iio7 and iio4/3 and compare them with iihalf-dim7 and iihalf-dim4/3 (with the slashed circle, of course). In the first "o" obviously refers to the triad quality. In the second, is the quality marker in one case "slashed-circle7" and in the other "slashed-circle" alone? (You can see this messes with the recognition of figures by the presence of numbers....)
Unfortunately, the computer requires a precision that we don't need when writing RNs by hand. Any thoughts on how to sort this out would be most welcome. I can't imagine how much time I've spent going around in circles with this.
Sam writes: This latter problem isn't too bad, because we can just use the long-form version of the first code. The real problem manifests itself, however, when we add in extender lines: \markup \rN { V 4---s3 } compiles "s3," not "#3," and of course { 4---s } compiles "4---s," not "4---#."
Yes, a search-and-replace needs to be done with the whole figure-string. What happens now is pretty rudimentary.
Same writes: I'm guessing the problems are related; do you know of any fixes or workarounds? { 4---"s3" } compiles #3, but pushes it to a lower level. I'm on 2.19.32.
Right, because "s3" is being taken as a new figure. As for a solution, honestly I don't know. I would say include a markup, but \rN requires strings. Use a Unicode flat, perhaps?
Sam writes: In any event, I've been using the code like crazy these last few weeks; this is REALLY terrific work!
Glad to hear it!
David
sambivens
Hi David,
(This is perhaps related to #1)
You state that alterations are only available before figures. However, the following markup compiles correctly: \markup \rN { V 5 s }
It fails, as you state, with the following code: \markup \rN { V s }
This latter problem isn't too bad, because we can just use the long-form version of the first code. The real problem manifests itself, however, when we add in extender lines: \markup \rN { V 4---s3 } compiles "s3," not "#3," and of course { 4---s } compiles "4---s," not "4---#."
I'm guessing the problems are related; do you know of any fixes or workarounds? { 4---"s3" } compiles #3, but pushes it to a lower level. I'm on 2.19.32.
In any event, I've been using the code like crazy these last few weeks; this is REALLY terrific work!
Sam