[no subject]

[Mátyás Seress]

Hi guys,

I just downloaded the Lilypond Notation Reference pdf for version 2.19.38
from here:
http://www.lilypond.org/doc/v2.19/Documentation/notation.pdf

and I noticed that in the Table of Contents the page numbers next to the
entries are not clickable hyperrefs like in previous verisons.

Do you know who could fix this? because it'd facilitate the navigation a
great deal.

Thank you! :)

Mat

Ezt az e-mailt egy Avast védelemmel rendelkező, vírusmentes számítógépről
küldték.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

problems with midi2ly

[mark damerell]

BUMP: please where is the manual?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: problems with midi2ly

[David Kastrup]

mark damerell  writes:

> BUMP: please where is the manual?

http://www.lilypond.org/doc/v2.18/Documentation/usage/invoking-midi2ly

-- 
David Kastrup

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

playback time

[Martin Tarenskeen]

Hi,

I know close to nothing about scheme programming. But I had an idea about 
a feature that is probably possible with a little scheme magick:


What I would like is a scheme function that calculates, based on the 
metronome tempi, the time that has passed since the beginning of a score. 
Then I would like to use that in a markup attached to a note. So that I 
can print something like 2'45" somewhere above a staff. Useful if you want 
to find the location of a musical passage on paper in the score when 
playing back an audio recording or midifile.


Or it could be used to indicate the total duration of a piece at the end 
of a score, something that I have often seen in scores by Bartok.


Maybe there is already a snippet for something like this, or maybe some of 
the scheme programmers here want to give it a try?


Thanks,

Martin

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

Re: grace-note spacing and triplets

[Jan-Peter Voigt]

Hi Simon,

thank you for your snippet! In my case, I will use the extra-offset 
variant, but I'll take yours for future use :-)


As there is a whole orchestra between flute and voice, I use this as 
acceptable tweak:


  \once \override NoteHead.extra-offset = #'(-1.5 . 0)
  \once \override Stem.extra-offset = #'(-1.5 . 0)
  \once \override Flag.extra-offset = #'(-1.5 . 0)
  \once \shape #'((-1.5 . 0) (-1.1 . -0.3) (-.7 . -0.3) (-0.3 . 0)) Slur

If one is interested, I attached a file, where I use the 
edition-engraver to apply this tweak.


Cheers
Jan-Peter

Am 22.03.2016 um 19:35 schrieb Simon Albrecht:

Hi Jan-Peter,

On 22.03.2016 15:10, Jan-Peter Voigt wrote:

Hi all,

I have a problem spacing grace notes under a series of triplets. In
the example, the grace notes produce a big gap between the tuplets or
collide with the accidentals.


It’s an annoying bug that this isn’t handled nicely, and there is no
nice workaround either. I could only concoct the following hack:

%%%
\version "2.19.38"

pseudograce =
#(define-music-function (parser location music) (ly:music?)
#{
  \tiny
  \temporary\stemUp
  \temporary\offset length -1 Stem

  $music
  \normalsize
  \revert Stem.direction
  \revert Stem.length
#})

% triplets played by the flute
flute = \new Staff \with {
   \tupletSpan 8
   beamExceptions = #'((end .
 (
   ((1 . 24) . (3 3 3 3 3 3 3 3))
   )))
} \tuplet 3/2 {
   gis'16( f'' e'') d''( c'' b') a'( gis' fis')
}

% sung words with grace notes
melody = \new Staff \new Voice {
   \autoBeamOff
   d''8*6/10 \pseudograce { c''16*4/5( } bis'8*6/10) \pseudograce
{a'16(}  gis'8)
} \addlyrics { Je -- su, ach! }

% in this score, the grace notes produce gaps between the tuplets
\score {
   <<
 \flute
 \melody
   >>
}
%%%

v2.19.25 is needed because offsetting Stem length only became possible
through issue 4516. Thanks David!

HTH, Simon


\version "2.19.38"
% include path to openlilylib and openlilylib/oll-core is needed!
\include "edition-engraver/edition-engraver.ily"

% I only use the edition-engraver in the Staff context
\consistEE Staff

\addEdition grace
\editionModList grace grace.spacing.Staff.B {
  \once \override NoteHead.extra-offset = #'(-1.5 . 0)
  \once \override Stem.extra-offset = #'(-1.5 . 0)
  \once \override Flag.extra-offset = #'(-1.5 . 0)
  \once \shape #'((-1.5 . 0) (-1.1 . -0.3) (-.7 . -0.3) (-0.3 . 0)) Slur
} #`((1 . ,(ly:make-moment 1/8 -1/16))(1 . ,(ly:make-moment 2/8 -1/16)))

% triplets played by the flute
flute = \new Staff \with {
  \tupletSpan 8
  beamExceptions = #'((end .
(
  ((1 . 24) . (3 3 3 3 3 3 3 3))
  )))
} \tuplet 3/2 {
  gis'16( f'' e'') d''( c'' b') a'( gis' fis')
}

