Re: Unterminated glissando

2019-02-15 Thread Thomas Morley
Am Fr., 15. Feb. 2019 um 14:04 Uhr schrieb Andrew Bernard
:
>
> Sorry people, my mistake - there were actually glissandos with no following 
> notes at the end of my score. Please ignore that.
>
> But I still see this, with no lines number:
>
> programming error: overwriting glissando
> continuing, cross fingers
>
> So my question partially stands. What does this mean? What should I look for?
>
> Andrew

Hi Andrew,

"programming error: overwriting glissando" comes from glissando-engraver.cc.

Though, I wasn't able to force this error with any code I tried.
Do you apply some Glissando-overrides?
Maybe some coding is not as clean as wished.

Anyway, it's pretty easy to get the "unterminated glissando"-warning.

To check in a long, complicated file I wrote a helper-tool.
It checks for grob::is-live?, sufficient for all unterminated
glissandi. Maybe it is of help for "programming error: overwriting
glissando" as well.

N.B.: it is not tested widely...

But here the code:

tst =
#(lambda (ctx)
  (let ((gliss '())
(gliss-to-test '()))
  (make-engraver
((initialize translator)
  (set! gliss '())
  (set! gliss-to-test '()))
(acknowledgers
  ((glissando-interface engraver grob source-engraver)
   (set! gliss
 (list grob
   (ly:prob-property
 (ly:grob-property grob 'cause)
 'origin)
((stop-translation-timestep translator)
   (if (and (pair? gliss) (ly:grob? (car gliss)))
   (set! gliss-to-test
 (cons
   (list
 (car gliss)
 (second gliss)
 (grob::rhythmic-location (car gliss)))
   gliss-to-test
((finalize translator)
  (if (pair? gliss-to-test)
  (let ((init #f))
(for-each
  (lambda (e)
(if (and (not (grob::is-live? (car e)))
 (not (equal? (car e) init))
 ;; mhh...Do I exclude too much?
 (pair? (third e)))
(format #t
"Check Glissandi: \n\tin file: ~a\n\tin music: measure ~a, moment ~a\n"
(second e)
(car (third e))
(ly:moment-main (cdr (third e)
(set! init (car e)))
  gliss-to-test)))

\layout {
  \context {
\Voice
\consists \tst
  }
}


Compiling:

<<
  \new Staff {
  s2. c'4\glissando s1
}
  \new Staff {
  c'1 c'1\glissando
}
  \new Staff {
  c'1 c'1\glissando
}
>>

returns (for my atest-83.ly-file):
[...]
warning: unterminated glissando
Check Glissandi:
in file: #
in music: measure 1, moment 3/4
warning: unterminated glissando
Check Glissandi:
in file: #
in music: measure 2, moment 0
warning: unterminated glissando
Check Glissandi:
in file: #
in music: measure 2, moment 0
[...]

HTH a bit,
  Harm

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


Re: Unterminated glissando

2019-02-15 Thread Andrew Bernard
Sorry people, my mistake - there were actually glissandos with no following
notes at the end of my score. Please ignore that.

But I still see this, with no lines number:

programming error: overwriting glissando
continuing, cross fingers

So my question partially stands. What does this mean? What should I look
for?

Andrew


On Fri, 15 Feb 2019 at 23:01, Andrew Bernard 
wrote:

> I get this:
>
> programming error: overwriting glissando
> continuing, cross fingers
> warning: unterminated glissando
> warning: unterminated glissando
> Preprocessing graphical objects..
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: bracket slurs?

2019-02-15 Thread Michael Gerdau
[snip]

> > 
> > \version "2.21.0"
> >
> > {
> >  \override TupletBracket.positions = #'(0.0 . 2.0)
> >  \omit TupletNumber
> >  \tuplet 2/2 { c'1 g' }
> > }
> > 
> >
> > Kind regards,
> > Michael
> 
> Could they be ligatures?
> 
> http://lilypond.org/doc/v2.19/Documentation/notation/ancient-notation_002d_002dcommon-features

Good pointer!

They indeed are likely ligatures.

I want them closer to the notes like slurs. I could achieve that by manually 
\override LigatureBracket.positions - is there an automatic way?

Kind regards,
Michael
-- 
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver

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


Unterminated glissando

2019-02-15 Thread Andrew Bernard
I get this:

programming error: overwriting glissando
continuing, cross fingers
warning: unterminated glissando
warning: unterminated glissando
Preprocessing graphical objects..

What does this mean actually? How can a glissando be unterminated - surely
it connects to the next available note. I checked - it's not the last notes
in the score.

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


Automatic lengthening of Lyrics extenders

2019-02-15 Thread Michael Gerdau
Dear lilyponders,

in vocal music especially multipart music lyrics extenders do greatly enhance 
readability how stuff is sung. Especially for long notes extenders come in 
handy - so far this is probably well established and not exactly new :)

This all works reasonably good for tied and slurred music. However when there 
is a long note (e.g. full, or breve or such) the current situation leaves room 
for improvement (to my knowledge).




\version "2.21.0"

{
  <<
  \new Staff { c''1 c2. c2. c1. }
  \addlyrics { bla __ bla __ bla __ bla __ }
  \new Staff { c''8( c'' c'' c'' c'' c'' c'' c'')
 c''8( c'' c'' c'' c'' c'')}
  \addlyrics { bla __ bla __ bla __ bla __ }
  >>
}
%

-- 
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver

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


Automatic lengthening of Lyrics extenders

2019-02-15 Thread Michael Gerdau
Dear lilyponders,

[hit sent too early the first time around]
in vocal music especially multipart music lyrics extenders do greatly enhance 
readability how stuff is sung. Especially for long notes extenders come in 
handy - so far this is probably well established and not exactly new 😊

This all works reasonably good for tied and slurred music. However when there 
is a long note (e.g. full, or breve or such) the current situation leaves room 
for improvement (to my knowledge).

I'm looking for an automatic way to have the extenders in the upper system 
similar to those in the lower system as of the example below.

Any ideas?


\version "2.21.0"

{
  <<
\new Staff { c''1 c''2. c''2. c''1. }
\addlyrics { bla __ bla __ bla __ bla __ }
\new Staff {
  c''8( c'' c'' c'' c'' c'' c'' c'')
  c''8( c'' c'' c'' c'' c'')
  c''8( c'' c'' c'' c'' c'')
  c''8( c'' c'' c'' c'' c'' c'' c'' c'' c'' c'' c'')
}
\addlyrics { bla __ bla __ bla __ bla __ }
  >>
}
%

Kind regards,
Michael
-- 
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver

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


bracket slurs?

2019-02-15 Thread Michael Gerdau
Hi Lilyponders,

in old(er) music like e.g. Melchior Franck I sometimes find brackets for slurs, 
most often between full notes. I have tried to mimic this using tuplet brackets 
but they are only similar and need manual tweaking each time w/r to their 
position. I'd also have to take care of melismata manually. All doable but...

Would it be (reasonably easily) possible to manipulate slurs such that they 
produce brackets instead of splines?


\version "2.21.0"

{
  \override TupletBracket.positions = #'(0.0 . 2.0)
  \omit TupletNumber
  \tuplet 2/2 { c'1 g' }
}


Kind regards,
Michael
-- 
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver

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


Prall in a staff space

2019-02-15 Thread Tyler Mitchell
I am attempting to put a prall within the staff, in spaces only,
similar to how a tenuto works.

Given the following bit of code:

\version "2.18.2"
\layout { \context { \Staff \remove Time_signature_engraver } }
\relative c' {
  \override Stem.length = #0
  f^\tenuto g^\tenuto f-\prall g-\prall |
  \override Script.Y-offset = #0
  \override Script.font-size = #-3
  f-\prall g-\prall
  \override Script.extra-offset = #'(0 . -0.5)
  f-\prall^\markup {*} g-\prall
}

(The note marked with the asterisk is the desired output.)

How does LilyPond know to place the tenuto within the staff, but
the prall outside of it? And how does it determine that the tenuto
should be placed in a space, but the prall should be placed on a
line?

As seen above, I've managed to use X-offset and extra-offset to
move the prall around (the font-size is just so it fits better) but
I can't figure out how to get it to place it always in the next
available space.

Thanks for any suggestions you may have.

Tyler

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


Trill spanner on pitched trills collision avoidance

2019-02-15 Thread N. Andrew Walsh
Hi List,

another issue I'm running into: According to NR 1.3.3, "consecutive trill
spans will work without explicit \stopTrillSpan commands, since successive
trill spanners will automatically become the right bound of the previous
trill."

However, in this example:

\version "2.19.82"

\relative c'' {

  %1
  \time 3/4
  R1*3/4

  | %2
  \time 5/4
  R1*5/4

  | %3
  \time 2/4
  r4
  \pitchedTrill
  d,\startTrillSpan  cis

  | %4
  \pitchedTrill
  d\startTrillSpan  des

}

--
That is not the case. In this example, the first trill spanner should
continue into the second, as the main note remains the same and only the
auxiliary note changes.

Also, some more general questions about how pitched trills work:

is it possible to have multiple auxiliary notes?
is it possible to attach fingering diagrams to each of them?
if I try to attach phrasing slurs from one main note to the next, I get an
error:  "warning: Ignoring grob for slur: TrillPitchAccidental.  avoid-slur
not set?" Does this warning matter? What should I do to avoid it?

Thanks for the help,

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