German User Forum down

[Manuela Gößnitzer]

Hi,

does anybody know anything about the German forum? The page is down since
yesterday, the site says "End of life". I am really sad because this forum
is very valuable for me,
greetings
Manuela
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Tie into top voice of multiple voices

[Simon Albrecht]

Am 01.04.2017 um 00:53 schrieb Mike Dean:

Having a hard time querying about this:
\version "2.19.42"

{
/% not at all sure how to resolve the warning about a unresolved tie:/
 b''8 as b2->~ |
<< {b1~\repeatTie | b4} \\
{ -.    | } >> e'8 ds e2 |

}


The << {} \\ {} >> construct creates two new voices. Thus, the second b 
is in another voice than the first. If you use
<< {} \new Voice {} >> instead, the first {} will be the continuation of 
the previously active voice:


\version "2.19.42"

{
   b''8 as b2->~ |
  <<
{
  \voiceOne
  b1~ |
  b4
}
\new Voice {
  \voiceTwo
  -.    |
  
}
  >>
  e'8 ds e2 |
}

I reformatted the code according to common and quite useful standards.

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

Tie into top voice of multiple voices

[Mike Dean]

Having a hard time querying about this:
\version "2.19.42"

{
*% not at all sure how to resolve the warning about a unresolved tie:*
 b''8 as b2->~ |
<< {b1~\repeatTie | b4} \\
{ -.    | } >> e'8 ds e2 |

}

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

Re: Control of spacing between left edge and first note

[Thomas Liggett]

Hello all,

Bumping this in the hope that someone might be able to help me continue my 
gradual ascent of the LIlyPond learning curve!

Thanks,
Thomas

