Re: Stem lenght and ledger lines

2018-04-16 Thread Malte Meyn



Am 16.04.2018 um 09:14 schrieb foxfanfare:

What exactly is Malte's new-flags?


I added 256th, 512th, and 1024th rest and flag glyphs to Emmentaler so 
that you can use these rests and the notes without beams, see issue 
5277: https://sourceforge.net/p/testlilyissues/issues/5277/


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


Re: Stem lenght and ledger lines

2018-04-16 Thread foxfanfare
Torsten Hämmerle wrote
> This is sheer coincidence - LilyPond always (!) extends the stems to the
> middle stave-line.
> As soon as there are more than two flags, they obscure the ledger lines.
> 
> Moreover, cue size note stems should not even extend to the middle
> stave-line but be a stave-space shorter, even when extended. Gould does
> not
> mention that explicitly, but one can see it in her examples.
> 
> I'm going to create an issue (and incidentally have already created a
> patch
> some time a go that still needs some testing for beams and tremolos).
> 
> Here's the current status showing cue notes in the lower staff and already
> using Malte's new mega-flags:
> 
> http://lilypond.1069038.n5.nabble.com/file/t3887/flagged-stems.png; 
> 
> All the best,
> Torsten

Thank you for your interest!
What exactly is Malte's new-flags?



--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

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


Re: Stem lenght and ledger lines

2018-04-15 Thread Torsten Hämmerle
foxfanfare wrote
> You can see Lilypond does this for 8th and 16th notes, but not further by
> default!

This is sheer coincidence - LilyPond always (!) extends the stems to the
middle stave-line.
As soon as there are more than two flags, they obscure the ledger lines.

Moreover, cue size note stems should not even extend to the middle
stave-line but be a stave-space shorter, even when extended. Gould does not
mention that explicitly, but one can see it in her examples.

I'm going to create an issue (and incidentally have already created a patch
some time a go that still needs some testing for beams and tremolos).

Here's the current status showing cue notes in the lower staff and already
using Malte's new mega-flags:

 

All the best,
Torsten




--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

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


Re: Stem lenght and ledger lines

2018-04-15 Thread Noeck
> You can see Lilypond does this for 8th and 16th notes, but not further by
> default!

LilyPond treats all flags equally as it starts the stem from the middle
of the staff. That’s why the 8th and 16th flag don’t reach the ledger
lines. (This is no comment on the actual issue which seems to be
extremely rare in the scores I have.)

Cheers,
Joram

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


Re: Stem lenght and ledger lines

2018-04-15 Thread foxfanfare
Sorry I thought I posted this one in the bug report subforum...



--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

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


Stem lenght and ledger lines

2018-04-15 Thread foxfanfare
Quote from Gould's book: The outer stave-lines must be clearly visible; tails
closer to noteheades will obscure ledger lines

\version "2.19.80"
\relative c' {

  \cadenzaOn
  \omit Score.TimeSignature  
  \autoBeamOff  
  e''8 e16 e32 a64 
}

You can see Lilypond does this for 8th and 16th notes, but not further by
default!

Manual corrected version:

\version "2.19.80"
\relative c' {

  \cadenzaOn
  \omit Score.TimeSignature  
  \autoBeamOff  
  e''8 e16 
  \override Stem #'length-fraction = #(magstep 2.75) 
  e32 
  \override Stem #'length-fraction = #(magstep 4.25) 
  a64
} 



--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

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