Re: Laissez viber ties dotted

[Malte Meyn]

Am 21.07.2016 um 03:14 schrieb Andrew Bernard:

How can one make a laissez vibrer tie dotted or dashed, as can be done for
a normal tie? Using \tieDotted has no effect.


This is because \tieDotted is a shorthand for
  \override Tie.dash-pattern = #'((0 1 0.1 0.75))
and laissez vibrer ties are not Tie grobs but LaissezVibrerTie grobs. 
There is no shorthand laissezVibrerTieDotted but you can use this 
override or create such a shorthand.


%%

\version "2.19.44"

{
  \override LaissezVibrerTie.dash-definition = #'((0 1 0.1 0.75))
  b\laissezVibrer
}

laissezVibrerTieDotted = \override LaissezVibrerTie.dash-definition = 
#'((0 1 0.1 0.75))


{
  \laissezVibrerTieDotted
  b\laissezVibrer
}

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

Re: \caps with Umlaut

[Shane Brandes]

While I use Frescobaldi, I was speaking as someone that has built a
few score of fonts for sale, knowing there is often a larger gap
between what is possible and what was likely done.

On Wed, Jul 20, 2016 at 7:06 PM, Mark Stephen Mrotek
 wrote:
> Shane,
>
> If you are using Frescobaldi, you could not use \caps and access the special 
> characters.
>
> Mark
>
> -Original Message-
> From: lilypond-user 
> [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
> Shane Brandes
> Sent: Wednesday, July 20, 2016 2:53 PM
> To: Jonathan Scholbach 
> Cc: LilyPond User Group 
> Subject: Re: \caps with Umlaut
>
> Small caps are a subset of a font, it is pretty rare to have small caps 
> worked out beyond the standard 26. This because they did not exist in Unicode 
> as a defined glyph. Unicode is still only has 24 small caps defined. Your 
> best bet is to try the Bold smaller size trick and see if that works.
>
> Shane Brandes
>
> On Wed, Jul 20, 2016 at 5:01 PM, Jonathan Scholbach  
> wrote:
>> Dear ponders,
>>
>> I am using \caps in a \markup which prints the name of the composer.
>> After having set a couple of pieces today it's the first time the
>> composer's name contains an umlaut (in this case an ä). And that was
>> when I found out, that \caps, as well as \smallCaps, "does not support
>> accented character" (quoted from
>> http://lilypond.org/doc/v2.19/Documentation/notation/font) - the ä -
>> is printed as a lowercase letter.
>>
>> The ME is:
>>
>> \version "2.19.22"
>>
>> \markup{ \caps Bartholomäus }
>>
>> How can I solve this problem? I mean, how can I achieve that \caps
>> works properly with umlauts and uses the uppercase umlaut?
>>
>> Your advice is very much appreciated,
>>
>> Jonathan
>>
>>
>>
>> ___
>> 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
>

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

Re: Slur over single note?

[Joel C. Salomon]

On 2016-07-20 3:48 AM, Urs Liska wrote:
> If I'm not mistaken this is a piano reduction?
> If that's the case i'd assume there's a tied note or two slurred ones in
> an instrumental part here.
> 
> I see two options here, depending on what you want with this score:
> 
> 1 (the scholarly approach):
> Get hold of the full score and see if there's a part that warrants the
> slur/tie. If you find somethign adjust the thing accordingly.


There may have been a full score somewhere, but WorldCat doesn’t
indicate that any libraries have it.  (At
 there’s a record of an
orchestrated “Selection from … Peter Pan”, but note “selection from” and
also the orchestration is by Fred Adlington not John Crook.)

Perhaps the Duke of York’s Theatre has in its archives a complete score,
and I am trying to find someone there whom I might ask about this.
(Amazingly enough, their web presence seems entirely dedicated to
selling people tickets to current performances and does not have their
archivist’s contact information prominently displayed.  It’s almost as
if my request is somehow an unusual one… ;) )

—Joel C. Salomon

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

Hyphenating words in lyrics across long repeats and across multiple pitches

[Mojca Miklavec]

Hello,

When I try to start a syllable that continues after the repeat, I have
a problem.

Lilypond complains loudly:
repeats.ly:24:38: warning: unterminated hyphen; removing

