Re: Spacing Cheat Sheet
Hi Joram,
Yes, of course, I can say now after your replay and explanation. Why
didn't I see this myself? For what you point out, of course I have seen
this with hierarchy and different kinds of staff grouping a lot of times
when reading the documentation. But I did not realize the consequences
of my reading. Your are a good teacher, and also a wee of mind reader,
which probably is one important making of being a successful teacher.
What you pointed out is exactly my case: no StaffGroup but ChoirStaff
and PianoStaff. So of course I my efforts to move the staves had no
effect by just copying from your sheet. Now I can say of course, but I
did not realize this. Your explanation has opened my eyes, and I have
come a few steps further towards the true understanding. Thank you!
Kaj
On 2015-03-12 01:31, Noeck wrote:
Dear Kaj,
you are brave to really dig through all this! That's a good thing. I
think I can help you here, too:
It is correct (and it works like expected) if you do
\override StaffGroup.StaffGrouper.staff-staff-spacing.padding = 30
like I wrote. But only (!) if your grouping context is a StaffGroup. In
case you have a PianoStaff or a ChoirStaff or anything else, you need to
override the property of that context. I.e.
\override PianoStaff.StaffGrouper.staff-staff-spacing.padding = 30
and the like.
There is a context hierarchy in LilyPond: A lower level context (e.g.
Voice) can be inside a staff, which can be inside a staff group, which
can be inside a score. Of course more complex nesting is possible.
The important thing for you is: The inner contexts inherit (take the
overrides) from the outer contexts. In your case, if you override the
StaffGrouper of the Score, that overrides the spacing for any
StaffGrouper in the Score. If you override the spacing for the
StaffGroup (and similar), only this kind of group is affected and if you
do so in the \with statement, only this particular context is affected.
Here is an example showing some possible overrides:
\version 2.18.2
\layout {
% no effect because there is no StaffGroup
% only PianoStaff and ChoirStaff
\override StaffGroup.StaffGrouper.staff-staff-spacing.padding = 60
% this works for the piano staff (upper group)
\override PianoStaff.StaffGrouper.staff-staff-spacing.padding = 15
% this works for all groups but the PianoStaff has more specific
% settings which are used instead
\override Score.StaffGrouper.staff-staff-spacing.padding = -2
\override Score.StaffGrouper.staff-staff-spacing.basic-distance = 0
}
\new PianoStaff
\new Staff { a }
\new Staff { b }
\new ChoirStaff
\new Staff { c }
\new Staff { d }
\new PianoStaff \with {
% this override only affects this second piano staff
% overriding the Score and PianoStaff overrides from
% the layout block above
\override StaffGrouper.staff-staff-spacing.padding = 4
}
\new Staff { e }
\new Staff { f }
Don't hesitate to ask again if things are still unclear.
Cheers,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Dear Kaj,
you are brave to really dig through all this! That's a good thing. I
think I can help you here, too:
It is correct (and it works like expected) if you do
\override StaffGroup.StaffGrouper.staff-staff-spacing.padding = 30
like I wrote. But only (!) if your grouping context is a StaffGroup. In
case you have a PianoStaff or a ChoirStaff or anything else, you need to
override the property of that context. I.e.
\override PianoStaff.StaffGrouper.staff-staff-spacing.padding = 30
and the like.
There is a context hierarchy in LilyPond: A lower level context (e.g.
Voice) can be inside a staff, which can be inside a staff group, which
can be inside a score. Of course more complex nesting is possible.
The important thing for you is: The inner contexts inherit (take the
overrides) from the outer contexts. In your case, if you override the
StaffGrouper of the Score, that overrides the spacing for any
StaffGrouper in the Score. If you override the spacing for the
StaffGroup (and similar), only this kind of group is affected and if you
do so in the \with statement, only this particular context is affected.
Here is an example showing some possible overrides:
\version 2.18.2
\layout {
% no effect because there is no StaffGroup
% only PianoStaff and ChoirStaff
\override StaffGroup.StaffGrouper.staff-staff-spacing.padding = 60
% this works for the piano staff (upper group)
\override PianoStaff.StaffGrouper.staff-staff-spacing.padding = 15
% this works for all groups but the PianoStaff has more specific
% settings which are used instead
\override Score.StaffGrouper.staff-staff-spacing.padding = -2
\override Score.StaffGrouper.staff-staff-spacing.basic-distance = 0
}
\new PianoStaff
\new Staff { a }
\new Staff { b }
\new ChoirStaff
\new Staff { c }
\new Staff { d }
\new PianoStaff \with {
% this override only affects this second piano staff
% overriding the Score and PianoStaff overrides from
% the layout block above
\override StaffGrouper.staff-staff-spacing.padding = 4
}
\new Staff { e }
\new Staff { f }
Don't hesitate to ask again if things are still unclear.
Cheers,
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Hi Joram, Time has gone since you helped me to understand the vertical spacing mystery in LilyPond. Well I am not ready yet for the big battle, but a lot has been clear since. And a lot of thanks for your very valuable sheet compiling the different items. But not always I have got things work the way I wished, and more than once I have been ready to give up the LilyPond project. Today I found something in your sheet loosening a lot of knots. I think a small mistake has slipped into it. The left column, lower part, says \override StaffGroup.StaffGrouper.staff-staff-spacing.padding = #2. At first this sounds reasonable, but I think that StaffGroup should be substituted with Score. Reading the Internals Reference confirms that the context StaffGroup does not create the grob StaffGrouper and also that StaffGrouper is not created by any engraver. Well, I am not the person to account for all this, but after reading the Notation Reference (http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-within-systems#spacing-of-grouped-staves) and the example there, I feel encouraged to announce my experience. My case worked with context Score but not with StaffGroup. The next line however: \override Staff.VerticalAxisGroup etc is perfectly correct as VerticalAxisGroup is created by Axis_Group_Engraver which belongs to the context Staff. Possibly the context Staff could also be use in the previous case, but I have not tested this. Best regards Kaj Den 2015-02-21 14:04, skrev Noeck: Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf The aim of this is not to explain everything – that is better done in the docs – but to give a visual summary of the spacing settings and an example (on the left) how to change them. If you know that there are different settings in the paper and in the layout block and that there are fixed distances (in mm, cm, in) and flexible spacings (minimum-distance, basic-distance, padding, strechability), then this cheat sheet should make it easier to adjust all these to your liking. Cheers, Joram PS: Lyrics and other nonstaff spacings are to be done. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Hi Trevor, thanks I missed that paragraph. See http://www.lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-paper-variables Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Noeck wrote Sunday, February 22, 2015 9:05 PM I would also be interested in how the stretchability value is used. I assumed it would be someting like \vfill in LaTeX, in this case only the relative value with respect to other spacings would be significant – i.e. the available extra space would be shared in proportions of the stretchability of the spacings. But this was just a guess. I think that is right. The Notation Reference says: stretchability – a unitless measure of the dimension’s relative propensity to stretch. If zero, the distance will not stretch (unless collisions would result). When positive, the significance of a particular dimension’s stretchability value lies only in its relation to the stretchability values of the other dimensions. For example, if one dimension has twice the stretchability of another, it will stretch twice as easily. See http://www.lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-paper-variables Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Hi, I would also be interested in how the stretchability value is used. I assumed it would be someting like \vfill in LaTeX, in this case only the relative value with respect to other spacings would be significant – i.e. the available extra space would be shared in proportions of the stretchability of the spacings. But this was just a guess. It looks like Kieren’s answer is closer to reality. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Thanks Trevor! So this with stretching demands to be the next thing to put your teeth into. /Kaj Den 2015-02-21 23:15, skrev Trevor Daniels: Kaj wrote Saturday, February 21, 2015 9:10 PM One thing (among others) I still do not understand: why are there three keys describing the distance between staves and systems? In the Notation Reference (http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables#structure-of-flexible-vertical-spacing-alists) one tries to describe how they are defined. But, if I understand it correct, the effective (resulting) distance will always be the biggest of the three, hence effective_distance = max(minimum-distance; basic-distance; padding). Is there any reason to use three, one should be sufficient. If they were adding like resulting_distance = minimum-distance + basic-distance + padding this could motivate the number, but I cannot read this from the manual. That is only true if the page has a ragged bottom. In that case no stretching or compression is required, and the various spacings are set at their natural values, specified by the effective_distance you show above (plus anything needed to avoid collisions). However, if ragged-bottom = ##f, the spacing between the various elements on the page needs to be adjusted so the page is exactly filled. That is when all four parameters come into play, as described on the page you reference above, to control the amount of stretching or compression required, and how it should be distributed between the elements on the page. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet (was: How to increase the distance betweensystems?)
Kaj wrote Saturday, February 21, 2015 9:10 PM One thing (among others) I still do not understand: why are there three keys describing the distance between staves and systems? In the Notation Reference (http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables#structure-of-flexible-vertical-spacing-alists) one tries to describe how they are defined. But, if I understand it correct, the effective (resulting) distance will always be the biggest of the three, hence effective_distance = max(minimum-distance; basic-distance; padding). Is there any reason to use three, one should be sufficient. If they were adding like resulting_distance = minimum-distance + basic-distance + padding this could motivate the number, but I cannot read this from the manual. That is only true if the page has a ragged bottom. In that case no stretching or compression is required, and the various spacings are set at their natural values, specified by the effective_distance you show above (plus anything needed to avoid collisions). However, if ragged-bottom = ##f, the spacing between the various elements on the page needs to be adjusted so the page is exactly filled. That is when all four parameters come into play, as described on the page you reference above, to control the amount of stretching or compression required, and how it should be distributed between the elements on the page. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Hi Kieren! Thanks for the info. You might be correct in what you suggest. However so far I have not seen any complete description of stretchability. There are some words in the paragraphs about Structure of flexible vertical spacing alists (the link I gave in my previous note), but those are for the experts, who already know how it works. The novice does not understand, since the description contains holes, where info is lacking or implied. Kaj Den 2015-02-21 22:27, skrev Kieren MacMillan: Hi Kaj (et al.), if I understand it correct, the effective (resulting) distance will always be the biggest of the three, hence effective_distance = max(minimum-distance; basic-distance; padding). Is there any reason to use three, one should be sufficient. If I understand correctly, three are required for compression and expansion calculations. For example, consider ((basic-distance . 4) (minimum-distance . 2) (padding . 1) (stretchability . 10)) When compressing a page, I believe #'stretchability is applied [inversely] against basic-distance - miminum-distance which in this case is 2 staff spaces. If instead you had ((basic-distance . 2) (minimum-distance . 2) (padding . 2) (stretchability . 10)), I believe there could/would be no compression done. Others (e.g., Keith) will have a more complete and accurate understanding of the intricacies of the spacing model — hopefully someone will chime in here to expand upon or correct what I’ve said. Hope this helps, 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: Spacing Cheat Sheet
On 2015-02-21 06:04 AM, Noeck wrote: Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf Very nicely done, sir! Printed and put on the wall, saved into my folder of really useful tools. 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
Spacing Cheat Sheet (was: How to increase the distance between systems?)
Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf The aim of this is not to explain everything – that is better done in the docs – but to give a visual summary of the spacing settings and an example (on the left) how to change them. If you know that there are different settings in the paper and in the layout block and that there are fixed distances (in mm, cm, in) and flexible spacings (minimum-distance, basic-distance, padding, strechability), then this cheat sheet should make it easier to adjust all these to your liking. Cheers, Joram PS: Lyrics and other nonstaff spacings are to be done. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet (was: How to increase the distance between systems?)
Hi Joram! Thanks a lot! This is most helpful for a Lily newbie like myself! /Peter Peter Danemo +46-70-653 21 91 E-post: petedom...@gmail.com Web: danemo.com 21 feb 2015 kl. 14:04 skrev Noeck noeck.marb...@gmx.de: Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf The aim of this is not to explain everything – that is better done in the docs – but to give a visual summary of the spacing settings and an example (on the left) how to change them. If you know that there are different settings in the paper and in the layout block and that there are fixed distances (in mm, cm, in) and flexible spacings (minimum-distance, basic-distance, padding, strechability), then this cheat sheet should make it easier to adjust all these to your liking. Cheers, Joram PS: Lyrics and other nonstaff spacings are to be done. ___ 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: Spacing Cheat Sheet (was: How to increase the distance between systems?)
On Sat, Feb 21, 2015 at 8:04 AM, Noeck noeck.marb...@gmx.de wrote: Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf The aim of this is not to explain everything – that is better done in the docs – but to give a visual summary of the spacing settings and an example (on the left) how to change them. If you know that there are different settings in the paper and in the layout block and that there are fixed distances (in mm, cm, in) and flexible spacings (minimum-distance, basic-distance, padding, strechability), then this cheat sheet should make it easier to adjust all these to your liking. Cheers, Joram PS: Lyrics and other nonstaff spacings are to be done. Thank you for sharing this, Joram! I think this will be a big help. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet
Hi, I've seen it once – didn't realize it is so similar. It doesn't contain the spacing within a score, though, which was the issue of the original thread. http://joramberger.de/files/LilypondSpacing.pdf Here's another visual guide that Abraham Lee created that's similar: http://lilypond.1069038.n5.nabble.com/attachment/164161/0/vertical-spacing-paper-variables.pdf I have to correct one thing: In contrast to lyrics, etc. (as described here: http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-within-systems#within_002dsystem-spacing-properties) the reference point of markup is the highest point. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet (was: How to increase the distance between systems?)
Hi Joram! I will say that compilations and overviews like this are most valuable and usable tools for people (like me) in the state where the different objects and concepts begin to come out of the shadows, but still you do not know the connections between them or their exact roles. So thank you very much. The sheet has got its deserved place on the wall ahead of me and the computer. One thing (among others) I still do not understand: why are there three keys describing the distance between staves and systems? In the Notation Reference (http://www.lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables#structure-of-flexible-vertical-spacing-alists) one tries to describe how they are defined. But, if I understand it correct, the effective (resulting) distance will always be the biggest of the three, hence effective_distance = max(minimum-distance; basic-distance; padding). Is there any reason to use three, one should be sufficient. If they were adding like resulting_distance = minimum-distance + basic-distance + padding this could motivate the number, but I cannot read this from the manual. Nor does your very good sheet give a definite answer. So I do not see the reason. Historical maybe? Kaj Den 2015-02-21 14:04, skrev Noeck: Hi Kaj, hi Lilypond users, I also would like to say that again that spacing is a bit daunting. But I hope with the help you got here, it is possible to adjust the spacing you need. The deeper understanding will come with time and it is difficult if one wants to understand everything at once. To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf The aim of this is not to explain everything – that is better done in the docs – but to give a visual summary of the spacing settings and an example (on the left) how to change them. If you know that there are different settings in the paper and in the layout block and that there are fixed distances (in mm, cm, in) and flexible spacings (minimum-distance, basic-distance, padding, strechability), then this cheat sheet should make it easier to adjust all these to your liking. Cheers, Joram PS: Lyrics and other nonstaff spacings are to be done. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing Cheat Sheet (was: How to increase the distance between systems?)
Hi Kaj (et al.), if I understand it correct, the effective (resulting) distance will always be the biggest of the three, hence effective_distance = max(minimum-distance; basic-distance; padding). Is there any reason to use three, one should be sufficient. If I understand correctly, three are required for compression and expansion calculations. For example, consider ((basic-distance . 4) (minimum-distance . 2) (padding . 1) (stretchability . 10)) When compressing a page, I believe #'stretchability is applied [inversely] against basic-distance - miminum-distance which in this case is 2 staff spaces. If instead you had ((basic-distance . 2) (minimum-distance . 2) (padding . 2) (stretchability . 10)), I believe there could/would be no compression done. Others (e.g., Keith) will have a more complete and accurate understanding of the intricacies of the spacing model — hopefully someone will chime in here to expand upon or correct what I’ve said. Hope this helps, 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: Spacing Cheat Sheet (was: How to increase the distance between systems?)
Noeck wrote To make the use of spacing settings easier, I put the most relevant settings on this page: http://joramberger.de/files/LilypondSpacing.pdf Thanks Joram, this is very helpful! Here's another visual guide that Abraham Lee created that's similar: http://lilypond.1069038.n5.nabble.com/attachment/164161/0/vertical-spacing-paper-variables.pdf Cheers, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/How-to-increase-the-distance-between-systems-new-try-tp172032p172144.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: Lilypond Cheat Sheet 2.18
alterations doesn't fit to \language français … I will update it within some days. … Done. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
2014/1/1 Noeck noeck.marb...@gmx.de: Hi all, as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: English: http://joramberger.de/files/lilypond_sheet_2.18_en.pdf German: http://joramberger.de/files/lilypond_sheet_2.18_de.pdf French*: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf *awesome*!!! Thanks Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
For this time/file, could you finish the text? There are some words missing in the articulations corner and in the basso numerato section. I would then care about re-alignment of the text boxes etc. to make it look nice again. ok, find it attached thanks Thanks to Federico there is now also an Italian version of this cheat sheet: http://joramberger.de/files/lilypond_sheet_2.18_it.pdf Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Good job! Thanks (I'll give the links on the French list when updated).
- Commentaire % … und %{ … %}
+ Commentaire % … et %{ … %}
[ ... ]
Perhaps too late, but
alterations doesn't fit to \language français
is - d
ish - sd
isis - dd
isih - dsd
es - b
eh - sb
eses - bb
eseh - bsb
NB
As it is my first post here in 2014, happy new year for everybody
--
Gilles
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Hi Gilles, Perhaps too late, but alterations doesn't fit to \language français Ah, thanks, I missed that. And no, it is not too late, I will update it within some days. This also concerns the other languages. Thanks again, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond Cheat Sheet 2.18
Hi all, as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: English: http://joramberger.de/files/lilypond_sheet_2.18_en.pdf German: http://joramberger.de/files/lilypond_sheet_2.18_de.pdf French*: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf I hope it makes life easier for you and others. Cheers, Joram * The French translation is probably rather poorly done by me. Corrections and other comments to all language versions are welcome! -- ## Changes The changes concerning these basic syntax elements are very limited: - tempo ranges with “-” instead of “~” - the tuplet syntax - some bar lines (! ; …) - the staccatissimo short cut -! - # and \default is no longer necessary in some cases ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
2014/1/1 Noeck noeck.marb...@gmx.de as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: English: http://joramberger.de/files/lilypond_sheet_2.18_en.pdf German: http://joramberger.de/files/lilypond_sheet_2.18_de.pdf French*: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf Hi Joram nice work if you send the .ly file I may translate it to italian ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
if you send the .ly file I may translate it to italian That would be nice. The editable source is an Inkscape svg file, you can download it by changing the file extension in the link from pdf to svg: http://joramberger.de/files/lilypond_sheet_2.18_en.svg Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Le 01/01/2014 18:50, Noeck disait :
Hi all,
* The French translation is probably rather poorly done by me.
Corrections and other comments to all language versions are welcome!
Good job! Thanks (I'll give the links on the French list when updated).
- Commentaire % … und %{ … %}
+ Commentaire % … et %{ … %}
vérification d'octave = overwrite!
- Punktierung
+ pointée
- Skalierung der Daure
+ Échelonnement de durée
- dynamique
+ nuance
- pause invisible
+ silence invisible
- 7^éme
+ 7^e
- erhöht
+ élève
- erniedrigt
+ abaisse
- Instrumentenspezifisch
- dépend de l'instrument
Cheers, und alles Gutes fürs Neujahr!
Jean-Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
2014/1/1 Noeck noeck.marb...@gmx.de: Hi all, as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: Hi Joram, I forwarded it to the german forum: http://www.lilypondforum.de/index.php?topic=1257.msg9147#msg9147 Many thanks, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Hi Jean-Charles, thanks for your comments! I have a few questions left: - pause invisible + silence invisible in general pause - silence, too? - erhöht + élève élève and not élevé? - erniedrigt + abaisse and not abaissé? I have updated it: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf Merci beaucoup et bonne nouvelle année 2014! Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
On Wed, Jan 1, 2014 at 12:50 PM, Noeck noeck.marb...@gmx.de wrote: Hi all, as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: English: http://joramberger.de/files/lilypond_sheet_2.18_en.pdf German: http://joramberger.de/files/lilypond_sheet_2.18_de.pdf French*: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf I hope it makes life easier for you and others. Cheers, Joram Thanks so much! And Happy New Year. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Thank you, Joram! P Noeck wrote: Hi all, as promised after the release of 2.16, I update my Lilypond cheat sheets for each stable version. After 2.18 came out recently, here is the corresponding version of my cheat sheet in three languages: English: http://joramberger.de/files/lilypond_sheet_2.18_en.pdf German: http://joramberger.de/files/lilypond_sheet_2.18_de.pdf French*: http://joramberger.de/files/lilypond_sheet_2.18_fr.pdf I hope it makes life easier for you and others. Cheers, Joram * The French translation is probably rather poorly done by me. Corrections and other comments to all language versions are welcome! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
2014/1/1 Noeck noeck.marb...@gmx.de if you send the .ly file I may translate it to italian That would be nice. The editable source is an Inkscape svg file, you can download it by changing the file extension in the link from pdf to svg: http://joramberger.de/files/lilypond_sheet_2.18_en.svg oh, too much trouble, I give up :( ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
That would be nice. The editable source is an Inkscape svg file, you can download it by changing the file extension in the link from pdf to svg: http://joramberger.de/files/lilypond_sheet_2.18_en.svg oh, too much trouble, I give up :( Oh, that’s a pity. I don’t want to urge you, but I’d like to propose some ways for anyone interested in a translation: 1. there is a list of words in the attachment which I would incorporate in the file. 2. svg files are plain text files like html, a simple search and replace would do (I would care about rearrangements if needed). 3. Inkscape is a very nice free software for vector graphics running on different operating systems. Using it and changing the text is really easy. Cheers, Joram Input Syntax Music Transposition Chords Polyphony Variables Comments and True/False Staves Staff Properties Clefs Key mode church modes Meter no meter Tempo Upbeat Triplets Repeat Bars and rehearsal marks Bar check line break possible line break Expressive Marks Attached to Notes and Chords Articulation Fingering Fermata, coda, change octave Specialist notation Grace notes Interval Ornaments, etc. Notes pitch rest alteration change octave force accidental octave check 1 / duration dotted note scaling of duration tremolo string articulation dynamics beam slur/phrasing slur tie bar check invisible rest rest at the height of an a repeat last chord Chords root duration minor diminished augmented major seventh remove degree augmented diminished add degree add thirds up to this degree bass add without inversion Drums Figured Bass degree third alteration 1 / duration brackets no figure figure instead of extender line Lyrics Repeat or Text size string-fret-finger ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
True, but I have a different problem: if the translated text is longer, objects should be re-aligned. See attached file. Before using Inkscape I did a quick search to see if there's a better way to handle localization of SVG files and I found this: http://www.svgopen.org/2008/papers/53-Translating_SVG_with_XLIFF_and_Open_Standards/ Probably too much for this cheatsheet, but it may be useful in the future Thanks for the link, I will look at it. That seems to be useful indeed. For this time/file, could you finish the text? There are some words missing in the articulations corner and in the basso numerato section. I would then care about re-alignment of the text boxes etc. to make it look nice again. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
Noeck noeck.marb...@gmx.de writes: 3. Inkscape is a very nice free software for vector graphics running on different operating systems. Using it and changing the text is really easy. When I try it it runs into all kinds of fonts issues. Apparently you used nonstandard fonts (except for Emmentaler). -- Johan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Cheat Sheet 2.18
When I try it it runs into all kinds of fonts issues. Apparently you used nonstandard fonts (except for Emmentaler). Yes, I chose some non-standard fonts ;) Century Schoolbook L (the text font Lilypond uses) Ubuntu Mono (Ubuntus monospace font) Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond cheat sheet
Hi Joram, Thank you for the updates cheat sheet. As a matter of fact I just printed both cheat sheets on one sheet of paper and laminated it. Two sides of invaluable LilyPond information :-) Hint 1: use heavier stock paper when printing double sided. Hint 2: print borderless for printing the other sheet (pale green background). Best regards, Olivier On Sun, Nov 11, 2012 at 10:45 PM, Noeck noeck.marb...@gmx.de wrote: Thank you for all your comments on my cheat sheet[1]! I included them and spotted some more. Here are the updated versions of the English and the German cheat sheet (in svg and pdf format)[2]: http://joramberger.de/files/lilypond_sheet_en.svg http://joramberger.de/files/lilypond_sheet_en.pdf http://joramberger.de/files/lilypond_sheet_de.svg http://joramberger.de/files/lilypond_sheet_de.pdf Because there is no script to produce it, but only an svg file, I cannot recommend including it in the documentation of LilyPond (just as a matter of file size and the reduced diff-ability). But, not just because I've made it, but especially from a user's point of view, I would suggest to make a link from the documentation to the cheat sheets of Reinhold Kainhofer (if he agrees) and me. (Perhaps from the bottom of this page: http://lilypond.org/doc/v2.16/Documentation/notation/cheat-sheet). For me personally it is a great help to have a cheat sheet while writing scores with LilyPond and I think many users would welcome it, but they would never find my website or Reinhold's. Both for beginners and more advanced users these could be useful in addition to the above mentioned existing cheat sheet of the documentation. Concerning the question how to update it for new versions: The documentation is for 2.16 anyway and a link could be removed in case it gets outdated. However, I intend to update it to the next stable version as soon as that comes out. But I cannot guarantee that for all eternity, though. Cheers, Joram [1] I have corrected Lilypond to LilyPond even though I dislike this capital P ;) [2] The website itself is not there yet, but the files are accessible. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
Am 09.11.2011 17:31, schrieb David Kastrup: Trevor Danielst.dani...@treda.co.uk writes: David Kastrup wrote Wednesday, November 09, 2011 3:03 PM The octave of notes may also be checked with the `\octaveCheck CONTROLPITCH' command. `CONTROLPITCH' is specified in absolute mode. This checks that the interval between the previous note and the `CONTROLPITCH' is within a fourth (i.e., the normal calculation of relative mode). This is a popular misconception, but it is wrong, as you can see by introducing various accidentals. I was merely quoting the manual, so if you have something to complain, do it there. within a fourth is equivalent to a distance of three staff spaces or less. Lilypond doesn't take accidentals into account (which is of course a good thing). c fis is a fourth c fis, is a fifth ces fis is a fourth - so it will be the fis above the ces although it sounds like a fifth. So I think the quoted sentences are correct. The popular misconception is that only an unaltered fourth counts as a fourth. You may think of suggesting a documentation enhancement to make this more clear, but I don't really think it is necessary. HTH Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
2011/11/8 Tim Roberts t...@probo.com:
Is there a simple mnemonic aid that can help me remember which part of a
given token is the one that carries forward? Individual notes are easy.
Within a chord is easy. I believe that the first note of a chord then
carries forward to the next token. But in polyphony (with ), is it the
last note that carries forward out of the polyphony? Does the second part
of a polyphonic set pick up from the end of the first part?
This shows it:
\score {
\relative f {
{ c d e f g a b c d e f g a b c }
{ e f g a b c d e f g a b c d e }
}
}
%%%
'e' in second expression is relative to last 'c' in first expression.
But if you always use music from variables and no polyphony inside
them, there is no doubt you control all relativeness:
musicOne = \relative f { c d e f g a b c d e f g a b c }
musicTwo = \relative f { e f g a b c d e f g a b c d e }
\score {
\relative f {
\musicOne
\musicTwo
}
}
%%%
This way you do not mix relative mode and polyphony.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
2011/11/10 Francisco Vila paconet@gmail.com:
musicOne = \relative f { c d e f g a b c d e f g a b c }
musicTwo = \relative f { e f g a b c d e f g a b c d e }
\score {
\relative f {
\musicOne
\musicTwo
}
}
%%%
This way you do not mix relative mode and polyphony.
Ooops, sorry this way you actuall mix. I meant
musicOne = \relative f { c d e f g a b c d e f g a b c }
musicTwo = \relative f { e f g a b c d e f g a b c d e }
\score {
\musicOne
\musicTwo
}
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
On Thu, Nov 10, 2011 at 10:30:15AM +0100, Urs Liska wrote: Am 09.11.2011 17:31, schrieb David Kastrup: Trevor Danielst.dani...@treda.co.uk writes: This is a popular misconception, but it is wrong, as you can see by introducing various accidentals. I was merely quoting the manual, so if you have something to complain, do it there. within a fourth is equivalent to a distance of three staff spaces or less. Lilypond doesn't take accidentals into account (which is of course a good thing). Yes. A doubly-augmented fourth is in the same octave, whereas a doubly-diminished fifth is in a different octave. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
Am 09.11.2011 00:59, schrieb Carl Sorensen: On 11/8/11 1:32 PM, Tim Robertst...@probo.com wrote: As I do more and more LilyPond data entry, I find the skill set development to be interesting. I've become pretty quick at data entry now, including dynamics and articulation marks. I've become pretty good at tweaking the output to get the effects I want. The skill that is NOT developing, apparently, is the skill to keep the relative octaves straight. Inevitably, my first test run ends up going diagonally straight off the page in one direction or other, with 20 or 30 ledger lines on each note. Is there a simple mnemonic aid that can help me remember which part of a given token is the one that carries forward? Individual notes are easy. Within a chord is easy. I believe that the first note of a chord then carries forward to the next token. But in polyphony (with ), is it the last note that carries forward out of the polyphony? If you are parsing notes, the last note parsed serves as the basis for the next note. To make this maybe even a little more concrete: It does _not_ depend on the context the notes live in - it depends only on the order in which they appear in the input file. ( If you are parsing chords, the first note in the last chord parsed serves as the basis for the next note. I got used to always writing chords from bottom to top, even when this implies more octavations. HTH Urs At least, that's my mental model. Thanks, Carl ___ 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: Cheat Sheet
On Wed, Nov 9, 2011 at 8:41 AM, Urs Liska li...@ursliska.de wrote: It does _not_ depend on the context the notes live in - it depends only on the order in which they appear in the input file. Thanks, that's an easy-to-remember rule. It deserves prominent placement in the documentation. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
Michael Ellis michael.f.el...@gmail.com writes: On Wed, Nov 9, 2011 at 8:41 AM, Urs Liska li...@ursliska.de wrote: It does _not_ depend on the context the notes live in - it depends only on the order in which they appear in the input file. Thanks, that's an easy-to-remember rule. It deserves prominent placement in the documentation. It is also wrong. This just holds for durations. Relative octaves are not tracked in the input, but instead are generated when \relative is called. This is established at the point of time when a music list is getting iterated. If you entered the whole music list naturally instead of having music functions and music variables provide bits and pieces, then you get roughly input order, except that after chords, the respective octave for the next element is taken from the first element of the chord. There may be further details. Use occasional octave checks if you tend to get things wrong. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
On Wed, Nov 9, 2011 at 9:38 AM, David Kastrup d...@gnu.org wrote: Michael Ellis michael.f.el...@gmail.com writes: On Wed, Nov 9, 2011 at 8:41 AM, Urs Liska li...@ursliska.de wrote: It does _not_ depend on the context the notes live in - it depends only on the order in which they appear in the input file. Thanks, that's an easy-to-remember rule. It deserves prominent placement in the documentation. It is also wrong. This just holds for durations. Relative octaves are not tracked in the input, but instead are generated when \relative is called. This is established at the point of time when a music list is getting iterated. If you entered the whole music list naturally instead of having music functions and music variables provide bits and pieces, then you get roughly input order, except that after chords, the respective octave for the next element is taken from the first element of the chord. There may be further details. Use occasional octave checks if you tend to get things wrong. Ah! So the simple rule about simple rules still applies :-) Back to my previous approach, then: Use point and click to select the first note with the wrong octave, change it, and re-run lilypond. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
Michael Ellis michael.f.el...@gmail.com writes:
Ah! So the simple rule about simple rules still applies :-)
Back to my previous approach, then: Use point and click to select the
first note with the wrong octave, change it, and re-run lilypond.
Or write octave checks.
In relative mode, it is easy to forget an octave changing mark. Octave
checks make such errors easier to find by displaying a warning and
correcting the octave if a note is found in an unexpected octave.
To check the octave of a note, specify the absolute octave after the
`=' symbol. This example will generate a warning (and change the
pitch) because the second note is the absolute octave `d''' instead of
`d'' as indicated by the octave correction.
\relative c'' {
c2 d='4 d
e2 f
}
The octave of notes may also be checked with the
`\octaveCheck CONTROLPITCH' command. `CONTROLPITCH' is specified in
absolute mode. This checks that the interval between the previous note
and the `CONTROLPITCH' is within a fourth (i.e., the normal calculation
of relative mode). If this check fails, a warning is printed, but the
previous note is not changed. Future notes are relative to the
`CONTROLPITCH'.
\relative c'' {
c2 d
\octaveCheck c'
e2 f
}
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
David Kastrup wrote Wednesday, November 09, 2011 3:03 PM
The octave of notes may also be checked with the
`\octaveCheck CONTROLPITCH' command. `CONTROLPITCH' is specified
in
absolute mode. This checks that the interval between the previous
note
and the `CONTROLPITCH' is within a fourth (i.e., the normal
calculation
of relative mode).
This is a popular misconception, but it is wrong, as
you can see by introducing various accidentals.
The calculation of nearest note in \relative mode is
based, not on pitches, but on position on the staff.
The octave is chosen so the number of staff-spaces
between the two note-heads is 3 or less.
For example,
\relative c'' {
b c % c is 1 staff space up, so is the c above
b d % d is 2 up or 5 down, so is the d above
b e % e is 3 up or 4 down, so is the e above
b a % a is 6 up or 1 down, so is the a below
b g % g is 5 up or 2 down, so is the g below
b f % f is 4 up or 3 down, so is the f below
}
See
http://www.lilypond.org/doc/v2.15/Documentation/learning/simple-notation
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
Trevor Daniels t.dani...@treda.co.uk writes: David Kastrup wrote Wednesday, November 09, 2011 3:03 PM The octave of notes may also be checked with the `\octaveCheck CONTROLPITCH' command. `CONTROLPITCH' is specified in absolute mode. This checks that the interval between the previous note and the `CONTROLPITCH' is within a fourth (i.e., the normal calculation of relative mode). This is a popular misconception, but it is wrong, as you can see by introducing various accidentals. I was merely quoting the manual, so if you have something to complain, do it there. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Cheat Sheet
As I do more and more LilyPond data entry, I find the skill set development to be interesting. I've become pretty quick at data entry now, including dynamics and articulation marks. I've become pretty good at tweaking the output to get the effects I want. The skill that is NOT developing, apparently, is the skill to keep the relative octaves straight. Inevitably, my first test run ends up going diagonally straight off the page in one direction or other, with 20 or 30 ledger lines on each note. Is there a simple mnemonic aid that can help me remember which part of a given token is the one that carries forward? Individual notes are easy. Within a chord is easy. I believe that the first note of a chord then carries forward to the next token. But in polyphony (with ), is it the last note that carries forward out of the polyphony? Does the second part of a polyphonic set pick up from the end of the first part? Yes, I can (and do) look this up, but if you have a quick mental rule, that would be a big help to me. -- Tim Roberts, t...@probo.com Providenza Boekelheide, Inc. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Cheat Sheet
On 11/8/11 1:32 PM, Tim Roberts t...@probo.com wrote: As I do more and more LilyPond data entry, I find the skill set development to be interesting. I've become pretty quick at data entry now, including dynamics and articulation marks. I've become pretty good at tweaking the output to get the effects I want. The skill that is NOT developing, apparently, is the skill to keep the relative octaves straight. Inevitably, my first test run ends up going diagonally straight off the page in one direction or other, with 20 or 30 ledger lines on each note. Is there a simple mnemonic aid that can help me remember which part of a given token is the one that carries forward? Individual notes are easy. Within a chord is easy. I believe that the first note of a chord then carries forward to the next token. But in polyphony (with ), is it the last note that carries forward out of the polyphony? If you are parsing notes, the last note parsed serves as the basis for the next note. If you are parsing chords, the first note in the last chord parsed serves as the basis for the next note. At least, that's my mental model. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On 09/12/2011 04:19 PM, Nick Payne wrote: ... elision by patrick... I can't print it from Adobe Reader on Ubuntu either. I also opened it in the default PDF document viewer that comes with Ubuntu (Evince), and in that, most of the text just displays as blocks of various sizes and shades - see attached screen dump of part of the page. That's strange! I just looked at it in evince 2.32.0 on Ubuntu 11.04 and it was beautiful. evince DID give 105 errors on the file, I'm attaching them. okular gave only 75 of the same errors, e.g. Error (294822): Dictionary key must be a name object. Running evince again gave 90 of the similar errors. acroread also showed it well. Printing: acroread - popup saying The document could not be printed evince - printed without error* okular - printed without error* * other than the errors mentioned above which don't seem to interfere with the rendering Patrick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On Mon, Sep 12, 2011 at 8:39 AM, Reinhold Kainhofer reinh...@kainhofer.comwrote: Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf Thanks, Reinhold! I, also, was unable to print the cheat sheet (Win XP) until I used the link provided by Robert Schaus to the online pdf converter : http://docupub.com/pdfconvert/ PS: I'm also planning to write a cheat sheet with basic tweaks/overrides and the various paper/header fields. But that might take a while. I would love to see it if and when you write it. Paper and header have been major problems for me. Ralph -- Ralph Palmer Brattleboro, VT USA palmer.r.vio...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On 13 Sep 2011, at 00:19, Nick Payne wrote: On 13/09/11 04:55, Reinhold Kainhofer wrote: Am Montag, 12. September 2011, 19:21:02 schrieb Helge Kruse: But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? No, printing is not disallowed. It is probably some incompatibility with Acrobat Reader. I can print it just fine from okular. I can't print it from Adobe Reader on Ubuntu either. I also opened it in the default PDF document viewer that comes with Ubuntu (Evince), and in that, most of the text just displays as blocks of various sizes and shades - see attached screen dump of part of the page. you could try the 'print as image' option in acrobat this works for me usually when i get the weird printouts Damian ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
If nothing else works, there is this (for command-line buffs possibly dissatisfactory) option of online conversion at, e.g., http://docupub.com/pdfconvert/ This worked for me, anyway. Nice work, Reinhold, and thanks for sharing! On Tuesday, September 13, 2011 10:34 AM, Damian leGassick damianlegass...@mac.com wrote: On 13 Sep 2011, at 00:19, Nick Payne wrote: On 13/09/11 04:55, Reinhold Kainhofer wrote: Am Montag, 12. September 2011, 19:21:02 schrieb Helge Kruse: But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? No, printing is not disallowed. It is probably some incompatibility with Acrobat Reader. I can print it just fine from okular. I can't print it from Adobe Reader on Ubuntu either. I also opened it in the default PDF document viewer that comes with Ubuntu (Evince), and in that, most of the text just displays as blocks of various sizes and shades - see attached screen dump of part of the page. you could try the 'print as image' option in acrobat this works for me usually when i get the weird printouts Damian ___ 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: Basic LilyPond Cheat Sheet
Great work. Thank you! When you have the time, fill in the second side of the page. we need to save trees O:-) Thank you alberto On 12/09/2011 10:56, Reinhold Kainhofer wrote: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. The cheat sheet is meant to be a quick summary of the things explained in the learning manual, but does not replace the learning manual. It simply is a quick reminder of all the stuff, once you have read the learning manual. Attached you can find the PDF version of this cheat sheet. I also provide nicely printed copies of the cheat sheet for basically my own costs (3€ per sheet + shipping): http://www.edition-kainhofer.com/en/lilypond/details/2111/ These copies are printed borderless on heavier paper and are laminated, so they are waterproof and hold for years. Chers, Reinhold PS: I'm also planning to write a cheat sheet with basic tweaks/overrides and the various paper/header fields. But that might take a while. This body part will be downloaded on demand. -- Alberto Simoes CEHUM ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Basic LilyPond Cheat Sheet
Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. The cheat sheet is meant to be a quick summary of the things explained in the learning manual, but does not replace the learning manual. It simply is a quick reminder of all the stuff, once you have read the learning manual. Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf I also provide nicely printed copies of the cheat sheet for basically my own costs (3€ per sheet + shipping): http://www.edition-kainhofer.com/en/lilypond/details/2111/ These copies are printed borderless on heavier paper and are laminated, so they are waterproof and should hold for years. Chers, Reinhold PS: I'm also planning to write a cheat sheet with basic tweaks/overrides and the various paper/header fields. But that might take a while. -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On Mon, Sep 12, 2011 at 14:39, Reinhold Kainhofer reinh...@kainhofer.com wrote: Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf Looks very nice! Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Reinhold Kainhofer reinh...@kainhofer.com writes: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. How does it relate/compare to appendix B in the notation manual? Anything you might consider worth adding there? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Am Montag, 12. September 2011, 14:48:51 schrieb David Kastrup: Reinhold Kainhofer reinh...@kainhofer.com writes: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. How does it relate/compare to appendix B in the notation manual? Anything you might consider worth adding there? The appendix B contains mostly similar snippets, but 1) my cheatsheet has more than those snippets (i.e. Appendix B corresponds more or less to my Basic Notation box; But my cheat sheet also shows command line usage, some contexts, examples for lyrics, hierarchies, markup), 2) takes way more than one sheet when printed, and 3) is not nearly as good-looking as my cheat sheet ;-) Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Am 12.09.2011 14:39, schrieb Reinhold Kainhofer: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. The cheat sheet is meant to be a quick summary of the things explained in the learning manual, but does not replace the learning manual. It simply is a quick reminder of all the stuff, once you have read the learning manual. Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf I also provide nicely printed copies of the cheat sheet for basically my own costs (3€ per sheet + shipping): http://www.edition-kainhofer.com/en/lilypond/details/2111/ These copies are printed borderless on heavier paper and are laminated, so they are waterproof and should hold for years. Ok, that's good for hardcore typesetters. I don't need it every day and would be satisfied with a cheap thin paper printout. But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? Best regards, Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
- Original Message - From: Helge Kruse helge.kruse-nos...@gmx.net To: lilypond-user@gnu.org Sent: Monday, September 12, 2011 6:21 PM Subject: Re: Basic LilyPond Cheat Sheet Am 12.09.2011 14:39, schrieb Reinhold Kainhofer: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. The cheat sheet is meant to be a quick summary of the things explained in the learning manual, but does not replace the learning manual. It simply is a quick reminder of all the stuff, once you have read the learning manual. Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf I also provide nicely printed copies of the cheat sheet for basically my own costs (3€ per sheet + shipping): http://www.edition-kainhofer.com/en/lilypond/details/2111/ These copies are printed borderless on heavier paper and are laminated, so they are waterproof and should hold for years. Ok, that's good for hardcore typesetters. I don't need it every day and would be satisfied with a cheap thin paper printout. But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? Hmm. I get Unable to start print job. So there's something strange going on. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Nice job, Rheinhold! Good choices for what to include and what to leave out. Cheers, Mike Am 12.09.2011 14:39, schrieb Reinhold Kainhofer: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On Sep 12, 2011, at 12:42 PM, Phil Holmes m...@philholmes.net wrote: - Original Message - From: Helge Kruse helge.kruse-nos...@gmx.net To: lilypond-user@gnu.org Sent: Monday, September 12, 2011 6:21 PM Subject: Re: Basic LilyPond Cheat Sheet Am 12.09.2011 14:39, schrieb Reinhold Kainhofer: Dear all, Sometimes it can be very useful -- in particular for new and not so experienced users -- to have the basic LilyPond syntax available compressed on one single sheet. I have created such a cheat sheet that displays the basic lilypond syntax and usage (without any tweaks and overrides) on one single page, while also being visually appealing. The cheat sheet is meant to be a quick summary of the things explained in the learning manual, but does not replace the learning manual. It simply is a quick reminder of all the stuff, once you have read the learning manual. Attached you can find the PDF version of this cheat sheet: http://www.fam.tuwien.ac.at/~reinhold/temp/2011-08-24_LilyPond_CheatSheet_Basic.pdf I also provide nicely printed copies of the cheat sheet for basically my own costs (3€ per sheet + shipping): http://www.edition-kainhofer.com/en/lilypond/details/2111/ These copies are printed borderless on heavier paper and are laminated, so they are waterproof and should hold for years. Ok, that's good for hardcore typesetters. I don't need it every day and would be satisfied with a cheap thin paper printout. But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? Hmm. I get Unable to start print job. So there's something strange going on. -- Phil Holmes Hmm, I had no trouble printing it from my iPad. Stan ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Am Montag, 12. September 2011, 19:21:02 schrieb Helge Kruse: But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? No, printing is not disallowed. It is probably some incompatibility with Acrobat Reader. I can print it just fine from okular. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
On 13/09/11 04:55, Reinhold Kainhofer wrote: Am Montag, 12. September 2011, 19:21:02 schrieb Helge Kruse: But when I try to send the PDF to my printer I get the messages Das Dokument konnte nicht gedruckt werden. (The document could be printed.) Keine zum Drucken ausgewählte Seiten vorhanden. (There are no pages selected to print.) When I look at the PDF document properties I can read Drucken: Zuläsig (Print: allowed). Is this intentionally inhibited with some scripts in the document or is there something incompatible with Acrobat Reader 9.4.2.220? No, printing is not disallowed. It is probably some incompatibility with Acrobat Reader. I can print it just fine from okular. I can't print it from Adobe Reader on Ubuntu either. I also opened it in the default PDF document viewer that comes with Ubuntu (Evince), and in that, most of the text just displays as blocks of various sizes and shades - see attached screen dump of part of the page. Nick attachment: Screenshot.png___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Basic LilyPond Cheat Sheet
Am 12.09.2011 20:55, schrieb Reinhold Kainhofer: No, printing is not disallowed. It is probably some incompatibility with Acrobat Reader. I can print it just fine from okular. Do you consider to make it Adobe compatible? Regards, Helge ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
