Re: Cannot include # in URL?

[Abraham Lee]

Hi, Tom!

On Sun, Oct 29, 2017 at 12:51 AM Tom Campbell  wrote:

> Can't figure out how to include # in a URL. When I do something like this:
>
> \markup {
> For more, see
> http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#durations
> }
>
>
> I get the following message:
>
> error: GUILE signaled an error for the expression beginning here
> For more, see
> http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#
>
>  durations
>
> How should I include # in a URL in text markup?
>

How about putting it in double quotes?

\markup {
  For more, see “
http://lilypond.org/doc/v2.18/Documentation/notation/writing-rhythms#
durations”
}

Best,
Abraham

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

Re: non-triplet tuplets collide with staff

[Thomas Morley]

Hi Mason,

please always state the version you use and a tiny example.
Maybe you would have spotted that

2017-10-28 23:38 GMT+02:00 Mason Hock :
> Lilypond by default seems to place all tuplet numbers/brackets so that they
> collide with the staff, with the exception of triplets, which it places
> outside the staff.

isn't true.

See
{
\cadenzaOn
\tuplet 2/1 { a4 a }
\tuplet 3/2 { a a a }
\tuplet 4/3 { a a a a }
\tuplet 5/4 { a a a a a }
\tuplet 6/5 { a a a a a a }
\tuplet 7/6 { a a a a a a a }
}
and
{
\tuplet 2/1 { a8 a }
\tuplet 3/2 { a a a }
\tuplet 4/3 { a a a a }
\tuplet 5/4 { a a a a a }
\tuplet 6/5 { a a a a a a }
\tuplet 7/6 { a a a a a a a }
}
Where the TupletBracket is printed depends on whether a Beam is
present or not, presence of other maybe colliding objects etc.
Has nothing to do if being a triplet or anything else.
Btw, what you call collisions is common practice in printed editions.

> I would like all tuplets outside of the staff like
> triplets.

> If I do both
>
> \override Staff.TupletNumber #'outside-staff-priority = #1
> \override Staff.TupletBracket #'outside-staff-priority = #1
>
> I get an error: "warning: Cannot set outside-staff-priority for element and
> elements' Y parent."


I agree it would be better to set outside-staff-priority for both,
Number and Bracket, and let LilyPond sort it out.
Alas, it doesn't work. You may write a feature-request to the bug-list.

For now you could do:

\override TupletBracket.after-line-breaking =
  #(lambda (grob)