Below an example that should read
   Oh, tralalala! Tralalali!

(Of course the hyphen would "kind of" work if I add "li!" at the end –
it would pretend as if the word was "Tra -- li" and would place the
hyphen to the wrong place.)

What's the best recipe to fix such cases?

\new PianoStaff <<
  \new Voice = "melody" \fixed c' {
\time 2/4
a2 | a2 |
\repeat volta 2 {
  a4 a4 |
}
\alternative {
  { a4 a4 |}
  { a2 | }
}
\bar "|."
  }
  % the last hyphen after 'Tra" is problematic and gets removed
  \context Lyrics = "lyrics" {
\lyricsto "melody" {
  Oh, tra -- la -- la -- la! Tra --
  % li!
}
  }
>>

Another problem are cases which I would intuitively write
tra -- _ -- la

where the first syllable "tra" would be sung across two pitches. But
if I do the above, the hyphen gets lost and I get "trala" that
looks as if I had two words rather than "tra  -  la" (I can add a full
example if the question is not clear).

Is there any way to get the hyphen back (other than adding an explicit
slur)? If I just add a slur, it would not always work because
different stanzas might be different.

Thank you,
Mojca


repeats.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to create a thick horizontal line (as its own staff)?

[Mojca Miklavec]

Dear David,

On 20 July 2016 at 22:49, David Nalesnik wrote:
> On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec wrote:
>>
>> One further thought.
>>
>> Given that it's super difficult to "transfer" information "across staves" ...
>>
>> Would it be feasible to allow the following input syntax (or something 
>> similar)?
>>
>> melody = { c a c \startPush f g a \stopPush h c d }
>> \new PianoStaff <<
>> \new Voice = "melody" \fixed c' {
>>   \melody
>>}
>>\new Dynamics \with {
>>  \override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = 1
>>} {
>>  \melody
>>}
>> >>
>>
>
> With the example I gave above, this would work fine.  The horizontal
> line engraver is only consisted to the Dynamics context, so the
> push/pull events will only produce a line there.  Conversely, the
> Dynamics context won't typeset the notes.

Nice.

> You will run into problems with this approach if you add dynamics to
> your melody, however, since they will of course appear in the Dynamics
> context.
>
> The best solution would be to define your own context.  (Instructions
> for doing this are found here:
> http://lilypond.org/doc/v2.19/Documentation/notation/defining-new-contexts)

Thank you. I skimmed over that text, but had no idea what I could use
it for earlier.

> I've gone ahead and defined an "AccordionPushPull" context which
> modifies the definition of a Dynamics context (definition found in
> engraver-init.ly in the source) to include the horizontal line
> engraver and nothing else.  So you can safely include your melody
> variable and not need to worry about extraneous elements being
> typeset.

Wonderful!
This is s much more elegant than typing it twice. It seems to work
with all the examples I have so far.

> P.S. I've attached two files, showing how you can cut down on the
> clutter in your input file by using an include.

Thank you. I already added the majority in one file, but wasn't sure
about layout / context part. Being able to remove also that makes me
even more happy :)

