Fwd: Re: Unexpected Stem behaviour

2017-03-31 Thread 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 =

Re: Unexpected Stem behaviour

2017-03-31 Thread 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

2017-03-31 Thread 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,

Re: Unexpected Stem behaviour

2017-03-31 Thread 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 > >

Re: Unexpected Stem behaviour

2017-03-31 Thread 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 >

Unexpected Stem behaviour

2017-03-31 Thread 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"

Re: Unexpected stem behaviour

2017-03-15 Thread Simon Albrecht
Am 15.03.2017 um 17:07 schrieb Gerard: \version 2.18.2 % bar 30 \relative bes'' << {bes4 c d} \\ {\relative bes'' {bes32 f d bes} \change Staff = "lower" {f,, d bes f} \change Staff = "upper" {c''' bes f c} \change Staff = "lower" {bes f c bes} \change Staff = "upper" {d'' bes f d} \change

Re: Unexpected stem behaviour

2017-03-15 Thread Phil Holmes
- Original Message - From: "Gerard" <trac...@qstone.nl> To: <lilypond-user@gnu.org> Sent: Wednesday, March 15, 2017 4:07 PM Subject: Unexpected stem behaviour Dear All, I noticed some weird behaviour with stem directions after compiling (both on Linux a

Unexpected stem behaviour

2017-03-15 Thread Gerard
Dear All, I noticed some weird behaviour with stem directions after compiling (both on Linux and Windows). Consider these two lines of code from a score: \version 2.18.2 % bar 30 \relative bes'' << {bes4 c d} \\ {\relative bes'' {bes32 f d bes} \change Staff = "lower" {f,, d bes f} \change