Re: Follow-up question to alternate music fonts
Urs Liska wrote Actually that's what I mean. I suggest to add the _ability_ to easily change the notation font through the make-pango-tree approach and let the user install additional fonts at will. As said this is the same as with any other (notation or any other) program. Of course you expect your word processor to let you choose from arbitrary fonts, but you're completely OK with installing fonts yourself. Urs Urs has the right idea. I never meant that the fonts needed to be included in the LilyPond code base, only more like an add-in function, so that probably answers my own question. For now, I'll look into the appropriate way/place to make these alternate fonts available to those who'd like to use them. Thank you all for your comments and thoughts on this matter! Happy Engraving! Abraham P.S. Urs, Unfortunately, the build scripts I use to create these fonts don't automatically pull the Bravura glyphs and put them in the right places for use in LilyPond. There were too many little things I did to put together the Profondo font that it's not an automated process. In any case, I don't think Bravura will be changing much, so I don't know if this will be much of a need in the future. I suppose an automated script for converting a SMuFL-compatible font to a LilyPond-compatible font could be created, but there'd have to be more of them out there for that to be useful since there's currently only Bravura follows this standard. I guess we'll see. Oh, and I looked into creating new functions so that the default ones can still be used. This is not difficult, but still requires a patched font.scm since the new functions also need to live in that file to work properly. They require some of the variables that exist only within the scope of the other classes/functions/variables in that file. I guess that's all for now :) -- View this message in context: http://lilypond.1069038.n5.nabble.com/Follow-up-question-to-alternate-music-fonts-tp164259p164385.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
2014-07-13 5:38 GMT+02:00 Paul Morris p...@paulwmorris.com:
Here we go:
Nice Paul !
And here's a complement to get rid of the gap between startStaff and stopStaff
:
\version 2.18.2
{
g d c d
c d
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
g d
c d c d
c d
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #1
g d
c d c d
}
Would you mind if I put it in the LSR ?
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
2014-07-13 9:46 GMT+02:00 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com: Would you mind if I put it in the LSR ? See : http://lsr.di.unimi.it/LSR/Item?id=928 Cheers, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Change order of above staff objects
Hello,
I have a score with some long tempo items. Since my part has multiple
full bar rests I get several rehearsal marks in the area of the tempo.
Unfortunately they are placed above the tempo. How can I get the
rehearsal mark immediately above the staff line?
Minimum example:
\version 2.18.0
{
\tempo Allegretto ma non troppo 4=100
\time 4/4
%\compressFullBarRests
R1*2 \mark\default
R1 R
b' d'' f'' a'' %c'''
}
The rehearsal mark is too high. Somehow it gets a lower place when I
remove *both* comment characters.
Regards
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Change order of above staff objects
Hi Helge,
2014-07-13 10:26 GMT+02:00 Helge Kruse helge.kr...@gmx.net:
How can I get the rehearsal mark immediately above the staff line?
Try :
\version 2.18.0
{
\once\override Score.MetronomeMark.outside-staff-priority = #2000
\tempo Allegretto ma non troppo 4=100
\time 4/4
\compressFullBarRests
R1*2
\mark\default
R1 R
b' d'' f'' a'' c'''
}
See also :
http://www.lilypond.org/doc/v2.18/Documentation/learning/outside_002dstaff-objects.html#the-outside_002dstaff_002dpriority-property
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
stem length in polyphony
Hi all,
I'm looking for a decent solution for, what seems to me as a tricky
situation :-)
I've attached an image and a .ly example.
I've tried overriding the beamed lengths of the 16th notes, but it does not
seem to work with e.g. \override Stem.details.beamed-lengths = #'(0.5) .
This override does work in a single voice.
I searched and found a possible solution, on a pdf I found on the web,
which looks good, but I have no idea how to achieve it in lilypond,
grtz,
Bart
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
\version 2.18.2
\include ../../../library/guitarstuff.ly
\include ../../../library/shorthand.ly
\header {
}
\paper {
}
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4 dis8 dis |
}
centerup = \relative e' {
\global
b16\rest g' fis e fis8 fis |
}
centerlow = \relative e {
\global
\override Stem.details.beamed-lengths = #'(0.5) s16 b' a g a16 b a b |
}
\score {
\new Staff \with {
} { \clef treble_8 \upper \\ \lower \\ \centerup \\ \centerlow }
\layout { }
\midi {
\context {
\Score
}
}
\header {
}
}
possible
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Skipping reminder accidentals in
The q may be used for repeated chords what makes notation efficient. I
duplicates the last chord literally. But when it contains reminder
accidentals they make no sense in the repeat. Is there a way to tell q
that it should skip these accidentals?
Example:
\relative c'
{
% q duplicates literally the accidentals
fis a d fis4 f! a d f! q q |
% desired output
fis a d fis4 f! a d f! f a d f q |
}
Regards Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stem length in polyphony
sorry, the image with the possible solution lacked an extension, second attempt is here http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/ 2014-07-13 10:52 GMT+02:00 bart deruyter bart.deruy...@gmail.com: Hi all, I'm looking for a decent solution for, what seems to me as a tricky situation :-) I've attached an image and a .ly example. I've tried overriding the beamed lengths of the 16th notes, but it does not seem to work with e.g. \override Stem.details.beamed-lengths = #'(0.5) . This override does work in a single voice. I searched and found a possible solution, on a pdf I found on the web, which looks good, but I have no idea how to achieve it in lilypond, grtz, Bart http://www.bartart3d.be/ On facebook https://www.facebook.com/pages/BartArt3D/169488999795102 On Twitter https://twitter.com/#%21/Bart_Issimo On Identi.ca http://identi.ca/bartart3d On Google+ https://plus.google.com/u/0/b/116379400376517483499/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Change order of above staff objects
Am 13.07.2014 10:44, schrieb Pierre Perol-Schneider:
\version 2.18.0
{
\once\override Score.MetronomeMark.outside-staff-priority = #2000
\tempo Allegretto ma non troppo 4=100
\time 4/4
\compressFullBarRests
R1*2
\mark\default
R1 R
b' d'' f'' a'' c'''
}
See also :
http://www.lilypond.org/doc/v2.18/Documentation/learning/outside_002dstaff-objects.html#the-outside_002dstaff_002dpriority-property
Great, this works perfectly. I searched the notation reference only but
missed the corresponding paragraph. But it's there:
4.4.3 Vertical collision avoidance
Regards Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stem length in polyphony
Hi Bart,
2014-07-13 10:52 GMT+02:00 bart deruyter bart.deruy...@gmail.com:
I've attached an image and a .ly example.
Here's what I'd do :
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
dis8 dis |
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
\override Beam.positions = #'(-3.5 . -3)
\tweak NoteColumn.force-hshift #1.1
a16 b
\tweak NoteColumn.force-hshift #1.1
a[ b] |
\revert Beam.positions
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}
I've tried overriding the beamed lengths of the 16th notes, but it does not
seem to work with e.g. \override Stem.details.beamed-lengths = #'(0.5) .
This override does work in a single voice.
Try : \override Beam.positions (see above).
I searched and found a possible solution, on a pdf I found on the web,
which looks good, but I have no idea how to achieve it in lilypond,
Try :
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
dis8 dis |
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
\stemUp
\override Beam.positions = #'(2 . 2.5)
\shiftOnn
a16 b a[ b] |
\revert Beam.positions
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line width
Charles Marshall wrote: How can the length of a ragged last line be adjusted? With ragged-last-line = ##t , the line is too short to look good; with = ##f , it's right-justified and too long. Quick and nasty: at the end, append (in any voice) \stopStaff s16*40 and adjust the 40 to suit. Cheers, Robin ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in
Helge Kruse helge.kr...@gmx.net writes:
The q may be used for repeated chords what makes notation efficient. I
duplicates the last chord literally. But when it contains reminder
accidentals they make no sense in the repeat. Is there a way to tell q
that it should skip these accidentals?
Example:
\relative c'
{
% q duplicates literally the accidentals
fis a d fis4 f! a d f! q q |
% desired output
fis a d fis4 f! a d f! f a d f q |
}
Well, just write the latter version. This is similar to
\new Voice \with { \remove Note_heads_engraver
\consists Completion_heads_engraver
}
{ c!\longa }
which I (wrongly) thought we had already dealt with. It appears I have
mentioned this when entering issue 3593 as having _also_ been discussed,
illustrating how important the bug squad is for not letting reports get
dropped silently.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
Am 13.07.2014 11:57, schrieb David Kastrup: fis a d fis4f! a d f! f a d f q Well, just write the latter version. Well. this means don't use q when you have accidentals in a chord. My example has a fourth chord. Without it the latter version doesn't have any q. It appears I have mentioned this when entering issue 3593 as having _also_ been discussed, illustrating how important the bug squad is for not letting reports get dropped silently. So is this considered as a bug? Since #3593 is closed it should be recorded as a new bug? Regards Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stem length in polyphony
Hey,
thanks, both work like a charm. I prefer the version with the stems up,
because the note heads are better positioned between the two other voices,
it's more clear that they belong together when playing.
grtz,
Bart
http://www.bartart3d.be/
On facebook https://www.facebook.com/pages/BartArt3D/169488999795102
On Twitter https://twitter.com/#%21/Bart_Issimo
On Identi.ca http://identi.ca/bartart3d
On Google+ https://plus.google.com/u/0/b/116379400376517483499/
2014-07-13 11:29 GMT+02:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
Hi Bart,
2014-07-13 10:52 GMT+02:00 bart deruyter bart.deruy...@gmail.com:
I've attached an image and a .ly example.
Here's what I'd do :
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
dis8 dis |
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
\override Beam.positions = #'(-3.5 . -3)
\tweak NoteColumn.force-hshift #1.1
a16 b
\tweak NoteColumn.force-hshift #1.1
a[ b] |
\revert Beam.positions
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}
I've tried overriding the beamed lengths of the 16th notes, but it does
not seem to work with e.g. \override Stem.details.beamed-lengths = #'(0.5)
. This override does work in a single voice.
Try : \override Beam.positions (see above).
I searched and found a possible solution, on a pdf I found on the web,
which looks good, but I have no idea how to achieve it in lilypond,
Try :
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
dis8 dis |
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
\stemUp
\override Beam.positions = #'(2 . 2.5)
\shiftOnn
a16 b a[ b] |
\revert Beam.positions
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
Helge Kruse helge.kr...@gmx.net writes: Am 13.07.2014 11:57, schrieb David Kastrup: fis a d fis4f! a d f! f a d f q Well, just write the latter version. Well. this means don't use q when you have accidentals in a chord. Reminder or forced accidentals, it would appear. My example has a fourth chord. Without it the latter version doesn't have any q. It appears I have mentioned this when entering issue 3593 as having _also_ been discussed, illustrating how important the bug squad is for not letting reports get dropped silently. So is this considered as a bug? Since #3593 is closed it should be recorded as a new bug? With q, it is more of an enhancement request. With Completion_heads_engraver, it is more of a bug than a limitation because you cannot really work around it. Both are separate requests concerning separate code. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Rehearsal marks in markup
I want to writing somthing like
\markup{\tempoFormat{Allegretto} \circle{1}-\circle{16} tacet}
To indicate that the player shall rest until the orchester is at
rehearshal mark 16. I would like to place this in the Dynamic line of
the PianoStaff
\new PianoStaff
\new Staff=upper { c'1 \bar || s1 | \mark#16 d'1 }
\new Dynamics { s1 s1^\markup{ Allegretto 1-16 tacet } \break s4 }
\new Staff=lower { R1s1 | d'1
The \circle{} is no Lilypond syntax. It shall indicate that the
rehearshal mark shall be displayed in the currently selected
#format-mark-circle-numbers.
I did not find a way to call the format-mark-circle-numbers function
to insert the reahearsal marks in the \markup. Additionally I would also
like to format the tempo in the format that is used in \tempo.
How can this be achived?
Regards Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rehearsal marks in markup
- Original Message -
From: Helge Kruse helge.kr...@gmx.net
To: lilypond-user@gnu.org
Sent: Sunday, July 13, 2014 1:15 PM
Subject: Rehearsal marks in markup
I want to writing somthing like
\markup{\tempoFormat{Allegretto} \circle{1}-\circle{16} tacet}
To indicate that the player shall rest until the orchester is at
rehearshal mark 16. I would like to place this in the Dynamic line of the
PianoStaff
\new PianoStaff
\new Staff=upper { c'1 \bar || s1 | \mark#16 d'1 }
\new Dynamics { s1 s1^\markup{ Allegretto 1-16 tacet } \break s4 }
\new Staff=lower { R1s1 | d'1
The \circle{} is no Lilypond syntax. It shall indicate that the rehearshal
mark shall be displayed in the currently selected
#format-mark-circle-numbers.
I did not find a way to call the format-mark-circle-numbers function to
insert the reahearsal marks in the \markup. Additionally I would also like
to format the tempo in the format that is used in \tempo.
How can this be achived?
Regards Helge
If you check circling text in the NR index, it shows a command that you
say doesn't exist. How about:
{ c''1 ^\markup { \circle { 16 } } }
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
On 13/07/14 11:49, David Kastrup wrote: Helge Kruse helge.kr...@gmx.net writes: Am 13.07.2014 11:57, schrieb David Kastrup: fis a d fis4f! a d f! f a d f q Well, just write the latter version. Well. this means don't use q when you have accidentals in a chord. Reminder or forced accidentals, it would appear. My example has a fourth chord. Without it the latter version doesn't have any q. It appears I have mentioned this when entering issue 3593 as having _also_ been discussed, illustrating how important the bug squad is for not letting reports get dropped silently. So is this considered as a bug? Since #3593 is closed it should be recorded as a new bug? With q, it is more of an enhancement request. With Completion_heads_engraver, it is more of a bug than a limitation because you cannot really work around it. Both are separate requests concerning separate code. I am just not really understanding what technically these are as the thread talks about 'note splitting' and the like and this thread talks about repeated chords/notes using 'q'. So if you could give me some appropriate tracker titles, I can hunt down the relevant threads and create the trackers more quickly. Thanks James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
James pkx1...@gmail.com writes: On 13/07/14 11:49, David Kastrup wrote: Helge Kruse helge.kr...@gmx.net writes: Am 13.07.2014 11:57, schrieb David Kastrup: fis a d fis4f! a d f! f a d f q Well, just write the latter version. Well. this means don't use q when you have accidentals in a chord. Reminder or forced accidentals, it would appear. My example has a fourth chord. Without it the latter version doesn't have any q. It appears I have mentioned this when entering issue 3593 as having _also_ been discussed, illustrating how important the bug squad is for not letting reports get dropped silently. So is this considered as a bug? Since #3593 is closed it should be recorded as a new bug? With q, it is more of an enhancement request. With Completion_heads_engraver, it is more of a bug than a limitation because you cannot really work around it. Both are separate requests concerning separate code. I am just not really understanding what technically these are as the thread talks about 'note splitting' and the like and this thread talks about repeated chords/notes using 'q'. So if you could give me some appropriate tracker titles, I can hunt down the relevant threads and create the trackers more quickly. For q this thread is, as far as I remember, first mention. For Completion_heads_engraver, there was the thread explicitly mentioned in the issue description of issue 3593. With Completion_heads_engraver the issue might be called Completion_heads_engraver should not repeat forced/cautionary accidentals I think the thread for that also mentioned articulations, but those are probably trickier: you'd likely want a tie/slur begin to move to the last generated note, but keep fingerings/text scripts on the first, and stuff like manual beams make my head hurt. The first approximation would likely just drop all articulations on repeated notes. For q (chord repeats), there is just one issue. chord repeats should not repeat forced/cautionary accidentals. That's pretty straightforward. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
Hi all, chord repeats should not repeat forced/cautionary accidentals. That’s pretty straightforward. Of course [because it’s 'common sense’], I agree this should be the default behaviour… But I think it would be nice if there were still a way to override that, e.g., q! and q? to repeat the accidentals. Cheers, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
Kieren MacMillan kieren_macmil...@sympatico.ca writes: Hi all, chord repeats should not repeat forced/cautionary accidentals. That’s pretty straightforward. Of course [because it’s 'common sense’], I agree this should be the default behaviour… But I think it would be nice if there were still a way to override that, e.g., q! and q? to repeat the accidentals. I don't see that this makes sense. a! cis d? q! is going to be what? a cis d q? is going to be what? At some point of time, one just has to accept that q is a shorthand. Once it becomes hard figuring out the proper semantics, we are leaving the shorthand realm. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
Schneidy wrote
Nice Paul !
And here's a complement to get rid of the gap between startStaff and
stopStaff:
Thanks, and nice fix for that little gap, although it appears it increases
the spacing between the notes, as in the second measure here:
http://lsr.di.unimi.it/LSR/Item?id=928
One limited workaround is to start and stop the staff at bar lines:
\version 2.18.2
{
g d c d
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
g d c d
}
{
g d c d
g d c d
}
Also, would it make sense to combine these snippets?
http://lsr.di.unimi.it/LSR/Item?id=928
http://lsr.di.unimi.it/LSR/Item?id=917
Or is it better to have two?
Cheers,
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Shorten-ledger-lines-tp164380p164419.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: stem length in polyphony
Am 13.07.2014 11:29, schrieb Pierre Perol-Schneider:
Hi Bart,
2014-07-13 10:52 GMT+02:00 bart deruyter bart.deruy...@gmail.com
mailto:bart.deruy...@gmail.com:
I've attached an image and a .ly example.
Here's what I'd do :
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
dis8 dis |
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
\override Beam.positions = #'(-3.5 . -3)
\tweak NoteColumn.force-hshift #1.1
a16 b
\tweak NoteColumn.force-hshift #1.1
a[ b] |
\revert Beam.positions
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}
Personally, I find it better not to change the beaming itself, but
rather to shift the lower one, as attached.
Best, Simonl
\version 2.18.2
global = {
\key e \minor
\time 2/4
}
upper = \relative e' {
\global
s2 |
\bar |.
}
lower = \relative e {
\global
e4
\override Beam.positions = #'(-5.5 . -5.5) % or similarâ¦
dis8 dis |
\revert Beam.positions
}
centerup = \relative e' {
\global
d16\rest g fis e fis8 fis |
}
centerlow = \relative e {
\global
s16 b' a g
a16 b a b |
}
\new Staff {
\clef treble_8
\upper \\ \lower \\ \centerup \\ \centerlow
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
2014-07-13 16:55 GMT+02:00 Paul Morris p...@paulwmorris.com:
Thanks, and nice fix for that little gap, although it appears it increases
the spacing between the notes, as in the second measure here:
http://lsr.di.unimi.it/LSR/Item?id=928
Yep, I've seen that but did not find any workaround.
One limited workaround is to start and stop the staff at bar lines:
\version 2.18.2
{
g d c d
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
g d c d
}
{
g d c d
g d c d
}
Ok.
Also, would it make sense to combine these snippets?
http://lsr.di.unimi.it/LSR/Item?id=928
http://lsr.di.unimi.it/LSR/Item?id=917
Or is it better to have two?
I'd rather keep both.
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Barline at beginning of lines of music.
On Sat, 2014-07-12 at 13:15 +0100, Richard Shann wrote:
I think I have it now:
http://www.lilypond.org/doc/v2.18/Documentation/notation/bars#index-bar-lines
This and other special bar lines may be inserted manually at any point.
When they coincide with the end of a measure they replace the simple bar
line which would have been inserted there automatically. When they do
not coincide with the end of a measure the specified bar line is
inserted at that point in the printed output.
would perhaps be better explained as:
This and other special bar lines may be inserted manually at any point.
Each special barline prescribes *three* things - what to show if the
barline occurs at the beginning of a line, what to show when it
coincides with the end of a line and what to show when it comes
elsewhere (ref: definBarline). When they coincide with the end of a
measure they replace the simple bar line which would have been inserted
there automatically. When they do not coincide with the end of a measure
the specified bar line is inserted at that point in the printed output,
according to its position on the line. If two \bar commands come one
after the other, the first is ignored.
I was getting stuck by imagining that \bar literally inserted a barline,
even though I had realized that it did something smarter.
This example fails to follow the description above:
\version 2.18.0
\defineBarLine ] #'(:|| || ||)
{
c2 \bar ] c2 \bar ]
\break
\bar ]
d
}
This I read as saying that \bar ] should show as a double bar when
mid-line (my interpretation of the third element of the list, called
span in the documentation. But it is typesetting as a horned solid
barline.
One of the things not stated in the 2.18 docs is what strings are
allowed as the first argument to \defineBarLine. The examples all show
strings consisting of already defined (?) barline types with optionally
extra stuff separated by a hyphen. Except, perhaps that ] used without
providing a \defineBarline for it doesn't typeset anything.
I'm now thoroughly confused :(
Richard
Richard
On Sat, 2014-07-12 at 00:38 +0200, Thomas Morley wrote:
2014-07-11 21:14 GMT+02:00 Richard Shann rich...@rshann.plus.com:
On Fri, 2014-07-11 at 18:11 +0100, James wrote:
On 11/07/14 18:00, Richard Shann wrote:
It is somewhat embarrassing to reply to one's own question but:
\defineBarLine | #'(| | |)
does the trick.
Richard
So do we need to improve the documentation?
If so, what do you suggest?
Well, clearly
This and other special bar lines may be inserted manually at any point
where they make good sense in terms of good music typesetting practice.
would be an truer.
Or did you mean, should that override be documented? I can't answer that
because I don't know if it is a stable feature - I just guessed. In fact
I have further problems of a similar nature. The chord chart requires
double bars to be printed despite a start-repeat bar following on the
next line - even writing
\defineBarLine || #'(|| || ||)
does not cause the double bar to appear at the line end. There is surely
a lack of detail about what the list elements (end begin span) actually
mean.
Richard
Well, the following works for me:
\defineBarLine || #'(|| || ||)
{
c1
\break
\bar ||
d
}
Could you provide a tiny example?
Cheers,
Harm
___
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: Skipping reminder accidentals in q
Hi David, At some point of time, one just has to accept that q is a shorthand. Once it becomes hard figuring out the proper semantics, we are leaving the shorthand realm. Point taken… But to imply that coming up with a logically consistent interpretation of each possibility is disingenuous. Here’s one obvious option: qrepeats the previous chord, with cautionary or forced accidentals not reindicated q! repeats the previous chord, reindicating any forced accidentals q? repeats the previous chord, reindicating any cautionary accidentals q!? repeats the previous chord, reindicating any forced accidentals or cautionary accidentals. So, in your specific examples: a! cis d? q! is going to be what? The same output as a! cis d? a! cis d a cis d q? is going to be what? The same output as a cis d a cis d Cheers, Kieren. ___ Kieren MacMillan, composer www: http://www.kierenmacmillan.info email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
On 14-07-13 01:46 AM, Pierre Perol-Schneider wrote:
2014-07-13 5:38 GMT+02:00 Paul Morris p...@paulwmorris.com
mailto:p...@paulwmorris.com:
Here we go:
Nice Paul !
And here's a complement to get rid of the gap between startStaff and
stopStaff :
\version 2.18.2
{
g d c d
c d
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
g d
c d c d
c d
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #1
g d
c d c d
}
Would you mind if I put it in the LSR ?
Cheers,
Pierre
How about tucking the overrides into variables, so they could be put
into an \include library?
\version 2.18.2
sledger = { % shorten ledger lines
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
}
lledger = { % lengthen ledger lines
\once\hide Staff.BarLine \bar |
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #1
}
\score {
\relative c' {
g d c d
c d
\sledger
g d
c d c d
c d
\lledger
g d
c d c d
}
\layout {}
}
Cheers,
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands. You need to be able to throw something back.
-Maya Angelou, poet (1928- )
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Skipping reminder accidentals in q
On 13/07/14 15:21, David Kastrup wrote: James pkx1...@gmail.com writes: On 13/07/14 11:49, David Kastrup wrote: Helge Kruse helge.kr...@gmx.net writes: Am 13.07.2014 11:57, schrieb David Kastrup: fis a d fis4f! a d f! f a d f q Well, just write the latter version. Well. this means don't use q when you have accidentals in a chord. Reminder or forced accidentals, it would appear. My example has a fourth chord. Without it the latter version doesn't have any q. It appears I have mentioned this when entering issue 3593 as having _also_ been discussed, illustrating how important the bug squad is for not letting reports get dropped silently. So is this considered as a bug? Since #3593 is closed it should be recorded as a new bug? With q, it is more of an enhancement request. With Completion_heads_engraver, it is more of a bug than a limitation because you cannot really work around it. Both are separate requests concerning separate code. I am just not really understanding what technically these are as the thread talks about 'note splitting' and the like and this thread talks about repeated chords/notes using 'q'. So if you could give me some appropriate tracker titles, I can hunt down the relevant threads and create the trackers more quickly. For q this thread is, as far as I remember, first mention. For Completion_heads_engraver, there was the thread explicitly mentioned in the issue description of issue 3593. With Completion_heads_engraver the issue might be called Completion_heads_engraver should not repeat forced/cautionary accidentals I think the thread for that also mentioned articulations, but those are probably trickier: you'd likely want a tie/slur begin to move to the last generated note, but keep fingerings/text scripts on the first, and stuff like manual beams make my head hurt. The first approximation would likely just drop all articulations on repeated notes. http://code.google.com/p/lilypond/issues/detail?id=4011 For q (chord repeats), there is just one issue. chord repeats should not repeat forced/cautionary accidentals. That's pretty straightforward. http://code.google.com/p/lilypond/issues/detail?id=4010 James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
Colin Campbell-8 wrote
How about tucking the overrides into variables, so they could be put into
an \include library?
Good call. Or how about a music function that takes a parameter and scales
the default values, as shown below?
One problem is you can end up hiding a bar line that doesn't need to be
hidden if you try to change ledger widths at a bar line. So I made two
functions, one for use at bar lines and one for use between them. Not
elegant but at least something... (Now if only there was no gap created by
\stopStaff \startStaff...)
Cheers,
-Paul
\version 2.18.2
scaleLedgers =
#(define-music-function (parser location s) (number?)
Changes the width of ledger lines. 0.25 is default value
for both length-fraction and minimum-length-fraction
properties. By default ledger lines extend beyond the note
head by 0.25 times the width of the notehead.
Scales the default value by s.
(define x (* 0.25 s))
#{
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #x
\override Staff.LedgerLineSpanner.minimum-length-fraction = #x
#})
scaleLedgersBetweenBars =
#(define-music-function (parser location s) (number?)
#{
% A hidden bar line corrects the gap created by \stopStaff
% and \startStaff when \scaleLedgers is not called at a
% bar line, but increases spacing between notes.
\once \hide Staff.BarLine
\bar |
\scaleLedgers #s
#})
\score {
\relative c' {
g d c d
\scaleLedgers #2
g d c d
\scaleLedgers #0.5
g d c d
\scaleLedgers #1
g d c d
c d
\scaleLedgersBetweenBars #2
g d
c d c d
c d
\scaleLedgersBetweenBars #0.5
g d
c d c d
}
\layout {}
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Shorten-ledger-lines-tp164380p164432.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Shorten ledger lines
Note, when applied to the end of a Staff group, the bar segment that
joins both staves is omitted.
Avoiding line breaks works as described.
Thanks ! Javier
%
\version 2.18.2
\score {
\new PianoStaff
\new Staff \with { \remove Time_signature_engraver }
\relative c'''{
\repeat unfold 7 { c c c c }
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
\repeat unfold 7 { c c c c }
}
\new Staff \with { \remove Time_signature_engraver }
\relative c'''{
\repeat unfold 7 { c c c c }
\stopStaff
\startStaff
\override Staff.LedgerLineSpanner.length-fraction = #0.1
\override Staff.LedgerLineSpanner.minimum-length-fraction = #0.1
\repeat unfold 7 { c c c c }
}
\layout { indent = 0.0 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
