German User Forum down

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

Re: Tie into top voice of multiple voices

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

Tie into top voice of multiple voices

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

Re: Control of spacing between left edge and first note

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

Re: Unusual beaming for piano music

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

Re: Unusual beaming for piano music

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!

Fwd: Re: Unexpected Stem behaviour

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 =

Re: Unexpected Stem behaviour

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

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,

Re: Elysium broken link

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 >>>

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

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

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

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

Re: Unexpected Stem behaviour

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 > >

Re: Unexpected Stem behaviour

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 >

Unexpected Stem behaviour

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"

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

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

Re: Unusual beaming for piano music

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

Confusion about note-column-accidentals

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

Re: Unusual beaming for piano music

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

Re: Unusual beaming for piano music

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