> Begin forwarded message:
> 
> From: Thomas Liggett 
> Subject: Re: Control of spacing between left edge and first note
> Date: 27 March 2017 at 1:56:04 PM NZDT
> To: Andrew Bernard 
> Cc: "lilypond-user@gnu.org" 
> 
> Hi Andrew,
> 
> With your help I've got the desired result – many thanks! (BTW I was
> able to set the "key-signature extra-space" without including that
> whole alist.) But I'd like to better understand the logic behind
> what's happening in my code below.
> 
> To produce a staff with no clef, key signature, time signature, or
> barlines, and to be able to specify the spacing between the left edge
> of the staff and the first note (i.e. to be able to produce diagrams
> comprising only staves with note-groups as in the example below):
> 
> * just making the clef a point-stencil, omitting the bar-engraver, and
> using \override LeftEdge.space-alist.clef = #'(extra-space . xxx)
> achieves this for the first system, but NOT for any subsequent systems
> (hence my original query)
> 
> To control the first system AND subsequent systems:
> 
> * a (semantically irrelevant) key signature is required (set to a
> point-stencil, otherwise extra space is introduced) – C major will
> suffice. Why? (What's the difference to Lilypond between "no key
> signature" and "a specified key signature of no sharps or flats"?!?)
> 
> * barlines, made transparent, are required to "reference off" as you
> say. (Transparent barlines, naturally, include space either side, so
> in order to have an arbitrary number of notes spaced evenly across a
> system – i.e. in this example, to avoid an extra space between the two
> groups of 8 notes – a time signature equal to the length of the system
> must be specified. But the nice thing about omitting the bar engraver
> in my original was that it avoided the need to specify a semantically
> irrelevant time signature.) But how are barlines even involved in
> controlling the space between the left edge of the staff and the first
> note?
> 
> Is it related to the issue Urs is dealing with in this thread?
> http://lists.gnu.org/archive/html/lilypond-user/2017-03/msg00627.html
> 
> Thanks again,
> Thomas
> 
> %
> 
> \version "2.19.41"
> 
> \paper { indent = 0 }
> 
> \layout {
>  \context {
>\Score
>\override LeftEdge.space-alist.clef = #'(extra-space . 2) % space
> between left edge and invisible clef
>\remove Bar_number_engraver
>  }
>  \context {
>\Staff
>\remove Time_signature_engraver
> %\remove Bar_engraver
>\override Clef.stencil = #point-stencil % make clef effectively invisible
>\override Clef.space-alist.key-signature = #'(extra-space . 0) %
> space between invisible clef and invisible key sig
>\override KeySignature.stencil = #point-stencil
>\override BarLine.transparent = ##t
>  }
> }
> \score {
>  \relative c'' {
>\clef "treble"
>\key c \major % comment out this line and see what happens!
>\time 4/2 % comment out this line and there's extra space added
> where default (4/4) barlines would be
>\stemUp
>b8 b c c d d e e f f g g a a b b \break
>b,, b c c d d e e f f g g a a b b
>  }
> }
> 
> %
> 
> 
> On Sat, Mar 11, 2017 at 6:01 PM Andrew Bernard  
> wrote:
>> 
>> Hi Thomas,
>> 
>> Try this perhaps.
>> 
>> [You have to retain clefs and barlines and render them transparent, so that 
>> they exist to reference off. One ought to be able to just set the value 
>> (key-signature extra-space . 8) say, but I am not sure why we need the whole 
>> shebang alist.]
>> 
>> 
>> Andrew
>> 
>> == snip
>> 
>> \version "2.19.56"
>> 
>> \paper { indent = 0 }
>> 
>> \score {
>>  \relative c'' {
>> 
>>\override Staff.KeySignature.stencil = #point-stencil
>>\override Staff.Clef.stencil = #point-stencil
>>\override Staff.BarLine.transparent = ##t
>> 
>>\key a \major
>>\stemUp
>>%
>> 
>>b8 b c c d d e e f f g g a a b b
>>\break
>>b,, b c c d d e e f f g g a a b b
>>  }
>> 
>>  \layout {
>>\context {
>>  \Score
>>  \remove Bar_number_engraver
>>}
>>\context {
>>  \Staff
>>  \remove Time_signature_engraver
>> 
>>  \override Clef.space-alist =
>>  #'((ambitus extra-space . 2.0)
>> (breathing-sign minimum-space . 0.0)
>> (cue-end-clef extra-space . 0.8)
>> (clef extra-space . 0.8)
>> (cue-clef extra-space . 0.8)
>> (staff-bar extra-space . 0.0)
>> (key-cancellation extra-space . 0.0)
>> (key-signature extra-space . 8)
>> (time-signature extra-space . 1.0)
>> (custos extra-space . 0.0)
>> (first-note fixed-space . 0.0)
>> (right-edge extra-space . 0.0))
>> 
>>}
>>  }
>> }
>> 
>> == snip
>> 

Re: Unusual beaming for piano music

[Juan Cristóbal Cerrillo]

This is wonderful.

A perfect example of the very intelligent ideas behind Lilypond.

And I second the idea of a contemporary notation bundle!

all best,

jc

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

Re: Unusual beaming for piano music

[Jeffery Shivers]

On Fri, Mar 31, 2017 at 4:44 AM, Andrew Bernard
 wrote:
> For anybody who comes across this matter in the future, my example code is
> attached - a bit too involved to be an MWE I am afraid.
>
> Gratitude to all for helping with this one!

Thanks for sharing this!

If/when openLilyLib proceeds with a contemporary notation bundle, I
think something like this would be really cool to have builtin,
perhaps with an intelligent interface for (optionally) auto-setting
the beam positions etc. I've also encountered / lost hair over / seen
in others' work this general notational problem a lot in the past few
years (don't ask me why us younger/contemporary composers are inclined
to do it :-) ).

Best,
Jeffery

-- 

Jeffery Shivers
 jefferyshivers.com
 soundcloud.com/jefferyshivers

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

Fwd: Re: Unexpected Stem behaviour

[Gerard]

Thanks Malte for your input.
It gives me some clues of how to pursue.

Gerard
\version "2.18.2"

\paper {  # (set-paper-size "a4" 'landscape)
  top-margin = 1.5\cm
  left-margin = 2\cm
  line-width = 26\cm
  bottom-margin = 1\cm
 
  markup-system-spacing #'padding = #6
}
\layout {}


