lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sharping naturals


From: David Raleigh Arnold
Subject: Re: sharping naturals
Date: Wed, 19 Aug 2015 19:30:48 -0400

On Mon, 10 Aug 2015 14:36:41 +0200
Peter Bjuhr <address@hidden> wrote:

> > When you use key signatures like A major or B Major you end
> > up with a lot of naturals in the score for which you may
> > have to manually add sharps.
> >
> > Is there a switch that will automatically sharp all the
> > naturals?
> 
> David, in a previous thread some time ago on a similar topic I think I 
> recall that you mentioned that this may be better seen as an editor task 
> than a task for LilyPond.
> 
> In Frescobaldi (since v 2.18) there is a tool (Tools->Pitch->Mode shift) 
> that adjusts the pitch to a given mode or scale. I just realized that 
> this may be able to accomplish the above:
> 
> If you enter:
> 
>    b c d e f g a
> 
> and use the Mode shift tool with the mode b major the result will be:
> 
>    b cis dis e fis gis ais
> 
> As mentioned before (in this thread), the problems start if you actually 
> do not want some of the notes to be sharpened. Then of course you'll 
> have to adjust this manually! But with a piece with only a few 
> exceptionds to the given key it may be worth while to use this method...

I seriously doubt it, since another tool uses "n". the "n" is only for
the few notes which otherwise would be changed by \follow. If you already
have typed some of the sharps, nothing will happen to them. Without \follow,
there is no reason to tolerate "n" in the input.

If I hadn't already done it by key signature with a simple sed script, I would 
use the
note list \follow fs cs ... because it is most flexible and would be
a simple search and replace rather than needing to fall through,
but that didn't occur to me until this latest discussion.

The problem with integration with lilypond is the range { }. That prevents
getting it sorted before the proper program sees it. If use of \follow and|or
relative could produce a new source file and|or a finished product
both \follow and \relative would be easier and more profitable to use IMO.
If truth in typing is the sole grounds for objection, \relative is a far
greater problem than \follow could ever be. IMO. Kindest regards, Rale



reply via email to

[Prev in Thread] Current Thread [Next in Thread]