Re: How does one get rid of a tagline?

[DJF]

On Dec 24, 2019, at 10:53 AM, Peter Toye  wrote:
> 
> I want an absolutely clean end to a score, but whatever I try I still get a 
> tagline advertising LilyPond. I've tried setting tagline to ##f and "" and 
> neither works.
> 

When I’ve had this happen, I inadvertently put the line outside the \header 
area (where it needs to be). I hope that your issue is this simple to fix!

-- Dan

Re: Espressivo marks

[DJF]

On Jul 26, 2020, at 12:32 PM, Martín Rincón Botero 
 wrote:
> 
> There's an old thread, where Thomas Morley came up with this script for 
> longer \espressivo marks. 
> This script however adds horizontal space before or after the note to make 
> room for the longer "articulation". Is there any way to prevent it from doing 
> that, for example by giving it more vertical space from the note? 
> Regards,
> Martín.

The \espressivo is treated like an articulation, so something like \once 
\override Script.padding = #1.0 put immediately before the note would move it 
higher.

Hope this helps,

Dan

Re: Multiple tempos at the same time and midi playback?

[DJF]

On Dec 13, 2018, at 7:33 AM, Yakir Arbib  wrote:
> 
> I write modern classical music in which each instrument has its' own
> separate tempo.  My question is, do you think it's possible to write
> something like that in LilyPond using separate tempo commands for each
> staff?
> 

To get a separate tempo marking in each staff, you would, in a \layout block, 
remove the Metronome_mark_engraver from the Score level, and add it to the 
Staff level. Because you’re new to LilyPond, I’ve attached a little longer and 
more complete example than usual and also included its contents below.

I would hasten to add that this is a visual fix only—the various tempi will not 
be rendered in MIDI playback. If you add a \midi { } line at the end of the 
\score block, it will use the last metronome mark (in the example below, 4 = 
110) as its tempo for all the parts. Someone more knowledgable than I will have 
to tell you if it's even possible to get separate tempi rendered 
simultaneously. I suspect not.

I hope this is helpful.

Dan

%

\version "2.19.80"

\layout {
  \context {
\Staff
\consists "Metronome_mark_engraver"
  }
  \context {
\Score
\remove "Metronome_mark_engraver"
  }
}

violin = \relative c'' {
  \key c \major
  \time 4/4
  \tempo 4 = 90
  a4 a a a
}

viola = \relative c' {
  \tempo 4 = 60
a4 a a a
}

cello = \relative c {
  \tempo 4 = 120
a4 a a a
}

contrabass = \relative c {
\tempo 4 = 110
a4 a a a 
}

violinPart = \new Staff \with {
  instrumentName = "Violin"
} \violin

violaPart = \new Staff \with {
  instrumentName = "Viola"
} { \clef alto \viola }

celloPart = \new Staff \with {
  instrumentName = "Cello"
 } { \clef bass \cello }

contrabassPart = \new Staff \with {
  instrumentName = "Contrabass"
} { \clef bass \contrabass }

\score {
  <<
\violinPart
\violaPart
\celloPart
\contrabassPart
  >>
}
%



tempo test.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Change right-end placement of VoiceFollower line

[DJF]

In the example below, I need the VoiceFollower line from the left hand to go to 
the A half-note in the right hand, not to the quarter rest. I’ve tried to see 
if I could move the right end of the line over using an \override, but I can 
only seem to move the entire line (like with 
VoiceFollower.bound-details.right.padding). Other setting combinations don’t 
seem to do anything,  or at least I haven’t yet found a combination that does 
what I need.

I could manually create a diagonal line--and I’ll do that only as a last 
resort--but I was curious if I’m missing something that might remedy this from 
within the VoiceFollower options. Any suggestions?

-- Dan


\version "2.19.80"

\score {
   \new PianoStaff
   <<
 \new Staff = "right"
  { \showStaffSwitch
a'4 \change Staff = "left" g8 f e d c b,
  }
  
  \new Staff = "left"
  { \clef bass   
\showStaffSwitch
a4 \change Staff = "right" r4 a'2
  }
   >>
}