testStaff = <<

\time 4/4
\context Staff = "upper" {  
	
	\clef "treble"
	\key es \major
 

	
\relative c''' <<
   % Upper Voice
	   {c2\( es4~\) [es8^\fermata r16 16]}
	   
	   \\
	   % Middle voices
		   \relative c''' { \change Staff = "upper" \stemDown {c32 bes as es} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t {c ~ bes ~ as ~ }
 \change Staff = "upper" \stemDown {as'32 bes as es}  \change Staff = "lower" \stemUp \set tieWaitForNote = ##t  {c ~ bes ~ as ~  }
 \change Staff = "upper" \stemDown {es'32 d c as} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t es ~ d ~ c ~ as~ 8 [r16 ]}
  
  \\
  % chords and ties
  \relative c'' { 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes as' ~ es ~  8 }
   s32   \override Tie.minimum-length = #6 \set tieWaitForNote = ##t {\hideNotes bes ~ as ~ es~ 8} 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes c~ as~  \unHideNotes 8~ 8 s16 s}
  }
  \\
  
  \relative c''' {s8 \stemDown 8 s8 8 }
  
  
   >>
   
}
  
  \context Staff = "lower" {

 \clef "treble"
	 \key es \major
	
 \relative c' {s2 s2}

  }
>>

\book{
  \score { << \testStaff >>}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unexpected Stem behaviour

[Malte Meyn]

Am 31.03.2017 um 16:45 schrieb Gerard:
> Any suggestion?

Read my previous answer.


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

Re: Unexpected Stem behaviour

[Gerard]

Dear All, I found a partial solution to the issues as mentioned in my 
previous Email.

See this attachment.

By adding a new voice the stem in the upperpart is now correct (issue 1).
However, issue 2 now is different: the ties are longer and extend over 
the chord.


Any suggestion?

Thanks,
Gerard
\version "2.18.2"

\paper {  # (set-paper-size "a4" 'landscape)
  top-margin = 1.5\cm
  left-margin = 2\cm
  line-width = 26\cm
  bottom-margin = 1\cm
 
  markup-system-spacing #'padding = #6
}
\layout {}


testStaff = <<

\time 4/4
\context Staff = "upper" {  
	
	\clef "treble"
	\key es \major
 

	
\relative c''' <<
   % Upper Voice
	   {c2\( es4~\) [es8^\fermata r16 16]}
	   
	   \\
	   % Middle voices
		   \relative c''' { \change Staff = "upper" \stemDown {c32 bes as es} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t {c ~ bes ~ as ~ }
 \change Staff = "upper" \stemDown {as'32 bes as es}  \change Staff = "lower" \stemUp \set tieWaitForNote = ##t  {c ~ bes ~ as ~  }
 \change Staff = "upper" \stemDown {es'32 d c as} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t es ~ d ~ c ~ as~ 8 [r16 ]}
  
  \\
  % chords and ties
  \relative c'' { 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes as' ~ es ~  8 }
   s32   \override Tie.minimum-length = #6 \set tieWaitForNote = ##t {\hideNotes bes ~ as ~ es~ 8} 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes c~ as~  \unHideNotes 8~ 8 s16 s}
  }
  \\
  
  \relative c''' {s8 \stemDown 8 s8 8 }
  
  
   >>
   
}
  
  \context Staff = "lower" {

 \clef "treble"
	 \key es \major
	
 \relative c' {s2 s2}

  }
>>

\book{
  \score { << \testStaff >>}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Elysium broken link

[Federico Bruni]

If you check the source, the link has been fixed already

Il 31 marzo 2017 07:47:37 CEST, Martin Tarenskeen  ha 
scritto:
>
>
>On Fri, 31 Mar 2017, Brian Barker wrote:
>
>> At 01:08 31/03/2017 +0200, Martin Tarenskeen wrote:
>>> I found this (broken?) link on 
>>> http://lilypond.org/doc/v2.19/Documentation/web/easier-editing
>>> 
>>> So what happened to this Elysium website?
>>
>> You might want contact its author; see http://thsoft.hu/en/Contact/ .
>>
>> Doesn't https://github.com/thSoft/elysium have what you need?
>
>Yes, I can find the files. But was hoping to find some background 
>information. And the broken link in the Lilypond documentation should
>be 
>reported to the buglist I guess?
>
>-- 
>
>MT
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to force script (articulation custom function) inside staff ?

[Les Éditions Valmajour - pg]

Thanks Malte!
It works well, I didn't notice before the difference in space between 
dashs and dots in different situations.
The only thing is that the size of the dot is bigger in Tenuto+Staccato 
than in Portato.

But I think it can work for me like that.
Thanks again!
Pierre

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

Re: How to force script (articulation custom function) inside staff ?

[Malte Meyn]

Am 31.03.2017 um 11:48 schrieb Les Éditions Valmajour - pg:
> Dear list members,
> I have to use lots of dots and dashes in a score, so I found a snippet
>  to apply an articulation
> (staccato) function to a long passage. I tried to adapt it for another
> articulation, the one I need (portato, = dot + dash)
> It works well, except the positioning: it remains outside the Staff.
> I would like to get the same positioning behavior than the default
> articulation (inside the staff)

Portato is something different than staccato plus tenuto in LilyPond:

\score {
  <<
\new Staff \with {
  instrumentName = "default -.--"
} \relative c'' {
  g8-.-- a-.-- b-.-- c-.--\downbow
  d-.-- c-.-- b-.-- a-.--\upbow
}
\new Staff \with {
  instrumentName = "default -_"
} \relative c'' {
  g8-_ a-_ b-_ c-_\downbow
  d-_ c-_ b-_ a-_\upbow
}
  >>
}

The portato (-_) is *one* single symbol instead of two separate ones
(dash + dot). This single symbol has no space to got inside the staff so
your function won’t work as expected.

You could try adding the dashes and the dots separately (define
addTenuto which adds "tenuto" instead of "portato"):

\new Staff \with { instrumentName = "+ \addStacc + \addTenuto" }
\relative c' {
  \addTenuto { \addStacc { g'8 a b c\downbow d c b a\upbow } }
}

But IMHO that looks bad because of different spacing between dash and
dot depending on whether they are inside the staff or outside.

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

Re: Unexpected Stem behaviour

[Malte Meyn]

Am 31.03.2017 um 12:27 schrieb Malte Meyn:
> The tie is attached to the note head you attached it to—but this note
> head is transparent. If you don’t use \hideNotes you can see that. The
> two note heads are printed side by side to prevent collision; you can
> turn that off by using
> 
>   (\once) \override NoteColumn.ignore-collision = ##t

But don’t forget to turn the collision prevention back on again:

\revert NoteColumn.ignore-collision

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

Re: Unexpected Stem behaviour

[Malte Meyn]

Hi Gerard,

please try to make minimal examples that are easier to understand
(http://lilypond.org/tiny-examples.html). These long lines and tons of
{} and <<>> aren’t easy to read.

Am 31.03.2017 um 11:55 schrieb Gerard:
> 1. The stems in red do not match the coding, length should be 8 in stead
> of 4

I tried to find any code that has to do with stem length for five
minutes but didn’t see that there was none because of missing line
breaks etc.

After these five minutes I realised that you meant that the note
duration isn’t represented by the stem/flag (flag is missing) instead of
an uncorrect stem length.

If you don’t use \hideNotes you can see what causes the missing flag:
The eigth notes are beamed together with the preceding transparent 32nd
notes. They have a (transparent) beam so no flag is set. You can use
\noBeam here to prevent beaming from and to this note:

8\noBeam

> 2. The tie on the red note seems to precede the note, not to follow it
> to the next.

The tie is attached to the note head you attached it to—but this note
head is transparent. If you don’t use \hideNotes you can see that. The
two note heads are printed side by side to prevent collision; you can
turn that off by using

(\once) \override NoteColumn.ignore-collision = ##t

> Any suggestions are welcome.

General suggestion: If you use transparent “fake” voices to create such
complicated polyphony, don’t make them transparent until all spacing
etc. is done and then, as a last step, insert \once \hideNotes,
\hideNotes and \unHideNotes.

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

Unexpected Stem behaviour

[Gerard]

Dear All,

I noticed two issues as in the attached sample.

1. The stems in red do not match the coding, length should be 8 in stead 
of 4


2. The tie on the red note seems to precede the note, not to follow it 
to the next.


Any suggestions are welcome.

Thanks,
Gerard
\version "2.18.2"

\paper {  # (set-paper-size "a4" 'landscape)
  top-margin = 1.5\cm
  left-margin = 2\cm
  line-width = 26\cm
  bottom-margin = 1\cm
 
  markup-system-spacing #'padding = #6
}
\layout {}


testStaff = <<

\time 4/4
\context Staff = "upper" {  
	
	\clef "treble"
	\key es \major
 

	
\relative c''' <<
   % Upper Voice
	   {c2 es4~ [es8^\fermata r16 16]}
	   
	   \\
	   % Middle voices
		   \relative c''' { \change Staff = "upper" \stemDown {c32 bes as es} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t {c ~ bes ~ as ~ }
 \change Staff = "upper" \stemDown {as'32 bes as \override NoteHead.color = #(rgb-color 1 0 0) es} \revert NoteHead.color \change Staff = "lower" \stemUp \set tieWaitForNote = ##t  {c ~ bes ~ as ~  }
 \change Staff = "upper" \stemDown {es'32 d c as} \change Staff = "lower" \stemUp \set tieWaitForNote = ##t es ~ d ~ c ~ as~ 8 [r16 ]}
  
  \\
  % chords and ties
  \relative c'' { 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes as' ~ es ~  \unHideNotes \override Stem.color = #(rgb-color 1 0 0) \stemDown 8 }
   s32   \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes bes ~ as ~ es~  \unHideNotes \stemDown 8} 
   s32 s \override Tie.minimum-length = #4 \set tieWaitForNote = ##t {\hideNotes c~ as~  \unHideNotes 8~ \revert Stem.color 8 s16 s}
 }
   >>
   
}
  
  \context Staff = "lower" {

 \clef "treble"
	 \key es \major
	
 \relative c' {s2 s2}

  }
>>

\book{
  \score { << \testStaff >>}
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

How to force script (articulation custom function) inside staff ?

[Les Éditions Valmajour - pg]

Dear list members,
I have to use lots of dots and dashes in a score, so I found a snippet 
 to apply an articulation 
(staccato) function to a long passage. I tried to adapt it for another 
articulation, the one I need (portato, = dot + dash)

It works well, except the positioning: it remains outside the Staff.
I would like to get the same positioning behavior than the default 
articulation (inside the staff)


I found a beginning of solution, but now the dots and dashes don't avoid 
collisions with the staff lines. (cf attached .ly). And I kinda feel 
that \override is not the clean trick.


Do anyone know how I can achieve this?
Thank you!
Best,
/Pierre
\version "2.18.2"

#(define (make-script x)
   (make-music 'ArticulationEvent
 'articulation-type x))

#(define (add-script m x)
   (case (ly:music-property m 'name)
 ((NoteEvent) (set! (ly:music-property m 'articulations)
(append (ly:music-property m 'articulations)
  (list (make-script x
   m)
 ((EventChord)(set! (ly:music-property m 'elements)
(append (ly:music-property m 'elements)
  (list (make-script x
   m)
 (else #f)))

#(define (add-staccato m)
   (add-script m "staccato"))

addStacc = #(define-music-function (parser location music)
  (ly:music?)
  (map-some-music add-staccato music))

%%% 

#(define (make-script x)
   (make-music 'ArticulationEvent
 'articulation-type x))

#(define (add-script m x)
   (case (ly:music-property m 'name)
 ((NoteEvent) (set! (ly:music-property m 'articulations)
(append (ly:music-property m 'articulations)
  (list (make-script x
   m)
 ((EventChord)(set! (ly:music-property m 'elements)
(append (ly:music-property m 'elements)
  (list (make-script x
   m)
 (else #f)))

#(define (add-portato m)
   (add-script m "portato"))

addPortato = #(define-music-function (parser location music)
(ly:music?)
(map-some-music add-portato music))


\paper {
  indent = #30
}

\score {
  <<
\new Staff \with { instrumentName = "defaut" } \relative c'' { g8-.-- a-.-- b-.-- c-.--\downbow d-.-- c-.-- b-.-- a-.--\upbow }
\new Staff \with { instrumentName = "+ \addStacc" } \relative c' { \addStacc { g'8 a b c\downbow d c b a\upbow } }
\new Staff \with { instrumentName = "+ \addPortato" } \relative c' { \addPortato { g'8 a b c\downbow d c b a\upbow } }  
\new Staff \with { instrumentName = "+ \addP + \ov." } \relative c' { \override Staff.Script.padding = #0
  \override Staff.Script.toward-stem-shift = ##t
  \override Staff.Script.quantize-position = ##t
  \addPortato { g'8 a b c\downbow d c b a\upbow }
}
  >>
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unusual beaming for piano music

[Andrew Bernard]

Hi Harm,

Well and indeed! Using this technique solves the problem. Thank you.
Curiously, I make heavy use of this in my scores, but just could not see my
way around it in this instance.

Image of exact solution attached. The crux of it is the transition between
up and down beaming where you can just say something like this for the
d-sharp in question:

 \once \override Stem.beaming = #'((0 1 2) . (14 15 16)) dis'''32

For anybody who comes across this matter in the future, my example code is
attached - a bit too involved to be an MWE I am afraid.

Gratitude to all for helping with this one!

Andrew



On 25 March 2017 at 08:25, Thomas Morley  wrote:

>
> Nevertheless, a hint (no idea whether it will be really helpful):
>
> {
> b'16^[
> \once \override Stem.beaming = #(cons (list 0  1) (list 0))
> g''16
> \once \override Stem.beaming = #(cons (list 0  1) (list 3 4 5))
> dis'16
> fis''32]
> }
>
>
\version "2.19.58"

% functions ==

setBeamPosAll =
#(define-music-function
  (left right)
  (number? number?)
  "Manually set beam position for following groups."
  #{
\override Beam.positions = #(cons left right)
  #})

setBeams =
#(define-music-function
  (left right)
  (number? number?)
  "Set the number of beams on each side of a beamed note.
  Only designed to be used for 'normal' cases.
  Specify the number of beams for the left and the number for the right side."
  (define seq
;; (seq start count)
;; make a sequence of integers, as a list
;; start: starting integer
;; count: how many elements
(lambda (start count)
  (let r ((i (+ start (- count 1))) (lis '()))
(if (< i start)
lis
(r (- i 1) (cons i lis))
  #{
\once \override Stem.beaming = #(cons (seq 0 left) (seq 0 right))
  #})

setBeaming =
#(define-music-function
  (positions)
  (pair?)
  "Specify left and right beaming and individual beams.
  Arg is a pair of lists of beam positions."
  #{
\once \override Stem.beaming = #(cons (car positions) (cdr positions))
  #})

% abbreviations ==

#(define t tuplet)
#(define sb setBeams)
#(define sbm setBeaming)
% stems and staff changes
tsd = { \change Staff = treble \stemDown }
tsu = { \change Staff = treble \stemUp }
bsu = { \change Staff = bass \stemUp }
bsd = { \change Staff = bass \stemDown }
#(define su stemUp)
#(define sd stemDown)


% exmaple ==

treble = {
  \clef "treble^8"
  \cadenzaOn % just remove barlines to declutter example
  \su
  \setBeamPosAll 8 8
  b'''16[ \t 5/4 { \sb 1 2 dis''' cis'' dis''' b'' \sb 2 1 f''' }
  \t 5/4 { \sb 1 2 d'' f''' bes'' f''' \sb 2 1 gis'' } \sb 1 2 b'' g'''^>
  \bsu \clef "treble^8"
  \sbm #'((0 1 2) . (14 15 16)) dis'''32
  \tsd
  \revert Beam.positions
  \sbm #'((0 1 2 ) . (1 0)) fis32
  \bsu
  \sbm #'((0 1) . (-1 0 1)) gis''' \tsd
  \sbm #'((-1 -2) . (-1 -2)) a16
  cis cis \sb 3 1 a32
  \bsu
  \sbm #'((0) . (0 -1 -2)) dis
  \tsd \sb 3 2 g \bsu
  \sbm #'((0 1) . (1 0 -1)) cis
  \tsd
  bes]
}

bass = {
  \clef bass
  s4 * 6
}

\score {
  \new PianoStaff \with {
\override VerticalAxisGroup.staff-staff-spacing =
#'((basic-distance . 14)
   (minimum-distance . 4)
   (padding . 1)
   (stretchability . 8))
  }
  <<
\new Staff = "treble" \with {
}
{ \treble }

\new Staff = "bass" \with {
}
{ \bass }
  >>

  \layout {
\context {
  \Score
  \accidentalStyle Score.dodecaphonic
}
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Confusion about note-column-accidentals

[Urs Liska]

Hi,

I'm confused about the handling of accidentals in tied notes/chords.

ly:note-column-accidentals returns either an AccidentalPlacement object
or an empty list. I found out that the AccidentalPlacement's X-extent
interacts in a somehow strange way with the NoteColumn's X-offset, but
that's (probably) not the issue here.

What I'm wondering here is: in a tied note/chord there is an
AccidentalPlacement object with an X-extent, even if the accidentals are
not displayed:

\version "2.19.57"

{
  \override TieColumn.after-line-breaking = 
  #(lambda (tc)
 (let* ((rb (ly:grob-parent (ly:spanner-bound tc RIGHT) Y))
(accs (ly:note-column-accidentals rb))
(accs-extent 
 (if (null? accs)
 "No AccidentalPlacement object."
 (ly:grob-property accs 'X-extent
   (display accs-extent)))
  
  % No accidentals in chord: No AccidentalPlacement object
  %1 ~ q
  % Accidentals in chord: AccidentalPlacement object on the right column
  % even if it is not shown.
  1 ~ q
}

% displays (-4.05 . -0.35)

In order to determine the spacing to the left of a tied note column I
thought I could rely on the presence or absence of the
AccidentalPlacement, but obviously this isn't the case. So could someone
give an explanation (or at least a suggestion) why this
AccidentalPlacement is there and - more importantly - how I can reliably
determine the presence or absence of the visual accidentals (at the time
of stencil override)? TIA Urs

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

Re: Unusual beaming for piano music

[Andrew Bernard]

Hi Harm,

Many thanks for all this work, but having the noteheads centred does not
help as I need to not have that - sorry, I never mentioned this aspect in
the original post actually because that was not the query.

Also, when I compile this example there are whitespace gaps all over, and I
can;t really deal with the 14 decimal place numbers easily. This is in no
way to denigrate yours or anyone's efforts, but I am forming the conclusion
this is something lilypond just cannot do.

In a case like this, I will just have to twist the arm of my composer
colleague to get him to notate the section in a more conventional way but
generally I only get a response when ALL technical avenues have been
pursued!

Andrew



On 25 March 2017 at 23:38, Thomas Morley  wrote:

>
>
> 2017-03-24 22:25 GMT+01:00 Thomas Morley :
>
> Anyway, here my attempt, some heavy ugliness in it, though, (see comments
> inline) ...
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Unusual beaming for piano music

[Andrew Bernard]

Hi Juan and Jeffery.

Thank you for taking the time to work on the beaming problem. Yes, the MS
shows noteheads with stems attached in the middle, but that is an
idiosyncrasy of the composer and one that I expunge in the engraving. The
solutions with the note stems centered therefore do not work for me, as
when using normal stem positioning in your examples the beams overlap the
stem.

I appreciate the tries, close, but no cigar! :-)

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