Issue 3174: Implement \accidental markup and \pitched command for transposable accidental markups

Issue 3174: Implement \accidental markup and \pitched command for transposable accidental markups

This is a building block for creating pitched ornaments behaving
sensibly under transposition.

It would be arguable to define \pitched differently so that it works
only on ornaments and does the stacking itself, like
c^\pitched\trill des

and instead give the current version of \pitched a name like \pitchify.

As it stands, here are the implemented meanings:

\accidental markup:
Draw an accidental based on the @var{pitch} property of the causing
event.  This is typically set in music using the (transposable)
@code{\pitched} command, like

@lilypond[verbatim,quote]
melody = \relative c'
  { \key c\major c2^\trill^\pitched des -\markup \accidental d! }
\new Staff { \melody }
\new Staff { \transpose c' e' \melody }
@end lilypond

\pitched music function: arguments pitch and music:
"Give @var{music} a pitch of @var{pitch}.

[Trevor Daniels, 2013-02-13 22:56:30]

I definitely prefer the alternative you suggest in para 3.
You would not then need the warning, which is only necessary due to the
complicated 2-stage interface.

https://codereview.appspot.com/7323060/diff/1/scm/define-markup-commands.scm
File scm/define-markup-commands.scm (right):

https://codereview.appspot.com/7323060/diff/1/scm/define-markup-commands.scm#...
scm/define-markup-commands.scm:2777: (ly:warning (_ "No pitch found.  Have you
forgot \\pitched?"))
Did you forget ...

[thomasmorley65, 2013-02-13 23:27:55]

On 2013/02/13 22:56:30, Trevor Daniels wrote:
> I definitely prefer the alternative you suggest in para 3.
> You would not then need the warning, which is only necessary due to the
> complicated 2-stage interface.

I'd second.

Regarding: 

melody = 
\relative c' { 
        %\override Script #'script-priority = #-100
        %\override TextScript #'script-priority = #100
        \key c\major 
        c2^\trill^\pitched des 
          -\markup 
             \accidental 
        d!
        c2^\prallprall^\pitched des 
          -\markup  % \fontsize #-6 \translate #'(0.6 . 0) 
             \accidental 
        d! 
}
\new Staff { \melody }
\new Staff { \transpose c' e' \melody }

Without the commented commands, TextScript and Script are switching their
positions and aren't well aligned (worse while using \prallprall).

Rather a matter of documentation/example.

[dak, 2013-02-14 09:21:07]

On 2013/02/13 23:27:55, thomasmorley65 wrote:
> On 2013/02/13 22:56:30, Trevor Daniels wrote:
> > I definitely prefer the alternative you suggest in para 3.
> > You would not then need the warning, which is only necessary due to the
> > complicated 2-stage interface.
> 
> I'd second.

Here is the deal: I can rename the current \pitched to \withPitch
which is quite in line with \withMusicProperty.
\withPitch/\accidental is a basic mechanism for passing transposition
information from music to markups.

The questions are

a) is this mechanism sufficient for pitched ornaments?
b) are there useful applications apart from pitched ornaments?

If both answers are "no", this approach does not lead anywhere.  With
regard to question a), the main question I see here is "should this be
tied into the accidental rule system".  If it isn't, it remains the
user's task to properly distribute accidentals and cautionaries.  Now
fortunately, the question "in-scale" or "out-of-scale" remains
constant under _chromatic_ transposition (and modal transposition is
quite less complete), so while this is cumbersome, it still tackles
the basic problem of transposability.  It also begs the question
whether we should not just be passing "pitch" but also
"force-accidental" and "cautionary" and have the \accidental markup
heed them.

Actually, force-accidental does not make much sense since setting it
to #f would mean having to check whether the current accidental rules
would demand an accidental, and that is a check that is, I think,
beyond the design of this feature as long as "should this be tied into
the accidental rule system" can be answered with "no".

So at any rate, the question this patch answers is the question "can
we pass information about transposed accidentals through to markups",
and the answer is "yes".  "Is this a good interface to pitched
ornamentations" has been answered "no", and "can it be a good building
block for a good interface to pitched ornamentations" will depend on
what we agree on being a good interface to pitched ornamentations.

So the message is "we can do", but we still need to figure out _what_
we can do.  Proposals?

[wl_gnu.org, 2013-02-14 09:38:40]

> Here is the deal: I can rename the current \pitched to \withPitch
> which is quite in line with \withMusicProperty.
> \withPitch/\accidental is a basic mechanism for passing
> transposition information from music to markups.
> 
> The questions are
> 
> a) is this mechanism sufficient for pitched ornaments?

I don't think so.  For example, mordents sometimes need *two*
accidentals, one written above and another one below.  But maybe this
can easily fixed by allowing a second, optional argument.

> b) are there useful applications apart from pitched ornaments?

Good question.  AFAIK, only ornaments need that.

> So the message is "we can do", but we still need to figure out
> _what_ we can do.  Proposals?

I'm currently lacking inspiration, sorry.


    Werner

[thomasmorley65, 2013-02-14 23:30:07]

On 2013/02/14 09:21:07, dak wrote:

> So the message is "we can do", but we still need to figure out _what_
> we can do.  Proposals?

Well, currently I don't have a good idea.

Though, some time ago Arnold posted his approach on -user:
http://lists.gnu.org/archive/html/lilypond-user/2012-06/msg00278.html
direct link to his code:
http://old.nabble.com/file/p33991423/pitchedArticulations.ly

Perhaps this might be useful, I hadn't a closer look, though.