% sung words with grace notes
melody = \new Staff \new Voice {
  \autoBeamOff
  d''8 \grace {c''16(}  bis'8) \grace {a'16(}  gis'8)
} \addlyrics { Je -- su, ach! }

% in this score, the grace notes produce gaps between the tuplets
\score {
  <<
\flute
\melody
  >>
}

% in this score the grace note-collision with accidentals is avoided with the tweak above
\score {
  <<
\flute
\melody
  >>
  \layout {
\context {
  \Score
  proportionalNotationDuration = #(ly:make-moment 1/24)
  \override SpacingSpanner.strict-note-spacing = ##t
  \editionID grace.spacing
}
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: grace-note spacing and triplets

[Jan-Peter Voigt]

Hi Harm,

this is interesting!? This is another very smart solution, but why/how 
does this work?

I will look for a way, to add the TextScript with the edition-engraver ...
The rest-solution is handy, but OTOH not easily applicable "externally". 
By the way, I tried succesfully 's4' instead of '\once \omit Rest r16*3/2'.


Thank you for these thoughts/snippet!

Cheers
Jan-Peter



Am 23.03.2016 um 01:31 schrieb Thomas Morley:

2016-03-22 15:10 GMT+01:00 Jan-Peter Voigt :

Hi all,

I have a problem spacing grace notes under a series of triplets. In the
example, the grace notes produce a big gap between the tuplets or collide
with the accidentals.

As this situation is evident a few times, I will probably use extra-offset
and place either the grace notes or the accidentals aside. So my question
is, how would you typesetters solve this case?

TIA
Jan-Peter



Hi Jan-Peter,

some thoughts on a minimal example...

\version "2.18.2"

%% for comparability
%% without any override:
{ \grace { c''16 s4 }  bis'8 }


myLayout = \layout { \override Score.SpacingSpanner.strict-note-spacing = ##t }

%% collision
\score { { \grace { c''16 }  bis'8 } \myLayout }

%% returns:
%% programming error: Cannot determine neighbors for floating column.
%% this was my first thought, no idea what's wrong, never seen this error before
\score { { \grace { c''16 s4 }  bis'8 } \myLayout }

%% not sure why this works
%% textLengthOn is _not_ set
\score { { \grace { c''16-\markup \hspace #3 }  bis'8 } \myLayout }

%% inserting a Rest works
%% r8 is too much r16 to less
%% thus scaling to avoid the dot
\score { { \grace { c''16 \once \omit Rest r16*3/2 }  bis'8 } \myLayout }


HTH a bit,
   Harm




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

Re: mute percussion notation

[Bernard]

Hi Colin,
It seems that the Percussion Notes table A.15 in the NR has some 
problems, in that the conga notes aren't visibly different. This 
snippet works for me:

*
\version "2.19.37"

\new DrumStaff  \with {
  drumStyleTable  = #congas-style
}
 <<
  \drummode {
 cghm4 cghm1 % muted
\bar "||"
  cgh4 cgh1 % open
}
 >>
**


This works fine for me also, thanks.

But for me it is not sufficient to create Djembé drumnotes.

I followed the link Thomas Morley gave me previous to customize percussion :

http://www.lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves

Which brought me very far.

I could even customize the markup of each (drum)note with info from 
http://lilypond-cookbook.tumblr.com/


I am very, very close. I could use the predefined bassdrum (bd) and 
bassdrum mute (bdm) the note image is ok, the mute token is correct. But 
I have to choose one specific staff line where the note is displayed. 
But the Djembé has three different kind of note, each one I would like 
to place on a different staffline. So I have to define my own drumnote.


Lilypond is highly flexible and many drumnotes are predefined. But I 
could not find info how to define my own drumnote.


I tried :



\version "2.18.2"

#(define mydrums '(
 (bassdrumdefault   #f   -1)
 (slap default   #f  0)))
one = \drummode {  bd  slap  }

\new DrumStaff
  \with {
  \override StaffSymbol #'line-count = #3
 }
   <<
  \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)

  \new DrumVoice { \voiceOne \one }
>>

-

But this results an error. althougth drumnote "slap" is defined it can 
not be used.

The error message with the use of "slap" was : unrecognised string
This example was based on :

http://www.lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves

Somewhere the "slap" note have to predefined, as the bassdrum note is. 
But how?


Thanks for all your help until now.



Cheers,
Colin





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

Re:

[Phil Holmes]

Looks like clicking on contents entries stopped working between 19.36 and 19.37 
- presumably as a result of the change to XeTeX.  Masamichi - do you have any 
idea about what could have caused this?

--
Phil Holmes


  - Original Message - 
  From: Mátyás Seress 
  To: lilypond-user 
  Sent: Wednesday, March 23, 2016 7:33 AM


  Hi guys,


  I just downloaded the Lilypond Notation Reference pdf for version 2.19.38 
from here:
  http://www.lilypond.org/doc/v2.19/Documentation/notation.pdf


  and I noticed that in the Table of Contents the page numbers next to the 
entries are not clickable hyperrefs like in previous verisons.


  Do you know who could fix this? because it'd facilitate the navigation a 
great deal.


  Thank you! :)


  Mat


Ezt az e-mailt egy Avast védelemmel rendelkező, vírusmentes 
számítógépről küldték. 
www.avast.com  



--


  ___
  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: mute percussion notation

[David Kastrup]

Bernard  writes:

> Hi Colin,
>> It seems that the Percussion Notes table A.15 in the NR has some
>> problems, in that the conga notes aren't visibly different. This
>> snippet works for me:
>> *
>> \version "2.19.37"
>>
>> \new DrumStaff  \with {
>>   drumStyleTable  = #congas-style
>> }
>>  <<
>>   \drummode {
>>  cghm4 cghm1 % muted
>> \bar "||"
>>   cgh4 cgh1 % open
>> }
>>  >>
>> **
>>
> This works fine for me also, thanks.
>
> But for me it is not sufficient to create Djembé drumnotes.
>
> I followed the link Thomas Morley gave me previous to customize percussion :
>
> http://www.lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves
>
> Which brought me very far.
>
> I could even customize the markup of each (drum)note with info from
> http://lilypond-cookbook.tumblr.com/
>
> I am very, very close. I could use the predefined bassdrum (bd) and
> bassdrum mute (bdm) the note image is ok, the mute token is
> correct. But I have to choose one specific staff line where the note
> is displayed. But the Djembé has three different kind of note, each
> one I would like to place on a different staffline. So I have to
> define my own drumnote.
>
> Lilypond is highly flexible and many drumnotes are predefined. But I
> could not find info how to define my own drumnote.
>
> I tried :
>
> 
>
> \version "2.18.2"
>
> #(define mydrums '(
>  (bassdrumdefault   #f   -1)
>  (slap default   #f  0)))
> one = \drummode {  bd  slap  }
>
> \new DrumStaff
>   \with {
>   \override StaffSymbol #'line-count = #3
>  }
><<
>   \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
>
>   \new DrumVoice { \voiceOne \one }
>>>
>
> -
>
> But this results an error. althougth drumnote "slap" is defined it can
> not be used.

It can once it has been input.  The drumStyleTable tells LilyPond how to
typeset drum notes once they are in the music.  It doesn't tell LilyPond
what drum notes are permitted in music.  So you need to use the existing
names, or amend the parser.

Amending the parser is done with

drumPitchNames.slap = #'slap

Note that you can define multiple names for the same definition in the
drum style table, so you can also add

drumPitchNames.sl = #'slap

and this will work without further changes to mydrums.

-- 
David Kastrup

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

Re: Dynamics placement

[Thomas Morley]

2016-03-23 2:56 GMT+01:00 Graham King :

> Here is a compilable example.  It is a bit long, but I think it is pretty
> close to minimal.
>
> In its defence: the first 32 lines are, effectively, snippet 739 modified
> to produce "dynamic text" instead of "text dynamic" (in this case, "mp
> dolce" instead of, say, "meno f").
> 
>
> Hi Graham,

a minimal example would have been:

\version "2.19.38"

music = { g'8(\p f'!) s2. }
\new StaffGroup \new Staff \music

The code from the lsr-snippet has nothing to do with it.
Below a little longer commented example.

Clearly a bug, please report.

%% Following note is moved away by DynamicText
%%
%% Bad behaviour goes away if the second note has no Accidental
%% or \voiceTwo is used
%% or if \new StaffGroup is deleted or replaced by \new ChoirStaff
%% \new GrandStaff does not work as well, though
%%
%% Worked fine with "2.18.2"

\version "2.19.38"

music = {
%% bad:
g'8(\p f'!) s2.
%% good:
%\voiceTwo
%g'8(\p f'!) s2.
}

\new StaffGroup
  \new Staff \music

%% Not required to trigger bad behaviour
%% Better visible, though
\layout { \override DynamicText.self-alignment-X = #LEFT }

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

Re: Dynamics placement

[Xavier Scheuer]

On 22 March 2016 at 23:41, Graham King  wrote:
>
> I've adopted Simon Albrecht's excellent suggestion in an earlier
> thread [1], and am now using code based on snippet 739 [2] to typeset
> some long dynamic markings.  This has solved a host of layout problems;
> however, it has introduced this nasty spacing issue:
>
>
> r2 r8 bes8(\mfdolce a bes) | g'4-.( f-.)
>
> where \mfdolce is the result of snippet 739's make-dynamic-script.
>
> Since the dynamic applies to the phrase rather than just the first
> note, is there a way to prevent it pushing the second note to the right?
> I would like it to overlap the second (and, if necessary, subsequent)
> note(s) of this phrase.  I've looked at section 4.4.3 of the Learning
> Manual [3] and things don't appear promising.

Hi,

I use Graham (Percival)'s "make-dynamic-extra", which has two main
advantages :
1. The dynamic only, and not the whole "dynamic + text", is centered
on the note (i.e. like a "normal" dynamic).
2. The dynamic is affecting the MIDI.

http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg00335.html

IIRC it did not have any drawbacks, but I haven't tried it recently
(maybe new versions of LilyPond brought some internal changes
unsuitable to "make-dynamic-extra").

Cheers,
Xavier

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

Re: mute percussion notation

[Simon Albrecht]

On 23.03.2016 11:23, David Kastrup wrote:

Bernard  writes:


Lilypond is highly flexible and many drumnotes are predefined. But I
could not find info how to define my own drumnote.

I tried :



\version "2.18.2"

#(define mydrums '(
  (bassdrumdefault   #f   -1)
  (slap default   #f  0)))
one = \drummode {  bd  slap  }

\new DrumStaff
   \with {
   \override StaffSymbol #'line-count = #3
  }
<<
   \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)

   \new DrumVoice { \voiceOne \one }
-

But this results an error. althougth drumnote "slap" is defined it can
not be used.

It can once it has been input.  The drumStyleTable tells LilyPond how to
typeset drum notes once they are in the music.  It doesn't tell LilyPond
what drum notes are permitted in music.  So you need to use the existing
names, or amend the parser.

Amending the parser is done with

drumPitchNames.slap = #'slap

Note that you can define multiple names for the same definition in the
drum style table, so you can also add

drumPitchNames.sl = #'slap

and this will work without further changes to mydrums.


Isn’t this the very latest 2.19.39 awesome alist syntax? Because the 
snip above states \version "2.18.2".


Best, Simon

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

Re: mute percussion notation

[Bernard]

On 23-03-16 11:23, David Kastrup wrote:

Bernard  writes:

Lilypond is highly flexible and many drumnotes are predefined. But I 
could not find info how to define my own drumnote. I tried : 
 \version "2.18.2" 
#(define mydrums '( (bassdrum default #f -1) (slap default #f 0))) 
one = \drummode { bd slap } \new DrumStaff \with { \override 
StaffSymbol #'line-count = #3 } << \set DrumStaff.drumStyleTable = 
#(alist->hash-table mydrums) \new DrumVoice { \voiceOne \one }

-

But this results an error. althougth drumnote "slap" is defined it can
not be used.

It can once it has been input.  The drumStyleTable tells LilyPond how to
typeset drum notes once they are in the music.  It doesn't tell LilyPond
what drum notes are permitted in music.  So you need to use the existing
names, or amend the parser.

Amending the parser is done with

drumPitchNames.slap = #'slap

Note that you can define multiple names for the same definition in the
drum style table, so you can also add

drumPitchNames.sl = #'slap

and this will work without further changes to mydrums.


Could you give a working code sample, for the syntax?
In a drumnote like bassdrum or bassdrummute or sidestick a lot of info 
is defined?

How can I define this myself.

F.e. In Djembé I would like (sorry I could not create an image file, so 
please compile it to see visual what I need) are :

\version "2.18.2"

%\relative c' {

 {
  e' b' f''
}
\addlyrics {
  bas tone slap
}

But then with 3 staff lines, percussion key, the mute token, and the use 
sidestick (ss) drum note. This last request requires the drummode as we 
use, to be able to use existing drumnotes.
So could you give an example how I would define f.e. dslapmute (Djembé 
slap mute) with abbrevation dsm?


Thanks.



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

Re: Dynamics placement

[Graham King]

On Tue, 2016-03-22 at 22:18 -0400, Kieren MacMillan wrote:

> Hi Graham,
> 
> > The unwelcome spacing between the 4th and 5th notes goes away if one:
> 
> … uses
> 
> mpdolce = -\tweak X-extent #empty-interval #(make-dynamic-atr-script "mp" 
> "dolce”)
> 

Thanks Kieran,
that's very helpful.  I've added

 (ly:music-set-property! dynamic 'tweaks (acons 'X-extent 0
(ly:music-property dynamic 'tweaks)))

in the appropriate place in the snippet.  I noted some fiddling with
X-extent in one of the snippets, but didn't understand it, and got a bit
confused by thinking that it was already set to zero (well, negative
infinity) according to the discussion of grob sizing in the Learning
Manual (section 4.4.3).

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

Re: mute percussion notation

[David Kastrup]

Simon Albrecht  writes:

> On 23.03.2016 11:23, David Kastrup wrote:
>
>> It can once it has been input.  The drumStyleTable tells LilyPond how to
>> typeset drum notes once they are in the music.  It doesn't tell LilyPond
>> what drum notes are permitted in music.  So you need to use the existing
>> names, or amend the parser.
>>
>> Amending the parser is done with
>>
>> drumPitchNames.slap = #'slap
>>
>> Note that you can define multiple names for the same definition in the
>> drum style table, so you can also add
>>
>> drumPitchNames.sl = #'slap
>>
>> and this will work without further changes to mydrums.
>
> Isn’t this the very latest 2.19.39 awesome alist syntax? Because the
> snip above states \version "2.18.2".

No, this was issue 3748.

commit a7eb9033f29d35d110afd1730a238f5c50e00369
Author: David Kastrup 
Date:   Sun Dec 22 20:38:22 2013 +0100

Issue 3748: Allow assignments with property paths to use x.y.z = value 
syntax

This is actually an embarrassing oversight in issue 2883: while it
became possible to rewrite

markup-system-spacing #'minimum-distance = #25
as
markup-system-spacing minimum-distance = #25

it has been overlooked to allow for the obvious

markup-system-spacing.minimum-distance = #25


This commit is indeed version 2.19.0, but there is also the cherry-picked

commit eff4ab669513f38f14cc6d01b24bead358124da1
Author: David Kastrup 
Date:   Sun Dec 22 20:38:22 2013 +0100

Issue 3748: Allow assignments with property paths to use x.y.z = value 
syntax

This is actually an embarrassing oversight in issue 2883: while it
became possible to rewrite

markup-system-spacing #'minimum-distance = #25
as
markup-system-spacing minimum-distance = #25

it has been overlooked to allow for the obvious

markup-system-spacing.minimum-distance = #25



in 2.18.0.  So this oversight has been corrected in 2.18.0 already.

The new developments allow numbers into alist indexes, and actually
referencing individual alist members syntactically.  But the assignment
syntax for symbols as indexes (and symbol list arguments) was
established earlier.  I think that the old

drumPitchNames #'slap = #'slap

has worked for a long long time (quite earlier than 2.12).  But it's
quite underdocumented.  I think it caught me by surprise when I first
discovered it in the parser.

-- 
David Kastrup

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

Re: mute percussion notation

[David Kastrup]

Bernard  writes:

>> Amending the parser is done with
>>
>> drumPitchNames.slap = #'slap
>>
>> Note that you can define multiple names for the same definition in the
>> drum style table, so you can also add
>>
>> drumPitchNames.sl = #'slap
>>
>> and this will work without further changes to mydrums.
>>
> Could you give a working code sample, for the syntax?

Uh, one just takes your example and adds the indicated line(s).

\version "2.18.2"

#(define mydrums '(
 (bassdrumdefault   #f   -1)
 (slap default   #f  0)))

drumPitchNames.slap = #'slap

one = \drummode {  bd  slap  }

\new DrumStaff
  \with {
  \override StaffSymbol #'line-count = #3
 }
   <<
  \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)

  \new DrumVoice { \voiceOne \one }
>>

works just fine.

> In a drumnote like bassdrum or bassdrummute or sidestick a lot of info
> is defined?
> How can I define this myself.

Uh, you did already?

> F.e. In Djembé I would like (sorry I could not create an image file,
> so please compile it to see visual what I need) are :
> \version "2.18.2"
>
> %\relative c' {
>
>  {
>   e' b' f''
> }
> \addlyrics {
>   bas tone slap
> }
>
> But then with 3 staff lines, percussion key, the mute token, and the
> use sidestick (ss) drum note. This last request requires the drummode
> as we use, to be able to use existing drumnotes.
> So could you give an example how I would define f.e. dslapmute (Djembé
> slap mute) with abbrevation dsm?

Uh, is there _anything_ actually unclear or do you just want me to do
all the work?

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

Re: Dynamics placement

[Graham King]

(bug-lilypond: a regression with note-spacing in proximity to dynamic
text.)

On Wed, 2016-03-23 at 11:38 +0100, Thomas Morley wrote:


> a minimal example would have been:
> 
> \version "2.19.38"
> 
> music = { g'8(\p f'!) s2. }
> \new StaffGroup \new Staff \music

Wow.  To get to that, I think I would have needed to know the cause of
the problem already.

> 
> 
> The code from the lsr-snippet has nothing to do with it.
> 
> Below a little longer commented example.
> 
> 
> Clearly a bug, please report.

Copied to bug-lilypond.

> 
> %% Following note is moved away by DynamicText
> %%
> %% Bad behaviour goes away if the second note has no Accidental 
> %% or \voiceTwo is used
> %% or if \new StaffGroup is deleted or replaced by \new ChoirStaff 
> %% \new GrandStaff does not work as well, though
> %%
> %% Worked fine with "2.18.2"
> 
> \version "2.19.38"
> 
> music = {
> %% bad:
> g'8(\p f'!) s2.
> %% good:
> %\voiceTwo
> %g'8(\p f'!) s2.
> }
> 
> \new StaffGroup
>   \new Staff \music
>   
> %% Not required to trigger bad behaviour
> %% Better visible, though
> \layout { \override DynamicText.self-alignment-X = #LEFT }
> 
> 
> Cheers,
> 
>   Harm
> 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: mute percussion notation

[Thomas Morley]

2016-03-23 12:45 GMT+01:00 David Kastrup :

> I think that the old
>
> drumPitchNames #'slap = #'slap
>
> has worked for a long long time (quite earlier than 2.12).  But it's
> quite underdocumented.  I think it caught me by surprise when I first
> discovered it in the parser.

/lilypond-git (master)$ git grep 'drumPitchNames'
Documentation/misc/ChangeLog-2.10:  * ly/drumpitch-init.ly
(drumPitchNames): add tamtam.
lily/parser.yy: SCM nn = parser->lexer_->lookup_identifier
("drumPitchNames");
lily/parser.yy: SCM nn = parser->lexer_->lookup_identifier
("drumPitchNames");
ly/drumpitch-init.ly:drumPitchNames =

Is not exactly what I would call _under_documented.

Though, I'm not sure I understand all yet.

Do the following two lines the same?
drumPitchNames.bla = #'bla
#(set! drumPitchNames (acons 'foo 'foo drumPitchNames))

How to put in a list? The following looks a bit clumsy.
#(for-each
   (lambda (sys) (set! drumPitchNames (acons sys sys drumPitchNames)))
   '(aa ab ac ad ae af)))
#(pretty-print (take drumPitchNames 10))

Thanks,
  Harm

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

Re: mute percussion notation

[David Kastrup]

Thomas Morley  writes:

> 2016-03-23 12:45 GMT+01:00 David Kastrup :
>
>> I think that the old
>>
>> drumPitchNames #'slap = #'slap
>>
>> has worked for a long long time (quite earlier than 2.12).  But it's
>> quite underdocumented.  I think it caught me by surprise when I first
>> discovered it in the parser.
>
> /lilypond-git (master)$ git grep 'drumPitchNames'
> Documentation/misc/ChangeLog-2.10:  * ly/drumpitch-init.ly
> (drumPitchNames): add tamtam.
> lily/parser.yy: SCM nn = parser->lexer_->lookup_identifier
> ("drumPitchNames");
> lily/parser.yy: SCM nn = parser->lexer_->lookup_identifier
> ("drumPitchNames");
> ly/drumpitch-init.ly:drumPitchNames =
>
> Is not exactly what I would call _under_documented.

I was talking about the alist assignment syntax, not drumPitchNames in
particular.

> Though, I'm not sure I understand all yet.
>
> Do the following two lines the same?
> drumPitchNames.bla = #'bla
> #(set! drumPitchNames (acons 'foo 'foo drumPitchNames))

You mean, apart from 'bla not being 'foo ?  Yes.

> How to put in a list? The following looks a bit clumsy.
> #(for-each
>(lambda (sys) (set! drumPitchNames (acons sys sys drumPitchNames)))
>'(aa ab ac ad ae af)))
> #(pretty-print (take drumPitchNames 10))

drumPitchNames.aa = #'aa
drumPitchNames.ab = #'ab
...


Programmatically, I'd not set drumPitchNames repeatedly.  Just use

drumPitchNames =
#(fold (lambda (n l) (acons n n l)) drumPitchNames '(aa ab ac ad ae af))

-- 
David Kastrup

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

Re: mute percussion notation

[Thomas Morley]

2016-03-23 13:49 GMT+01:00 David Kastrup :

> Programmatically, I'd not set drumPitchNames repeatedly.  Just use
>
> drumPitchNames =
> #(fold (lambda (n l) (acons n n l)) drumPitchNames '(aa ab ac ad ae af))


Much better.

Thanks,
  Harm

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

Re: Dynamics placement

[Thomas Morley]

2016-03-23 13:21 GMT+01:00 Graham King :
> (bug-lilypond: a regression with note-spacing in proximity to dynamic
> text.)
>
> On Wed, 2016-03-23 at 11:38 +0100, Thomas Morley wrote:
>
>
>> a minimal example would have been:
>>
>> \version "2.19.38"
>>
>> music = { g'8(\p f'!) s2. }
>> \new StaffGroup \new Staff \music
>
> Wow.  To get to that, I think I would have needed to know the cause of
> the problem already.

Nope.
I simply commented code-fragments and tried out several things.
But yes, creating minimal examples _is_ difficult sometimes and takes
some time and effort.
But if you finally managed to spot a bug, you didn't waste the time of
a developer, who already may have started to research the bug-cause or
even fixing it.

Btw, better to write a new mail to the bug-list, instead of just cc-ing them.
It makes life a little bit easier for our bug-squad-members.

Cheers,
  Harm

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

Re: Dynamics placement

[Graham King]

On Wed, 2016-03-23 at 11:47 +0100, Xavier Scheuer wrote:

> I use Graham (Percival)'s "make-dynamic-extra", which has two main
> advantages :
> 1. The dynamic only, and not the whole "dynamic + text", is centered
> on the note (i.e. like a "normal" dynamic).
> 2. The dynamic is affecting the MIDI.
> 
> 
> http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg00335.html
> 
> 
> IIRC it did not have any drawbacks, but I haven't tried it recently
> (maybe new versions of LilyPond brought some internal changes
> unsuitable to "make-dynamic-extra").

Thanks Xavier,
the code seems to work with 2.19.35, but it has no effect on the
original problem.  Nevertheless it is good to know of its existence.  
There are so many approaches to creating dynamics with text, and so much
skill and inventiveness has been applied to them over the years, that it
seems a pity that none has been internalised by lilypond.  

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

Re: mute percussion notation

[Bernard]

On 23-03-16 12:58, David Kastrup wrote:


Uh, one just takes your example and adds the indicated line(s).
Ok, thanks I got it, and it works for me now.
Uh, is there _anything_ actually unclear or do you just want me to do
all the work?


No, of course not, the syntax was only not clear to me.

I have now everything working with the following code :
--

\version "2.18.2"

mute = "+"

#(define djembe '(
 (dslapdefault   #f   2)
 (dslapmutedefault   #f   2)))


drumPitchNames.dslap  = #'dslap
drumPitchNames.dslapmute  = #'dslapmute


one = \drummode {  dslap dslapmute^\mute   }

\new DrumStaff
  \with {
  \override StaffSymbol #'line-count = #3
 }
   <<
  \set DrumStaff.drumStyleTable = #(alist->hash-table djembe)

  \new DrumVoice { \voiceOne \one }
>>


Visual it looks exactly how I would like it.  Whoh! Thanks you all!

But is there a way to make the voice more consistent, by adding the mute 
in the definition?


so I could call :
one = \drummode {  dslap dslapmute   }

instead of :
one = \drummode {  dslap dslapmute^\mute   }

And if I could add abbreviation in the definition like dslapmute as dsm, 
equal to bassdrum and bd, I would be more then happy.


Thanks again for your great support.






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

Re: mute percussion notation

[Thomas Morley]

2016-03-23 14:42 GMT+01:00 Bernard :
>
> But is there a way to make the voice more consistent, by adding the mute in
> the definition?
>
> so I could call :
> one = \drummode {  dslap dslapmute   }
>
> instead of :
> one = \drummode {  dslap dslapmute^\mute   }
>
> And if I could add abbreviation in the definition like dslapmute as dsm,
> equal to bassdrum and bd, I would be more then happy.



Hi Bernard,

you should read the relevant section of the NR and the posts of this
thread again and think about it.
Then redo it.
Maybe once more.
It's all said or linked already.

Nevertheles:

#(define djembe '(
 (dslapdefault   #f   2)
 (dslapmutedefault   "stopped"2)))


drumPitchNames.dslap  = #'dslap
drumPitchNames.dslapmute  = #'dslapmute
drumPitchNames.dsm  = #'dslapmute

one = \drummode {  dslap dsm   }

\new DrumStaff
  \with {
  \override StaffSymbol #'line-count = #3
 }
   <<
  \set DrumStaff.drumStyleTable = #(alist->hash-table djembe)

  \new DrumVoice { \voiceOne \one }
>>

-Harm

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

Re: mute percussion notation

[Pierre-Luc Gauthier]

When one remaps note names like that, is it also possible to map midi
notes to those names?

Could there be sort of a assignment somewhere between the note (e.g.
dsm or dslapmute) and the midi note (e.g. note 62 on channel 10)?

I did not find documentation on the subject.

Last week I transcribed Anderson's "The Typewriter" so this thread is
relevant to me.

Here is my MWE :

http://lilybin.com/yo9s8b/2

%%%
\version "2.18.2"

\header {
  title = \markup {\smallCaps "The Data Typewriter"}
  composer = \markup {\smallCaps "LaJoy Randallson"}
}

#(define typewriter '((key default #f  0)
  (cr default #f -2)
  (bell default #f 2)))

drumPitchNames.key = #'key
drumPitchNames.cr = #'cr
drumPitchNames.bell = #'bell

% The "key" note should use the midi note 70 or Maracas
% The "carriage return: note should use the midi note 74 or Long Guiro
% The "bell" note should use the midi note 81 or Open Triangle

percussionI = \drummode {

  \override Staff.StaffSymbol.line-positions = #'(0)
  \override Staff.BarLine.bar-extent = #'(-2 . 2)
  \set DrumStaff.drumStyleTable = #(alist->hash-table typewriter)

  key8\f^"Typewriter key click" key key key key key key key |
  key key key key key4 key8 key |
  key key key key key key key key |
  bell4\laissezVibrer^"Bell" r cr->_"Carriage return" r |
}

percussionIPart =
\new DrumStaff {
  \new DrumVoice {
\percussionI
  }
}

\score {
  \percussionIPart
  \layout {}
  \midi {}
}
%%%

Thanks
-- 
Pierre-Luc Gauthier
\version "2.18.2"

\header {
  title = \markup {\smallCaps "The Data Typewriter"}
  composer = \markup {\smallCaps "LaJoy Randallson"}
}

#(define typewriter '((key default #f  0)
  (cr default #f -2)
  (bell default #f 2)))

drumPitchNames.key = #'key
drumPitchNames.cr = #'cr
drumPitchNames.bell = #'bell

% The "key" note should use the midi note 70 or Maracas
% The "carriage return: note should use the midi note 74 or Long Guiro
% The "bell" note should use the midi note 81 or Open Triangle

percussionI = \drummode {

  \override Staff.StaffSymbol.line-positions = #'(0)
  \override Staff.BarLine.bar-extent = #'(-2 . 2)
  \set DrumStaff.drumStyleTable = #(alist->hash-table typewriter)

  key8\f^"Typewriter key click" key key key key key key key |
  key key key key key4 key8 key |
  key key key key key key key key |
  bell4\laissezVibrer^"Bell" r cr->_"Carriage return" r |
}

percussionIPart =
\new DrumStaff {
  \new DrumVoice {
\percussionI
  }
}

\score {
  \percussionIPart
  \layout {}
  \midi {}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: mute percussion notation

[David Kastrup]

Pierre-Luc Gauthier  writes:

> When one remaps note names like that, is it also possible to map midi
> notes to those names?
>
> Could there be sort of a assignment somewhere between the note (e.g.
> dsm or dslapmute) and the midi note (e.g. note 62 on channel 10)?
>
> I did not find documentation on the subject.

It would appear that midiDrumPitches are used for initializing
drumPitchTable in some context in ly/performer-init.ly so it should be
possible to add stuff to drumPitchTable in a similar manner and then
create a new drumPitchTable context property from it for some suitable
context.

You need to dig through the respective files to find all the information
I guess.

-- 
David Kastrup

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

Re: mute percussion notation

[David Kastrup]

David Kastrup  writes:

> Pierre-Luc Gauthier  writes:
>
>> When one remaps note names like that, is it also possible to map midi
>> notes to those names?
>>
>> Could there be sort of a assignment somewhere between the note (e.g.
>> dsm or dslapmute) and the midi note (e.g. note 62 on channel 10)?
>>
>> I did not find documentation on the subject.
>
> It would appear that midiDrumPitches are used for initializing
> drumPitchTable in some context in ly/performer-init.ly so it should be
> possible to add stuff to drumPitchTable in a similar manner and then

I mean, "... to midiDrumPitches in a similar manner ..."

> create a new drumPitchTable context property from it for some suitable
> context.
>
> You need to dig through the respective files to find all the information
> I guess.

-- 
David Kastrup

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

Re:

[Mátyás Seress]

Thank you for picking it up so quickly!

Ezt az e-mailt egy Avast védelemmel rendelkező, vírusmentes számítógépről
küldték.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2016-03-23 14:41 GMT+01:00 Masamichi HOSODA :

> > Looks like clicking on contents entries stopped working between 19.36
> and 19.37 - presumably as a result of the change to XeTeX.  Masamichi - do
> you have any idea about what could have caused this?
> [...snip...]
>
> For PDF document building,
> current LilyPond uses texinfo.tex ver. 2016-02-15.14.
> It cannot create any PDF links with XeTeX.
>
> Today, I've commited
> XeTeX table of contents page number link support
> to texinfo.tex.
> http://lists.gnu.org/archive/html/texinfo-commits/2016-03/msg00017.html
>
> However, still some PDF links (@xref related links)
> are not able to create with XeTeX.
> http://lists.gnu.org/archive/html/bug-texinfo/2016-03/msg00052.html
>
> Anyway, texinfo.tex that is contained by current LilyPond
> can not create any PDF links with XeTeX at present.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: mute percussion notation

[Pierre-Luc Gauthier]

> David Kastrup  writes:
>> You need to dig through the respective files to find all the information

Thanks, I'll look into those.

-- 
Pierre-Luc Gauthier

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

\balloonText does not work outside a construct

[Pierre-Luc Gauthier]

Hi,

I wonder why doesn't the \balloonText command work outside a  construct?

In the MWE included, LilyPond throws errors if you remove the < > construct.

Is it by design?

%%%
\version "2.18.2"

\score {
  \new Staff {
\new Voice \with { \consists "Balloon_engraver" }

% The example bellow is working
\balloonGrobText #'NoteHead #'(3 . 4) \markup { "Note head 1" }
g'2.

% This is only working in chord <> construct
2.

% e.g. this does not work
%a'2.-\balloonText #'(3 . -2) \markup { "Note head 3" }

  }
}
%%%

On a side note,
I brute forced the  line :
\override BalloonTextItem.annotation-balloon = ##f
for quite awhile.
I use it to remove the "square" around the balloon subject.
I guess my (second) question is: how do you guys know how many # to use if any?
What documentation would you recommend for me to demystify this?

Thanks
-- 
Pierre-Luc Gauthier
\version "2.18.2"

\score {
  \new Staff {
\new Voice \with { \consists "Balloon_engraver" }

% The example bellow is working
\balloonGrobText #'NoteHead #'(3 . 4) \markup { "Note head 1" }
g'2.

% This is only working in chord <> construct
2.

% e.g. this does not work
%a'2.-\balloonText #'(3 . -2) \markup { "Note head 3" }

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

Where is the latest articulate.ly?

[Daniel Birns]

The one I found on a mailing list from 2011 doesn’t seem to handle even slurs 
or staccato.

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

Re:

[Masamichi HOSODA]

> Looks like clicking on contents entries stopped working between 19.36 and 
> 19.37 - presumably as a result of the change to XeTeX.  Masamichi - do you 
> have any idea about what could have caused this?
[...snip...]

For PDF document building,
current LilyPond uses texinfo.tex ver. 2016-02-15.14.
It cannot create any PDF links with XeTeX.

Today, I've commited
XeTeX table of contents page number link support
to texinfo.tex.
http://lists.gnu.org/archive/html/texinfo-commits/2016-03/msg00017.html

However, still some PDF links (@xref related links)
are not able to create with XeTeX.
http://lists.gnu.org/archive/html/bug-texinfo/2016-03/msg00052.html

Anyway, texinfo.tex that is contained by current LilyPond
can not create any PDF links with XeTeX at present.

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

midi articulation

[Daniel Birns]

Hi all,

Okay, I see what articulate.ly does. However… has anyone tried to do this 
within the midi generator. I debugged the python_midi.c file, and I can see 
what it’s doing. Geez, it seems like at the point where the midi file is being 
generated, lilypond ought to know everything about what’s the score, and ought 
to be able to apply articulation easily and much more correctly at that point.

Has anyone tried doing this? My guess is it’s nowhere near as easy as I think 
it should be. But, honestly, the midi files suck. As a Sibelius user, this is a 
showstopper — Sibelius does a beautiful job at this, and it seems like it 
shouldn’t be difficult for lilypond to do the same.

I’m a software developer — not python, nor guile , but just about everything 
else, but especially C++. I could do guile and python if needed. Perhaps I 
should try this, but is there interest? Do I have time for this? And why 
haven’t the others who know a great deal more about this than I do, done this?

Thanks. No criticism at all intended: I think lilypond is amazing. 

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

Re: Where is the latest articulate.ly?

[Malte Meyn]

Am 23.03.2016 um 18:13 schrieb Daniel Birns:

The one I found on a mailing list from 2011 doesn’t seem to handle even slurs 
or staccato.


It’s part of vanilla LilyPond since version 2.14 (see 
http://lilypond.org/doc/v2.14/Documentation/changes/) and has been 
improved several times since then. And version 2.19 supports some 
articulations even without including articulate.ly (see 
http://lilypond.org/doc/v2.19/Documentation/changes/).


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

Re: Where is the latest articulate.ly?

[Daniel Birns]

I see the articulate.ly. I guess they decided against lilywrap. 

-d
> On Mar 23, 2016, at 3:23 PM, Malte Meyn  wrote:
> 
> 
> 
> Am 23.03.2016 um 18:13 schrieb Daniel Birns:
>> The one I found on a mailing list from 2011 doesn’t seem to handle even 
>> slurs or staccato.
> 
> It’s part of vanilla LilyPond since version 2.14 (see 
> http://lilypond.org/doc/v2.14/Documentation/changes/) and has been improved 
> several times since then. And version 2.19 supports some articulations even 
> without including articulate.ly (see 
> http://lilypond.org/doc/v2.19/Documentation/changes/).
> 
> ___
> 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: midi articulation

[Malte Meyn]

Am 23.03.2016 um 18:21 schrieb Daniel Birns:

Okay, I see what articulate.ly does. However… has anyone tried to do this 
within the midi generator.


I think so: see the second-to-last bullet point at 
http://lilypond.org/doc/v2.19/Documentation/changes/



But, honestly, the midi files suck. As a Sibelius user, this is a showstopper — 
Sibelius does a beautiful job at this, and it seems like it shouldn’t be 
difficult for lilypond to do the same.


Are you sure this is only the midi files? I think the quality of the 
sound fonts is at least equally important.



And why haven’t the others who know a great deal more about this than I do, 
done this?


Probably more people focus on LilyPond’s goal to get the best possible 
music engraving/typesetting.


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

Re: midi articulation

[Simon Albrecht]

On 23.03.2016 18:21, Daniel Birns wrote:

I see what articulate.ly does. However… has anyone tried to do this within the 
midi generator.


Without knowing much about the topic, I’d say it would be very welcome, 
since articulate.ly messes up printed output.



I’m a software developer — not python, nor guile , but just about everything 
else, but especially C++. I could do guile and python if needed. Perhaps I 
should try this, but is there interest?


Certainly, new developers are very welcome! Especially if you know C++ – 
you’ll have to take a decent dive into guile, though.
You could have a look, if there are any related issues in our tracker: 
, and you could write 
to the -devel mailing list. I believe it has been Heikki Tauriainen who 
has last been working in this area.


HTH,
Yours, Simon

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

Re: PDF page number hyperrefs?

[Simon Albrecht]

Hi Mátyás,

by the way: a subject is helpful :-)
Only saying…

Yours, Simon

On 23.03.2016 08:33, Mátyás Seress wrote:

Hi guys,

I just downloaded the Lilypond Notation Reference pdf for version 
2.19.38 from here:

http://www.lilypond.org/doc/v2.19/Documentation/notation.pdf

and I noticed that in the Table of Contents the page numbers next to 
the entries are not clickable hyperrefs like in previous verisons.


Do you know who could fix this? because it'd facilitate the navigation 
a great deal.


Thank you! :)

Mat

Ezt az e-mailt egy Avast védelemmel rendelkező, vírusmentes 
számítógépről küldték.
www.avast.com 
 





___
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

Make the span bar go from top to bottom through all staves

[Joseph N. Srednicki]

Hello:

 

Please see the attached example of an organ score.

 

Is it possible to make the span bars for the measures to extend through all
staves of the system so that the bar lines appear as one solid line from top
to bottom? 

 

Can someone advise on how to do this?

 

I tried the various options that I saw in the documentation, but to no
avail. 

 

Thanks for your help.

 

Joe Srednicki

===

\version "2.19.35"

\language "english"

 

global = {

  \key c \minor

  \numericTimeSignature

  \time 2/4

  \tempo "Adagio" 8 = 72

 

  \override StaffGroup.BarLine #'allow-span-bar = ##t

}

 

clavTwo = \relative c'' {

 

  \global

 

  \hideNotes g'2~ %

 

 

  \unHideNotes g2~ % 1

 

  g4 f16 e d c | %2

 

}

 

rightOne = \relative c'' {

  \global

 

  \skip 2

 

  \skip 2 | % 1

 

}

 

rightTwo = \relative c'' {

  \global

 

  \skip 2

 

 

  \skip 2 | % 1

 

}

 

leftOne = \relative c' {

  \global

 

  \skip 2

 

   r16_\pp g (d' c b c d b) | % 2

 

}

 

leftTwo = \relative c' {

  \global

 

  \skip 2

 

  \skip 16 g16 f ef d e f8 | % 1

 

}

 

pedal = \relative c {

  \global

 

  \skip 2

 

  R2 | % 1

 

}

 

\score {

 

  <<

%

\new Staff = "upper" \with {instrumentName = "Clav. 2"} { \clef treble
\clavTwo }

\new PianoStaff

 

 

  \new StaffGroup \with {instrumentName = "Clav. 1"} {

  <<

 

\new Staff = "right" << \rightOne \\ \rightTwo >>

\new Staff = "left" { \clef bass << \leftOne \\ \leftTwo >> }

  >>

  }

  \new Staff = "pedal"\with {instrumentName = "Pedal"} { \clef bass
\pedal }

  >>

}

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

Re: Make the span bar go from top to bottom through all staves

[Simon Albrecht]

On 24.03.2016 00:34, Joseph N. Srednicki wrote:


Is it possible to make the span bars for the measures to extend 
through all staves of the system so that the bar lines appear as one 
solid line from top to bottom?




Of course: just make it one StaffGroup (or PianoStaff, as you like). I’d 
suggest something like the attached. (A propos: your inline code was 
messed up on the way; please send your e-mail as plain text only or 
attach the code)


Yours, Simon
\version "2.19.35"
\language "english"

global = {
  \key c \minor
  \numericTimeSignature
  \time 2/4
  \tempo "Adagio" 8 = 72
}

clavTwo = \relative c'' {
  \global
  \hideNotes g'2~ %
  \unHideNotes g2~ % 1
  g4 f16 ef d c | %2
}

rightOne = \relative c'' {
  \global
  \skip 2
  \skip 2 | % 1
}

rightTwo = \relative c'' {
  \global
  \skip 2
  \skip 2 | % 1
}

leftOne = \relative c' {
  \global
  \skip 2
  r16_\pp g (d' c b c d b) | % 2
}

leftTwo = \relative c' {
  \global
  \skip 2
  \skip 16 g16 f ef d ef f8 | % 1
}

pedal = \relative c {
  \global
  \skip 2
  R2 | % 1
}

\score {
  \new StaffGroup <<
\new Staff = "upper" \with {instrumentName = "Clav. 2"} { \clef treble \clavTwo }
\new StaffGroup \with {
  systemStartDelimiter = #'SystemStartSquare
  instrumentName = "Clav. 1"
} {
  <<
\new Staff = "right" << \rightOne \\ \rightTwo >>
\new Staff = "left" { \clef bass << \leftOne \\ \leftTwo >> }
  >>
}
\new Staff = "pedal"\with {instrumentName = "Pedal"} { \clef bass \pedal }
  >>
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Where is the latest articulate.ly?

[Thomas Morley]

2016-03-24 0:02 GMT+01:00 Daniel Birns :
> I continue to get very odd results with articulate.ly.

Please study the relevant section in NR
http://www.lilypond.org/doc/v2.18/Documentation/notation/the-articulate-script
There you can read
"After altering your input file this way, the visual output is heavily
altered, but the standard \midi block will produce a better MIDI file.
"
Thus it's good practise to use two scores, one with \layout only
another with \midi only

> Here’s a zip file
> with the problem.

It's quite tedious to have a zip file, better attach the code in one file.

> Please do ‘lilypond test.ly’ with articulate.ly available
> to be included.
>
> The problem looks like it’s generating 2 voices instead of one. One voice is
> all rests. It’s not due to the ‘global’ voice I have, because I removed that
> and the problem remains.
>
> 1) The notes and rests are much more than should fit in the bar, and
> 2) they don’t make any sense to read, and

see above

> 3) The midi sounds just like it did before articulate.ly

try:

\include "articulate.ly"

#(define ac:normalFactor '(1 . 2))
%% 

\score {
  %\unfoldRepeats %needed if showLastLength
  \unfoldRepeats \articulate
  <<
\new Staff \with {
  instrumentName = #"Guitar 1 "
  shortInstrumentName = #""
}
<<\global \guitarOne>>
  >>
  \midi {}
}

Though there aren't that much articulations in your code ...

>
> -d
>> On Mar 23, 2016, at 3:23 PM, Malte Meyn  wrote:
>>
>>
>>
>> Am 23.03.2016 um 18:13 schrieb Daniel Birns:
>>> The one I found on a mailing list from 2011 doesn’t seem to handle even
>>> slurs or staccato.
>>
>> It’s part of vanilla LilyPond since version 2.14 (see
>> http://lilypond.org/doc/v2.14/Documentation/changes/) and has been improved
>> several times since then. And version 2.19 supports some articulations even
>> without including articulate.ly (see
>> http://lilypond.org/doc/v2.19/Documentation/changes/).

Most recent articulate.ly:
http://git.savannah.gnu.org/cgit/lilypond.git/tree/ly/articulate.ly

Cheers,
  Harm

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

Re: Where is the latest articulate.ly?

[Daniel Birns]

On Mar 23, 2016, at 4:58 PM, Thomas Morley 
mailto:thomasmorle...@gmail.com>> wrote:

2016-03-24 0:02 GMT+01:00 Daniel Birns 
mailto:danielbi...@quantumintech.com>>:
I continue to get very odd results with articulate.ly.

Please study the relevant section in NR
http://www.lilypond.org/doc/v2.18/Documentation/notation/the-articulate-script
There you can read
"After altering your input file this way, the visual output is heavily
altered, but the standard \midi block will produce a better MIDI file.
"
Thus it's good practise to use two scores, one with \layout only
another with \midi only

Here’s a zip file
with the problem.

It's quite tedious to have a zip file, better attach the code in one file.

Please do ‘lilypond test.ly’ with 
articulate.ly available
to be included.

The problem looks like it’s generating 2 voices instead of one. One voice is
all rests. It’s not due to the ‘global’ voice I have, because I removed that
and the problem remains.

1) The notes and rests are much more than should fit in the bar, and
2) they don’t make any sense to read, and

see above

3) The midi sounds just like it did before articulate.ly

try:

\include "articulate.ly"

#(define ac:normalFactor '(1 . 2))
%% 

\score {
 %\unfoldRepeats %needed if showLastLength
 \unfoldRepeats \articulate
 <<
   \new Staff \with {
 instrumentName = #"Guitar 1 "
 shortInstrumentName = #""
   }
   <<\global \guitarOne>>

 \midi {}
}

Though there aren't that much articulations in your code ...


-d
On Mar 23, 2016, at 3:23 PM, Malte Meyn 
mailto:lilyp...@maltemeyn.de>> wrote:



Am 23.03.2016 um 18:13 schrieb Daniel Birns:
The one I found on a mailing list from 2011 doesn’t seem to handle even
slurs or staccato.

It’s part of vanilla LilyPond since version 2.14 (see
http://lilypond.org/doc/v2.14/Documentation/changes/) and has been improved
several times since then. And version 2.19 supports some articulations even
without including articulate.ly (see
http://lilypond.org/doc/v2.19/Documentation/changes/).

Most recent articulate.ly:
http://git.savannah.gnu.org/cgit/lilypond.git/tree/ly/articulate.ly

Cheers,
 Harm

___
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: Where is the latest articulate.ly?

[Daniel Birns]

[Sorry about the previous email where I didn’t say anything. If you press send 
by mistake, o well…]

I continue to get very odd results with articulate.ly.

Please study the relevant section in NR
http://www.lilypond.org/doc/v2.18/Documentation/notation/the-articulate-script
There you can read
"After altering your input file this way, the visual output is heavily
altered, but the standard \midi block will produce a better MIDI file.
"
Thus it's good practise to use two scores, one with \layout only
another with \midi only


Got it.

Here’s a zip file
with the problem.

It's quite tedious to have a zip file, better attach the code in one file.

Please do ‘lilypond test.ly’ with 
articulate.ly available
to be included.

The problem looks like it’s generating 2 voices instead of one. One voice is
all rests. It’s not due to the ‘global’ voice I have, because I removed that
and the problem remains.

1) The notes and rests are much more than should fit in the bar, and
2) they don’t make any sense to read, and

see above

Got it.


3) The midi sounds just like it did before articulate.ly

try:

\include "articulate.ly"

#(define ac:normalFactor '(1 . 2))

So, the default is 7/8 (though I’m not sure yet what 1 . 2 is…) but I wondered 
about 7/8. CPE Bach says normally notes are play for 1/2 their duration, so 7/8 
is not detectable I think.

Anyway, that did it. Apparently you’ve had to write this to many others as well…

I doubt 7/8 is correct for anything except perhaps organ…

Anyway, thanks a lot, Harm.

-d


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

Grab a constant from the OS?

[Stan Mulder]

I do this successfully for my tagline (the line at the bottom of the last
page.):

lilystring = #(string-append "Engraved in LilyPond " (lilypond-version) " -
Linux")

\header {
  title = "My Song"
  tagline = \markup {
\column {
  \fontsize #-2 \lilystring
}
  }
}

It produces this text:

"Engraved in LilyPond 2.19.38 - Linux"

But I would like it to read like this:

"Engraved in LilyPond 2.19.38 - Linux Mint 17.3"

I'm not sure where external constants come from, like grabbing the current
version of the OS. From lilypond or from scheme? I have not worked with
scheme at all, but if it is from scheme, is there a recommended tutorial
that would help with this? And how can I accomplish the immediate goal?

Stan


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

RE: Make the span bar go from top to bottom through all staves

[Joseph N. Srednicki]

Thanks, Simon. You told me exactly what to do.

I will make sure to use plain text in the future for emails so that code
does not get messed up.

Thanks again.

Joe Srednicki

-Original Message-
From: Simon Albrecht [mailto:simon.albre...@mail.de] 
Sent: Wednesday, March 23, 2016 7:49 PM
To: Joseph N. Srednicki ; lilypond-user@gnu.org
Subject: Re: Make the span bar go from top to bottom through all staves

On 24.03.2016 00:34, Joseph N. Srednicki wrote:
>
> Is it possible to make the span bars for the measures to extend 
> through all staves of the system so that the bar lines appear as one 
> solid line from top to bottom?
>

Of course: just make it one StaffGroup (or PianoStaff, as you like). I'd
suggest something like the attached. (A propos: your inline code was messed
up on the way; please send your e-mail as plain text only or attach the
code)

Yours, Simon


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

Re: Where is the latest articulate.ly?

[Simon Albrecht]

On 24.03.2016 01:10, Daniel Birns wrote:

So, the default is 7/8 (though I’m not sure yet what 1 . 2 is…)


'(1 . 2), equivalent to (cons 1 2), is a scheme pair.

but I wondered about 7/8. CPE Bach says normally notes are play for 
1/2 their duration,


That’s a very debatable quote. Numerical relations can only say so much, 
and it depends on instrument, style, character, etc. etc. You’d have to 
ask to which exact instrument and what situation Emanuel would have 
referred here. It’s a huge topic to discuss, but 1/2 as a default is 
definitely a very uncommon choice.



so 7/8 is not detectable I think.


Oh yes, of course it is. It’s the equivalent to some kind of 
‘non-legato’, which is the most ‘neutral’ articulation I can think of.


Best, Simon

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

Re: Where is the latest articulate.ly?

[Thomas Morley]

2016-03-24 1:22 GMT+01:00 Simon Albrecht :
> On 24.03.2016 01:10, Daniel Birns wrote:
>>
>> So, the default is 7/8 (though I’m not sure yet what 1 . 2 is…)
>
>
> '(1 . 2), equivalent to (cons 1 2), is a scheme pair.
>
>> but I wondered about 7/8. CPE Bach says normally notes are play for 1/2
>> their duration,
>
>
> That’s a very debatable quote. Numerical relations can only say so much, and
> it depends on instrument, style, character, etc. etc. You’d have to ask to
> which exact instrument and what situation Emanuel would have referred here.
> It’s a huge topic to discuss, but 1/2 as a default is definitely a very
> uncommon choice.
>
>> so 7/8 is not detectable I think.
>
>
> Oh yes, of course it is. It’s the equivalent to some kind of ‘non-legato’,
> which is the most ‘neutral’ articulation I can think of.
>
> Best, Simon

My suggestion of 1/2 was meant to make it overly clear that
\articulate indeed _does_ work.
One should find a more convincing value ofcourse ...

Cheers,
  Harm

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

custom multi-measure rests

[Flaming Hakama by Elaine]

I'd like to figure out how to execute something found in some Jazz charts
for drums.
It is a compact way to indicate "play time for X measures" in a single
measure.

Here are two examples from the googlesphere:

The measure marked as "Play 7"
http://www.quickgigcharts.com/wp-content/uploads/edd/2015/09/Feeling-Good-Feature-image.jpg

The measure marked as "Play 7 (time)"
http://www.mikejamesjazz.com/media/writing_items/drums/mellotone_drums.gif


Those demonstrate the concept, but not the execution I would prefer.
The way I'd like it to look is more like:

| ( 7 ) |

This is overall similar to a multi-measure rest, but with the following
differences:
  o The number should be in the middle of the staff, rather than over the
staff.
  o The number should be surrounded by large parenthesis
  o The lines on either side of the parenthesis should be thick but
squiggly (or even just a bunch of tildes.)

Is it possible to define such a new style for displaying multi-measure
rests?
It doesn't have to be exactly the style--I'd settle for the diagonal line
in the first example.

The main point is, I'd like some other format for multi-measure rest that
is distinct from the usual ones.  I can add text to clarify the
interpretation to the performer.

The other requirement is that I'd also like to use them in
combination--some charts will have both actual multi-measure rests as well
as blocks of "time" represented by this new format of multi-measure rest.

I'd appreciate hearing any thoughts on whether this is possible.


Thanks,

David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Grab a constant from the OS?

[Thomas Morley]

2016-03-24 1:20 GMT+01:00 Stan Mulder :
> I do this successfully for my tagline (the line at the bottom of the last
> page.):
>
> lilystring = #(string-append "Engraved in LilyPond " (lilypond-version) " -
> Linux")
>
> \header {
>   title = "My Song"
>   tagline = \markup {
> \column {
>   \fontsize #-2 \lilystring
> }
>   }
> }
>
> It produces this text:
>
> "Engraved in LilyPond 2.19.38 - Linux"
>
> But I would like it to read like this:
>
> "Engraved in LilyPond 2.19.38 - Linux Mint 17.3"
>
> I'm not sure where external constants come from, like grabbing the current
> version of the OS. From lilypond or from scheme? I have not worked with
> scheme at all, but if it is from scheme, is there a recommended tutorial
> that would help with this? And how can I accomplish the immediate goal?
>
> Stan


#(utsname:sysname (uname))
?

Cheers,
  Harm

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

Flag stencil

[Andrew Bernard]

When making a custom flag stencil, how does one go about getting all the flags 
added to the stem, for the various note values, not just one?

Here’s what I have so far, which only makes one flag for any value. I want to 
draw my own paths, not add glyphs from the font.

Andrew


— snip

\version "2.19.38"

#(define flag-stil
   (lambda (grob)
 (let* ((stem (ly:grob-parent grob X))
(is-up? (eqv? (ly:grob-property stem 'direction ) UP))
(duration (ly:grob-property stem 'duration-log))
)
   (make-path-stencil
`(moveto 0 0
   lineto 1.5 -1
   lineto 1.5 -1.5
   lineto 0 -0.5
   closepath)
0.1 1 1 #t)
   )))

notes = {
  c'4 c'8 c'16 c'32
}

{
  \override Flag.stencil = #flag-stil
  \notes
}

— snip



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

Re: Grab a constant from the OS?

[Andrew Bernard]

Hi Stan,

If you have not worked with Scheme, this may be a fine point, but the system 
identification function that Thomas showed comes from Guile, the Scheme 
implementation used by lilypond. So you won’t find pure Scheme tutorials on 
this function.

Here’s the Guile reference page:

https://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/System-Identification.html#System-Identification

For learning Scheme, there is a light tutorial which is good: Teach Yourself 
Scheme in Fixnum Days

http://ds26gte.github.io/tyscheme/index.html

As for other ‘external’ variables, you may perhaps want to get environment 
variables or runtime information, and there are ways to do that also:

https://www.gnu.org/software/guile/manual/html_node/Runtime-Environment.html#Runtime-Environment


Andrew



On 24/03/2016, 11:20, "Stan Mulder" 
 wrote:

I'm not sure where external constants come from, like grabbing the current
version of the OS. From lilypond or from scheme? I have not worked with
scheme at all, but if it is from scheme, is there a recommended tutorial
that would help with this? And how can I accomplish the immediate goal?



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

Re: midi articulation

[H. S. Teoh]

On Wed, Mar 23, 2016 at 05:21:13PM +, Daniel Birns wrote:
> Hi all,
> 
> Okay, I see what articulate.ly does. However… has anyone tried to do
> this within the midi generator. I debugged the python_midi.c file, and
> I can see what it’s doing. Geez, it seems like at the point where the
> midi file is being generated, lilypond ought to know everything about
> what’s the score, and ought to be able to apply articulation easily
> and much more correctly at that point.
> 
> Has anyone tried doing this? My guess is it’s nowhere near as easy as
> I think it should be. But, honestly, the midi files suck. As a
> Sibelius user, this is a showstopper — Sibelius does a beautiful job
> at this, and it seems like it shouldn’t be difficult for lilypond to
> do the same.
> 
> I’m a software developer — not python, nor guile , but just about
> everything else, but especially C++. I could do guile and python if
> needed. Perhaps I should try this, but is there interest? Do I have
> time for this? And why haven’t the others who know a great deal more
> about this than I do, done this?
> 
> Thanks. No criticism at all intended: I think lilypond is amazing. 
[...]

As far as I understand it (and I could be wrong), lilypond's original
authors did not regard midi support as important, as lilypond's original
mission was to typeset music and do it well.  So the original midi
support was tacked on as an afterthought and was pretty rudimentary, and
as far as I can tell, hasn't changed very much since then.  This was
probably one of the main reasons articulate.ly was invented in the first
place.

Be that as it may, I for one thing would be glad if somebody would take
the time to improve midi generation so that it's not so atrocious.  My
ideal conception of it is to have some kind of mapping mechanism for
translating notation into midi that offers the same configurability and
expressive power as the notation syntax itself, such that the user would
be able to, for example, specify how phrases should be rendered, whether
a particular Staff should emit Expression events for crescendos or
merely increment the velocity of the notes (as is currently done,
piano-style), how to translate breathing marks, or any mark, for that
matter (e.g., trill mark on a timpani Staff should emit tremolos or
switch to a different program for rolls).  The defaults ought to produce
pretty decent midi, but should be overridable by the user.

In any case, midi itself is rather limited, as the built-in limit of 16
channels is too restrictive for rendering large orchestral scores. For
this purpose I have written an auxiliary helper program that renders
individual StaffGroup's into separate midi files, to be separately
rendered by a software midi synth and then mixed into a single file
afterwards.  The program also generates suitable MIDI program switching
macros for implementing different articulations. Such functionality is
probably beyond the scope of lilypond, though conceivably one could
implement the necessary infrastructure for the user to be able to do
such things within lilypond itself, as opposed to resorting to external
tools.


T

-- 
"How are you doing?" "Doing what?"

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