staffswitch-test.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Change right-end placement of VoiceFollower line

[DJF]

On May 15, 2019, at 9:29 AM, Robin Bannister  wrote:
> 
> << s4 \new Voice r4 >>

That worked perfectly. I’m thrilled and amused that it took such little code 
for a solution, though I’ll admit that it took me a few minutes to understand 
why it worked. Very clever. Thank you!

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

Re: Error message

[DJF]

> On Jun 23, 2019, at 1:38 AM, Craig Dabelstein  
> wrote:
> 
> Hi Lilyponders,
> 
> Can anyone tell me what this error message means when trying to compile a 
> file?
> 
> Drawing 
> systems.../home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/flower/include/drul-array.hh:35:
>  failed assertion `d == 1 || d == -1'
> Exited with exit status 1.

This is my least favorite kind of error! Whenever I have these, it often 
concerns beaming, especially when LP is trying to beam more than two notes but, 
because of a misplaced octave or perhaps a clef change, it can't draw a 
satisfactory beam. Sometimes, just turning off beaming in 4s can allow the file 
to compile so that you can start investigating. 

http://lilypond.org/doc/v2.19/Documentation/notation/beams.en.html

If that doesn't work, and if the file has been compiling fine right along, I'll 
assume the issue has to do with the part most recently entered. I'll stick a %} 
at the end of the part and then pick a reasonable point to put a %{ and, with 
that section now "turned off", I'll see if the piece can compile. If not, I 
keep moving the %{ earlier and earlier until it does.

Hope this helps,

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

Re: how to implement the snippet in the attachment

[DJF]

On Oct 31, 2019, at 10:02 AM, Jinsong Zhao  wrote:
> 
> hi there,
> I am trying to transcribe a music sheet.  I have encountered the snippet in 
> the attachment.  I don't figure out a way to implement it.  I am now using an 
> alternative way like:

Use hidden notes in the second voice to accomplish this.

\relative c'' {
\key f \major
<<{bes2 ~ 8  4} \\
{r4  ~ \hideNotes 8 \unHideNotes s8 s4 } >>
}

--
Dan

Re: How to layout in unison and part music score?

[DJF]

On Feb 3, 2018, at 6:27 AM, lyuser.theg...@spamgourmet.com wrote:
> This would be what I need :) Unfortunately, I'm too dumb. Sorry, I'm a
> c, c++, c#, python, ruby, latex  and many other - developer, but the
> lilypond syntax manages to confuse me every time. I'm happy to set
> simple scores with lilypond and I really like it - but often, I just
> don't get it.
> 
> Could you please detail your pointer to the docs? An example would
> really be helpfull!

Markus,

I've made various choral scores like this, but it took quite awhile to get to 
the point of feeling somewhat comfortable about it. This is why I've enclosed 
an example for you. It's not intended to be definitive (I'm hard an expert at 
this yet) but rather a practical example that has worked for me in the past. 
It’s but one way of several that could be used to accomplish the task. It uses 
a unison voice staff in addition to the TTB voices, though you could also 
combine the unison voice with the first tenor part. It really all depends on 
how you want the score to look. Until such time as Kieren makes a demo/tutorial 
(which would be fantastic, I'm sure, and most welcome), I hope this helps to 
move you toward your goal.

—
Dan


\version "2.19.80"

global = { 
  \time 4/4
  \key f \major
}

unisonVoice = \relative c' {
\global
\clef "treble_8"
\repeat unfold 10 { a2 f }
R1*5
\repeat unfold 10 { a2 f }
\bar "|."
}

verseUnisonVoice = \lyricmode {
  hi there hi there hi there hi there hi there
  hi there hi there hi there hi there hi there
  sing now sing now sing now sing now sing now
  sing now sing now sing now sing now sing now
}

tenorOne = \relative c' { 
  \global
  \clef "treble_8" 
  R1*10
  \repeat unfold 5 { bes2 g }
  R1*10 
}

verseTenorOne = \lyricmode {
  bye now bye now bye now bye now bye now
}

tenorTwo = \relative c' { 
  \global
  \clef "treble_8" 
  R1*10
  \repeat unfold 5 { g2 e }
  R1*10  
}

verseTenorTwo = \lyricmode {
  bye now bye now bye now bye now bye now
}

bassOne = \relative c { 
  \global
  \clef bass
  R1*10
  \repeat unfold 5 { e2 c }
  R1*10
}

verseBassOne = \lyricmode {
  bye now bye now bye now bye now bye now
}

\layout { 
  \context {
  \Staff \RemoveEmptyStaves
  \override VerticalAxisGroup.remove-first = ##t
  \override VerticalAxisGroup.remove-empty = ##t
  }
}

\score {
  << 
\new ChoirStaff
<< 
   % enable choir bracket to show even on single staff
   \override ChoirStaff.SystemStartBracket.collapse-height = #4
  
\new Staff \with { instrumentName = "Voices" } { \unisonVoice } 
\addlyrics { \verseUnisonVoice }
\new Staff { \tenorOne } \addlyrics { \verseTenorOne }
\new Staff { \tenorTwo } \addlyrics { \verseTenorTwo }
\new Staff { \bassOne } \addlyrics { \verseBassOne }
>>
>>

}



test-TTB.ly
Description: Binary data


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

Re: fingering

[DJF]

> Gianmaria Lari  wrote:
>  
> But now the number inside the circle are too small. How could I keep the size 
> like in the first example and keep the fingering more separated?
 
> My english didn't help me :) I would like to keep the different fingering 
> elements in a vertical line but introduce some space between them.

This first solution doesn’t address the spacing or small size concerns you 
have, but it does make what you currently have more readable:

\version “2.19.80"
\fixed c' { 
\override Fingering.whiteout = ##t 
\override StringNumber.whiteout = ##t
\override Fingering.font-size = #-8
\set fingeringOrientations = #'(left)
\set stringNumberOrientations = #'(left)
  1
}

Below is an alternate, above-the-staff solution. You can adjust the spacing 
with the StringNumber.padding setting.

\version “2.19.80"
\fixed c' { 
\override Fingering.font-size = #-5
\override StringNumber.padding = #0.1
\set fingeringOrientations = #'(up)
\set stringNumberOrientations = #'(up)
  1
}

I’m not sure if these help you or not … perhaps someone else knows if it’s 
possible to control the vertical spacing within the staff; various methods I 
tried didn’t work.

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

Re: Using a tick as a bar line and vertically repositioning it

[DJF]

On Mar 14, 2017, at 2:57 PM, Joseph N. Srednicki  
wrote:
> 
> \version "2.19.54"
> \relative c {
>   \time 2/4
>   c' c \bar"'" |
>   c c \bar "|."
> }

You can modify the \breathe mark or just \include “gregorian.ly” in your file. 
You also have to set the regular bar line not to print, so I like to put it all 
in a variable. See 
http://lilypond.org/doc/v2.19/Documentation/notation/chants-psalms-and-hymns 
 
for options.

\version "2.19.54"

\include "gregorian.ly"

tick = { \divisioMinima \bar "" }

\relative c {
  \time 2/4
  c' c \tick |
  c c \bar "|."
}

I hope this helps,

Dan

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

Cross-staff tie interferes with staff spacing

[DJF]

I’ve got a cross-staff tie in an organ piece which appears to be responsible 
for adding unwanted space between the L.H. staff and the Pedal staff. If I 
comment out the \shape line, the spacing then conforms as expected, using the 
values in the second VerticalAxisGroup block, but then the tie goes way up 
above the R.H. staff. 

There are a few programming errors in the log: “My pure_y_common is a 
VerticalAlignment, which might contain several staves” and “Some of my 
vertical-skyline-elements are outside my VerticalAxisGroup”.

I have a suspicion that I may be going about this (staff spacing) in a way 
which is not ideal, but it’s what I’ve been using and it largely works. I’ll 
happily take any comments on that, but my primary concern at present is getting 
the tie in the right place, and, at the same time, having the proper spacing to 
the Pedal staff. I’d be grateful for any advice.

-- Dan



\version "2.19.58"

rightOne = \relative c' {
   4 g' fis 
}

leftOne = \relative c {
  \shape #'((-0.8 . -12.0) (-0.8 . -11.0) (-1.9 . -10.0) (-0.7 . -7.0)) Tie
   \change Staff = "right" \stemDown a2 
}

pedal = \relative c {
  a4 b2 
}

\score {
  <<
\new PianoStaff \with { \remove "Vertical_align_engraver" } % removes extra 
space before pedal staff
<<
  \new Staff = "right" \with  { 
\override VerticalAxisGroup.default-staff-staff-spacing =
#'((basic-distance . 12.3)
   (minimum-distance . 9)
   (padding . 1)
   (stretchability . 15)) } % section above controls spacing between hands
  { \rightOne }
 
\new Staff = "left" \with  {  
\override VerticalAxisGroup.default-staff-staff-spacing =
#'((basic-distance . 9.5)
   (minimum-distance . 7.0)
   (padding . 0)
   (stretchability . 0)) } % section above controls spacing between LH and 
pedal
{ \clef bass \leftOne }
>>
  \new Staff = "pedal" { \clef bass \pedal }
  >>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Phrasing Slur disappearing

[DJF]

It was difficult to decipher your very complex score, so I simplified it. It 
now appears to work, and I hope this helps you. 

--
Dan




test1.ly
Description: Binary data


> On Apr 8, 2017, at 10:25 AM, Gerard  wrote:
> 
> Dear All,
> 
> at a certain point in my score the phrasing slur disappears.
> In the attached example 1, two measures taken out of the score, the phrasing 
> slur is printed as it should.
> 
> As soon as I add the preceding measure, in example 2, the phrasing slur 
> disappears.
> All with the same warning while compiling.
> 
> Some advice is appreciated.
> 
> Thanks, Gerard
> 
> ___
> 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: Cross-staff tie interferes with staff spacing

[DJF]

On Apr 9, 2017, at 2:36 AM, Engraver  wrote:
> 
> I think the problem is the cross-staff tie itself. Without the \shape line it 
> is drawn above the right-hand staff, but the inner workings of lilypond 
> somehow 'remember'  the original starting point, i.e. above the left hand 
> staff. If you use the \shape line to visually lower the starting point of the 
> tie, you lower the original starting point of the tie as well, hence pushing 
> the pedal staff down.
> 
> Perhaps it's better to mimic the cross-staff tie with a cross-staff slur.
> 
> Regards,
> Auke
> 

Using a slur is a good work-around; I can live with that. Thank you!

--
Dan


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

Changing the length of voice follower lines

[DJF]

I’ve got a piano piece with many voice follower lines from one hand to the 
other. Most often the lines end up being too long and unsightly, extending 
through beams and stems. I know how to move them with 
VoiceFollower.extra-offset, but I can’t figure out how to change their length. 
I messed around with other things, like extents, but I don’t really understand 
those (I understand them theoretically, but not practically) and, anyway, 
nothing ever gets changed regardless of the values I use. Can’t help but think 
there’s probably an obvious answer, but I’m certainly not finding it!

What could I add below to shorten the right (top) end of the voice-follow line? 

Thanks for any help.

--
Dan


\version "2.19.58"

\score {
 \new PianoStaff 
   <<
 \new Staff = "right" \relative c'
 { \clef treble 2. f'4 }

\new Staff = "left" \relative c
{ \showStaffSwitch
  \clef bass r4 bes ees4 
  \change Staff = "right" \stemDown d'8 f, }
  >>
}



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

Changing the length of voice follower lines

[DJF]

I’ve got a piano piece with many voice follower lines from one hand to the 
other. Most often the lines end up being too long and unsightly, extending 
through beams and stems. I know how to move them with 
VoiceFollower.extra-offset, but I can’t figure out how to change their length. 
I messed around with other things, like extents, but I don’t really understand 
those (I understand them theoretically, but not practically) and, anyway, 
nothing ever gets changed regardless of the values I use. Can’t help but think 
there’s probably an obvious answer, but I’m certainly not finding it!

What could I add below to shorten the right (top) end of the voice-follow line? 

Thanks for any help.

--
Dan


\version "2.19.58"

\score {
  \new PianoStaff 
<<
  \new Staff = "right" \relative c'
  { \clef treble 2. f'4 }

 \new Staff = "left" \relative c
 { \showStaffSwitch
   \clef bass r4 bes ees4 
   \change Staff = "right" \stemDown d'8 f, }
>>  
}



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

Re: Changing the length of voice follower lines

[DJF]

2017-04-28 21:04 GMT+02:00 DJF :
>> I’ve got a piano piece with many voice follower lines from one hand to the 
>> other. Most often the lines end up being too long and unsightly, extending 
>> through beams and stems. I know how to move them with 
>> VoiceFollower.extra-offset, but I can’t figure out how to change their 
>> length. I messed around with other things, like extents, but I don’t really 
>> understand those (I understand them theoretically, but not practically) and, 
>> anyway, nothing ever gets changed regardless of the values I use. Can’t help 
>> but think there’s probably an obvious answer, but I’m certainly not finding 
>> it!
>> 
> On Apr 28, 2017, at 6:27 PM, Thomas Morley  wrote:
>   \once \override VoiceFollower.bound-details.right.padding = 2.4
>   %% Similar for bound-details.left.padding
>   %% Other keys are possible as well
> 
> HTH,
>  Harm

Many thanks for this! I had read a section in the Internals reference (I 
believe) which made me think that bound-details might hold a possible answer, 
but I couldn’t figure out what the correct syntax would need to be for the rest 
of the line … then I thought I just might be on the wrong track altogether. Now 
it makes sense. I appreciate your help!

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

Note spacing issue with accidental

[DJF]

In the code below, the last eighth note in voice two of both the right and left 
hand are too far to the right (even slightly more so in the piece from which 
this excerpt is taken, shown in the attached image). I’ve fiddled with various 
values using  \once \override NoteColumn.force-hshift and  \once \override 
Score.NoteColumn.X-offset but nothing ever happens. I think that the issue is 
the proximity (to the upper note) of the sharp on the C in the alto, because 
when I make it a C-natural, the spacing is normal. I don’t know what else to 
try … any hints? 

— 
Dan


\version "2.19.58"

rightOne = \relative c' { 
  \key g \major 
  d8 e fis g 
}

rightTwo = \relative c' { 
  c4 \tuplet 3/2 { d4 cis8 } 
}

leftOne = \relative c' { 
  \key g \major
  \tuplet 3/2 4 { a8 g fis g fis e } 
}

leftTwo = \relative c {
  c4 \tuplet 3/2 { b4 bes8 }
}

\score { 
  << 
\new PianoStaff <<
  \new Staff = "right" { << \rightOne \\ \rightTwo >> }
  \new Staff = "left" { \clef bass << \leftOne \\ \leftTwo >> }
>>
  >>
}

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

Re: Note spacing issue with accidental

[DJF]

> On May 11, 2017, at 1:40 PM, Knute Snortum  wrote:
> 
> I think you have to move the accidental to get the note to move.  I don't 
> really like the way the following looks, but at least it's an example of 
> moving the accidental:
> 
> rightTwo = \relative c' { 
>   c4 \tuplet 3/2 { d4 \tweak Accidental.Y-offset -0.25 cis8 } 
> }

Yeah, you’re right … not a perfect solution, but still quite helpful and works 
well, at least in this particular instance. Thank you!

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

Tied note with accidental over bar line adds unwanted space

[DJF]

When there’s an accidental on the uppermost note in a chord which is tied over 
a bar line, Lilypond makes space in the next bar as if the accidental were 
reprinted when two other conditions are true: there’s an accidental in a lower 
chord note, and--no surprise--if the interval between the notes is less than a 
6th. Of course, this causes the lower note's accidental to be too far left from 
its notehead.

You can see this displacement on the first beat of bars 2 & 3 in the example 
below, whereas subsequent tie/accidental combinations are fine.

I tried searching the bug reports for this, but clearly there’s an art to that 
I don’t yet possess, so I finally gave up …

I’ve seen an example of moving an accidental in a single note using \once 
\override Staff.AccidentalPlacement.right-padding, but that doesn’t seem to 
work in a chord. But even if I were able to do that, there would still be 
unwanted extra space after the bar line. The only thing I’ve found to do is 
change the tie to a slur (then tweak it, of course, so it looks like a tie) and 
then remove the accidental in the next bar (I don’t need MIDI output, so the 
wrong note isn’t a problem). 

This, though, has already come up several times in the music I’m currently 
working on, so I was wondering if there's another workaround or something I’m 
missing. Any suggestions?

\version “2.19.39"

\score {
  \new Staff \relative c' {
  \key ees \major
  \time 2/4 \clef treble 
 4 
4  
4 
4 
4 a~
2
   }
}

--
Dan

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

Re: Tied note with accidental over bar line adds unwanted space

[DJF]

On Apr 20, 2016, at 12:41 PM, David Kastrup  wrote:
> 
> Kieren MacMillan  writes:
> 
>> Hi Dan,
>> 
>> \version "2.19.39"
>> 
>> \score {
>>  \new Staff \relative c' {
>>  \key ees \major
>>  \time 2/4 \clef treble
>>  4 
>>  4  
>>  4 
>>  <\tweak Accidental.stencil ##f aeses des>4 
>>  4 a~
>>  2
>>   }
>> }
> 
> \tweak Accidental.stencil ##f
> 
>may be written a bit more high-level as
> 
> \single \omit Accidental
> 
>> It does look like a bug, though.
> 
> Yes, but I think we have an issue number for it already.  It's an effect
> of ties-over-linebreaks (and their effect on accidentals) being known at
> a point of time where the spacing is already rather fixed.
> 
> Another effect of the accidental being removed rather late in the game
> is that _if_ there is a line break (and the accidental is consequently
> left printed), another accidental _following_ right behind is left in
> place when it should be elided.  Better than removing it when it would
> be necessary, but still a nuisance.
> 
> -- 
> David Kastrup

I really appreciate these helpful and elegant solutions. Thank you both very 
much!

—
Dan


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

Re: Replying to posts

[DJF]

On Apr 29, 2016, at 12:20 AM, Andrew Bernard  wrote:
> 
> Hi Tim,
> 
> On 29 April 2016 at 13:48, Tim McNamara  wrote:
> 
>> Most mailing lists send a copy of the rules with the "welcome e-mail" that 
>> is sent someone subscribes to the list.  It's been long enough that I don't 
>> remember what the one I received said on the topic.
> 
> I just checked with a new subscription. No code or guidelines or hints
> are sent to new subscribers.
> 
> Andrew
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

It seems that all messages sent to the list have an automatic footer, as above. 
Couldn’t a line simply be added to that with something like this: Want to send 
a message to this list? Read these guidelines first: 

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

making a dashed line from one staff to another

[DJF]

I’m trying to draw a dashed line between notes in two staves. Ideally (using my 
example below), the line needs to start in the middle of the left-hand staff 
immediately above the first grace note and be long enough to end directly below 
the E-flat of the right hand. I can only manage one or the other … If I make 
the line longer (increasing the 6.9 #), it moves the staves apart even more, 
without changing where the line begins or ends in relation to the pitches. If I 
adjust the extra-offset, I can make the line start where I want, but that 
results in too much white space below the E-flat. Is there a way to get rid of 
that white space, or increase the length of the line without moving the staves 
apart, or is there a better way to approach this? 

The first picture uses the code below (with the line not starting low enough, 
but ending at the right spot). The second shows the white space if the Y of the 
extra-offset is set to -2.3 (the line starting where I want, but not ending 
where it should).

I’ll be grateful for any advice.

—
Dan


\version "2.19.39"

rightOne = \relative c' {
 f16 aes des ees ees,16 aes c ees
}

leftOne = \relative c' {
  \tuplet 3/2 { c8 bes aes' } 
  \once \override TextScript.extra-offset = #'( 1.0 . 0.0 )
   \acciaccatura { bes,16^\markup { 
 \override #'(thickness . 0.7)
 \override #'(off . 0.3)
 \draw-dashed-line #'(1.9 . 6.9) }
   c } bes4  
}

\score {
  \new PianoStaff 
  <<
\new Staff = "right"
  { \rightOne }
  \new Staff = "left"
  { \leftOne }
  >>
}

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

Re: making a dashed line from one staff to another

[DJF]

Thank you, Andrew & Klaus. Both solutions are excellent and very helpful. I 
learn quite a lot every week from being on this list!

Cheers,

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

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

[DJF]

On Jun 16, 2016, at 8:28 PM, Harald Christiansen  wrote:
> 
> I need to add some supplemental white space between piano staff lines (to 
> avoid a crowded look and near clashes).

Harald,

I think you were on the right track with staffgroup spacing, but sometimes 
implementing this stuff in scores can be confusing (at least I've found it so).

I had the same issue, and, after some research, came up with a template that 
works for me. The example below is a minimal version of that. If you try 
changing the values in the \score block (basic-distance, minimum-distance, 
padding, and stretchability), you can see how each value plays a role. As long 
as the values are sensible (in relation to each other), you can get quite good 
results. I generally leave the padding at 1 or 0, most often changing the basic 
& minimum distances—just enough to make that one system look good that you’re 
trying to improve, without making all the others too spread out. It will take 
some trial and error, but it does get easier to figure out with experience.

The key bit that allows this control is removing the Vertical_align_engraver. 
Also, in the \paper block, the system-system spacing (or other spacing 
variables you might use) obviously plays a role in overall spacing, but I 
always try compiling before using any of those to see how things look before I 
start messing.

I hope this is helpful.

—
Dan


\version "2.19.39"

\paper {
%  system-system-spacing.basic-distance = #22
  indent = 0\cm
  ragged-last-bottom = ##f
}

global = { 
  \time 4/4
  \key c \major
}
  
rightOne = \relative c' {
  \global
  c4 d e f
  g a b c
  \repeat unfold 50 { c,4 d e f 
   g a b c }
  \bar "|."
}

rightTwo = \relative c' {
  \global
  \repeat unfold 51 { c4 c c c 
   c c c c }
}

leftOne = \relative c' {
  \global
  c4 b a g
  f e d c
  \repeat unfold 50 { c'4 b a g
   f e d c }
}

leftTwo = \relative c {
  \global
\repeat unfold 51 { c4 c c c 
 c c c c }
}

\score {  
  \new PianoStaff \with { \remove "Vertical_align_engraver" }
<<
\new Staff = "right" \with {   
 \override VerticalAxisGroup.default-staff-staff-spacing =
  #'((basic-distance . 12)
   (minimum-distance . 8)
   (padding . 1)
   (stretchability . 16)) } 
  { \clef treble << \rightOne \\ \rightTwo >> }

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

}
  }

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

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

[DJF]

On Jun 21, 2016, at 5:57 PM, Harald Christiansen  wrote:
> 
> So, I eventually ended up solving the problem by using \markup with a
> two rows of blank strings attached to the E6, something like:
> e^\markup { \override #'(baseline-skip . 5) \column { " " " " } } i.e.
> adding an empty box with the desired high and depth above the note (it
> also have width but I can live with that).

That’s an interesting, creative solution that I wouldn’t have thought of 
trying, but it seems to have a side effect of making the next system much too 
close.

If, instead, you use something like this as your \paper block, you should get 
the same result, but with better spacing surrounding the system:

\paper {
  top-margin = 8\mm
  bottom-margin = 9\mm
  top-system-spacing.basic-distance = #12
  system-system-spacing =
  #'((basic-distance . 15.5)
   (minimum-distance . 13)
   (padding . 1)
   (stretchability . 17))
%  ragged-last-bottom = ##f
}

Another option would be to adjust the staff-height from 20 to 21. It solves the 
issue quite nicely, IMHO, but I’m not sure of your priorities.

I realize that these solutions don’t really speak to your quest of finding a 
“proper, general solution,” but at least there are ways to get fairly 
acceptable results, and without too much effort. Different scores may well 
require different solutions. If it looks good in the end, isn’t that enough?

Good luck, and if you find something else that works, I hope you’ll let us know.

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

Notes on wrong side of stem in triads

[DJF]

I’ve used Lilypond extensively—especially for organ music—and have never seen 
noteheads in a chord appear on the wrong side of the stem. Unfortunately, I 
can’t reproduce the enclosed problem in a minimal example because the same code 
works fine in a file by itself. This is in the left hand of an organ part, and 
I’m using 2.19.39, though I tried it with the latest version as well with the 
same result. However, the chords look fine with 2.18, but using that version 
that isn’t an option because it creates many other (and more significant) 
issues. If I put the stem direction up, the chords also look fine … but, of 
course, they all need to be stems down. This was also happening in one 
right-hand chord in a subsequent bar, but ultimately I changed that chord 
slightly and it’s no longer an issue there. This only seems to happen with 
(some) triads …

I’m using a choir & organ template generated from within Frescobaldi … this 
happens no where else in the 86-bar piece, and no errors are generated when 
compiling.

The code for the example is below, but, like I said, it works just fine out of 
the context of my piece: 

8 16  8[ ]  

Any thoughts?

—
Dan

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

Re: Notes on wrong side of stem in triads

[DJF]

> 2016-10-17 10:09 GMT+02:00 Pierre Perol-Schneider 
> mailto:pierre.schneider.pa...@gmail.com>>:
> Hi Dan,
> At least you'll find a workaround here:
> http://lsr.di.unimi.it/LSR/Item?id=861 
> <http://lsr.di.unimi.it/LSR/Item?id=861>
> 
> On Oct 18, 2016, at 3:43 AM, Pierre Perol-Schneider 
>  wrote:
> Hi Dan,
> One silly question: Does that change anything if you don't force the A 
> natural sign; e.g.:
> 8 16  8[ ]  
> 
> ??
> Cheers,
> Pierre


Pierre, I appreciate your stab at a work-around. While the LSR you mentioned 
does help get all the note heads in the right spot, the major side effect is 
that the 8th note beams disappear. So that I could “go to press”, I did use 
that code, however, and graphically inserted some beams into the final PDF. Not 
ideal, to be sure … but it was better than the alternative!

And no, removing the forced A natural sign doesn’t change anything.

> 2016-10-17 9:48 GMT+02:00 Davide Liessi  <mailto:davide.lie...@gmail.com>>:
> 2016-10-17 3:46 GMT+02:00 DJF mailto:delf...@me.com>>:
> > Unfortunately, I can’t reproduce the enclosed problem in a minimal example 
> > because the same code works fine in a file by itself.
> 
> "Minimal example" means that if you remove anything the problem is
> gone, so if the code works in what you call a minimal example, that
> was *not* a minimal example for your problem: sometimes bugs are
> encountered only in long scores.


Davide, I do understand the concept of a minimal example … it’s just that I 
couldn’t get to that point. I really had tried myriad things to isolate the 
issue. In the past, I have spent weeks working on some little (but important) 
problems and usually I find the solution before seeking help from the list. I 
just didn’t have weeks to spend this time, and this particular problem seemed 
so random in comparison. If you really want to see the score, send me a private 
note, but, as I’ve mentioned above, I had to finish it so I could move on to 
other things. Unsolved mysteries are irksome, though!

Best wishes,

Dan

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

Re: Dorico release and tutorials

[DJF]

On Oct 19, 2016, at 8:21 PM, Andrew Bernard  wrote:
> 
> There's no trial download version, and no educational or other discount
> pricing.
> 

Actually, at 
http://www.steinberg.net/en/newsandevents/news/newsdetail/article/dorico-is-now-available-3939.html
 

 it says:

There is educational pricing for qualifying teachers and students and a special 
time-limited crossgrade offer for qualifying Sibelius and Finale users.

At the regular shop page, only two options appear to add to your cart: “Dorico 
Full Version” and “Crossgrade from Sibelius, Finale or Notion” … with the 
crossgrade pricing at $279.99 (US). The Education version actually appears on a 
separate page 
(http://www.steinberg.net/en/shop/education/educational_products.html 
) with 
various (and somewhat confusing) pricing from $159.99 to $349.99.

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