Re: function to replace notes by rests

[Jacques Menu]

Hello Marc,

Thanks for teaching me this.

As it turns out, we’re better off specifying durations at crucial points to 
avoid « inheriting » such default values, see:

  c'4 d e f \notesToRests \fragment f'8 e c2

below.

JM


\version "2.19.32"

notesToRests =
#(define-music-function (music) (ly:music?)
   (music-map
(lambda (m)
  (if (eq? (ly:music-property m 'name) 'NoteEvent)
  (make-music 'RestEvent
'duration (ly:music-property m 'duration))
  m))
music))

\relative {
  c'4 d e f \notesToRests { g a b2 g8 c } f e c2
}

\relative {
  c'4 d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
}


fragment = \relative { g'4 a b2 g8 c }

\relative {
  c'4 d e f \notesToRests \fragment f'8 e c2
}



> Le 24 nov. 2015 à 08:32, Marc Hohl  a écrit :
> 
> Am 24.11.2015 um 08:27 schrieb Jacques Menu:
>> Hello Malte,
>> 
>> Interesting, but why are there halves instead of quarters in the second
>> staff?
>> 
> 
> Because the first \relative bock ends with halves and this duration is
> used for the next \relative block as well.
> 
> Just using \relative multiple times doesn't reset the default duration to 4 
> (which would be quite a nuisance, anyway).
> 
> Marc
> 
>> JM
>> 
>> 
>> \version "2.19.32"
>> 
>> notesToRests =
>> #(define-music-function (music) (ly:music?)
>>(music-map
>> (lambda (m)
>>   (if (eq? (ly:music-property m 'name) 'NoteEvent)
>>   (make-music 'RestEvent
>> 'duration (ly:music-property m 'duration))
>>   m))
>> music))
>> 
>> \relative {
>>   c' d e f \notesToRests { g a b2 g8 c } f e c2
>> }
>> 
>> \relative {
>>   c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
>> }
>> 
>> 
>> 
>>> Le 24 nov. 2015 à 08:21, Malte Meyn >> > a écrit :
>>> 
>>> 
>>> 
>>> Am 24.11.2015 um 08:10 schrieb Marc Hohl:
 Thanks or sharing! The drawbacks in relative mode are neglectable, I'll
 use absolute mode.
 
>>> 
>>> Alternatively you could use
>>> 
>>> 1. another \relative block inside of notesToRests
>>> \relative {
>>>  c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
>>> }
>>> 
>>> or
>>> 
>>> 2. octave checks if you don’t mind the warnings
>>> \relative {
>>>  c' d e f \notesToRests { g a b2 g8 c } f='' e c2
>>> }
>>> 
>>> ___
>>> 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


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

Re: function to replace notes by rests

[Marc Hohl]

Am 24.11.2015 um 08:27 schrieb Jacques Menu:

Hello Malte,

Interesting, but why are there halves instead of quarters in the second
staff?



Because the first \relative bock ends with halves and this duration is
used for the next \relative block as well.

Just using \relative multiple times doesn't reset the default duration 
to 4 (which would be quite a nuisance, anyway).


Marc


JM


\version "2.19.32"

notesToRests =
#(define-music-function (music) (ly:music?)
(music-map
 (lambda (m)
   (if (eq? (ly:music-property m 'name) 'NoteEvent)
   (make-music 'RestEvent
 'duration (ly:music-property m 'duration))
   m))
 music))

\relative {
   c' d e f \notesToRests { g a b2 g8 c } f e c2
}

\relative {
   c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
}




Le 24 nov. 2015 à 08:21, Malte Meyn mailto:lilyp...@maltemeyn.de>> a écrit :



Am 24.11.2015 um 08:10 schrieb Marc Hohl:

Thanks or sharing! The drawbacks in relative mode are neglectable, I'll
use absolute mode.



Alternatively you could use

1. another \relative block inside of notesToRests
\relative {
  c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
}

or

2. octave checks if you don’t mind the warnings
\relative {
  c' d e f \notesToRests { g a b2 g8 c } f='' e c2
}

___
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: function to replace notes by rests

[Jacques Menu]

Hello Malte,

Interesting, but why are there halves instead of quarters in the second staff?

JM


\version "2.19.32"

notesToRests =
#(define-music-function (music) (ly:music?)
   (music-map
(lambda (m)
  (if (eq? (ly:music-property m 'name) 'NoteEvent)
  (make-music 'RestEvent
'duration (ly:music-property m 'duration))
  m))
music))

\relative {
  c' d e f \notesToRests { g a b2 g8 c } f e c2
}

\relative {
  c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
}



> Le 24 nov. 2015 à 08:21, Malte Meyn  a écrit :
> 
> 
> 
> Am 24.11.2015 um 08:10 schrieb Marc Hohl:
>> Thanks or sharing! The drawbacks in relative mode are neglectable, I'll
>> use absolute mode.
>> 
> 
> Alternatively you could use
> 
> 1. another \relative block inside of notesToRests
>   \relative {
> c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
>   }
> 
> or
> 
> 2. octave checks if you don’t mind the warnings
>   \relative {
> c' d e f \notesToRests { g a b2 g8 c } f='' e c2
>   }
> 
> ___
> 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: function to replace notes by rests

[Malte Meyn]

Am 24.11.2015 um 08:10 schrieb Marc Hohl:

Thanks or sharing! The drawbacks in relative mode are neglectable, I'll
use absolute mode.



Alternatively you could use

1. another \relative block inside of notesToRests
\relative {
  c' d e f \notesToRests \relative { g' a b2 g8 c } f' e c2
}

or

2. octave checks if you don’t mind the warnings
\relative {
  c' d e f \notesToRests { g a b2 g8 c } f='' e c2
}

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

RE: tieWaitForNote

[Mark Stephen Mrotek]

Malte Meyn,

Perfect!
Thank you.

Mark

-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Malte Meyn
Sent: Monday, November 23, 2015 11:05 PM
To: lilypond-user@gnu.org
Subject: Re: tieWaitForNote



Am 24.11.2015 um 06:53 schrieb Mark Stephen Mrotek:
> Everything is correct except that the ties do not appear. What is my
error?

