Re: Towards a new pitch representation

[Felipe Gonçalves Assis]

Hi Carl,

>
> Hi, Felipe.
>
> I've looked at your patch, but I'm having a bit of trouble seeing how the
> patch resolves the issues that are identified in issue 1278.
>
> I must admit that i've not yet fully understood Hans's emails on issue 1278.
>
> How do your new two-element alterations improve the situation?
>

You don't need to go back to those emails. I hope the attachment in my
last email can help. But for a simple example of how my patch works,
when you type, e.g., ciseh' in a LilyPond input file, this is mapped to a
pitch that has as alteration (1 . -1), meaning "one semitone minus one
quarter-tone", which might then be typeset as a sharp with a down-arrow.

In contrast, cih' has as alteration (0 . 1), which might be mapped to
a natural with an up-arrow.

The current representation cannot make that distinction, both alterations
would be 1/4 (for this reason ciseh is not even defined).

>
> It would be very helpful for me to discuss this patch if you had a test file
> that shows how the new features are used.
>

I am very sorry for forgetting to provide this. I am attaching some examples.

arrows.ly demonstrates the functionality requested in issue 1278.
dodecaphonic-adapted.ly is an adaptation of the snippet dodecaphonic.ly
using the new interfaces.

> It would be even better if there were a test file that compiled but didn't
> behave properly in 2.13.44, and then a corresponding file that does behave
> properly in your patch.
>

This is an enhancement request for which we have files that did not
compile in the previous version, but that now produce nice scores
(again, see arrows.ly).

Thanks,
Felipe

arrows.ly
Description: Text Data

dodecaphonic-adapted.ly
Description: Text Data