> Just to demonstrate how you could make an engraver to create different
> behavior, I wrote one to color note heads red.
>
> Add this definition to accordion.ily:
>
> accordionRedPushEngraver =
> #(lambda (context)
>(let ((push? #f))
>  (make-engraver
>   (listeners ((accordion-push-span-event engraver event)
>   (if (= START (ly:event-property event 'span-direction))
>   (set! push? #t)
>   (set! push? #f
>   (acknowledgers
>((note-head-interface engraver grob source-engraver)
> (if push?
> (set! (ly:grob-property grob 'color) red)))
>
> Then add the engraver in example.ly like this:
>
> \new PianoStaff <<
>   \new Staff <<
> \new Voice = "melody" \with { \consists \accordionRedPushEngraver } {
>   \melody
> }

Cool!

That's another very strong reason for wanting to encode the
information just once.
(Not that I would be able to come up with such a definition myself. :)

... Time to head for the next challenge.

Thanks again,
Mojca

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

Laissez viber ties dotted

[Andrew Bernard]

How can one make a laissez vibrer tie dotted or dashed, as can be done for
a normal tie? Using \tieDotted has no effect.

I use the \extendLV functions from LSR to make long ones, and often need to
have these extended ties dotted.

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

Re: Lilypond Internals Reference LyricText font-size

[Carl Sorensen]

On 7/20/16 11:29 AM, "Colin Tennyson"  wrote:

>About this documentation:
>http://lilypond.org/doc/v2.18/Documentation/internals/lyrictext
>
>
> font-size (number):
>
>1.0
>
>The font size, compared to the Œnormal¹ size. 0 is style-sheet¹s normal
>size, -1 is smaller, +1 is bigger. Each step of 1 is approximately 12%
>larger; 6 steps are exactly a factor 2 larger. Fractional values are
>allowed.

0 is the normal size for all fonts in a style-sheet.

1 is the default font-size for LyricText.

This means that LyricText is 12% larger than the default font size in the
style sheet.

That is, the font size you get by default in LyricText is exactly the same
font size you would get if you did

\override LyricText.font-size = 1.


The reason this is somewhat confusing is because it is automatically
generated, and there are a number of different grobs that use the
font-interface and therefore have a font-size property.  For example,
NoteName grobs have a font-size property, but their default font-size is
0, so it's not listed (because it is the style-sheet default).  Same with
TextScript grobs.

HTH,

Carl


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

RE: \caps with Umlaut

[Mark Stephen Mrotek]

Shane,

If you are using Frescobaldi, you could not use \caps and access the special 
characters.

Mark

-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Shane Brandes
Sent: Wednesday, July 20, 2016 2:53 PM
To: Jonathan Scholbach 
Cc: LilyPond User Group 
Subject: Re: \caps with Umlaut

Small caps are a subset of a font, it is pretty rare to have small caps worked 
out beyond the standard 26. This because they did not exist in Unicode as a 
defined glyph. Unicode is still only has 24 small caps defined. Your best bet 
is to try the Bold smaller size trick and see if that works.

Shane Brandes

On Wed, Jul 20, 2016 at 5:01 PM, Jonathan Scholbach  
wrote:
> Dear ponders,
>
> I am using \caps in a \markup which prints the name of the composer.
> After having set a couple of pieces today it's the first time the 
> composer's name contains an umlaut (in this case an ä). And that was 
> when I found out, that \caps, as well as \smallCaps, "does not support 
> accented character" (quoted from
> http://lilypond.org/doc/v2.19/Documentation/notation/font) - the ä - 
> is printed as a lowercase letter.
>
> The ME is:
>
> \version "2.19.22"
>
> \markup{ \caps Bartholomäus }
>
> How can I solve this problem? I mean, how can I achieve that \caps 
> works properly with umlauts and uses the uppercase umlaut?
>
> Your advice is very much appreciated,
>
> Jonathan
>
>
>
> ___
> 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


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

Re: \caps with Umlaut

[Simon Albrecht]

On 20.07.2016 23:01, Jonathan Scholbach wrote:

\version "2.19.22"

\markup{ \caps Bartholomäus }

How can I solve this problem? I mean, how can I achieve that \caps works
properly with umlauts and uses the uppercase umlaut?


In the long run, your best bet is to use a special small caps font. 
Unfortunately, it’s not easy to find a good, free text font with 
matching small caps… Personally, I like Alegreya, but I know it’s quite 
unusual.


Best, Simon

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

Re: \caps with Umlaut

[Shane Brandes]

Small caps are a subset of a font, it is pretty rare to have small
caps worked out beyond the standard 26. This because they did not
exist in Unicode as a defined glyph. Unicode is still only has 24
small caps defined. Your best bet is to try the Bold smaller size
trick and see if that works.

Shane Brandes

On Wed, Jul 20, 2016 at 5:01 PM, Jonathan Scholbach
 wrote:
> Dear ponders,
>
> I am using \caps in a \markup which prints the name of the composer.
> After having set a couple of pieces today it's the first time the
> composer's name contains an umlaut (in this case an ä). And that was
> when I found out, that \caps, as well as \smallCaps, "does not support
> accented character" (quoted from
> http://lilypond.org/doc/v2.19/Documentation/notation/font) - the ä - is
> printed as a lowercase letter.
>
> The ME is:
>
> \version "2.19.22"
>
> \markup{ \caps Bartholomäus }
>
> How can I solve this problem? I mean, how can I achieve that \caps works
> properly with umlauts and uses the uppercase umlaut?
>
> Your advice is very much appreciated,
>
> Jonathan
>
>
>
> ___
> 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: How to create a thick horizontal line (as its own staff)?

[David Nalesnik]

On Wed, Jul 20, 2016 at 3:49 PM, David Nalesnik
 wrote:

>
> On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec
>  wrote:

>>
>> I would be super happy if there was a way to enter the input
>> information only once because repeating it twice is calling for
>> errors. But also because \startPush and \stopPush could then do
>> different things inside the main melody.
>>
>> The "\new Voice" could ignore the \startPush/\stopPush directives (or
>> do something special with them) and "\new Dynamics" could ignore
>> typesetting the actual musical notes. I don't know how much tweaking
>> of LilyPond internals would be needed to achieve that though.
>
> In this case, I believe you'd need to write another engraver.  It
> would listen for the push and pull events and do something different,
> like create the downbows or color notes.  No problem at all.

Just to demonstrate how you could make an engraver to create different
behavior, I wrote one to color note heads red.

Add this definition to accordion.ily:

accordionRedPushEngraver =
#(lambda (context)
   (let ((push? #f))
 (make-engraver
  (listeners ((accordion-push-span-event engraver event)
  (if (= START (ly:event-property event 'span-direction))
  (set! push? #t)
  (set! push? #f
  (acknowledgers
   ((note-head-interface engraver grob source-engraver)
(if push?
(set! (ly:grob-property grob 'color) red)))

Then add the engraver in example.ly like this:

\new PianoStaff <<
  \new Staff <<
\new Voice = "melody" \with { \consists \accordionRedPushEngraver } {
  \melody
}

[snip]


Adding Scripts (downbows) looks a bit harder, but I suppose it could be done.

David N

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

\caps with Umlaut

[Jonathan Scholbach]

Dear ponders,

I am using \caps in a \markup which prints the name of the composer.
After having set a couple of pieces today it's the first time the
composer's name contains an umlaut (in this case an ä). And that was
when I found out, that \caps, as well as \smallCaps, "does not support
accented character" (quoted from
http://lilypond.org/doc/v2.19/Documentation/notation/font) - the ä - is
printed as a lowercase letter.

The ME is:

\version "2.19.22"

\markup{ \caps Bartholomäus }

How can I solve this problem? I mean, how can I achieve that \caps works
properly with umlauts and uses the uppercase umlaut?

Your advice is very much appreciated,

Jonathan



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

Re: How to create a thick horizontal line (as its own staff)?

[David Nalesnik]

Hi Mojca,

On Wed, Jul 20, 2016 at 10:05 AM, Mojca Miklavec
 wrote:
> Dear David (and others),
>
> One further thought.
>
> Given that it's super difficult to "transfer" information "across staves" ...
>
> Would it be feasible to allow the following input syntax (or something 
> similar)?
>
> melody = { c a c \startPush f g a \stopPush h c d }
> \new PianoStaff <<
> \new Voice = "melody" \fixed c' {
>   \melody
>}
>\new Dynamics \with {
>  \override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = 1
>} {
>  \melody
>}
> >>
>

With the example I gave above, this would work fine.  The horizontal
line engraver is only consisted to the Dynamics context, so the
push/pull events will only produce a line there.  Conversely, the
Dynamics context won't typeset the notes.

You will run into problems with this approach if you add dynamics to
your melody, however, since they will of course appear in the Dynamics
context.

The best solution would be to define your own context.  (Instructions
for doing this are found here:
http://lilypond.org/doc/v2.19/Documentation/notation/defining-new-contexts)

I've gone ahead and defined an "AccordionPushPull" context which
modifies the definition of a Dynamics context (definition found in
engraver-init.ly in the source) to include the horizontal line
engraver and nothing else.  So you can safely include your melody
variable and not need to worry about extraneous elements being
typeset.


> There are modes like "\new RhythmicStaff" that discard half of the
> information about the scores.
>
> I would be super happy if there was a way to enter the input
> information only once because repeating it twice is calling for
> errors. But also because \startPush and \stopPush could then do
> different things inside the main melody.
>
> The "\new Voice" could ignore the \startPush/\stopPush directives (or
> do something special with them) and "\new Dynamics" could ignore
> typesetting the actual musical notes. I don't know how much tweaking
> of LilyPond internals would be needed to achieve that though.

In this case, I believe you'd need to write another engraver.  It
would listen for the push and pull events and do something different,
like create the downbows or color notes.  No problem at all.

Hope this helps--

David N

P.S. I've attached two files, showing how you can cut down on the
clutter in your input file by using an include.

%


accordion.ily
Description: Binary data
\version "2.19.30"

\include "accordion.ily"

global = {
  \time 2/4
  \key f \major
}

melody = {
  \global
  \partial 4 c'8 c'
  c'8 c'4 c'8~
  c'8 c'4 d'8~
  d'4 e'8 e'~
  e'8 f'4.~
  f'2~
  f'8 a a a
  a8 bes c' \startPush c'~
  \break
  c'8 d'4.~
  d'2~
  d'8 c' c' c'
  c'8 bes a \startPull g~
  g2~
  g2~
  g8 c' s4
}

\new PianoStaff <<
  \new Staff <<
\new Voice = "melody" {
  \melody
}

\new Lyrics \lyricsto "melody" {
  \repeat unfold 50 { "foo" }
}
  >>

  \new AccordionPushPull \with {
\override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = 1
  } {
\melody
  }

  \new Staff = "staff" <<
\new Voice = "bass" {
  \clef bass
  \global
  r4
  R2*3
  \repeat unfold 7 { d,8  }
  c,8 
  \repeat unfold 3 { bes,,8  f,  }
  bes,8  f, 
  \repeat unfold 2 { c,8  g,  }
  c,8  c, d,
}
\new Lyrics \with {
  alignAboveContext = "staff"
}
\lyricmode {
  \skip 4
  \skip 2*3
  "9"8 "8" "9" "8"
  "9" "8" "9" "8"
  "9" "8" "9" "8"
  "9" "8" "4" "1"
  "6" "5" "4" "5"
  "6" "5" "4" "5"
  "6" "5" "4" "3"
  "4" "3" "2" "3"
  "4" "3" "2" "3"
  "4" "3" "4" "9"
  "7" "6" "7" "9"
}
  >>
>>

\layout {
  ragged-last = ##t
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Lilypond Internals Reference LyricText font-size

[Colin Tennyson]

About this documentation:
http://lilypond.org/doc/v2.18/Documentation/internals/lyrictext


 font-size (number):

1.0

The font size, compared to the ‘normal’ size. 0 is style-sheet’s normal
size, -1 is smaller, +1 is bigger. Each step of 1 is approximately 12%
larger; 6 steps are exactly a factor 2 larger. Fractional values are
allowed.


So:
The steps are the sixth root of 2. For abbreviation I will refer to that
root as 1.1225

the description refers to "style-sheet's normal size"
I checked this page:
http://lilypond.org/doc/v2.18/Documentation/learning/style-sheets
The word 'normal' does not occur on that page.

In another thread forum contributor tisimst mentioned there is a
"add-pango-fonts function in scm/font.scm"
that is used by Lilypond to determine a normal size given a particular staff
size. 

Documentation request: 
Explicit documentation of "style-sheet's normal size"




About the default value:
The default is 1.0, not 0

Now, the number that is entered for the font size adjustment is an exponent.
2.5 steps larger says: multiply the current font size with 1.1225 to the
power of 2.5

What I expect is that a step of zero is neutral; any number to the power 0
is 1, multiplying by 1 is neutral.

In other words, I expect that the step number that is entered will be
_added_ to whatever the default is (that way the user doesn't have to know
what that default is).

But instead the default step size (here 1.0) is _replaced_ with the entered
number.
If you enter 0, the lyric font size will become 1.225 smaller, which is
counter-intuitive.

Documentation request:
Description of this behavior.


Colin Tennyson





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Lilypond-Internals-Reference-LyricText-font-size-tp192882.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Lyrics.LyricText.font-size in layout block

[Colin Tennyson]

Hello tisimst, hello Noeck,

thank you for your replies.

You have explained to me why a very small number, -0.2, has such a noticable
effect.
I infer that Lilypond _replaces_ the step value for the LyricText font-size
with the entered step number (rather than performing an addition.)

So when I entered -0.2 the actual change was from 1.0 to -0.2, which is of
course a noticable change.


For completeness (and because David Kastrup insisted a minimal example
should always be provided) I created a minimal example 
I took a measure of Choir from the snippet repository, and I added a paper
block with one line in it, and a layout block with one line in it

Steps to repeat:
Try it with various values for the override: -1, 0, 1


+++

\version "2.18.2"
\language "english"

global = {
  \key c \major
  \time 4/4
  \dynamicUp
}
sopranonotes = \relative c'' {
  c2 d c d 
}
sopranowords = \lyricmode { do do do do }
altonotes = \relative c'' {
  c2 d c d
}
altowords = \lyricmode { re re re re }
tenornotes = {
  \clef "G_8"
  c2 d c d
}
tenorwords = \lyricmode { mi mi mi mi }
bassnotes = {
  \clef bass
  c2 d c d
}
basswords = \lyricmode { mi mi mi mi }


\paper {
  #(layout-set-staff-size 22)
}


\score {
  \new ChoirStaff <<
\new Staff <<
  \new Voice = "soprano" <<
\global
\sopranonotes
  >>
  \new Lyrics \lyricsto "soprano" \sopranowords
>>
\new Staff <<
  \new Voice = "alto" <<
\global
\altonotes
  >>
  \new Lyrics \lyricsto "alto" \altowords
>>
\new Staff <<
  \new Voice = "tenor" <<
\global
\tenornotes
  >>
  \new Lyrics \lyricsto "tenor" \tenorwords
>>
\new Staff <<
  \new Voice = "bass" <<
\global
\bassnotes
  >>
  \new Lyrics \lyricsto "bass" \basswords
>>
  >>
  \layout { \override Lyrics.LyricText.font-size = #-1 }
}




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Lyrics-LyricText-font-size-in-layout-block-tp192840p192881.html
Sent from the User mailing list archive at Nabble.com.

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

Re: Lyrics.LyricText.font-size in layout block

[tisimst]

On Wed, Jul 20, 2016 at 12:34 AM, Noeck [via Lilypond] <
ml-node+s1069038n192857...@n5.nabble.com> wrote:

> Hi Abraham,
>
> Am 20.07.2016 um 01:05 schrieb tisimst:
> > Shouldn't it be without the -1 though?
>
> In general, yes. The default is 1.0, so I wrote it for this case of
> lycris. If you enter font-size=1.0 in this formula, you get a factor of
> 1.0 (with respect to the default lyrics font size). With the general
> formula factor = 2^(font-size/6) you get a factor of 2^(1/6) with
> respect to the normal font-size 0 (12% larger). So it depends what you
> mean by the factor.
>

I thought of that after I sent my message, but thanks for clarifying your
formula.

--
Abraham Lee




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Lyrics-LyricText-font-size-in-layout-block-tp192840p192878.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Simultaneous accidental breaks cross-staff stem

[Joel C. Salomon]

On 2016-07-20 1:56 AM, Malte Meyn wrote:
> Am 19.07.2016 um 22:39 schrieb Joel C. Salomon:
>>  From “Arrival of the Wolves”: an accidental in the upper Staff’s
>> voiceOne shifts a chord in its voiceTwo so it no longer aligns with the
>> corresponding note in the lower Staff, yielding the attached result.
> 
> You can force the  to the right place with
>   \once \override NoteColumn.force-hshift = 0
> Then you’ll need to shift the a sharp too:
>   \once \override NoteColumn.force-hshift = -1 (or -1.1?)

Thanks; that worked.  It seems, though, that I should have been able to
achieve the same effect with forcing a positive hshift on the B in the
lower staff (which is actually closer to the printed score), but when I
tried it I could not see that the note moved at all.

Searching the documentation turns up
:

> Changing [the force-hshift property] permits a note column to be moved
> in situations where the note columns overlap. Note that it has no
> effect on note columns that do not overlap.

And it looks like the lower-staff B has moved anyhow; hmm….  Okay, I
think this has given me some insight into what force-hshift is actually
doing.

Thank you,
—Joel Salomon

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

Re: Defining a function that passes contents between braces to a markup

[Mojca Miklavec]

On 19 July 2016 at 14:36, David Kastrup wrote:
>
> Well, let's put this in perspective.  I've been throwing stuff at you
> without the slightest attempt of toning it down to beginners' level,
> basically expecting you to ask back where required.  I cannot remember
> any list newcomer ingest stuff at that rate and level and pump out new
> iterations.  Either our documentation has improved a lot over time or
> you are just good at picking stuff up and secondguessing system design.
> Knowing your background, it's likely more of the latter.

It's just that I want to learn playing the instrument while I still
have some free time and motivation.

But in contrast to say a guitar (where one can find the chords behind
every corner) it's a very specific market because I would mostly like
to learn "national music" (sadly many of the nice songs from elsewhere
might not be "playable" on the instrument) and with such a small
population most of the scores are either:
- handwritten (often in some hardly legible script)
- written without sufficient information or without "playing aid"
- accessible only via "YouTube tutorials" or some software showing the
buttons to be pressed
- super expensive
- very often non-existing

I would like to start with freely accessible (and "editable") scores
of at least the old national songs (with unknown authors, so no
problems with author rights etc.). If enough people contribute, the
collection could grow fast enough.

But:
- I need to do it while I'm still motivated (and before I learn too
much; because then motivation for adding the playing aid will then
decrease :)
- I need a fast and efficient way to enter the scores

Currently I'm able to enter the pitches fast enough, but adding button
names (and the basses) is still a horrible time waster that I want to
avoid and something that should be fixed if I want to continue the
effort. Most likely I will eventually have to use an external program
for "conversion" between pitches and button numbers.

Mojca

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

Re: How to create a thick horizontal line (as its own staff)?

[Mojca Miklavec]

Dear David (and others),

One further thought.

Given that it's super difficult to "transfer" information "across staves" ...

Would it be feasible to allow the following input syntax (or something similar)?

melody = { c a c \startPush f g a \stopPush h c d }
\new PianoStaff <<
\new Voice = "melody" \fixed c' {
  \melody
   }
   \new Dynamics \with {
 \override VerticalAxisGroup.nonstaff-nonstaff-spacing.padding = 1
   } {
 \melody
   }
>>

There are modes like "\new RhythmicStaff" that discard half of the
information about the scores.

I would be super happy if there was a way to enter the input
information only once because repeating it twice is calling for
errors. But also because \startPush and \stopPush could then do
different things inside the main melody.

The "\new Voice" could ignore the \startPush/\stopPush directives (or
do something special with them) and "\new Dynamics" could ignore
typesetting the actual musical notes. I don't know how much tweaking
of LilyPond internals would be needed to achieve that though.

Thank you,
Mojca

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

Running midi -> ly conversion

[Mojca Miklavec]

Hi,

I wonder if there is any easier (more intuitive) way to run the midi
to lilypond conversion on Mac than

arch -32 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python
/Applications/LilyPond.app/Contents/Resources/bin/midi2ly test.midi

which additionally complains about

/Applications/LilyPond.app/Contents/Resources/bin/midi2ly:945:
RuntimeWarning: Python C API version mismatch for module midi: This
Python has API version 1013, module midi has version 1012.
  import midi

(I didn't try to debug the problem because it was only an annoying
warning, so I ignored it for now.)


1.) Are there any plans to start distributing official 64-bit binaries for Mac?


2.) Are there any plans to allow using Python 3? I initially tried to run

> /Applications/LilyPond.app/Contents/Resources/bin/midi2ly test.midi
  File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly", line 534
sys.stderr.write ("SKIP: %s\n" % `e`)
 ^
SyntaxError: invalid syntax

Not that Python 3 compatibility would really help here because there
are further problems with the fact that LilyPond ships 32-bit
libraries and has to run on a 64-bit system. But if I manage to
compile lilypond natively, that would help.


3.) Would it be feasible to add a menu entry to the GUI to do the
conversion? Or perhaps at least add an entry about running midi2ly to
http://lilypond.org/macos-x.html


Thank you,
Mojca

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

Re: Cross staff stems between notes of different durations

[Simon Albrecht]

On 20.07.2016 15:14, Kieren MacMillan wrote:




Maybe even better would be a possibility to just use \change Staff = 
"id" inside a chord.


Best, Simon

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

Re: Cross staff stems between notes of different durations

[Rutger Hofman]

For me, this just works, with differentlyHeaded and with different 
durations for the same NoteHead type:


\version "2.19.39"

\score {
\new PianoStaff \with {
\consists #Span_stem_engraver
} <<
\new Staff = RH <<
\time 3/4
\relative c'' {
c4 \mergeDifferentlyHeadedOn \crossStaff { c2 }
}
>>
\new Staff = LH <<
\relative c' {
\clef bass
% \voiceOne
c4 c c
}
>>
>>
}


\score {
\new PianoStaff \with {
\consists #Span_stem_engraver
} <<
\new Staff = RH <<
\time 3/4
\relative c'' {
c4 \mergeDifferentlyHeadedOn \crossStaff { c8 c c c }
}
>>
\new Staff = LH <<
\relative c' {
\clef bass
% \voiceOne
c4 c c
}
>>
>>
}



On 07/20/2016 02:40 PM, Andrew Bernard wrote:

Total silence? No thoughts, anybody?

Andrew



On 18 July 2016 at 11:45:51 PM, Andrew Bernard wrote:


If one wants to have cross staff stems between notes of different
durations, found often in the contemporary music I set, is there a
lilypond setting of some sort to do this?



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

Re: Cross staff stems between notes of different durations

[Kieren MacMillan]

Hi Andrew,

> Total silence? No thoughts, anybody?

Until we have the ability to say, e.g.,

  

which could easily be music-function-ized, I think your hack (or something 
similar) is all you’ve got.

Would love to be proven wrong, though!

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Cross staff stems between notes of different durations

[Andrew Bernard]

Total silence? No thoughts, anybody?

Andrew



On 18 July 2016 at 11:45:51 PM, Andrew Bernard wrote:

If one wants to have cross staff stems between notes of different
durations, found often in the contemporary music I set, is there a
lilypond setting of some sort to do this?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Slur over single note?

[Urs Liska]

Am 20.07.2016 um 04:26 schrieb Andrew Bernard:
> All the rest of the signs are phrasing slurs in this snippet. I would
> say it’s also a phrasing slur, and not a mistake or error.
>

I disagree. I have skimmed through the whole score, and I'm still nearly
sure (maybe now 98.5 % instead of merely 98 %) that this is an engraving
error.

If I'm not mistaken this is a piano reduction?
If that's the case i'd assume there's a tied note or two slurred ones in
an instrumental part here.

I see two options here, depending on what you want with this score:

1 (the scholarly approach):
Get hold of the full score and see if there's a part that warrants the
slur/tie. If you find somethign adjust the thing accordingly.

2 (the flashy approach):
Use the scholarLY package and produce a nice annotation with footnote.
See attached input and result files.

Of course you can base 2) on the results of 1)

Best
Urs

> The Peter Pan score seems to be full of such _descriptive_
> indications. Not all scores are entirely _prescriptive_.
>
> Andrew
>
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

\version "2.19.45"

\include "scholarly/package.ly"


\new Staff
\relative a {
  \clef bass
  <<
{
  \voiceOne
  \criticalRemark \with {
message = "In the piano reduction there is a spurious tie or slur
   that spans the whole measure but isn't continued
   after the line break"
footnote-offset = #'(-0.5 . 1)
footnote-text = "Spurious tie/slur. See critical remarks"
  }
  LaissezVibrerTie
  a1 \laissezVibrer
}
\new Voice {
  \voiceTwo
  a,8 r r4 r2
}
  >>
  8
}

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

Re: Lyrics.LyricText.font-size in layout block

[Noeck]

Hi Abraham,

Am 20.07.2016 um 01:05 schrieb tisimst:
> Shouldn't it be without the -1 though?

In general, yes. The default is 1.0, so I wrote it for this case of
lycris. If you enter font-size=1.0 in this formula, you get a factor of
1.0 (with respect to the default lyrics font size). With the general
formula factor = 2^(font-size/6) you get a factor of 2^(1/6) with
respect to the normal font-size 0 (12% larger). So it depends what you
mean by the factor.

Best,
Joram

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