If you really want these note length values you need a << >> construct but
without \\ because that would create new Voices. The only new Voice you need
is the one for the rest because LilyPond cannot put a r8 and a g4. to the
same stem (that's what it tries if you use << >> without \\).

\version "2.18.2"

\relative c {
   \key e \minor
   \time 6/8
   \set tieWaitForNote = ##t
   \tieDown
   <<
 \new Voice { \voiceOne r8 }
 { s8 s d'~ }
 { g,4.~ }
 { s8 b4~ }
   >>
   4.
   \tieNeutral
}

___
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: Automatically transforming a FiguredBass line into a sequence of chords ?

[Malte Meyn]

Am 23.11.2015 um 23:56 schrieb Michael Gerdau:

Hi list,

does someone know of a function or snipped that automatically transforms
some music together with a FigruedBass line into a sequence of chords


I once wanted to do that but I hadn’t enough time and automatic a 
correct right hand for a figured bass is really complex so I abandoned 
the project ...

http://lists.gnu.org/archive/html/lilypond-user/2014-04/msg00168.html


like illustrated in the example below ?


Probably that’s much simpler that a totally correct and playable 
version. It seems like you don’t care about parallel fifths (m. 1 to 2) 
and don’t add notes that aren’t explicitely there (f. e. <6 5> like in 
m. 3 always means <6 5 3> so you would have to add an e).


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

Re: function to replace notes by rests

[Marc Hohl]

Am 23.11.2015 um 21:41 schrieb Malte Meyn:

Am 23.11.2015 um 10:46 schrieb Marc Hohl:

As the file is a bit lengthy, I think of a way to just redefine
\xNotes to change every note to its corresponding rest, instead of
rewriting the whole file (or using sed or any other external script).

Has anyone a scheme routine at hand that does exactly this job?


Malte,


I wrote this but it doesn’t work well in relative mode:

\version "2.19.30"

notesToRests =
#(define-music-function (music) (ly:music?)
(music-map
 (lambda (m)
   (if (eq? (ly:music-property m 'name) 'NoteEvent)
   (make-music 'RestEvent
 'duration (ly:music-property m 'duration))
   m))
 music))

\relative {
   c' d e f \notesToRests { g a b2 g8 c } f e c2
}


Thanks or sharing! The drawbacks in relative mode are neglectable, I'll 
use absolute mode.


Marc


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

Re: tieWaitForNote

[Malte Meyn]

Am 24.11.2015 um 06:53 schrieb Mark Stephen Mrotek:

Everything is correct except that the ties do not appear. What is my error?


If you really want these note length values you need a << >> construct 
but without \\ because that would create new Voices. The only new Voice 
you need is the one for the rest because LilyPond cannot put a r8 and a 
g4. to the same stem (that’s what it tries if you use << >> without \\).


\version "2.18.2"

\relative c {
  \key e \minor
  \time 6/8
  \set tieWaitForNote = ##t
  \tieDown
  <<
\new Voice { \voiceOne r8 }
{ s8 s d'~ }
{ g,4.~ }
{ s8 b4~ }
  >>
  4.
  \tieNeutral
}

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

Re: Strange LilyPond crash

[Marc Hohl]

Am 24.11.2015 um 00:12 schrieb Thomas Morley:
[...]


So,
commit b416f10429d8d3881445d9000ff422dc67176df1
Author: David Kastrup 
Date:   Wed Jul 15 23:30:30 2015 +0200

 Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes

 There is still one shortcoming: the percent repeats will not contain any
 material apart from the percent itself.  In particular, no Timing
 changes will be repeated.  If there are meter changes or \partial
 commands inside of percent repeats, they need to occur in parallel
 passages outside of any percent repeat, if necessary in a separate
 "timing track".

is indeed the problem.


Thanks for your work on this issue!



Now it would be nice I'd could come up with a tiny example...

Though, very strange things happen, like:

assume file-1.ly with

foo = { some-music }
buzz = { some-other-music }

and

file-2.ly with

\include "file-1.ly"
\score {
   <<
   \new Staff \foo
   \new Staff \buzz
   >>

compiling file-2.ly causes a segfault.
commenting \new Staff \buzz still causes a segfault
additional commenting(!) buzz = { some-other-music } in file-1.ly,
and the segfault disappears!!!
But it's not consistent! It depends what else is defined in those files.


Yep. Moreover, if I removed some notes from buzz, the segfault 
disappeared, but adding one single note causes Lilypond to crash,

and we talk about scores with 3-5 pages or even less.


No idea how to boil it down to a small example.


Sorry for the initial wrong info,


No problem at all – thanks for your time and work!

Marc


   Harm




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

RE: tieWaitForNote

[Mark Stephen Mrotek]

Hwaen Ch'uqi,

Thank you for your reply. I shall try your suggestion.

Mark

-Original Message-
From: Hwaen Ch'uqi [mailto:hwaench...@gmail.com] 
Sent: Monday, November 23, 2015 10:13 PM
To: Mark Stephen Mrotek 
Cc: lilypond-user Mailinglist 
Subject: Re: tieWaitForNote

Greetings Mark,

I believe that ties only work if the notes they are connecting are in the same 
voice. In your example, you have called \voiceOne, \voiceTwo, and \voiceThree. 
However, your resulting chord is in none of those voices. Would it be possible 
to avoid that construct altogether?
Something like

\relative c'' {

\key e \minor

\clef treble

\time 6/8

\set tieWaitForNote = ##t

g,8~ b~ d~ 4. }

And then manipulate ties individually if needed?

Hwaen Ch'uqi


On 11/24/15, Mark Stephen Mrotek  wrote:
> Hello,
>
>
>
> Everything is correct except that the ties do not appear. What is my error?
>
>
>
> \version "2.18.2"
>
>
>
> \relative c'' {
>
>   \clef treble
>
>   \key e \minor
>
>   \time 6/8
>
>
>
> << {b8\rest s \set tieWaitForNote = ##t d,~ } \\
>
>  {\set tieWaitForNote = ##t g,4.~ } \\
>
>  {s8 \set tieWaitForNote = ##t b4~ } >> 4. |
>
>
>
> }
>
>
>
> Thank you for your kind attention.
>
>
>
> Mark Stephen Mrotek
>
>


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

Re: tieWaitForNote

[Hwaen Ch'uqi]

Greetings Mark,

I believe that ties only work if the notes they are connecting are in
the same voice. In your example, you have called \voiceOne, \voiceTwo,
and \voiceThree. However, your resulting chord is in none of those
voices. Would it be possible to avoid that construct altogether?
Something like

\relative c'' {

\key e \minor

\clef treble

\time 6/8

\set tieWaitForNote = ##t

g,8~ b~ d~ 4. }

And then manipulate ties individually if needed?

Hwaen Ch'uqi


On 11/24/15, Mark Stephen Mrotek  wrote:
> Hello,
>
>
>
> Everything is correct except that the ties do not appear. What is my error?
>
>
>
> \version "2.18.2"
>
>
>
> \relative c'' {
>
>   \clef treble
>
>   \key e \minor
>
>   \time 6/8
>
>
>
> << {b8\rest s \set tieWaitForNote = ##t d,~ } \\
>
>  {\set tieWaitForNote = ##t g,4.~ } \\
>
>  {s8 \set tieWaitForNote = ##t b4~ } >> 4. |
>
>
>
> }
>
>
>
> Thank you for your kind attention.
>
>
>
> Mark Stephen Mrotek
>
>

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

tieWaitForNote

[Mark Stephen Mrotek]

Hello,

 

Everything is correct except that the ties do not appear. What is my error?

 

\version "2.18.2"

 

\relative c'' {

  \clef treble

  \key e \minor

  \time 6/8

 

<< {b8\rest s \set tieWaitForNote = ##t d,~ } \\

 {\set tieWaitForNote = ##t g,4.~ } \\

 {s8 \set tieWaitForNote = ##t b4~ } >> 4. |

 

}

 

Thank you for your kind attention.

 

Mark Stephen Mrotek

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

Re: Strange LilyPond crash

[Thomas Morley]

2015-11-22 1:59 GMT+01:00 Thomas Morley :
> 2015-11-21 17:31 GMT+01:00 Thomas Morley :
>> 2015-11-21 16:42 GMT+01:00 David Kastrup :
>>> Marc Hohl  writes:
>>>
 As soon as I remove an instrumental part at random (or even some
 notes), the crash may or may not disappear. I am not sure but IIRC a
 file that compiled fine during one run crashed without having done any
 changes to that specific file (nor its includes).  Is it possible that
 the self-compiled version I am using has some internal errors that may
 cause the crash? I update the git repository regularly and re-compile
 lilypond after applying the latest patches.
>>>
>>> Both 2.19.29 and 2.19.30 had really bad problems that could be
>>> exacerbated by "large files".  Your segfault does not look related to
>>> that as far as I can tell.
>>>
>>> --
>>> David Kastrup
>>
>>
>>
>> Hi Marc,
>>
>> I'd like to offer you send me the zipped files offlist.
>> Maybe a second pair of eyes watching the real code may help.
>>
>> Cheers,
>>   Harm
>
> Hi Marc,
>
> thanks for your files.
> Up to know I can't come up with a tiny example.
>
> Though, some observations:
> (1)
> All works with 2.18.2 (after downgrading the syntax)
> (2)
> Replacing all occurances of
> \repeat percent ...
> with
> \repeat unfold ...
> make it work with a build from latest master
>
> Thus I suspected
>
> commit [rb416f10429d8d3881445d9000ff422dc67176df1]
> Author: David Kastrup 
> Date:   Wed Jul 15 23:30:30 2015 +0200
>
> Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes
>
> There is still one shortcoming: the percent repeats will not contain any
> material apart from the percent itself.  In particular, no Timing
> changes will be repeated.  If there are meter changes or \partial
> commands inside of percent repeats, they need to occur in parallel
> passages outside of any percent repeat, if necessary in a separate
> "timing track".
>
> Which was the last commit I found for this area of code.
>
> Though a build from one commit before:
> cd3c64ba5131d64d7f0b76487054f8fac1364e61
> returned the same segfaults.
>
> Will continue testings tomorrow.
>
> Cheers,
>   Harm

Ok, made a mistake.

One commit before is:
11a9e5701316d46d34993fadb85482282c9753cc

A build from this one works!

So,
commit b416f10429d8d3881445d9000ff422dc67176df1
Author: David Kastrup 
Date:   Wed Jul 15 23:30:30 2015 +0200

Issue 3693: Let Percent_repeat_iterator be unfazed by Timing changes

There is still one shortcoming: the percent repeats will not contain any
material apart from the percent itself.  In particular, no Timing
changes will be repeated.  If there are meter changes or \partial
commands inside of percent repeats, they need to occur in parallel
passages outside of any percent repeat, if necessary in a separate
"timing track".

is indeed the problem.


Now it would be nice I'd could come up with a tiny example...

Though, very strange things happen, like:

assume file-1.ly with

foo = { some-music }
buzz = { some-other-music }

and

file-2.ly with

\include "file-1.ly"
\score {
  <<
  \new Staff \foo
  \new Staff \buzz
  >>

compiling file-2.ly causes a segfault.
commenting \new Staff \buzz still causes a segfault
additional commenting(!) buzz = { some-other-music } in file-1.ly,
and the segfault disappears!!!
But it's not consistent! It depends what else is defined in those files.

No idea how to boil it down to a small example.


Sorry for the initial wrong info,
  Harm

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

Automatically transforming a FiguredBass line into a sequence of chords ?

[Michael Gerdau]

Hi list,

does someone know of a function or snipped that automatically transforms
some music together with a FigruedBass line into a sequence of chords
like illustrated in the example below ?

%%%
\version "2.19.31"

bcMusic = \relative {
  c2 c | c c | c c | c c |
}

bcFigures = \figuremode {
  \override Staff.BassFigureAlignmentPositioning #'direction = #DOWN
  \bassFigureExtendersOn
  \set figuredBassPlusDirection = #RIGHT
  \set figuredBassAlterationDirection = #RIGHT
  <5 3>2 <5 3> | <6 5+ 2>4 <6 4! 2> <6 4! 2>2 | <6\! 5> <6 5> |
  <9 4>4 <8 3>4 <8 3>2
}

\markup { "Is there a function that transforms this FiguredBass line..." }
<<
  \new Staff {
\clef bass \bcMusic
  }
  \new FiguredBass \bcFigures
>>

result = \relative {
  2  | 4  2 |
| 4  2 |
}

\markup { "...automatically into this sequence of chords ?" }
\new Staff { \clef bass \result }

\markup { "(hoping I got it right manually :)" }

%%%

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

signature.asc
Description: This is a digitally signed message part.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: No blot in custom bar line

[Simon Albrecht]

On 23.11.2015 23:02, David Nalesnik wrote:

Hi Simon,

On Mon, Nov 23, 2015 at 3:40 PM, Simon Albrecht 
mailto:simon.albre...@mail.de>> wrote:


Hello,

I’ve defined a custom bar line, following the examples in
scm/bar-line.scm. Now I would have expected the whole ‘blot’
business to give me round edges, at least with \override
Staff.BarLine.rounded = ##t, but it doesn’t. Why?

The value for blot that you end up using is tiny.  (I get a value of 
0.016.)  Try substituting 0.08 for a better appearance.  I'm not sure 
at the moment how you'd go about *calculating* a more reasonable value.


After quite some scouring I found the source for this small value: 
scm/paper.scm, lines 91f. read:

;;  sync with feta
(setm! 'blot-diameter (* 0.4 pt))
It works to just replace (layout-blot-diameter grob) in the definition 
for calc-blot by 0.1. Thus, there’s still the safety that a smaller 
value will be chosen for either very thin or very short bar-lines – 
OTOH, when is that supposed to happen? :-)


Yours, Simon

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

Re: outside-staff-priority?

[Simon Albrecht]

On 23.11.2015 23:05, Ralph Palmer wrote:



On Mon, Nov 23, 2015 at 4:56 PM, Stephen MacNeil 
mailto:classicalja...@gmail.com>> wrote:


\override Score.MetronomeMark.padding = #5

\tempo "Mod. fast Bulgar" 4 = 110-115


My thanks to both Stephen and to Malte Meyn. Yes, I missed "Score". I 
was using Staff. "outside.staff.priority" would imply something other 
than "Staff" context, wouldn't it.


That’s not the point – the point is that the Metronome_mark_engraver 
lives in Score.


Yours, Simon

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

Re: outside-staff-priority?

[David Kastrup]

Ralph Palmer  writes:

> On Mon, Nov 23, 2015 at 4:56 PM, Stephen MacNeil 
> wrote:
>
>> \override Score.MetronomeMark.padding = #5
>>
>> \tempo "Mod. fast Bulgar" 4 = 110-115
>>
>
> My thanks to both Stephen and to Malte Meyn. Yes, I missed "Score". I was
> using Staff. "outside.staff.priority" would imply something other than
> "Staff" context, wouldn't it.

No.  But the Metronome_mark_engraver (?) lives at Score level since it
only puts down one mark per score.  So for anything but Score,

\override xxx.MetronomeMark.yyy ...

will not have an effect since the MetronomeMark grob is emitted at Score
level and so takes its initial properties only from Score-level
overrides.

-- 
David Kastrup

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

Re: outside-staff-priority?

[Ralph Palmer]

On Mon, Nov 23, 2015 at 4:56 PM, Stephen MacNeil 
wrote:

> \override Score.MetronomeMark.padding = #5
>
> \tempo "Mod. fast Bulgar" 4 = 110-115
>

My thanks to both Stephen and to Malte Meyn. Yes, I missed "Score". I was
using Staff. "outside.staff.priority" would imply something other than
"Staff" context, wouldn't it. My mistake.

Thanks again,

Ralph

-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: No blot in custom bar line

[David Nalesnik]

Hi Simon,

On Mon, Nov 23, 2015 at 3:40 PM, Simon Albrecht 
wrote:

> Hello,
>
> I’ve defined a custom bar line, following the examples in
> scm/bar-line.scm. Now I would have expected the whole ‘blot’ business to
> give me round edges, at least with \override Staff.BarLine.rounded = ##t,
> but it doesn’t. Why?


The value for blot that you end up using is tiny.  (I get a value of
0.016.)  Try substituting 0.08 for a better appearance.  I'm not sure at
the moment how you'd go about *calculating* a more reasonable value.

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

RE:outside-staff-priority?

[Stephen MacNeil]

\override Score.MetronomeMark.padding = #5

\tempo "Mod. fast Bulgar" 4 = 110-115


HTH


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

No blot in custom bar line

[Simon Albrecht]

Hello,

I’ve defined a custom bar line, following the examples in 
scm/bar-line.scm. Now I would have expected the whole ‘blot’ business to 
give me round edges, at least with \override Staff.BarLine.rounded = 
##t, but it doesn’t. Why?
Also, it’s a bit of a nuisance that calc-blot isn’t publicly available. 
Would there be a problem with changing that? And would it require 
anything but to use define-public for it?


TIA, Yours Simon


\version "2.18.2"
% dupe from scm/bar-line.scm, line 64ff. and 30ff.
% TODO: make this publicly available
#(define (layout-blot-diameter grob)
  "Get the blot diameter of the @var{grob}'s corresponding layout."
  (let* ((layout (ly:grob-layout grob))
 (blot-diameter (ly:output-def-lookup layout 'blot-diameter)))

blot-diameter))
#(define (calc-blot thickness extent grob)
  "Calculate the blot diameter by taking @code{'rounded}
and the dimensions of the extent into account."
  (let* ((rounded (ly:grob-property grob 'rounded #f))
 (blot (if rounded
   (let ((blot-diameter (layout-blot-diameter grob))
 (height (interval-length extent)))

 (cond ((< thickness blot-diameter) thickness)
   ((< height blot-diameter) height)
   (else blot-diameter)))
   0)))

blot))
#(define (make-bach-bar-line grob extent)
  "Draw a v-centered half bar line, to model Seb. Bach’s use (e.g. in 
BWV 226)."

  (let* ((line-thickness (layout-line-thickness grob))
 (thickness (* (ly:grob-property grob 'hair-thickness 1)
   line-thickness))
 (extent (interval-scale extent 1/3))
 (bottom (interval-start extent))
 (top (interval-end extent))
 (blot (calc-blot thickness extent grob)))

(ly:round-filled-box (cons 0 thickness)
 (cons bottom top)
 blot)))
#(add-bar-glyph-print-procedure "b" make-bach-bar-line)
#(define-bar-line "b" "b" #f #f)

#(set-global-staff-size 100)
{
  c''4
  \once\override Staff.BarLine.rounded = ##t
  \bar "b"
}
%
\version "2.18.2"
% dupe from scm/bar-line.scm, line 64ff. and 30ff.
% TODO: make this publicly available
#(define (layout-blot-diameter grob)
  "Get the blot diameter of the @var{grob}'s corresponding layout."
  (let* ((layout (ly:grob-layout grob))
 (blot-diameter (ly:output-def-lookup layout 'blot-diameter)))

blot-diameter))
#(define (calc-blot thickness extent grob)
  "Calculate the blot diameter by taking @code{'rounded}
and the dimensions of the extent into account."
  (let* ((rounded (ly:grob-property grob 'rounded #f))
 (blot (if rounded
   (let ((blot-diameter (layout-blot-diameter grob))
 (height (interval-length extent)))

 (cond ((< thickness blot-diameter) thickness)
   ((< height blot-diameter) height)
   (else blot-diameter)))
   0)))

blot))
#(define (make-bach-bar-line grob extent)
  "Draw a v-centered half bar line, to model Seb. Bach’s use (e.g. in BWV 226)."
  (let* ((line-thickness (layout-line-thickness grob))
 (thickness (* (ly:grob-property grob 'hair-thickness 1)
   line-thickness))
 (extent (interval-scale extent 1/3))
 (bottom (interval-start extent))
 (top (interval-end extent))
 (blot (calc-blot thickness extent grob)))

(ly:round-filled-box (cons 0 thickness)
 (cons bottom top)
 blot)))
#(add-bar-glyph-print-procedure "b" make-bach-bar-line)
#(define-bar-line "b" "b" #f #f)

#(set-global-staff-size 100)
{
  c''4
  \once\override Staff.BarLine.rounded = ##t
  \bar "b"
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: outside-staff-priority?

[Malte Meyn]

Am 23.11.2015 um 21:58 schrieb Ralph Palmer:

I tried setting the outside-staff-priority of each
and/or both, but without success.


\override Score.MetronomeMark.outside-staff-priority = 1501
% or
\override Score.RehearsalMark.outside-staff-priority = 999

You probably missed the “Score.”


I'm also not sure if MetronomeMark is the
correct designation for the \tempo indication.


Yes, it is.

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

outside-staff-priority?

[Ralph Palmer]

Greetings -

I'm running LY 2.19.31 under Win7.

In the following snippet, I would like to move the Rehearsal Mark below the
tempo indication, or, conversely, move the tempo indication above the
Rehearsal Mark. I cannot figure out how to do either. I would greatly
appreciate some help. I tried setting the outside-staff-priority of each
and/or both, but without success. I'm also not sure if MetronomeMark is the
correct designation for the \tempo indication.

Thanks in advance for any assistance,

Ralph

%%% begin snippet 

\version "2.19.31"
\include "english.ly"

tune =
\relative c' {
\clef treble
  \key d \minor
  \time 2/4

\tempo "Mod. fast Bulgar" 4 = 110-115

r8 a d e |
  \repeat volta 2 {
\mark \default
f4^Dm e8 d |
  }
  \break
}


\score {
  \tune
}

%% end snippet 

-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com


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

Re: function to replace notes by rests

[Malte Meyn]

Am 23.11.2015 um 10:46 schrieb Marc Hohl:

As the file is a bit lengthy, I think of a way to just redefine
\xNotes to change every note to its corresponding rest, instead of
rewriting the whole file (or using sed or any other external script).

Has anyone a scheme routine at hand that does exactly this job?


I wrote this but it doesn’t work well in relative mode:

\version "2.19.30"

notesToRests =
#(define-music-function (music) (ly:music?)
   (music-map
(lambda (m)
  (if (eq? (ly:music-property m 'name) 'NoteEvent)
  (make-music 'RestEvent
'duration (ly:music-property m 'duration))
  m))
music))

\relative {
  c' d e f \notesToRests { g a b2 g8 c } f e c2
}

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

Re: [WAS] Staff ends before \clef, \time and \key

[Pierre Perol-Schneider]

Nice! Thank you Simon.
In fact, in that particular case I have no choice, I have to follow the
composer's indications.
But i'l keep your tweak in mind anyway.

Cheers,
Pierre

2015-11-23 21:18 GMT+01:00 Simon Albrecht :

> How about
> %%%
> \version "2.19.31"
> {
>   \key e\major
>   \time 3/4
>   % mes.98
>   s2.
>   \once\override Score.BreakAlignment.break-align-orders = #(make-vector 3
> '(key-cancellation
> key-signature
> staff-bar))
>   \key e \minor
>   \bar "||"
> }
> %%
> I can’t get the tweak on X-extent to work here…
>
> Yours, Simon
>
> On 23.11.2015 20:52, Pierre Perol-Schneider wrote:
>
>> 'cause of a DS to the former key sig.
>>
>> 2015-11-23 20:45 GMT+01:00 Simon Albrecht > >:
>>
>>
>> On 23.11.2015 10:36, Pierre Perol-Schneider wrote:
>>
>> Hi,
>>
>> See:
>>
>> http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182
>>
>> Reminder:
>>
>> %% Here works fine:
>> \version "2.18.2"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>> }
>>
>> %% Bug here:
>> \version "2.19.32"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>>   %% workaround but not satisfying:
>>   %\grace s4
>> }
>>
>>
>> The question is: why would one want a key signature if the staff
>> dies anyway?
>>
>> Yours, Simon
>>
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [WAS] Staff ends before \clef, \time and \key

[Simon Albrecht]

How about
%%%
\version "2.19.31"
{
  \key e\major
  \time 3/4
  % mes.98
  s2.
  \once\override Score.BreakAlignment.break-align-orders = 
#(make-vector 3 '(key-cancellation

key-signature
staff-bar))
  \key e \minor
  \bar "||"
}
%%
I can’t get the tweak on X-extent to work here…

Yours, Simon

On 23.11.2015 20:52, Pierre Perol-Schneider wrote:

'cause of a DS to the former key sig.

2015-11-23 20:45 GMT+01:00 Simon Albrecht >:


On 23.11.2015 10:36, Pierre Perol-Schneider wrote:

Hi,

See:

http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182

Reminder:

%% Here works fine:
\version "2.18.2"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
}

%% Bug here:
\version "2.19.32"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
  %% workaround but not satisfying:
  %\grace s4
}


The question is: why would one want a key signature if the staff
dies anyway?

Yours, Simon





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

Re: [WAS] Staff ends before \clef, \time and \key

[Pierre Perol-Schneider]

'cause of a DS to the former key sig.

2015-11-23 20:45 GMT+01:00 Simon Albrecht :

> On 23.11.2015 10:36, Pierre Perol-Schneider wrote:
>
>> Hi,
>>
>> See:
>> http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182
>>
>> Reminder:
>>
>> %% Here works fine:
>> \version "2.18.2"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>> }
>>
>> %% Bug here:
>> \version "2.19.32"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>>   %% workaround but not satisfying:
>>   %\grace s4
>> }
>>
>
> The question is: why would one want a key signature if the staff dies
> anyway?
>
> Yours, Simon
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [WAS] Staff ends before \clef, \time and \key

[Simon Albrecht]

On 23.11.2015 10:36, Pierre Perol-Schneider wrote:

Hi,

See: 
http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182


Reminder:

%% Here works fine:
\version "2.18.2"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
}

%% Bug here:
\version "2.19.32"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
  %% workaround but not satisfying:
  %\grace s4
}


The question is: why would one want a key signature if the staff dies 
anyway?


Yours, Simon

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

Re: [WAS] Staff ends before \clef, \time and \key

[Pierre Perol-Schneider]

Or even:
\version "2.19.32"
{
  \key e\major
   \time 3/4
   % mes.98
a'2.
  \bar "||"
  \tweak KeySignature.X-extent #'(0 . 1.4)
  \key e \minor
  s8
}


2015-11-23 20:29 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Thanks to you guys:
> http://lilypond.1069038.n5.nabble.com/Kerning-a-clef-td183994.html
> I've just found what I was lokking for:
>
> \version "2.19.32"
> {
>   \key e\major
>\time 3/4
>% mes.98
> a'2.
>   \bar "||"
>   \tweak KeySignature.space-alist.next-note #'(extra-space . 0.2)
>   \key e \minor
>   \grace s4
> }
>
> Cheers,
> ~Pierre
>
> 2015-11-23 10:36 GMT+01:00 Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com>:
>
>> Hi,
>>
>> See:
>> http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182
>>
>> Reminder:
>>
>> %% Here works fine:
>> \version "2.18.2"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>> }
>>
>> %% Bug here:
>> \version "2.19.32"
>> {
>>   \key e\major
>>\time 3/4
>>% mes.98
>> s2.
>>   \bar "||"
>>   \key e \minor
>>   %% workaround but not satisfying:
>>   %\grace s4
>> }
>>
>> Does anyone has a better workaround/solution ?
>>
>> Cheers,
>> Pierre
>>
>>
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: [WAS] Staff ends before \clef, \time and \key

[Pierre Perol-Schneider]

Thanks to you guys:
http://lilypond.1069038.n5.nabble.com/Kerning-a-clef-td183994.html
I've just found what I was lokking for:

\version "2.19.32"
{
  \key e\major
   \time 3/4
   % mes.98
a'2.
  \bar "||"
  \tweak KeySignature.space-alist.next-note #'(extra-space . 0.2)
  \key e \minor
  \grace s4
}

Cheers,
~Pierre

2015-11-23 10:36 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi,
>
> See:
> http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182
>
> Reminder:
>
> %% Here works fine:
> \version "2.18.2"
> {
>   \key e\major
>\time 3/4
>% mes.98
> s2.
>   \bar "||"
>   \key e \minor
> }
>
> %% Bug here:
> \version "2.19.32"
> {
>   \key e\major
>\time 3/4
>% mes.98
> s2.
>   \bar "||"
>   \key e \minor
>   %% workaround but not satisfying:
>   %\grace s4
> }
>
> Does anyone has a better workaround/solution ?
>
> Cheers,
> Pierre
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ‘Kerning’ a clef

[Simon Albrecht]

On 23.11.2015 20:01, Kieren MacMillan wrote:

Hi Simon,


I’d like the clef to take less space, especially to the right, and at best to 
overlap with the following note. How can I achieve that?

\version "2.19.31"
{
  a'8
  \tweak Clef.space-alist.next-note #'(extra-space . 0)
  \tweak Clef.X-extent #empty-interval
  \clef bass a, b, c
}

This is obviously extreme; adjust the X-extent as desired.


Thanks, that’s good.

There are two issues, though:
– the \tweak version spills over to the next clef and
– the vertical position of the beam changes:

%%
\version "2.19.31"
{
  a'8
  \once\override Staff.Clef.space-alist.next-note = #'(extra-space . 0)
  \once\override Staff.Clef.X-extent = #'(0 . .8)
  \clef bass a, b, c
  \clef treble a'8
  \tweak Clef.space-alist.next-note #'(extra-space . 0)
  \tweak Clef.X-extent #'(0 . 0)
  \clef bass a, b, c

  \clef treble a'4
}

(output attached)

I’ll go for the bug-list with these.

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

Re: ‘Kerning’ a clef

[Simon Albrecht]

On 23.11.2015 19:58, David Kastrup wrote:

Simon Albrecht  writes:


have a look at the attached image. I’d like the clef to take less
space, especially to the right, and at best to overlap with the
following note. How can I achieve that? extra-spacing-width obviously
can only increase spacing

Negative numbers exist.


But don’t have any effect here:

\version "2.19.31"
{
  a'8 \tweak Clef.extra-spacing-width #'(0 . -2) \clef bass a, b, c
}

Yours, Simon

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

Re: ‘Kerning’ a clef

[Kieren MacMillan]

Hi Simon,

> I’d like the clef to take less space, especially to the right, and at best to 
> overlap with the following note. How can I achieve that?

\version "2.19.31"
{
 a'8
 \tweak Clef.space-alist.next-note #'(extra-space . 0)
 \tweak Clef.X-extent #empty-interval
 \clef bass a, b, c
}

This is obviously extreme; adjust the X-extent as desired.

Hope this helps!
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: ‘Kerning’ a clef

[David Kastrup]

Simon Albrecht  writes:

> have a look at the attached image. I’d like the clef to take less
> space, especially to the right, and at best to overlap with the
> following note. How can I achieve that? extra-spacing-width obviously
> can only increase spacing

Negative numbers exist.

-- 
David Kastrup

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

‘Kerning’ a clef

[Simon Albrecht]

Hello,

have a look at the attached image. I’d like the clef to take less space, 
especially to the right, and at best to overlap with the following note. 
How can I achieve that? extra-spacing-width obviously can only increase 
spacing, and the following doesn’t work either:


%
\version "2.19.31"
{
  a'8 \tweak Clef.space-alist.next-note #'(extra-space . 0) \clef bass 
a, b, c

}
%

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

Re: question about overrides within repeats

[David Kastrup]

David Nalesnik  writes:

> My question would be: when does the evaluation of a grob's stencil
> normally happen?  My guess is this normal evaluation is happening
> based on a haphazard input, that using 'before-line-breaking and
> 'after-line-breaking is forcing a later evaluation, at a time when
> grobs have been better arranged by timing.
>
> (Please understand that this is largely a guess.  I'm finding the code
> incredible hard to follow.)

Some stencils will depend on the particular line break choices, some
not.

This code is incredibly hard to follow because the optimization problem
LilyPond has to solve leads to complex patterns of evaluating things
(and throwing a lot of them away).  And unfortunately the complexity is
distributed all over the place instead of having its code condensed into
one well-documented framework.

"well-documented" and "LilyPond code" rarely fit well into the same
sentence anyway.  But the code for this problem alone already makes it a
particularly bad area.

-- 
David Kastrup

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

Re: question about overrides within repeats

[David Nalesnik]

On Sun, Nov 22, 2015 at 2:44 PM, David Kastrup  wrote:

> Thomas Morley  writes:
>
> > Though, why it is that arbitrary?
> >
> > Look at this variation and the attached image:
> >
> > \version "2.19.29"
> > #(define test-nmbrs
> >   (let ((nmbrs (circular-list 1 2 3 4)))
> > (lambda (grob)
> >   (let ((n (car nmbrs)))
> > (set! nmbrs (cdr nmbrs))
> > (grob-interpret-markup grob (number->string n))
> >
> > {
> >   \repeat unfold 8 {
> > \once \override TextScript.stencil = #test-nmbrs
> > c''4^\markup "foo"
> >   }
> > }
>
> Well, it is exactly 2 variants of 1, 2, 3, 4 each.  I suspect that the
> order of grob evaluation at some point when a system is printed depends
> on the order of memory addresses.
>
> Find that point and you'll likely also have the culprit for various
> other stuff behaving non-deterministically, like what is drawn on top of
> what and other things frequently turning up in "make check".
>
>
Here's something interesting.

Setting the stencil during 'before-line-breaking or 'after-line-breaking
works for the short example that Harm provided.  In longer examples,
after-line-breaking goes astray after several lines.  Compare:

 \version "2.19.29"

#(define test-nmbrs
  (let ((nmbrs (circular-list 1 2 3 4)))
(lambda (grob)
  (let ((n (car nmbrs)))
(set! nmbrs (cdr nmbrs))
(set! (ly:grob-property grob 'stencil)
  (grob-interpret-markup grob (number->string n)))

{
  \repeat unfold 200 {
%% works:
\once \override TextScript.before-line-breaking = #test-nmbrs
%% jumbling after 3 lines:
% \once \override TextScript.after-line-breaking = #test-nmbrs
c''4^\markup ""
  }
}

%%%
In any case, the output of these variants is notably less screwed-up than
the original, where jumbling happens almost immediately.

My question would be: when does the evaluation of a grob's stencil normally
happen?  My guess is this normal evaluation is happening based on a
haphazard input, that using 'before-line-breaking and 'after-line-breaking
is forcing a later evaluation, at a time when grobs have been better
arranged by timing.

(Please understand that this is largely a guess.  I'm finding the code
incredible hard to follow.)

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

Re: Property/ies to control the shape of ties/slurs

[lilypond]

Am 2015-11-23 11:41, schrieb Urs Liska:

I think for now (the current project) I'll try to find a setting that
matches *most* cases and tweak the others manually. There are pretty 
few

ones in this score so it'll be OK. But maybe this really is a feature
request for a new property?



If we start something like this, I would like to add a feature that I 
miss: offsetting the endpoints of a slur/tie/... like

  \once \override Slur.left-X-offset = -1.5
This should behave like
  \shape #'((0 . 0) (? . 0) (? . 0) (-1.5 . 0)) Slur
and find correct values for the ? automatically (same for right and Y). 
This would be nice because the ? values depend on the length of the slur 
and you have to guess correct values by trial-and-error.


(I hope I didn't overlook a setting that does this ...)

Slur.positions does something similar but only for Y direction and it 
doesn't work always as I expect.


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

Re: Gounod - Le Rendez Vous

[Alberto Simões]

On 23/11/2015 00:03, Simon Albrecht wrote:
It seems that you intentionally replaced -! by -. in Valse 1, however 
the original uses them distinctly and I’d stick with that. 


Ah, I see what you mean. Wasn't aware of that symbol... shame on me :-)

Thanks
Alberto

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

Re: Gounod - Le Rendez Vous

[Alberto Simões]

Hi, Simon

On 23/11/2015 00:03, Simon Albrecht wrote:
The last measure of the Introduction actually has only two quarters 
(the half note isn’t dotted), to be complemented by the immediately 
following upbeat for Valse 1.


Damn. I though I had that correct, as I recall from when I was looking 
to it :( Thanks for pointing it up.
It seems that you intentionally replaced -! by -. in Valse 1, however 
the original uses them distinctly and I’d stick with that.
Now I got confused. will check what -! is for in the docs to try to 
understand your comment. :-)



The hairpins in Valse 4 should stop at the third beat, I think.


Will need to compare with the original. Will give it another look
It would probably be better English to begin the Credits sentence with 
‘Thanks to…’. 

Hehehe, sure :-) For me it would be easier in Portuguese O:-)

See you later,
Best,
Alberto


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

Re: Gounod - Le Rendez Vous

[Alberto Simões]

Hi, Abraham,

On 22/11/2015 22:27, tisimst wrote:
I think there was a misunderstanding about the voicing in Valse 2. The 
beamed groups should NOT be in \voiceOne. They should be in \oneVoice. 
That should clean up the space taken up by their respective slurs, too.


Yep, I understood you were suggesting to make them the first voice.
I agree that making their beam go down will take less space. Will try 
later today, as that is quite fast.


Nevertheless, I would not like to join notes in, for example, measures 
5, 7 or 21 (Valse 2). I really thing this distinction might be relevant, 
expressing that the ones joined together can be played with the same 
"force", but that when they are separated, the melody is only the upper 
voice (my humble opinion, but as the original typeset back me, I will 
keep them as they are). :-) :-)


Thanks,
Alberto

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

Re: Fwd: Slash chords

[jmechmech]

Perfect for a snippet : 



\version "2.18.2"

#(define (lower-extension pitch chbass)
   "Return lowered markup for pitch note name."
   #{
 \markup \raise #-1.9 \halign #0.2
 #(note-name->markup pitch chbass)
   #})


\layout {
  \context {
\ChordNames
slashChordSeparator = \markup {
  % the \hspace commands simulate kerning
  \hspace #-1.2
  \lower #0.8 \rotate#-35 \scale #'(1 . 1.3) "|"
  \hspace #-1.4
}
chordNoteNamer = #lower-extension
  }
}

\score {
  \new StaffGroup <<
\chords {
  f2.:m c4:7/e c2:maj7
  f2:m/a f/g c:7/g c:7/e e/f
}
\new Staff { \key aes \major \time 3/4 c'4 aes'2 c'4 bes'2 r4 r r r r r
r r r  }
  >>
  \layout { }
}





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Fwd-Slash-chords-tp183832p183985.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: Property/ies to control the shape of ties/slurs

[Urs Liska]

Am 23.11.2015 um 10:49 schrieb Noeck:
> Hi Urs,
>
> you probably know these pages:
>
> http://www.lilypond.org/doc/v2.18/Documentation/internals/slur
> http://www.lilypond.org/doc/v2.18/Documentation/internals/slur_002dinterface
> http://www.lilypond.org/doc/v2.18/Documentation/internals/tie
> http://www.lilypond.org/doc/v2.18/Documentation/internals/tie_002dinterface
>
> It looks to me like the Slur.details or the ratio could be a way to
> tweak slur shapes in general. However, for me it would be a lot of
> guessing and try-and-error to find out what the effects are.
>
> For me your example looked like you want to make the vertical extend
> larger, 'ratio' had a promising description but I could not see any effect.

Actually the description suggests that the steepness at the edges should
be changed, something like

 ___
|   |

instead of

 ___
/   \

for a higher ratio. But as you I didn't see any noticeable difference  -
and it wouldn't be what I need.

height-limit is actually much closer, and I don't know how I could
manage to misread its description.

Unfortunately I don't seem to find a setting that is completely
satisfying. If I increase height-limit by a value that has the desired
effect on the long ties I showed in the images it makes the shorter ties
way too high.

I have the impression that in addition to height-limit we should have a
property that doesn't operate on the absolute height of the tie but on
the relative slope, so longer ties are allowed to be higher than shorter
ones.

I think for now (the current project) I'll try to find a setting that
matches *most* cases and tweak the others manually. There are pretty few
ones in this score so it'll be OK. But maybe this really is a feature
request for a new property?

Best
Urs

>
> Cheers,
> Joram
>
> ___
> 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: Property/ies to control the shape of ties/slurs

[David Kastrup]

Urs Liska  writes:

> Am 23.11.2015 um 10:39 schrieb David Kastrup:
>> Urs Liska  writes:
>>
>>> I don't seem to be able to find the right property to control the shape
>>> of ties.
>>>
>>> I would like to make the default appearance of ties less flat than what
>>> you see in the first attachment. I *think* what I want is having a
>>> steeper slope. But reading through the IR for tie and tie-interface I
>>> didn't see anything.
>>>
>>> Using
>>> \shape #'((0 . 0) (0 . .75) (0 . .75) (0 . 0)) Tie
>>>
>>> results in the second attachment, which is what I'd like to achieve. But
>>> I don't want to use \shape but set some properties so I can put it in a
>>> stylesheet.
>>>
>>> Any suggestions?
>> Uh, \shape ... Tie _is_ an override.  You don't get closer to "set some
>> properties" than that.
>>
>
> Maybe I wasn't clear: I want to alter the default shape of ties to have
> a steeper slope. \shape is not an override but a \once \override and has
> to be applied to individual ties. But I want to change the appearance in
> a stylesheet.

\once is ignored in context definitions/modifications.

At any rate, you can also play with settings height-limit and ratio.

-- 
David Kastrup

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

Re: Property/ies to control the shape of ties/slurs

[Noeck]

Hi Urs,

you probably know these pages:

http://www.lilypond.org/doc/v2.18/Documentation/internals/slur
http://www.lilypond.org/doc/v2.18/Documentation/internals/slur_002dinterface
http://www.lilypond.org/doc/v2.18/Documentation/internals/tie
http://www.lilypond.org/doc/v2.18/Documentation/internals/tie_002dinterface

It looks to me like the Slur.details or the ratio could be a way to
tweak slur shapes in general. However, for me it would be a lot of
guessing and try-and-error to find out what the effects are.

For me your example looked like you want to make the vertical extend
larger, 'ratio' had a promising description but I could not see any effect.

Cheers,
Joram

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

Re: Property/ies to control the shape of ties/slurs

[Marc Hohl]

Am 23.11.2015 um 10:45 schrieb Urs Liska:



Am 23.11.2015 um 10:39 schrieb David Kastrup:

Urs Liska  writes:


I don't seem to be able to find the right property to control the shape
of ties.

I would like to make the default appearance of ties less flat than what
you see in the first attachment. I *think* what I want is having a
steeper slope. But reading through the IR for tie and tie-interface I
didn't see anything.

Using
 \shape #'((0 . 0) (0 . .75) (0 . .75) (0 . 0)) Tie

results in the second attachment, which is what I'd like to achieve. But
I don't want to use \shape but set some properties so I can put it in a
stylesheet.

Any suggestions?

Uh, \shape ... Tie _is_ an override.  You don't get closer to "set some
properties" than that.



Maybe I wasn't clear: I want to alter the default shape of ties to have
a steeper slope. \shape is not an override but a \once \override and has
to be applied to individual ties. But I want to change the appearance in
a stylesheet.



There is Tie.details.height-limit that is set to 1.
Perhaps the slope increases if you encrease height-limit?

(Not tested.)

HTH,

Marc


Urs

___
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

function to replace notes by rests

[Marc Hohl]

Hi list,

I have a melody with some spoken passages, written like this:

c4 d e f \xNotes { b b b b } f e d c

Now I need a midi file that contains the "normal" notes only:

c4 d e f r r r r f e d c

As the file is a bit lengthy, I think of a way to just redefine
\xNotes to change every note to its corresponding rest, instead of 
rewriting the whole file (or using sed or any other external script).


Has anyone a scheme routine at hand that does exactly this job?

I remember vaguely that there has been something like this on the 
archives, but I did not find it again ...


TIA,

Marc

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

Re: Property/ies to control the shape of ties/slurs

[Urs Liska]

Am 23.11.2015 um 10:39 schrieb David Kastrup:
> Urs Liska  writes:
>
>> I don't seem to be able to find the right property to control the shape
>> of ties.
>>
>> I would like to make the default appearance of ties less flat than what
>> you see in the first attachment. I *think* what I want is having a
>> steeper slope. But reading through the IR for tie and tie-interface I
>> didn't see anything.
>>
>> Using
>> \shape #'((0 . 0) (0 . .75) (0 . .75) (0 . 0)) Tie
>>
>> results in the second attachment, which is what I'd like to achieve. But
>> I don't want to use \shape but set some properties so I can put it in a
>> stylesheet.
>>
>> Any suggestions?
> Uh, \shape ... Tie _is_ an override.  You don't get closer to "set some
> properties" than that.
>

Maybe I wasn't clear: I want to alter the default shape of ties to have
a steeper slope. \shape is not an override but a \once \override and has
to be applied to individual ties. But I want to change the appearance in
a stylesheet.

Urs

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

Re: question about overrides within repeats

[David Kastrup]

Werner LEMBERG  writes:

>> Well, System::post_processing ends by creating the stencils of a
>> system in reverse order.  That's probably not helping.
>
> A bug?

No, there is no guaranteed order of stencilization.  But making stuff
more random gratuitously is still going to annoy people.

-- 
David Kastrup

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

Re: Property/ies to control the shape of ties/slurs

[David Kastrup]

Urs Liska  writes:

> I don't seem to be able to find the right property to control the shape
> of ties.
>
> I would like to make the default appearance of ties less flat than what
> you see in the first attachment. I *think* what I want is having a
> steeper slope. But reading through the IR for tie and tie-interface I
> didn't see anything.
>
> Using
> \shape #'((0 . 0) (0 . .75) (0 . .75) (0 . 0)) Tie
>
> results in the second attachment, which is what I'd like to achieve. But
> I don't want to use \shape but set some properties so I can put it in a
> stylesheet.
>
> Any suggestions?

Uh, \shape ... Tie _is_ an override.  You don't get closer to "set some
properties" than that.

-- 
David Kastrup

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

[WAS] Staff ends before \clef, \time and \key

[Pierre Perol-Schneider]

Hi,

See:
http://lilypond.1069038.n5.nabble.com/Staff-ends-before-clef-time-and-key-td174133.html#a174182

Reminder:

%% Here works fine:
\version "2.18.2"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
}

%% Bug here:
\version "2.19.32"
{
  \key e\major
   \time 3/4
   % mes.98
s2.
  \bar "||"
  \key e \minor
  %% workaround but not satisfying:
  %\grace s4
}

Does anyone has a better workaround/solution ?

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

Property/ies to control the shape of ties/slurs

[Urs Liska]

I don't seem to be able to find the right property to control the shape
of ties.

I would like to make the default appearance of ties less flat than what
you see in the first attachment. I *think* what I want is having a
steeper slope. But reading through the IR for tie and tie-interface I
didn't see anything.

Using
\shape #'((0 . 0) (0 . .75) (0 . .75) (0 . 0)) Tie

results in the second attachment, which is what I'd like to achieve. But
I don't want to use \shape but set some properties so I can put it in a
stylesheet.

Any suggestions?

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

Re: missing stem

[Urs Liska]

Hi Bogi,

regarding two of the comments on your request you may also wish to read
the following (temporary) pages:

Am 23.11.2015 um 01:14 schrieb Simon Albrecht:
> first: your code example can be made much easier to read if you add
> some spaces and line breaks, and get indenting right (this is done
> automatically by Frescobaldi, a great program for working with
> LilyPond files ):

https://bookbranches.openlilylib.org/introduction/toolchain/code-structure.html

Am 23.11.2015 um 01:12 schrieb Andrew Bernard:
>
> Allow me also to recommend the development releases - in general they
> are of excellent quality and really very stable for most practical
> purposes.
>
> Andrew
>
>

https://bookbranches.openlilylib.org/introduction/toolchain/lilypond.html

Urs

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