Re: "Guide notes"

2017-11-13 Thread David Wright
On Tue 07 Nov 2017 at 18:02:09 (+0100), Malte Meyn wrote:
> 
> 
> Am 07.11.2017 um 16:45 schrieb David Wright:
> >Thanks for the replies. I did try specifying a chord, but the
> >"pitch" parameter won't take it.
> 
> That’s because I didn’t know that you wanted chords … Of course it’s
> possible to specify a chord, see the following code. There’s only
> one reason I first only allowed pitches: You then wouldn’t have to
> input the duration.
> 
> 
> %%%
> 
> \version "2.19.80"
> 
> enharmonicGuide =
> #(define-music-function (music guide) (ly:music? ly:music?)
>#{
>  \afterGrace #music {
>\once \omit Stem
>\override ParenthesesItem.font-size = -1
>\override ParenthesesItem.padding = 0.1
>\parenthesize
>#guide
>  }
>#})
> 
> afterGraceFraction = 15/16
> 
> \relative {
>   2 \enharmonicGuide  4
>   2 
> }
> 
> %%%

That works well, thanks. The only difference from my published
example is that each note is individually parenthesised. But
that's perfectly fine for my sort of use: performance copies,
not publication.

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: "Guide notes"

2017-11-07 Thread Malte Meyn



Am 07.11.2017 um 16:45 schrieb David Wright:

Thanks for the replies. I did try specifying a chord, but the
"pitch" parameter won't take it.


That’s because I didn’t know that you wanted chords … Of course it’s 
possible to specify a chord, see the following code. There’s only one 
reason I first only allowed pitches: You then wouldn’t have to input the 
duration.



%%%

\version "2.19.80"

enharmonicGuide =
#(define-music-function (music guide) (ly:music? ly:music?)
   #{
 \afterGrace #music {
   \once \omit Stem
   \override ParenthesesItem.font-size = -1
   \override ParenthesesItem.padding = 0.1
   \parenthesize
   #guide
 }
   #})

afterGraceFraction = 15/16

\relative {
  2 \enharmonicGuide  4
  2 
}

%%%

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: "Guide notes"

2017-11-07 Thread David Wright
On Wed 01 Nov 2017 at 16:51:19 (+0100), Malte Meyn wrote:
> 
> 
> Am 01.11.2017 um 16:03 schrieb David Wright:
> >I've sung (strictly, not sung) a great many of these
> >without knowing what they're officially called.
> >I've created this one with what looks like an awful
> >hack. Is there a better way in LP? (Googling
> > lilypond guide note
> >turns up anything but.)
> 
> You could try to use \afterGrace for that:
> 
> %%%
> 
> \version "2.19.80"
> 
> enharmonicGuide =
> #(define-music-function (music guide) (ly:music? ly:pitch?)
>#{
>  \afterGrace #music {
>\once \omit Stem
>\override ParenthesesItem.font-size = -1
>\override ParenthesesItem.padding = 0.1
>\parenthesize
>$guide 4
>  }
>#})
> 
> afterGraceFraction = 15/16
> 
> \relative {
>   fis''2 \enharmonicGuide dis es
>   c a
> }
> 
> %%%
> 
> Try different values for font-size and padding. Also, I find the way
> LilyPond handles after-grace notes by default not optimal. You can
> either try using different afterGraceFraction values (like above) or
> the following override:
>   \override Score.SpacingSpanner.strict-grace-spacing = ##t
> The latter looks bad for this minimal example but might work better
> than setting afterGraceFraction in other contexts.

Thanks for the replies. I did try specifying a chord, but the
"pitch" parameter won't take it. So I'll probably stick with my
trill method. (I can't hear an effect in the MIDI so I haven't
bothered with tagging it either.)

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: "Guide notes"

2017-11-01 Thread Ben

On 11/1/2017 11:03 AM, David Wright wrote:

I've sung (strictly, not sung) a great many of these
without knowing what they're officially called.
I've created this one with what looks like an awful
hack. Is there a better way in LP? (Googling
 lilypond guide note
turns up anything but.)

I can live with this as it's good enough for almost
everything I do. But if you know this dangerous
corner¹, you can see that the hack doesn't scale
to the two notes in the bass staff: you get just
one bite of the cherry.

¹ Finzi, God is gone up—I hasten to add that I'm
not setting it: it just makes a good example of
the potential problem, which here occurs five
times in three locations.

Cheers,
David.


Hi David,

Maybe something like this? Just a start...

 \tiny
  \override Stem.stencil = ##f
  \override Flag.stencil = ##f
  \override ParenthesesItem.font-size = #0
   <\parenthesize ees''>4
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: "Guide notes"

2017-11-01 Thread Malte Meyn



Am 01.11.2017 um 16:03 schrieb David Wright:

I've sung (strictly, not sung) a great many of these
without knowing what they're officially called.
I've created this one with what looks like an awful
hack. Is there a better way in LP? (Googling
 lilypond guide note
turns up anything but.)


You could try to use \afterGrace for that:

%%%

\version "2.19.80"

enharmonicGuide =
#(define-music-function (music guide) (ly:music? ly:pitch?)
   #{
 \afterGrace #music {
   \once \omit Stem
   \override ParenthesesItem.font-size = -1
   \override ParenthesesItem.padding = 0.1
   \parenthesize
   $guide 4
 }
   #})

afterGraceFraction = 15/16

\relative {
  fis''2 \enharmonicGuide dis es
  c a
}

%%%

Try different values for font-size and padding. Also, I find the way 
LilyPond handles after-grace notes by default not optimal. You can 
either try using different afterGraceFraction values (like above) or the 
following override:

  \override Score.SpacingSpanner.strict-grace-spacing = ##t
The latter looks bad for this minimal example but might work better than 
setting afterGraceFraction in other contexts.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


"Guide notes"

2017-11-01 Thread David Wright
I've sung (strictly, not sung) a great many of these
without knowing what they're officially called.
I've created this one with what looks like an awful
hack. Is there a better way in LP? (Googling
lilypond guide note
turns up anything but.)

I can live with this as it's good enough for almost
everything I do. But if you know this dangerous
corner¹, you can see that the hack doesn't scale
to the two notes in the bass staff: you get just
one bite of the cherry.

¹ Finzi, God is gone up—I hasten to add that I'm
not setting it: it just makes a good example of
the potential problem, which here occurs five
times in three locations.

Cheers,
David.
\header { tagline = ##f }
{
  \key e \major
  \time 3/4
  r4 r g'
  \once \override TrillSpanner.stencil = ##f \pitchedTrill dis''2.
  \startTrillSpan ees''
  \key aes \major
  4 \stopTrillSpan q q
}
{
  \clef bass
  \key e \major
  \time 3/4
  gis2 e4
  \once \override TrillSpanner.stencil = ##f \pitchedTrill 2.
  \startTrillSpan  %%% wrong %%%
  \key aes \major
  g?4 \stopTrillSpan g g
}


guide-note.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user