Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread David Wright
On Thu 23 Jun 2016 at 09:45:51 (+1000), Harald Christiansen wrote: > I got your email and I've tried. > > In my case it either increases the space between the G and F keys within > the PianoStaff (which I don't want) > or does nothing (depending on where I place it) Well it would do. That's

Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread Thomas Morley
2016-06-23 1:45 GMT+02:00 Harald Christiansen : > Hi Thomas, > > I got your email and I've tried. > > In my case it either increases the space between the G and F keys within the > PianoStaff (which I don't want) Well, then I completely misunderstood your request. Sorry for

Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread Harald Christiansen
Hi Thomas, I got your email and I've tried. In my case it either increases the space between the G and F keys within the PianoStaff (which I don't want) or does nothing (depending on where I place it) Regards. On Thu, Jun 23, 2016 at 8:49 AM, Thomas Morley wrote: >

Re: \accidentalStyle for common choir notation

2016-06-22 Thread Simon Albrecht
On 22.06.2016 12:30, Phil Holmes wrote: Again, not at all. Piano players must read more than one staff at a time, and therefore an accidental on one staff might be felt to affect pitches on other staves. Singers (like orchestral players) have no need to see the music of the other voices

Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread Thomas Morley
2016-06-23 0:41 GMT+02:00 Harald Christiansen : > Hi Dan, > > Not as creative as you may think. > > Essentially Lilipond as Tex is about stacking boxes with some rubber > space/bands in between. > > If you read Chapter 11 "Boxes" of TeXbook (Donald Knuth) you will understand

Re: drawing glissando line with (gliss) as text across line

2016-06-22 Thread Thomas Morley
2016-06-22 23:48 GMT+02:00 Ryan Michael : > Interesting. your example works perfectly in itself. But when I port it over > to my score I get the following error: > > Wrong type argument in position 1 (expecting Stencil): () > > I believe it calls it on this line: > >

Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread Harald Christiansen
Hi Dan, Not as creative as you may think. Essentially Lilipond as Tex is about stacking boxes with some rubber space/bands in between. If you read Chapter 11 "Boxes" of TeXbook (Donald Knuth) you will understand what I am talking about. What I did is "add a box on top of the tallest box in the

Vertical justification after \pagebreak

2016-06-22 Thread Br. Gabriel-Marie | SSPX
In my music, I have the chorus at the top and the verses following. Since my music is longer than one page, it overflows to the next. So, since I'm using two pages, I figured I would insert a \pagebreak so that the chorus is on page 1 and the verses on page 2. This works fine, but now my

Re: drawing glissando line with (gliss) as text across line

2016-06-22 Thread Ryan Michael
Interesting. your example works perfectly in itself. But when I port it over to my score I get the following error: Wrong type argument in position 1 (expecting Stencil): () I believe it calls it on this line: (spanner-stencil-x-length (interval-length (ly:stencil-extent spanner-stencil

Re: drawing glissando line with (gliss) as text across line

2016-06-22 Thread Thomas Morley
2016-06-22 22:42 GMT+02:00 Ryan Michael : > Hello, I am trying to engrave the following gesture: > > % > bes16\glissando > \tuplet 3/2{ aes8\glissando-\markup{\teeny"glissando between Ab and Bb"} > \once \hide NoteHead a8\glissando \once \hide NoteHead

drawing glissando line with (gliss) as text across line

2016-06-22 Thread Ryan Michael
Hello, I am trying to engrave the following gesture: % bes16\glissando \tuplet 3/2{ aes8\glissando-\markup{\teeny"glissando between Ab and Bb"} \once \hide NoteHead a8\glissando \once \hide NoteHead a16\glissando bes16~} my idea is to draw the first 16th

Re: Ask about the typesetting of Lilypond

2016-06-22 Thread Wilbert Berendsen
Op Tue, 14 Jun 2016 19:08:14 +0200 "m.tarensk...@zonnet.nl" schreef: > In my experience it's often better to wait with adding \break > commands until the score is complete. Sometimes Lilypond > automatically chooses better linebreak choices then. I sometimes use the

Re: how to get short broken ties

2016-06-22 Thread Werner LEMBERG
>> Note that this is not a theoretical issue. Especially in French >> impressionistic piano music like the works of Debussy and Ravel >> I've seen such a notation, and having a `\shortTie' command would >> be handy. > > See . Ah, ok,

Re: Placement of Chorus for Hymn

2016-06-22 Thread BGM
Harm - thanks! That's more like what I imagined. It lets me keep the chorus and the verses in separate vars - it's just what I was hoping for. Thanks for taking the time! -- View this message in context:

Re: \accidentalStyle for common choir notation

2016-06-22 Thread Phil Holmes
- Original Message - From: "David Wright" To: "Jonathan Scholbach" Cc: "Phil Holmes" ; Sent: Tuesday, June 21, 2016 5:45 PM Subject: Re: \accidentalStyle for common choir notation On Tue

Re: Placement of Chorus for Hymn

2016-06-22 Thread Thomas Morley
2016-06-22 3:57 GMT+02:00 BGM : > Actually, no, you can't assume I haven't tried it, thank you very much. > > I was hoping there was a more graceful way of doing it besides using skips. > > But skips work. I guess I'll just use skips. > > Thank you for your time. I do

Re: Custom / Fine tuning vertical space between piano staff lines

2016-06-22 Thread Thomas Morley
2016-06-17 2:28 GMT+02:00 Harald Christiansen : > Hi, > > I need to add some supplemental white space between piano staff lines (to > avoid a crowded look and near clashes). > > I looked long and hard at TFM _and_ whatever snippets I could find, but > unfortunately I am