Lilypond on the web
Hello I just wanted to download the beta release of Lilypond. But I was lazy and just entered Lilypond in my Chrome web browser. Interestingly the second hit was http://lilypond.org/web/ what is a bit dated as it describes 2.12.3. Shall this stay on the server? Regards Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond on the web
2013/11/10 Helge Kruse helge.kruse-nos...@gmx.net Hello I just wanted to download the beta release of Lilypond. But I was lazy and just entered Lilypond in my Chrome web browser. Interestingly the second hit was http://lilypond.org/web/ what is a bit dated as it describes 2.12.3. Shall this stay on the server? The first result of 'lilypond' in google and duckgogo search is lilypond.org Maybe you searched 'lilypond web'? Anyway, there's an issue for this problem: https://code.google.com/p/lilypond/issues/detail?id=1272 and I see that we need a rewrite/redirect rule to put in .htaccess ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
On 11/10/2013 01:39 AM, Gilberto Agostinho wrote: And Peter, if I may bother you a bit more, could you also have a look on this message I posted some days ago if you have the time? http://lilypond.1069038.n5.nabble.com/Bar-numbers-position-td153274.html It also concerns notation standards, specifically the position of bar numbers, and I would be very glad to hear what you and Ms. Gould think about it (I really need to buy this book as soon as possible!). Thanks and take care! Gilberto I look into it and reply in that thread! Best Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \on-the-fly #first-page not working in bookTitleMarkup ?
So this time a less minimal example with a book and two bookparts.
The book title, which I would love to have on the first page, will never
get engraved.
In the meantime I experimented a bit more and found out that \on-the-fly
#first-page works very well in the page headers/footers, but doesn't work
in the bookTitleMarkup.
Jakub
--- snip
\version 2.17.24
\paper {
bookTitleMarkup = \markup {
\column {
\on-the-fly #first-page \fromproperty #'header:title
\fromproperty #'header:subtitle
}
}
}
\book {
\header {
title = Example book
}
\bookpart {
\header {
subtitle = part 1
}
\score { \relative c' { a } }
}
\bookpart {
\header {
subtitle = part 2
}
\score { \relative c' { b } }
}
}
--- /snip
2013/11/9 Eluze elu...@gmail.com
Jakub Pavlík wrote
Hi,
I would like to have the full book title on the first page of the first
bookpart only and an abbreviated book title on the first pages of the
subsequent bookparts.
unfortunately your code does not involve any \book or \bookpart where we
could see what you mean...
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/on-the-fly-first-page-not-working-in-bookTitleMarkup-tp153577p153608.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
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
Hi David, I am sorry if I expressed myself badly, I never wanted to say that you are proposing to judge things solely by the eye, while I propose to only use strict rules. What I wrote before was just a comment that came to my head while reading your message; I think I would have better expressed myself by using something like: we, as a group of people trying to improve LilyPond, should always be careful on how to judge things. I might personally like A or B, but using a book such as Gould's will always be the best way to go. Best regards, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beam-positions-and-time-signature-spacing-tp153538p153629.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: Beam positions and time signature spacing
Thanks a lot Peter, I will keep an eye on it. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beam-positions-and-time-signature-spacing-tp153538p153630.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: \on-the-fly #first-page not working in bookTitleMarkup ?
Hi Jakub, The book title, which I would love to have on the first page, will never get engraved. Don’t forget to put print-all-headers = ##t in your \paper block! Hope this helps, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar numbers position
Here is a short example of LilyPond's default bar numbers (left) and my personal tweaks (right). http://lilypond.1069038.n5.nabble.com/file/n153633/bar_no.png Now compare LilyPond's default output of bar numbers with these examples from our own Essay ( http://www.lilypond.org/doc/v2.17/Documentation/essay-big-page ): Bach's Cello Suite, Bärenreiter BA 320, ©1950: http://www.lilypond.org/doc/v2.17/Documentation/pictures/baer-suite1-fullpage.png Bach's Cello Suite, Henle no. 666, ©2000: http://www.lilypond.org/doc/v2.17/Documentation/pictures/henle-suite1-fullpage.png Bach’s Fugue in G minor from the Well-Tempered Clavier, Book I, BWV 861, Bärenreiter BA5070 (Neue Ausgabe Sämtlicher Werke, Serie V, Band 6.1, 1989): http://www.lilypond.org/doc/v2.17/Documentation/pictures/bwv861-baer-small.png -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bar-numbers-position-tp153274p153633.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: Beam positions and time signature spacing
Gilberto Agostinho gilbertohasn...@gmail.com writes: Hi David, I am sorry if I expressed myself badly, I never wanted to say that you are proposing to judge things solely by the eye, while I propose to only use strict rules. What I wrote before was just a comment that came to my head while reading your message; I think I would have better expressed myself by using something like: we, as a group of people trying to improve LilyPond, should always be careful on how to judge things. I might personally like A or B, but using a book such as Gould's will always be the best way to go. No, it isn't. If the very best authority states that A and V should be kerned by -0.15 em spaces and this looks bad, there are a number of possible explanations: a) the font metrics for our font are different: an em space might have a different relation to the letters b) the glyphs may be different to what the authority was working with c) the unadjusted placement may be different to what the authority was working with d) there might be a typo in print or in interpreting the wording One should never _discard_ what an authority has to say and should try tracking its reasoning, but if the results from following instructions don't actually lead to convincing results (in particular when comparing them with the printed results), one needs to do better than follow instructions. And more often than not, heeding all constraints mentioned in instructions at the same time is not even possible sensibly, and then one needs to relax them using sensible priorities. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Using the 'avoid-slur property (redux)
\version 2.17.95
\relative c { \override Slur.outside-staff-priority = #0 f16\mf( f a'8\p a8)
}
I play with #555. I change it to #0 (or #5) and it works.
Question: what is the difference of # number #555 and #0 (or #5)?
Emmanuel,
Ming
2. RE:Using the 'avoid-slur property (redux) (Daniel Rosen)
--
Message: 2
Date: Sun, 10 Nov 2013 03:47:25 +
From: Daniel Rosen drose...@gmail.com
To: Eluze elu...@gmail.com, lilypond-user@gnu.org
lilypond-user@gnu.org
Subject: RE: Using the 'avoid-slur property (redux)
Message-ID:
16ec1eb64c3829458f85e80f7458ffd955dd0...@enigma.rosen.lan
Content-Type: text/plain; charset=us-ascii
-Original Message-
From: Eluze [mailto:elu...@gmail.com]
Sent: Saturday, November 09, 2013 7:48 PM
To: lilypond-user@gnu.org
Subject: Re: Using the 'avoid-slur property (redux)
Am 09.11.2013 21:20, schrieb Daniel Rosen:
In the following example, I can't figure out how to get the DynamicText to
appear inside the Slur:
\version 2.17.95
\relative c {
f16( f a'8\p a8)
}
This is exactly the same question as the one posed in this thread from a
few years ago
(http://thread.gmane.org/gmane.comp.gnu.lilypond.general/42664/focus=4
2680), but the answer given concerning DynamicTexts confuses me a little---
is there no way to make this happen?
this seems to do it (but without avoid-slur):
\override Slur.outside-staff-priority = #555
Eluze
Hmm, I guess my example was too tiny. Here it is, again, modified; I need the
mf marking to be outside the slur but the p marking inside.
\version 2.17.95
\relative c {
\override Slur.outside-staff-priority = #555
f16\mf( f a'8\p a8)
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
David Kastrup wrote If the very best authority states that A and V should be kerned by -0.15 em spaces and this looks bad If it looks bad according to whom? There are tons of people on this list, each one possibly having his own view of what a pretty score consists of. David Kastrup wrote One should never _discard_ what an authority has to say and should try tracking its reasoning, but if the results from following instructions don't actually lead to convincing results (in particular when comparing them with the printed results), one needs to do better than follow instructions. And more often than not, heeding all constraints mentioned in instructions at the same time is not even possible sensibly, and then one needs to relax them using sensible priorities. Surely what you say here is very reasonable David, but you are being kind of relativistic here. We are not talking here about moving something by 0.01 units, are we? Have you seen how my .PNG example above compares to Gould's own examples? I would not dare to say these things are little poetic licenses we allowed ourselves to take. I am always and only posting here about things that (IMO) LilyPond got very wrongly. I am not going to measure the distance between a clef and the time signature and say look, authority A says we should have 2.5 units here, but LilyPond outputs only 2.47, what an absurd! -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beam-positions-and-time-signature-spacing-tp153538p153638.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: Using the 'avoid-slur property (redux)
Ming,
On Sun, Nov 10, 2013 at 5:46 AM, MING TSANG tsan...@rogers.com wrote:
\version 2.17.95
\relative c {
\override Slur.outside-staff-priority = #0
f16\mf( f a'8\p a8)
}
I play with #555. I change it to #0 (or #5) and it works.
Question: what is the difference of # number #555 and #0 (or #5)?
Well, in this case, none. Neither DynamicText nor Slur has a default
setting of 'outside-staff-priority. So any value you give to
Slur.outside-staff-priority (even -3000) is going to get the same result.
Now, of course, if you were trying to get a RehearsalMark to be under the
Slur, you'd have to select a value for Slur.outside-staff-priority that's
greater than the value for RehearsalMark, which is 1500.
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
still no ultimate way to create three-staff piano layout
It seems that there is no ultimate way to create three-staff piano layout.
When typing solo piano piece, there is no problem. The following does the job:
\score {
\new PianoStaff \with {
\remove Keep_alive_together_engraver
}
\new Staff = right \right
\new Staff = left \left
\new Staff = leftExtra \with { \RemoveEmptyStaves \override
VerticalAxisGroup.remove-first = ##t } \leftExtra
}
The question is: what if three-staff piano is part of orchestra? In orchestral
score, when piano is tacet, the whole PianoStaff should be removed from the
page.
Adding \RemoveEmptyStaves to every Staff is a bad idea, because when the
right staff has some nmusic and the left staff is empty - only the right
will be shown (And I want the left to be shown also!)
\score {
\new PianoStaff \with {
\remove Keep_alive_together_engraver
}
\new Staff = right \with { \RemoveEmptyStaves } \right
\new Staff = left \with { \RemoveEmptyStaves } \left
\new Staff = leftExtra \with { \RemoveEmptyStaves \override
VerticalAxisGroup.remove-first = ##t } \leftExtra
}
So, is there any way to create such layout? Maybe it's possible to:
1) remove single Staff from PianoStaff without removing
Keep_alive_together_engraver?
2) make Keep_alive_together_engraver to keep alive only two highest Staves in
PianoStaff?
-Karol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Using the 'avoid-slur property (redux)
Hi Ming,
On Sun, Nov 10, 2013 at 7:31 AM, MING TSANG tsan...@rogers.com wrote:
David,
Please take a look at the .png screen capture and the .ly file. The mf
was place inside and outside the slur.
\version 2.17.95
\markup with outside-staff-priority = #500.
\relative c {
\override Slur.outside-staff-priority = #500
f16\mf( f a'8\p a8)
}
\markup with outside-staff-priority = #0.
\relative c {
\override Slur.outside-staff-priority = #0
f16\mf( f a'8\p a8)
}
Ah, OK. It's because you need to consider DynamicLineSpanner, which has an
outside-staff-priority of 250.
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: still no ultimate way to create three-staff piano layout
karol wrote
The question is: what if three-staff piano is part of orchestra? In
orchestral score, when piano is tacet, the whole PianoStaff should be
removed from the page.
Adding \RemoveEmptyStaves to every Staff is a bad idea, because when the
right staff has some nmusic and the left staff is empty - only the
right will be shown (And I want the left to be shown also!)
\score {
\new PianoStaff \with {
\remove Keep_alive_together_engraver
}
\new Staff = right \with { \RemoveEmptyStaves } \right
\new Staff = left \with { \RemoveEmptyStaves } \left
\new Staff = leftExtra \with { \RemoveEmptyStaves \override
VerticalAxisGroup.remove-first = ##t } \leftExtra
}
So, is there any way to create such layout? Maybe it's possible to:
1) remove single Staff from PianoStaff without removing
Keep_alive_together_engraver?
2) make Keep_alive_together_engraver to keep alive only two highest
Staves in PianoStaff?
I think you can group or nest these contexts, eg.
\new StaffGroup \with { }
\new PianoStaff
\new Staff = A \A
\new Staff = B \B
\new Staff = C \C \with { }
and then (with \removeEmpty... specified) will always keep together but
staff C can be removed if it doesn't play.
maybe you have to construct an example to see how this works
hth
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/still-no-ultimate-way-to-create-three-staff-piano-layout-tp153648p153653.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
lilypond web is down???
Hi, is lilypond web down? I make a test whit www.isup.me and gives me that lilypond is down. Any hint? Do I miss a down news post? Thanks ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: still no ultimate way to create three-staff piano layout
Hi all,
I think you can group or nest these contexts, eg.
\new StaffGroup \with { }
\new PianoStaff
\new Staff = A \A
\new Staff = B \B
\new Staff = C \C \with { }
and then (with \removeEmpty... specified) will always keep together but
staff C can be removed if it doesn't play.
Maybe wrap it up as a custom context (e.g., \PianoThreeStaff), so that
template-level control — and sharing with the community at large — is easy?
Good luck!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond web is down???
Il dom, nov 10, 2013 at 4:18 , Marcos Press tdy.p...@gmail.com ha scritto: Hi, is lilypond web down? I make a test whit www.isup.me and gives me that lilypond is down. Any hint? Do I miss a down news post? confirmed it happens sometimes, probably they are doing maintenance..it's sunday :-) try again later ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond web is down???
Ok! Thanks! 2013/11/10 Federico Bruni fedel...@gmail.com Il dom, nov 10, 2013 at 4:18 , Marcos Press tdy.p...@gmail.com ha scritto: Hi, is lilypond web down? I make a test whit www.isup.me and gives me that lilypond is down. Any hint? Do I miss a down news post? confirmed it happens sometimes, probably they are doing maintenance..it's sunday :-) try again later ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
Message: 7 Date: Sat, 9 Nov 2013 16:29:26 -0800 (PST) From: Gilberto Agostinho gilbertohasn...@gmail.com To: lilypond-user@gnu.org Subject: Re: Beam positions and time signature spacing Message-ID: 1384043366945-153614.p...@n5.nabble.com Content-Type: text/plain; charset=us-ascii Hi David, ... I didn't try to modify the space-alist property, and I will have a look on it. But (as usual with my posts here), I am not trying to type a specific score right now, I am just commenting on how to improve LilyPond. I think you would be more successful in this endeavor if you would quote enough of the message you are replying to to give us poor readers enough context to figure out what you're saying. In this case we don't even know to whom you're replying - I can think of at least two Davids who are regular correspondents on this list. I know that at least I would benefit from this custom. Haven't you noticed that most other posters do it? Regards, Patrick Karl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
Patrick or Cynthia Karl-2 wrote Message: 7 Date: Sat, 9 Nov 2013 16:29:26 -0800 (PST) From: Gilberto Agostinho lt; gilbertohasnofb@ gt; To: lilypond-user@ Subject: Re: Beam positions and time signature spacing Message-ID: 1384043366945-153614.post@.nabble Content-Type: text/plain; charset=us-ascii Hi David, ... I didn't try to modify the space-alist property, and I will have a look on it. But (as usual with my posts here), I am not trying to type a specific score right now, I am just commenting on how to improve LilyPond. I think you would be more successful in this endeavor if you would quote enough of the message you are replying to to give us poor readers enough context to figure out what you're saying. In this case we don't even know to whom you're replying - I can think of at least two Davids who are regular correspondents on this list. I know that at least I would benefit from this custom. Haven't you noticed that most other posters do it? Regards, Patrick Karl ___ lilypond-user mailing list lilypond-user@ https://lists.gnu.org/mailman/listinfo/lilypond-user Hi Patrick, Sorry for the confusion, I am used to simply go to nabble.com to post, answer or simply check what is going on with LilyPond, and I realize now that by merely clicking reply to someone's message is not enough to find out where the reply was aimed (there are no automatic quotes or anything like this, contrary to using an e-mail). So I will be more careful and add quotes via the button up there; sorry for any confusion. Regards, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beam-positions-and-time-signature-spacing-tp153538p153659.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: Beam positions and time signature spacing
Gilberto Agostinho gilbertohasn...@gmail.com writes: Sorry for the confusion, I am used to simply go to nabble.com to post, answer or simply check what is going on with LilyPond, and I realize now that by merely clicking reply to someone's message is not enough to find out where the reply was aimed (there are no automatic quotes or anything like this, contrary to using an e-mail). So I will be more careful and add quotes via the button up there; sorry for any confusion. Uh, you quoted _everything_. Please don't. It's usually simple enough to use your mail reader or news reader or the web interface or whatever to get more context (as there are headers indicating the message threading). However, Patrick, judging from his quote, was responding to a _digests_. Those lose all threading information. The answer, _obviously_, is not to indiscriminately quote everything. That would makes the impact of thread posts grow quadratically with thread length, and of digest answers grow exponentially. So obviously one quotes _only_ what is immediately relevant to the reply. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beam positions and time signature spacing
dak wrote So obviously one quotes _only_ what is immediately relevant to the reply. Sorry, I will be more careful from now on. Thanks for pointing it out. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beam-positions-and-time-signature-spacing-tp153538p153662.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: Bar numbers position
2013/11/2 Gilberto Agostinho gilbertohasn...@gmail.com: Hello all, Today, while searching for scores at Mutopia, I came across this one produced in LilyPond 2.9.9: http://www.mutopiaproject.org/ftp/BachJS/BWV849/bwv849b/bwv849b-a4.pdf http://www.mutopiaproject.org/ftp/BachJS/BWV849/bwv849b/bwv849b.ly What intrigued me here is the position of the bar numbers. [] So my question(s) is(are): why there was a change in the bar number position between these two LilyPond versions? And why the decision of having them to the left and not to the right of this vertical line? Does anyone know if there is any standards related to this? I don't know what was the reason for the change, but... 2013/11/10 Gilberto Agostinho gilbertohasn...@gmail.com: Now compare LilyPond's default output of bar numbers with these examples from our own Essay ( http://www.lilypond.org/doc/v2.17/Documentation/essay-big-page ): Bach's Cello Suite, Bärenreiter BA 320, ©1950: http://www.lilypond.org/doc/v2.17/Documentation/pictures/baer-suite1-fullpage.png Bach's Cello Suite, Henle no. 666, ©2000: http://www.lilypond.org/doc/v2.17/Documentation/pictures/henle-suite1-fullpage.png Bach’s Fugue in G minor from the Well-Tempered Clavier, Book I, BWV 861, Bärenreiter BA5070 (Neue Ausgabe Sämtlicher Werke, Serie V, Band 6.1, 1989): http://www.lilypond.org/doc/v2.17/Documentation/pictures/bwv861-baer-small.png ...i believe the barnumbers in the engraved examples interfere with clefs. I've seen some scores where similarly placed barnumbers looked like clef transposition (especially when the first bar in a system was 8th or 15th, and the number was placed right above the clef...). I believe that LilyPond's placement has the advantage of being unambiguous. best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Automated custom clef settings for custom staves
Hi everyone,
Say you have a custom staff that needs custom settings for each of the
different clefs, namely middleCPosition to put the notes on the right lines
and spaces, and clefPosition to put the clef in the right vertical position.
You can put these settings into a variable and use that instead of the usual
syntax for setting a clef:
myBass = {
\clef bass
\set Staff.middleCPosition = #-2
\set Staff.clefPosition = #1
}
(Previous discussion:
http://lists.gnu.org/archive/html/lilypond-user/2013-02/msg00247.html )
But I figured out another way to do it that lets you use the standard input for
setting and changing clefs. See the snippet below. It stores the standard
clef function in a variable and then overwrites clef with a new music
function that passes the input/parameter through to the standard clef function
and also changes the other settings, depending on the clef.
It seems to work well. The only down side (so far) is that it affects all
clefs regardless of what kind of staff they're on. So if you try to put a
standard staff in the same file with your custom staff, the positions of notes
and clefs on the standard staff won't be correct.
So my question is whether there is some way to determine whether a given clef
is to be on a given custom staff or not, and only apply these setting changes
when that's the case. I've made an unsuccessful attempt at this using an
engraver, which I'll post in a follow-up email.
Thanks,
-Paul
%% BEGIN SNIPPET %%
\version 2.17.95
% Note: customization values are just for demo purposes
% and don't make sense for actual use
standardClefFunction = #clef
clef =
#(define-music-function (parser location clef-type) (string-or-symbol?)
#{
\standardClefFunction #clef-type
#(cond
((or (equal? clef-type treble) (equal? clef-type G))
#{
\set Staff.middleCPosition = #-4
\set Staff.clefPosition = #-4
#})
((or (equal? clef-type bass) (equal? clef-type F))
#{
\set Staff.middleCPosition = #3
\set Staff.clefPosition = #4
#})
((or (equal? clef-type alto) (equal? clef-type C))
#{
\set Staff.middleCPosition = #-1
\set Staff.clefPosition = #-1
#}))
#})
\layout {
\context {
\Staff
\name MyCustomStaff
\alias Staff
\override StaffSymbol.line-positions = #'(-4 -2 2 4)
% omitting other customizations to make tiny example
}
\context { \Score \accepts MyCustomStaff }
% omitting other contexts to make tiny example
}
music =
{
\clef treble
c'2 c'
\clef bass
c' c'
\clef alto
c' c'
\clef treble^8
c' c'
\clef tenor
c' c'
}
\new MyCustomStaff {
\music
}
\new Staff {
\music
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automated custom clef settings for custom staves
Below is my attempt to use a custom engraver to set custom clef settings but
only when the clefs appear in a particular custom staff context.
It doesn't quite work since the setting changes take effect too late. The
first note after the new clef is placed on the staff before the change to
middleCPosition has happened, and the change in clefPosition causes a
second clef to be drawn for each clef (after that first note), at the newly set
position.
Ideally the way to handle this *very* *very* marginal issue, would be to have
the default settings for middleCPosition and clefPosition for each kind of
clef, loaded at the staff level for each staff (as staff context properties?)
where the user could override them for any given staff and clef.
And... I think the phrase for that is patches welcome ?
I just wanted to share my attempt at this in case anyone else tries to go down
the same road.
-Paul
%% BEGIN SNIPPET %%
\version 2.17.95
% Note: customization values are just for demo purposes
% and don't make sense for actual use
\layout {
\context {
\Staff
\name MyCustomStaff
\alias Staff
\override StaffSymbol.line-positions = #'(-4 -2 2 4)
% omitting other customizations to make tiny example
}
\context { \Score \accepts MyCustomStaff }
% omitting other contexts to make tiny example
}
\layout {
\context {
\Score
\consists
#(make-engraver
(acknowledgers
((clef-interface engraver grob source-engraver)
(let* ((ctx (ly:translator-context source-engraver))
(ctx-name (ly:context-name ctx))
(glyph (ly:grob-property grob 'glyph))
(glyph-name (ly:grob-property grob 'glyph-name)))
;; (display glyph-name)(newline)
;; (display glyph)(newline)
;; (display ctx-name)(newline)
(if (equal? ctx-name 'MyCustomStaff)
(cond
;; G / Treble clef
((equal? glyph clefs.G)
(ly:context-set-property! ctx 'clefPosition 2)
(ly:context-set-property! ctx 'middleCPosition 10))
;; F / Bass clef
((equal? glyph clefs.F)
(ly:context-set-property! ctx 'clefPosition -2)
(ly:context-set-property! ctx 'middleCPosition -10))
;; C / Alto etc clef
((equal? glyph clefs.C)
(ly:context-set-property! ctx 'clefPosition 1)
(ly:context-set-property! ctx 'middleCPosition 6
}
}
music =
{
\clef treble
c' c' c' c'
\clef bass
c' c' c' c'
\clef alto
c' c' c' c'
\clef treble^8
c' c' c' c'
\clef tenor
c' c' c' c'
}
\new MyCustomStaff {
\music
}
\new Staff {
\music
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automated custom clef settings for custom staves
Paul Morris p...@paulwmorris.com writes: Ideally the way to handle this *very* *very* marginal issue, would be to have the default settings for middleCPosition and clefPosition for each kind of clef, loaded at the staff level for each staff (as staff context properties?) where the user could override them for any given staff and clef. And... I think the phrase for that is patches welcome ? Unlikely. That sounds like a whole awful mess without any apparent advantage. If you want a differently located clef, define it with another name rather than have particular staves messing with clef positions. Patches welcome is more for stuff that appears useful but is not currently a goal for anybody. Stuff that is likely to get accepted/appreciated when a patch is actually presented. So far I have seen nothing suggesting that this would be the case here. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automated custom clef settings for custom staves
dak wrote Paul Morris lt; paul@ gt; writes: Ideally the way to handle this *very* *very* marginal issue, would be to have the default settings for middleCPosition and clefPosition for each kind of clef, loaded at the staff level for each staff (as staff context properties?) where the user could override them for any given staff and clef. And... I think the phrase for that is patches welcome ? Unlikely. That sounds like a whole awful mess without any apparent advantage. If you want a differently located clef, define it with another name rather than have particular staves messing with clef positions. Patches welcome is more for stuff that appears useful but is not currently a goal for anybody. Stuff that is likely to get accepted/appreciated when a patch is actually presented. So far I have seen nothing suggesting that this would be the case here. Ok, good to have your feedback, and I can accept this assessment. There are surely bigger fish to fry in terms of LilyPond development and benefit for users. Just for the record though, for me the ideal or goal would be to be able to put the same music (in standard LilyPond syntax) including any clefs or clef changes, into either a custom staff or standard staff, and get the output you'd want for each. That separates content from presentation and LilyPond does a great job with this in almost all cases I've come across. Clefs are the rare exception. Currently you have to make changes in the music (the content) for custom clefs to work, whether that's defining a new clef with a non-standard name, or manually setting the middleCPosition and clefPosition with each clef change, optionally using tags to be able to strip out the custom parts in order to use the music with a standard staff. The custom clef music function at the top of this thread makes this separation of content and presentation possible when it comes to clefs. But it does require that you use only one type of staff in any given file. So that's quite good, at any rate, for such marginal use cases as these. Thanks, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Automated-custom-clef-settings-for-custom-staves-tp153665p153668.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: Automated custom clef settings for custom staves
Paul Morris p...@paulwmorris.com writes: Currently you have to make changes in the music (the content) for custom clefs to work, whether that's defining a new clef with a non-standard name, A definition of a new clef will usually occur outside of the music. or manually setting the middleCPosition and clefPosition with each clef change, optionally using tags to be able to strip out the custom parts in order to use the music with a standard staff. Sorry, I can't even make sense from what you write. The custom clef music function at the top of this thread makes this separation of content and presentation possible when it comes to clefs. I don't see that it does anything like that. It makes some clefs behave in surprising/unconsistent manner. But it does require that you use only one type of staff in any given file. So that's quite good, at any rate, for such marginal use cases as these. We have a number of clefs (like soprano, tenor, alto clef) that have different positions and shifts. It is no problem defining any such thing. I don't understand the problem. I have no clue what you are trying to achieve and why. You want some clefs to print different clefs than asked for when in a different staff. Why? How is that a useful feature? If you want a different clef, why should it be named the same? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar numbers position
Hi Janek, Janek Warchoł wrote ...i believe the barnumbers in the engraved examples interfere with clefs. I've seen some scores where similarly placed barnumbers looked like clef transposition (especially when the first bar in a system was 8th or 15th, and the number was placed right above the clef...). I believe that LilyPond's placement has the advantage of being unambiguous. I think you are right on this, it seems very logical. I only pointed it out because I never saw this style of bar numbers before. Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Bar-numbers-position-tp153274p153673.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: Automated custom clef settings for custom staves
David Kastrup wrote I don't understand the problem. I have no clue what you are trying to achieve and why. You want some clefs to print different clefs than asked for when in a different staff. Why? Ok, sounds like my examples were too tiny to make things clear. The custom staves I'm working with are for some of the alternative/experimental music notation systems like the ones shown here: http://musicnotation.org/systems/ The notes are mapped to different staff positions than the standard ones, and that means you also need custom clefs that work for that different mapping. (You have to set middleCPosition to get the notes in the right place on the staff for a given clef, and clefPosition to put the clef in the right place on the staff.) Hopefully that clarifies what I'm talking about. I am aware that it is a very marginal use case. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Automated-custom-clef-settings-for-custom-staves-tp153665p153674.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: \on-the-fly #first-page not working in bookTitleMarkup ?
Jakub Pavlík wrote So this time a less minimal example with a book and two bookparts. The book title, which I would love to have on the first page, will never get engraved. a minimal example is not defined by its length but by its accurateness in showing the problematic point(s). what happens if you omit the \on-the-fly condition in the bookTitleMarkup definition? In the meantime I experimented a bit more and found out that \on-the-fly #first-page works very well in the page headers/footers, but doesn't work in the bookTitleMarkup. yep - and you can find it in NR: Custom layout for headers and footers The \markup command \on-the-fly can be used to add markup conditionally to header and footer text defined within the \paper block, [...] hth Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/on-the-fly-first-page-not-working-in-bookTitleMarkup-tp153577p153675.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: What's the best way to fix these beams and staff spacing?
Adding the additional space via markup worked. Is this an issue I should create a bug tracker for? -- View this message in context: http://lilypond.1069038.n5.nabble.com/What-s-the-best-way-to-fix-these-beams-and-staff-spacing-tp153566p153678.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: still no ultimate way to create three-staff piano layout
Thanks Eluze!
So this is how three-staff piano layout should look like:
\score {
\new StaffGroup \with {
systemStartDelimiter = #'SystemStartBrace
\override VerticalAxisGroup #'staff-staff-spacing =
#'((basic-distance . 9)
(minimum-distance . 7)
(padding . 1)
(stretchability . 5))
}
\new PianoStaff \with {
\remove System_start_delimiter_engraver
\remove Span_bar_engraver
}
\new Staff = right \right
\new Staff = left \left
\new Staff = leftExtra \with {
\RemoveEmptyStaves
\override VerticalAxisGroup.remove-first = ##t
} \leftExtra
}
-Karol
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: still no ultimate way to create three-staff piano layout
karol wrote So this is how three-staff piano layout should look like: [...] yes - but please if you go public (eg. LSR) - and I hope you will - don't call the variables left or right; leftHand and rightHand seems less confusable within LilyPond thanks Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/still-no-ultimate-way-to-create-three-staff-piano-layout-tp153648p153680.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
glissando between notes within a semitone and Staff/TabStaff problems
This is a follow up to this thread:
http://lists.gnu.org/archive/html/lilypond-user/2012-05/msg00245.html
I've just come across the same problem and I have a couple of questions:
1. lilypond, by default, doesn't show the glissando line between two
noteheads positioned on the same staff line, because the end points are at
the same height and the glissando thickness is not big enough to make it
visible. Is this the expected behaviour?
2. AFAIK I cannot control the glissando in Voice without affecting also the
glissando displayed in TabVoice. On the other hand, I can control glissando
in TabVoice without altering the one in Voice. There's a workaround? (no
tags please :-))
%% SNIPPET
\version 2.17.96
music = \relative c' {
% flat glissando lines are visible on staff spaces
% they are not visible on staff lines, unless the thickness is increased
f4\glissando fis
g\glissando gis
\override Glissando.thickness = #2
a\glissando ais
b\glissando bis
c\glissando cis
% this override alters also TabVoice
\once \override Voice.Glissando.bound-details.left.Y = #.7
\once \override Voice.Glissando.bound-details.right.Y = #1.3
d\glissando dis
}
\score {
\new StaffGroup
\new Staff \music
\new TabStaff \music
\layout {
ragged-right = ##f
\context {
\Score
%\override Glissando.thickness = #2
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Preventing tempo marks stacking (redux)
Consider the following example:
\version 2.17.95
{
\compressFullBarRests
\tempo Allegro moderato 4 = 104
R1*20
\tempo Molto meno mosso 4 = 72
R1*20
\tempo Tempo primo
R1
}
I'd like the MultiMeasureRests to expand automatically so that the
MetronomeMarks don't get stacked on top of one another. Is there a way to make
this happen? (When this question was asked on the list a couple years ago
(http://thread.gmane.org/gmane.comp.gnu.lilypond.general/63752/focus=63799) the
answer appeared to be no, but I thought I'd ask again since that's a response
I'm extremely unaccustomed to hearing from this community. :-P )
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: alternatives at beginning or middle
Almost eight years ago, on 11/30/2005, Mats Bengtsson wrote:
Quoting Stuart Lowe stu...@stuartlowe.com:
Lilypond seems to handle alternative endings on repeated parts very
well. What about alternative beginnings, or even an
alternative somewhere in the middle?
Can someone tell me how I would do this?
I don't know if there is any standardized notation for such things.
However, if you want to have the brackets and labels, take a look
at the section on Manual Repeat Commands in the manual.
Is this still the only option?
I'm trying to typeset something like the score shown in
http://youtu.be/xucuWOMmPio. Below is a cut-down version of a source
file that seems to accomplish this result. To my (beginner's) eye, this
looks kind of messy. But is there a better way?
--Joel Salomon
\version 2.16.2
\score {
\relative c'' {
% This line is only played the first time
\set Score.repeatCommands = #'((volta 1.))
\partial 4 a4 | c c c c |
\set Score.repeatCommands = #'((volta #f) (volta 2.--3.))
\bar |:
\set Timing.measureLength = #(ly:make-moment 1 4)
b4 |
\set Timing.measureLength = #(ly:make-moment 4 4)
g4 g g g |
\set Score.repeatCommands = #'((volta #f) (volta 1.--3.))
b4 c d e | f e d c |
\set Score.repeatCommands = #'((volta #f) (volta 1.--2))
\set Timing.measureLength = #(ly:make-moment 3 4)
a4 a a |
\set Score.repeatCommands = #'((volta #f) end-repeat (volta 3.))
\set Timing.measureLength = #(ly:make-moment 4 4)
c4 c c c |
\set Score.repeatCommands = #'((volta #f))
\bar |.
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Preventing tempo marks stacking (redux)
Hi Daniel,
Try this:
\version 2.17.29
\layout {
\context {
\Score
\override Clef.break-align-anchor-alignment = #RIGHT
\override MetronomeMark.extra-spacing-width = #'(-0.5 . 0.5)
\override MetronomeMark.Y-offset = #3.0
\override MetronomeMark.outside-staff-padding = #0.8
\override MetronomeMark.non-break-align-symbols = #'(paper-column-interface)
\override RehearsalMark.break-align-symbols = #'(staff-bar key-signature
clef)
\override RehearsalMark.extra-spacing-width = #'(-0.5 . 0.5)
\override RehearsalMark.Y-offset = #3.0
\override RehearsalMark.outside-staff-padding = #0.8
}
}
{
\compressFullBarRests
\tempo Allegro moderato 4 = 104
R1*20
\tempo Molto meno mosso 4 = 72
R1*20
\tempo Tempo primo
R1
}
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Preventing tempo marks stacking (redux)
-Original Message-
From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca]
Sent: Sunday, November 10, 2013 7:24 PM
To: Daniel Rosen
Cc: Lilypond-User Mailing List
Subject: Re: Preventing tempo marks stacking (redux)
Hi Daniel,
Try this:
\version 2.17.29
\layout {
\context {
\Score
\override Clef.break-align-anchor-alignment = #RIGHT
\override MetronomeMark.extra-spacing-width = #'(-0.5 . 0.5)
\override MetronomeMark.Y-offset = #3.0
\override MetronomeMark.outside-staff-padding = #0.8
\override MetronomeMark.non-break-align-symbols = #'(paper-column-
interface)
\override RehearsalMark.break-align-symbols = #'(staff-bar key-signature
clef)
\override RehearsalMark.extra-spacing-width = #'(-0.5 . 0.5)
\override RehearsalMark.Y-offset = #3.0
\override RehearsalMark.outside-staff-padding = #0.8
}
}
{
\compressFullBarRests
\tempo Allegro moderato 4 = 104
R1*20
\tempo Molto meno mosso 4 = 72
R1*20
\tempo Tempo primo
R1
}
Hope this helps!
Kieren.
Kieren,
Thanks for the reply, but this doesn't do what I need---I still need the
MetronomeMarks to be aligned with the BarLines.
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Preventing tempo marks stacking (redux)
Hi Daniel, Thanks for the reply, but this doesn't do what I need---I still need the MetronomeMarks to be aligned with the BarLines. Oh… Maybe Keith (cc’ed here) can help — he’s the one I got that set of overrides from. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: still no ultimate way to create three-staff piano layout
Hi, yes - but please if you go public (eg. LSR) - and I hope you will - don't call the variables left or right; leftHand and rightHand seems less confusable within LilyPond Might I suggest pianoUpper/pianoLower/pianoThird, or pianoI/pianoII/pianoIII, or similar? It's not a fact that the left hand always plays the lower staff, and the right the upper, etc. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Crash with \repeat ... \alternative and \remove Bar_engraver on 2.17.26
I was researching a method for defining form (repeats, rehearsal
marks, etc.) and line breaking in separate, hidden parallel staff
contexts, and ran across the following crash:
GNU LilyPond 2.17.26
Processing `bug6-crash.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems.../usr/local/share/lilypond/2.17.26/scm/bar-line.scm:913:28: In
procedure ly:grob-array-length in expression (ly:grob-array-length bar-array):
/usr/local/share/lilypond/2.17.26/scm/bar-line.scm:913:28: Wrong type argument
in position 1 (expecting Grob_array): ()
Can someone please determine whether the latest beta still does
this, and if so, whether a bug report is warranted?
The interaction appears to be between '\remove Bar_engraver' and
the alternative ending. Remove either one and the problem goes away.
Thank you,
Jim
\version 2.17.26
form = \new Staff \with {
\remove Bar_engraver
} \repeat volta 2 {
s1
} \alternative {
s1 % first ending
s1 % second ending
} % form
\score {
\form
} % score
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Preventing tempo marks stacking (redux)
On Sun, 10 Nov 2013 16:39:26 -0800, Kieren MacMillan kieren_macmil...@sympatico.ca wrote: Hi Daniel, Thanks for the reply, but this doesn't do what I need---I still need the MetronomeMarks to be aligned with the BarLines. Oh… Maybe Keith (cc’ed here) can help — he’s the one I got that set of overrides from. Cheers, Kieren. I can never remember the overrides, so I defined the set to space marks as \markLengthOn and got it into LilyPond versions 2.17.19 and later. At the same time, people were unhappy with the default placement of tempo over barlines http://code.google.com/p/lilypond/issues/detail?id=712#c9 so I changed the default put them over where the first note in the measure would go. The incantations for tempo marks are \override Score.MetronomeMark #'non-break-align-symbols = #'(multi-measure-rest-interface) %% to start the tempo mark over the barline % #'(paper-column-interface) %% to start the tempo mark over first note-column For reasons I could never figure out http://code.google.com/p/lilypond/issues/detail?id=684 MetronomeMark uses a different interface than the rehearsal marks and bar numbers. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automated custom clef settings for custom staves
David Kastrup wrote Paul Morris lt; paul@ gt; writes: Currently you have to make changes in the music (the content) for custom clefs to work, whether that's defining a new clef with a non-standard name, A definition of a new clef will usually occur outside of the music. I understand that, but if you then *use* that new clef in the music, then you can't use that music on a standard staff since the new clef only makes sense on the custom staff. Here's an example, imagine you'd like to create some sheet music where the same music is shown on a traditional staff and also on an alternative staff (with a chromatic note layout), back to back to allow for an easy comparison. You'd like to have a single variable that contains the music (the content) and then two staves, one standard and one customized, and have that same music in each of them (the presentation). Currently clefs are the only real obstacle for this ideal scenario. You would have to have separate copies of the music for each staff so that you can customize the clef (especially the settings for middleCPosition and clefPosition) for the custom staff. So you can get what you want by having two copies of the music, or by using LilyPond's tag feature to include both a standard and a custom clef in the music for every time a clef is needed, and then tag them separately and use the tags to select which you want to include and omit for each staff. David Kastrup wrote The custom clef music function at the top of this thread makes this separation of content and presentation possible when it comes to clefs. I don't see that it does anything like that. It makes some clefs behave in surprising/unconsistent manner. In a full example that wasn't just the tiny example I gave, this function would indeed make the clefs behave in the way that is needed for the custom staff. (But at the same time it would cause them not to work for the standard staff, hence you can't use both types of staff in the same file if you use this function.) David Kastrup wrote I don't understand the problem. I have no clue what you are trying to achieve and why. You want some clefs to print different clefs than asked for when in a different staff. Why? How is that a useful feature? If you want a different clef, why should it be named the same? So that you can use music input (that uses the standard clefs in it) for both standard and alternative types of staves, as described above. Sure, you could create a different clef with a different name and definition, but then you have to have two copies of the music, or use tags as described above. Many of these alternative notation systems use clefs that are equivalent to the traditional clefs in terms of when they are used in the music (i.e. they are used for the same register or pitch range). Essentially they have their own version of a treble clef, a bass clef, etc. That's why I've looked for a way to be able to redefine what a bass clef and a treble clef mean for a given custom staff (at the staff level). That way the musical content can stay the same, while it just gets a different presentation. But I understand that this is an ideal scenario for me (and maybe not many others), and that often such scenarios do not make it to realization. At any rate, I don't want to belabor this discussion, but I did want to try to answer your questions and make myself more clear. In a way I think I have been so consistently amazed by LilyPond's flexibility and extensibility, that my expectations have risen accordingly. Now coming across something that seems like it can't be done in the way that I'd ideally like to be able to do it... and I still try to find a way to make that work, even though there are other ways to get the same job done. So that we're even having a discussion about this is a tribute to LilyPond's great flexibility and extensibility. Thanks for all that you and the others on the dev team do to make LilyPond better and better. -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Automated-custom-clef-settings-for-custom-staves-tp153665p153688.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: Automated custom clef settings for custom staves
Paul Morris p...@paulwmorris.com schrieb:
David Kastrup wrote
Paul Morris lt;
paul@
gt; writes:
Currently you have to make changes in the music (the content) for
custom clefs to work, whether that's defining a new clef with a
non-standard name,
A definition of a new clef will usually occur outside of the music.
I understand that, but if you then *use* that new clef in the music,
then
you can't use that music on a standard staff since the new clef only
makes
sense on the custom staff.
I didn't really follow this thread, but wouldn't the following be possible?
music = {
Some music }
trad = { \music }
custom = {
custom-clef-definition
\music
}
?
You could do without the trad wrapper, it's just there to clarify the
intention.
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: What's the best way to fix these beams and staff spacing?
Michael Rivers michaeljrivers at gmail.com writes: Adding the additional space via markup worked. Is this an issue I should create a bug tracker for? There is a close one http://code.google.com/p/lilypond/issues/detail?id=1702 LilyPond's strategy, spacing the staves and then deciding how to set the beams, does a good job on the examples there if you remove the forced stem directions. The strategy does not work so well when the beam is forced between staves. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Is this issue 2802?
Reducing this to a minimal example doesn't seem to be trivial so I'm hesitant to put in the time before I ask, ... Does the attached image look like issue 2802? The vertical moment of the ChordName staff is aligned too far left, and collides with the key signature of the melody staff. http://code.google.com/p/lilypond/issues/detail?id=2802 I encounter this somewhat regularly, so if anyone has a workaround, I'd appreciate it. If an ME is necessary to get a workaround, holler, and I'll hack away at one. I've encountered mis-alignment of both rhythmic staves and chord staves. Thank you! Jim attachment: crop.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