(ly:grob-set-property!
  (if (and (ly:stencil-empty? (ly:grob-property grob 'stencil))
   (ly:grob? (ly:grob-object grob 'tuplet-number)))
  (ly:grob-object grob 'tuplet-number)
  grob)
  'outside-staff-priority
  100))

Cheers,
  Harm

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

Re: Cannot include # in URL?

[Tom Campbell]

Worked like a charm, Abraham. Thank you so much. That made my night!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

How to get \fromproperty to work with score headers?

[Shevek]

Does anyone know if there's an updated version of
http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers?
It's listed as "to do" in the snippet, but I believe that dates back to
several years ago. I'd like to use \fromproperty #'header:piece to put
movement titles at the top of pages. 

If there isn't a newer version that supports this, I can mess around with
trying to get it working, but I'd appreciated it if anyone can point me in
the right direction to start; what would score-level headers be called? is
the existing snippet structure adequate or is more complexity needed to cope
with bookparts consisting of multiple scores?



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

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

Re: How to get \fromproperty to work with score headers?

[Malte Meyn]

Am 29.10.2017 um 11:21 schrieb Shevek:

Does anyone know if there's an updated version of
http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers?
It's listed as "to do" in the snippet, but I believe that dates back to
several years ago. I'd like to use \fromproperty #'header:piece to put
movement titles at the top of pages.


It looks like \fromproperty doesn’t take score-level headers into 
account. The following code shows “Toplevel silence” in all page 
headers. If you don’t define a toplevel piece header, nothing is shown.




\version "2.19.80"

% taken from titling-init.ly, replaced instrument by piece
\paper {
  oddHeaderMarkup =  \markup
  \fill-line {
""
\on-the-fly #not-part-first-page \fromproperty #'header:piece
\on-the-fly #print-page-number-check-first \fromproperty 
#'page:page-number-string

  }
  evenHeaderMarkup = \markup
  \fill-line {
\on-the-fly #print-page-number-check-first \fromproperty 
#'page:page-number-string

\on-the-fly #not-part-first-page \fromproperty #'header:piece
""
  }
}

\header {
  title = "Suite of silences"
  piece = "Toplevel silence"
}

\score { \header { piece = "Silence I"   } R1*100 }
\score { \header { piece = "Silence II"  } R1*100 }
\score { \header { piece = "Silence III" } R1*100 }
\score { \header { piece = "Silence IV"  } R1*100 }
\score { \header { piece = "Silence V"   } R1*100 }
\score { \header { piece = "Silence VI"  } R1*100 }



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

dead link in http://lilypond.org/doc/v2.18/Documentation/

[bb]

http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion
the link
Schnipsel: Percussion.
http://lilypond.org/doc/v2.18/Documentation/snippets/schlagzeug -> not
found
In the english version it's active
http://lilypond.org/doc/v2.18/Documentation/snippets/percussion

Regards

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

Re: dead link in http://lilypond.org/doc/v2.18/Documentation/

[Malte Meyn]

Am 29.10.2017 um 15:33 schrieb bb:

http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion
the link
Schnipsel: Percussion.
http://lilypond.org/doc/v2.18/Documentation/snippets/schlagzeug -> not
found
In the english version it's active
http://lilypond.org/doc/v2.18/Documentation/snippets/percussion


Forwarding to bug-lilypond. This bug report is about the German version 
of the documentation (“Schnipsel” = snippets) but it’s the same f. e. in 
Spanish.


Same for 2.19.
Same for other links to the snippets.

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

Small caps not working in bookTitleMarkup?

[Patrick Hubers]

Hi,

I'm trying to create titles in small caps by modifying the 
bookTitleMarkup in my stylesheet. For some reason, all font modifiers 
(\bold, \italic etc.) seem to work, except for \caps or \smallCaps.


I have the line

\bold \fontsize #6 { \fromproperty #'header:title }

in my stylesheet, which works great, but adding \caps is not working. 
However, if I put that modifier in my header block (title = \markup { 
\caps "My Title") I get perfect small caps in my output, while still 
seeing the effects of the \bold and \fontsize modifiers from my stylesheet.


Am I doing something wrong, have I missed something in the docs or did I 
encounter a bug?


Thanks for any assistance!

Regards, Patrick


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

Re: How to get \fromproperty to work with score headers?

[Graham King]

On Sun, 2017-10-29 at 03:21 -0700, Shevek wrote:

> Does anyone know if there's an updated version of
> http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers?
> It's listed as "to do" in the snippet, but I believe that dates back to
> several years ago. I'd like to use \fromproperty #'header:piece to put
> movement titles at the top of pages. 
> 
> If there isn't a newer version that supports this, I can mess around with
> trying to get it working, but I'd appreciated it if anyone can point me in
> the right direction to start; what would score-level headers be called? is
> the existing snippet structure adequate or is more complexity needed to cope
> with bookparts consisting of multiple scores?
> 

How about approaching the problem from another direction?  Would
something like this be OK?

\version "2.19.40"

htitle="Trahe me post te"
hcomposer="Victoria"

\header {
  title=\htitle
  composer=\hcomposer
}

{ c''1 \pageBreak 1 \pageBreak 1 }

\paper{
  evenHeaderMarkup=\markup  \fill-line {
\fromproperty #'page:page-number-string
\htitle \hcomposer
  }
  oddHeaderMarkup= \markup  \fill-line {
\on-the-fly #not-first-page \hcomposer
\on-the-fly #not-first-page \htitle 
\on-the-fly #not-first-page \fromproperty #'page:page-number-string
  }
}

With acknowledgments to Nacho Alvarez for the idea.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Small caps not working in bookTitleMarkup?

[Malte Meyn]

Am 29.10.2017 um 15:50 schrieb Patrick Hubers:

Hi,

I'm trying to create titles in small caps by modifying the 
bookTitleMarkup in my stylesheet. For some reason, all font modifiers 
(\bold, \italic etc.) seem to work, except for \caps or \smallCaps.


[…]

Am I doing something wrong, have I missed something in the docs or did I 
encounter a bug?


Could you please give a minimal example code?

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

Re: Small caps not working in bookTitleMarkup?

[Malte Meyn]

Am 29.10.2017 um 16:41 schrieb Malte Meyn:



Am 29.10.2017 um 15:50 schrieb Patrick Hubers:

Hi,

I'm trying to create titles in small caps by modifying the 
bookTitleMarkup in my stylesheet. For some reason, all font modifiers 
(\bold, \italic etc.) seem to work, except for \caps or \smallCaps.


[…]

Am I doing something wrong, have I missed something in the docs or did 
I encounter a bug?


Could you please give a minimal example code?


I just found out that this is a know bug: 
https://sourceforge.net/p/testlilyissues/issues/1482/ There you can also 
find a workaround.


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

Re: Small caps not working in bookTitleMarkup?

[Patrick Hubers]

Op 29-10-2017 om 16:41 schreef Malte Meyn:

Am 29.10.2017 um 15:50 schrieb Patrick Hubers:
I'm trying to create titles in small caps by modifying the 
bookTitleMarkup in my stylesheet. For some reason, all font modifiers 
(\bold, \italic etc.) seem to work, except for \caps or \smallCaps.



Could you please give a minimal example code?


Sure, I was already preparing one for follow up. Attached are a score 
"test.ly" and a stylesheet "test.ily" that's included from the score. 
Adding \caps (or \smallCaps) to the title in the score gives the desired 
output, adding it to the bookTitleMarkup does nothing.


Any insights appreciated!

Regards, Patrick

\version "2.19.32"

\include "test_stylesheet.ily"

\header {
  title = \markup \caps "These should be caps"
}

\score {
  \relative c' { c d e c }
}

\version "2.19.32"

\paper {

  bookTitleMarkup = \markup {
   \caps \bold \fromproperty #'header:title
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Small caps not working in bookTitleMarkup?

[Patrick Hubers]

Op 29-10-2017 om 16:48 schreef Malte Meyn:

[...]
I just found out that this is a know bug: 
https://sourceforge.net/p/testlilyissues/issues/1482/ There you can 
also find a workaround.

Ah, thanks for that!

I'll see if I can get it to work with the options mentioned there.

Regards, Patrick



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

Re: Small caps not working in bookTitleMarkup?

[Ben]

On 10/29/2017 12:09 PM, Patrick Hubers wrote:

Op 29-10-2017 om 16:48 schreef Malte Meyn:

[...]
I just found out that this is a know bug: 
https://sourceforge.net/p/testlilyissues/issues/1482/ There you can 
also find a workaround.

Ah, thanks for that!

I'll see if I can get it to work with the options mentioned there.

Regards, Patrick


Hi Patrick,

I believe if you use a font that has small caps it should work just 
fine. IIRC it's only an issue if the font itself doesn't have a smallcaps.


Good luck with the workaround!


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

Re: How to get \fromproperty to work with score headers?

[Graham King]

On Sun, 2017-10-29 at 15:30 +, Graham King wrote:

> On Sun, 2017-10-29 at 03:21 -0700, Shevek wrote: 
> 
> > Does anyone know if there's an updated version of
> > http://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level headers?
> > It's listed as "to do" in the snippet, but I believe that dates back to
> > several years ago. I'd like to use \fromproperty #'header:piece to put
> > movement titles at the top of pages. 
> > 
> > If there isn't a newer version that supports this, I can mess around with
> > trying to get it working, but I'd appreciated it if anyone can point me in
> > the right direction to start; what would score-level headers be called? is
> > the existing snippet structure adequate or is more complexity needed to cope
> > with bookparts consisting of multiple scores?
> > 
> 
> How about approaching the problem from another direction?  Would
> something like this be OK?
> 
> \version "2.19.40"
> 
> htitle="Trahe me post te"
> hcomposer="Victoria"
> 
> \header {
>   title=\htitle
>   composer=\hcomposer
> }
> 
> { c''1 \pageBreak 1 \pageBreak 1 }
> 
> \paper{
>   evenHeaderMarkup=\markup  \fill-line {
> \fromproperty #'page:page-number-string
> \htitle \hcomposer
>   }
>   oddHeaderMarkup= \markup  \fill-line {
> \on-the-fly #not-first-page \hcomposer
> \on-the-fly #not-first-page \htitle 
> \on-the-fly #not-first-page \fromproperty
> #'page:page-number-string
>   }
> }
> 
> With acknowledgments to Nacho Alvarez for the idea. 

I don't think this will work for "bookparts with multiple scores."  You
need a proper expert...
Apologies for the noise.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: dead link in http://lilypond.org/doc/v2.18/Documentation/

[Federico Bruni]

It's a known problem, already in the tracker


Il 29 ottobre 2017 15:46:47 CET, Malte Meyn  ha scritto:
>Am 29.10.2017 um 15:33 schrieb bb:
>>
>http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion
>> the link
>> Schnipsel: Percussion.
>> http://lilypond.org/doc/v2.18/Documentation/snippets/schlagzeug ->
>not
>> found
>> In the english version it's active
>> http://lilypond.org/doc/v2.18/Documentation/snippets/percussion
>
>Forwarding to bug-lilypond. This bug report is about the German version
>
>of the documentation (“Schnipsel” = snippets) but it’s the same f. e.
>in 
>Spanish.
>
>Same for 2.19.
>Same for other links to the snippets.
>
>___
>bug-lilypond mailing list
>bug-lilyp...@gnu.org
>https://lists.gnu.org/mailman/listinfo/bug-lilypond
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to get \fromproperty to work with score headers?

[Saul Tobin]

That's essentially what I've been doing, but it requires making each score
a bookpart unto itself. It's an okay solution, but it's nice to be able to
start a new movement mid-page.

Thanks anyway for the suggestion, though!

On Sun, Oct 29, 2017 at 9:21 AM, Graham King 
wrote:

> On Sun, 2017-10-29 at 15:30 +, Graham King wrote:
>
> On Sun, 2017-10-29 at 03:21 -0700, Shevek wrote:
>
> Does anyone know if there's an updated version 
> ofhttp://lsr.di.unimi.it/LSR/Snippet?id=467 to work with score-level 
> headers?It's listed as "to do" in the snippet, but I believe that dates back 
> toseveral years ago. I'd like to use \fromproperty #'header:piece to 
> putmovement titles at the top of pages.
> If there isn't a newer version that supports this, I can mess around 
> withtrying to get it working, but I'd appreciated it if anyone can point me 
> inthe right direction to start; what would score-level headers be called? 
> isthe existing snippet structure adequate or is more complexity needed to 
> copewith bookparts consisting of multiple scores?
>
> How about approaching the problem from another direction?  Would something
> like this be OK?
>
> \version "2.19.40"
>
> htitle="Trahe me post te"
> hcomposer="Victoria"
>
> \header {
>   title=\htitle
>   composer=\hcomposer
> }
>
> { c''1 \pageBreak 1 \pageBreak 1 }
>
> \paper{
>   evenHeaderMarkup=\markup  \fill-line {
> \fromproperty #'page:page-number-string
> \htitle \hcomposer
>   }
>   oddHeaderMarkup= \markup  \fill-line {
> \on-the-fly #not-first-page \hcomposer
> \on-the-fly #not-first-page \htitle
> \on-the-fly #not-first-page \fromproperty #'page:page-number-string
>   }
> }
>
> With acknowledgments to Nacho Alvarez for the idea.
>
> I don't think this will work for "bookparts with multiple scores."  You
> need a proper expert...
> Apologies for the noise.
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Cross-staff beam slope - can it be specified?

[David Sumbler]

On Sat, 2017-10-28 at 08:49 -0400, Ben wrote:
> On 10/27/2017 1:33 PM, David Sumbler wrote:
> > In the above rather silly example, the beam between the 2 cross-
> > staff
> > notes slopes slightly upwards.  If I add a dynamic, say \f , after
> >  > g>2. in line 7, the staves are forced further apart, and the beam
> > slopes slightly downwards.
> > 
> > If I now add a further dynamic, say ^\p , to the lower staff after
> >  > c>2. in line 9, the staves are forced still further apart and the
> > beam
> > now has a large downward slope.
> > 
> > The problem I have is that, in "real life", I don't know how far
> > apart
> > the staves will be because of the space requirements of other parts
> > of
> > the music.  Generally I would prefer to allow Lilypond to determine
> > where line ends etc. should be, so I don't even know which bits of
> > the
> > music will affect the slope of the beam.  And even if I did know,
> > an
> > alteration to the music in the closely preceding and following bars
> > might well affect the spacing of the staves and hence the slope of
> > the
> > beam.
> > 
> > Is there any way of ensuring that the beam always has a
> > predetermined
> > slope - say 10° downwards - and that the stem lengths will
> > automatically be adjusted to allow for this?
> > 
> > David
>  
> Hello,
> 
> Check out this older post here, it deals with cross beam slopes:
> http://lilypond.1069038.n5.nabble.com/Adjusting-beam-slope-with-cross
> -staff-notes-td140283.html
> 
> David Nalesnik wrote a function where instead of specifying the
> absolute values for positions, it allows you to indicate
> displacements from the values LilyPond would use by default.
> 
> It sounds like that's what you are looking for, does this help?

Thanks for your reply.  I have had a look at David's function, but it
doesn't seem to be suitable in this case.  It allows one to specify
vertical off-sets for the ends of a beam relative to the offsets
Lilypond would use by default.  But my problem is that those defaults
may change depending on spacing issues caused by changes in the music
in the few bars before or after the notes with the beam.

What I really need is some way of specifying the relative vertical
heights of the ends of the beam whilst leaving Lilypond to determine
the absolute vertical position.  If I had sufficient understanding of
the inner workings of Lilypond, I am sure that I could fairly easily
write the necessary Scheme code.  But I don't have that understanding,
so I shall have to make do with tweaking the beam position once the
rest of the music is absolutely finalized.

David

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

Re: non-triplet tuplets collide with staff

[Mason Hock]

Thanks for clarifying. My score only uses triplets for unbeamed notes, 
and I mistakenly misattributed the number and bracket placement to the 
ratio rather than the presence of beams. Next time I'll test with a 
simpler example like the one you include.


Your solution works well in 2.18.2. Thanks!

Mason

On Sun, Oct 29, 2017 at 2:03 AM, Thomas Morley 
 wrote:

Hi Mason,

please always state the version you use and a tiny example.
Maybe you would have spotted that

2017-10-28 23:38 GMT+02:00 Mason Hock :
 Lilypond by default seems to place all tuplet numbers/brackets so 
that they
 collide with the staff, with the exception of triplets, which it 
places

 outside the staff.


isn't true.

See
{
\cadenzaOn
\tuplet 2/1 { a4 a }
\tuplet 3/2 { a a a }
\tuplet 4/3 { a a a a }
\tuplet 5/4 { a a a a a }
\tuplet 6/5 { a a a a a a }
\tuplet 7/6 { a a a a a a a }
}
and
{
\tuplet 2/1 { a8 a }
\tuplet 3/2 { a a a }
\tuplet 4/3 { a a a a }
\tuplet 5/4 { a a a a a }
\tuplet 6/5 { a a a a a a }
\tuplet 7/6 { a a a a a a a }
}
Where the TupletBracket is printed depends on whether a Beam is
present or not, presence of other maybe colliding objects etc.
Has nothing to do if being a triplet or anything else.
Btw, what you call collisions is common practice in printed editions.


 I would like all tuplets outside of the staff like
 triplets.



 If I do both

 \override Staff.TupletNumber #'outside-staff-priority = #1
 \override Staff.TupletBracket #'outside-staff-priority = #1

 I get an error: "warning: Cannot set outside-staff-priority for 
element and

 elements' Y parent."



I agree it would be better to set outside-staff-priority for both,
Number and Bracket, and let LilyPond sort it out.
Alas, it doesn't work. You may write a feature-request to the 
bug-list.


For now you could do:

\override TupletBracket.after-line-breaking =
  #(lambda (grob)
(ly:grob-set-property!
  (if (and (ly:stencil-empty? (ly:grob-property grob 
'stencil))

   (ly:grob? (ly:grob-object grob 'tuplet-number)))
  (ly:grob-object grob 'tuplet-number)
  grob)
  'outside-staff-priority
  100))

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

order of events given to engravers

[Maurits Lamers]

Hi all,

I came across something peculiar in the order in which events are sent out to 
the engravers.
Assuming I have listeners on notes, rests and breaks, it turns out that a break 
event in special cases can be sent after other events on the same moment.
So, my question is: when a break happens at the same moment at which other 
events takes place, can I assume the break should always be handled first?

cheers

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

Re: order of events given to engravers

[David Kastrup]

Maurits Lamers  writes:

> Hi all,
>
> I came across something peculiar in the order in which events are sent
> out to the engravers.
> Assuming I have listeners on notes, rests and breaks, it turns out
> that a break event in special cases can be sent after other events on
> the same moment.
> So, my question is: when a break happens at the same moment at which
> other events takes place, can I assume the break should always be
> handled first?

No.  Listeners should just collect the events they are interested in,
and the actual processing should happen in process-music.  The order in
which listeners see events at the same time step is not defined.

-- 
David Kastrup

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

slurs between pairs of notes horizontally close and vertically distant

[Mason Hock]

I'm working on a score with many pairs of notes a sixth or seventh 
apart slurred together. When the stem of the second note of a pair is 
down, the slur intersects the accidental. If I increase 
'Slur.details.accidental-collision' the slur avoids the accidental, but 
is not as well-shaped. For most pairs Lilypond acheives a good 
compromise, but sometimes the slur is quite distant from the notes and 
the endpoints of the slur are close to the same height, making it 
unclear that the curve represents a slur between the two pitches.


It seems that the bad slurs occur when there is not a lot of horizontal 
space between the two notes. In the example below, the slur between the 
half notes in the second bar looks much better than the slur between 
the same two pitches as eighth notes in the first bar. Even the third 
and fourth slurs look much better than the first and second because the 
accidentals add just a tiny bit more horizontal space.


From reading this 
 
it sounds like slurs are very difficult to shape well automatically. 
It's impressive that Lilypond does this well before manual tweaking. 
However, this issue occurs so many times in this score that it would 
take way too long for me to fix each one manually with \shape.


Since Lilypond really only seems to have trouble when the notes are 
very close to each other horizontally, perhaps a way to fix the slurs 
globally would be to set a minimum horizontal space between notes. 
However, Lilypond's horizontal spacing is not the issue and I'd rather 
not override something that it is doing well. Also, I expect that the 
horizontal space needed to fix the slur depends on the vertical 
distance and stem direction of the first note


I would prefer a solution that only affects the slurs. Perhaps the 
issue would be fixed by allowing greater curvature for slurs. For 
example, if the first slur began close to the staff, looped all the way 
around the flat, then came back down and ended close to the second 
notehead, it would look a little odd but would be a large improvement. 
Some of the more adequate slurs might also be improved by this, and I 
don't see any that it would break. I would have no idea how to 
implement this though.


Does anyone have any suggestions?

Thanks,

Mason

%

\version "2.18.2"
\language "english"

% slurs are shaped well but intersect accidentals
\relative c' {
 \accidentalStyle neo-modern
 c'8( af') cqs,( aqf') cs,( a') ctqs,( aqs') |  c,2( af') |
 \tuplet 3/2 {f,4( e') fqs,(} \tuplet 3/2 {eqs') gf,( f')} |
 g,( ef') gqs,8( eqf') gs,( e') |
}

% slurs avoid accidentals but are not well-shaped
\relative c' {
 \accidentalStyle neo-modern
 \override Slur.details.accidental-collision = #30
 c'8( af') cqs,( aqf') cs,( a') ctqs,( aqs') |  c,2( af') |
 \tuplet 3/2 {f,4( e') fqs,(} \tuplet 3/2 {eqs') gf,( f')} |
 g,( ef') gqs,8( eqf') gs,( e') |
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Footnotes

[Dave Hartley]

I'm currently typesetting some music for our school choir, SATB with a
piano part and a small percussion part. I *tried* to get some additional
directions to the performers inserted as footnotes, but I don't seem to be
able to get the footnotes in *\markup attached to notes* working at all.

MWE:
%%
\version "2.18.2"
\markup { The \auto-footnote footnote "Here it is" works here. }
{c '^\markup { I want a \auto-footnote footnote "Does this work?" here } }
%%

The annoying thing is that it is *almost* working, as there is a gap left
for the footnote marker, but both it and the actual footnote are just not
there.

Reading the manual (
http://lilypond.org/doc/v2.18/Documentation/notation/creating-footnotes) I
can see that only musical expressions (which attached markup is definitely
not) and stand-alone text (again, attached markup isn't that either).

My question: is there any way to place a footnote at the bottom of a page
from markup attached to a note? I've "made do" with using simple markup to
give the performance instructions, but I'd like to be able to do this sort
of thing in the future. Any guidance would be most appreciated.

-- 
Stop the Madness.  Boycott Word attachments.

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

Re: Footnotes

[Ben]

On 10/29/2017 5:41 PM, Dave Hartley wrote:
I'm currently typesetting some music for our school choir, SATB with a 
piano part and a small percussion part. I /tried/ to get some 
additional directions to the performers inserted as footnotes, but I 
don't seem to be able to get the footnotes in *\markup attached to 
notes* working at all.


MWE:
%%
\version "2.18.2"
\markup { The \auto-footnote footnote "Here it is" works here. }
{c '^\markup { I want a \auto-footnote footnote "Does this work?" here } }
%%

The annoying thing is that it is /almost/ working, as there is a gap 
left for the footnote marker, but both it and the actual footnote are 
just not there.


Reading the manual 
(http://lilypond.org/doc/v2.18/Documentation/notation/creating-footnotes) 
I can see that only musical expressions (which attached markup is 
definitely not) and stand-alone text (again, attached markup isn't 
that either).


My question: is there any way to place a footnote at the bottom of a 
page from markup attached to a note? I've "made do" with using simple 
markup to give the performance instructions, but I'd like to be able 
to do this sort of thing in the future. Any guidance would be most 
appreciated.




Hello,

Maybe these links could help you?

http://lilypond.1069038.n5.nabble.com/footnotes-should-work-on-markup-attached-to-a-note-td169259.html
http://lilypond.1069038.n5.nabble.com/footnotes-in-markup-attached-to-notes-not-working-td169260.html

IIRC auto-footnote is really only used for markup outside of music 
expressions etc.


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

Re: Footnotes

[Ben]

On 10/29/2017 5:41 PM, Dave Hartley wrote:
I'm currently typesetting some music for our school choir, SATB with a 
piano part and a small percussion part. I /tried/ to get some 
additional directions to the performers inserted as footnotes, but I 
don't seem to be able to get the footnotes in *\markup attached to 
notes* working at all.


MWE:
%%
\version "2.18.2"
\markup { The \auto-footnote footnote "Here it is" works here. }
{c '^\markup { I want a \auto-footnote footnote "Does this work?" here } }
%%

The annoying thing is that it is /almost/ working, as there is a gap 
left for the footnote marker, but both it and the actual footnote are 
just not there.


Reading the manual 
(http://lilypond.org/doc/v2.18/Documentation/notation/creating-footnotes) 
I can see that only musical expressions (which attached markup is 
definitely not) and stand-alone text (again, attached markup isn't 
that either).




On 10/29/2017 5:41 PM, Dave Hartley wrote:
I'm currently typesetting some music for our school choir, SATB with a 
piano part and a small percussion part. I /tried/ to get some 
additional directions to the performers inserted as footnotes, but I 
don't seem to be able to get the footnotes in *\markup attached to 
notes* working at all.


MWE:
%%
\version "2.18.2"
\markup { The \auto-footnote footnote "Here it is" works here. }
{c '^\markup { I want a \auto-footnote footnote "Does this work?" here } }
%%

The annoying thing is that it is /almost/ working, as there is a gap 
left for the footnote marker, but both it and the actual footnote are 
just not there.


Reading the manual 
(http://lilypond.org/doc/v2.18/Documentation/notation/creating-footnotes) 
I can see that only musical expressions (which attached markup is 
definitely not) and stand-alone text (again, attached markup isn't 
that either).


My question: is there any way to place a footnote at the bottom of a 
page from markup attached to a note? I've "made do" with using simple 
markup to give the performance instructions, but I'd like to be able 
to do this sort of thing in the future. Any guidance would be most 
appreciated.




Something like this?
(see attached)


\version "2.19.80"
\relative c''\footnote #'(1 . 2) "Here is your footnote" a

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

Re: Footnotes

[Dave Hartley]

On 10/29/2017 5:41 PM, Dave Hartley wrote:

I'm currently typesetting some music for our school choir, SATB with a
piano part and a small percussion part. I *tried* to get some additional
directions to the performers inserted as footnotes, but I don't seem to be
able to get the footnotes in *\markup attached to notes* working at all.

MWE:
%%
\version "2.18.2"
\markup { The \auto-footnote footnote "Here it is" works here. }
{c '^\markup { I want a \auto-footnote footnote "Does this work?" here } }
%%

The annoying thing is that it is *almost* working, as there is a gap left
for the footnote marker, but both it and the actual footnote are just not
there.

Reading the manual (http://lilypond.org/doc/v2.18/Documentation/notation/
creating-footnotes) I can see that only musical expressions (which attached
markup is definitely not) and stand-alone text (again, attached markup
isn't that either).

My question: is there any way to place a footnote at the bottom of a page
from markup attached to a note? I've "made do" with using simple markup to
give the performance instructions, but I'd like to be able to do this sort
of thing in the future. Any guidance would be most appreciated.

On 30 October 2017 at 12:26, Ben  wrote:

> Maybe these links could help you?
>
> http://lilypond.1069038.n5.nabble.com/footnotes-should-
> work-on-markup-attached-to-a-note-td169259.html
> http://lilypond.1069038.n5.nabble.com/footnotes-in-
> markup-attached-to-notes-not-working-td169260.html
>
> IIRC auto-footnote is really only used for markup outside of music
> expressions etc.
>

Thanks Ben, those links confirm what I already suspected, that footnotes in
markup attached to notes do not work.


On 30 October 2017 at 12:33, Ben  wrote:

> Something like this?
> (see attached)
>
\version "2.19.80"
> \relative c''\footnote #'(1 . 2) "Here is your footnote" a


Not really, I want to be able to supply some performance hints to the
markup *without* having that line from the note.

I have exactly the same issue using the manual \footnote form:


\version "2.18.2"
\markup { The footnote \footnote "*" "* Here it is" works here. }
{c '^\markup { I want a footnote \footnote \super + "+ Does this work?"
here } }


So my question now is: is there *some* way to place markup at the bottom of
the current page? That is, can I "fake" a footnote by putting the footnote
mark in the markup attached to the note, and simply place the footnote
manually at the bottom of the page?

Cheers

Dave


-- 
Stop the Madness.  Boycott Word attachments.

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

Re: Footnotes

[Malte Meyn]

Am 30.10.2017 um 07:21 schrieb Dave Hartley:



On 30 October 2017 at 12:33, Ben > wrote:


Something like this?
(see attached)

\version "2.19.80"
\relative c''\footnote #'(1 . 2) "Here is your footnote" a 



Not really, I want to be able to supply some performance hints to the 
markup /without/ having that line from the note.




How about this?

\version "2.19.80"

{
  \override Score.FootnoteItem.annotation-line = ##f
  \footnote #'(1 . 2) "Here is your footnote"
  a'
}

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