Pondings
Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! If you refresh the page, you'll see two announcements, each of which is in two languages. For the time being we're posting all content, regardless of language, on the homepage. We'll be putting a mechanism in place soon to be able to diffuse multilingual content automatically to the appropriate pages. Send me your pondings so that I can post them! People are more likely to download the software if they see that we're a lively community that is getting LilyPond-typeset music out into the world. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clickable table of contents
Hello Àlex and Frederico,
the toc-markup is executed/expanded, when the markuplist with
table-of-contents is created. So \fromproperty #'header:title gets the
title from the bookpart containing the tocs.
To have a method, that sets the title and the toc item in one step,
there has to be another way to store title/toc information. One could
write a scheme-function to create the bookpart, which contains the title
*and* the \tocItem command.
I use my own functions, to collect music and process books. But it is a
bit too complex to explain in a few lines here.
Cheers,
Jan-Peter
On 07.05.2012 00:26, Federico Bruni wrote:
Il 04/05/2012 16:57, Álex R. Mosteo ha scritto:
I would also be interested on how to get automatically a ToC entry
for each
song, I'm currently doing it like this:
\tocItem \markup Author - Song
\bookpart {
\header { title=Song subtitle=Author }
which causes some nagging duplication. But this is secondary anyway.
Now I see why your title is not clickable: you must put \tocItem
inside \bookpart:
markuplist \table-of-contents
\pageBreak
\bookpart {
\header { title=Song subtitle=Author }
\tocItem \markup Author - Song
\score { c'1 }
}
I don't know how to get automatically the ToC entry from the header.
You probably have to fiddle with \fromproperty #'header:title
If you have a look at ly/toc-init.ly you see:
\paper {
tocItemMarkup = \markup \fill-line {
\fromproperty #'toc:text
\fromproperty #'toc:page
}
}
You should find a way to tell lilypond to replace the content of
#'toc:text
This content is defined inside \tocitem \markup { here }
But this doesn't print anything:
\markuplist \table-of-contents
\pageBreak
\bookpart {
\header { title=Song subtitle=Author }
\tocItem \markup \fill-line {
\fromproperty #'header:title
\fromproperty #'header:subtitle
}
\score { c'1 }
}
___
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: Pondings
2012/5/7 m...@apollinemike.com m...@apollinemike.com: Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! Thank you, but it works only on the English page (i.e. if your browser's first language is set to English). Greetlings, Hraban ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pondings
2012/5/7 Henning Hraban Ramm hra...@fiee.net: 2012/5/7 m...@apollinemike.com m...@apollinemike.com: Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! Thank you, but it works only on the English page (i.e. if your browser's first language is set to English). That's because translators still have to update their versions of the front page. The problem I see, on the other hand, is that no matter how many times I refresh the page, I always see only the two English tweets. -- 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: Pondings
On 7 mai 2012, at 10:02, Francisco Vila wrote: 2012/5/7 Henning Hraban Ramm hra...@fiee.net: 2012/5/7 m...@apollinemike.com m...@apollinemike.com: Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! Thank you, but it works only on the English page (i.e. if your browser's first language is set to English). That's because translators still have to update their versions of the front page. The problem I see, on the other hand, is that no matter how many times I refresh the page, I always see only the two English tweets. I just pushed the translations into the code base - they'll take some time to surface on the webpage. Sorry for the misinformation. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pondings
m...@apollinemike.com m...@apollinemike.com writes: On 7 mai 2012, at 10:02, Francisco Vila wrote: 2012/5/7 Henning Hraban Ramm hra...@fiee.net: 2012/5/7 m...@apollinemike.com m...@apollinemike.com: Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! Thank you, but it works only on the English page (i.e. if your browser's first language is set to English). That's because translators still have to update their versions of the front page. The problem I see, on the other hand, is that no matter how many times I refresh the page, I always see only the two English tweets. I just pushed the translations into the code base - they'll take some time to surface on the webpage. Sorry for the misinformation. I repeat my suggestion to use the same pondings on every page, filtered through _all_ of the languages in the browser preferences. The page choice itself is based on the _first_ supported language. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pondings
Am 07.05.2012 10:09, schrieb David Kastrup: m...@apollinemike.comm...@apollinemike.com writes: On 7 mai 2012, at 10:02, Francisco Vila wrote: 2012/5/7 Henning Hraban Rammhra...@fiee.net: 2012/5/7 m...@apollinemike.comm...@apollinemike.com: Hey LilyPond users, Just a note to let you know that the Pondings column is now live on lilypond.org! Thank you, but it works only on the English page (i.e. if your browser's first language is set to English). That's because translators still have to update their versions of the front page. The problem I see, on the other hand, is that no matter how many times I refresh the page, I always see only the two English tweets. I just pushed the translations into the code base - they'll take some time to surface on the webpage. Sorry for the misinformation. I repeat my suggestion to use the same pondings on every page, filtered through _all_ of the languages in the browser preferences. The page choice itself is based on the _first_ supported language. And I really stronly suggest, that - in addition to discussing the technical aspects - people think about submitting entries to Mike. I can't imagine that there aren't quite a few 'tweetable' projects out there. And I would consider it a very contraproductive 'statement' if it would remain a list of only two projects ... Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pondings
2012/5/7 Urs Liska li...@ursliska.de: And I really stronly suggest, that - in addition to discussing the technical aspects - people think about submitting entries to Mike. I can't imagine that there aren't quite a few 'tweetable' projects out there. And I would consider it a very contraproductive 'statement' if it would remain a list of only two projects ... Would you tweet about a small LilyPond song score in a church magazine? That’s one of my regular uses, and I consider it too minor. My other main use are song sheets/booklets for my private pleasure, and since they contain mostly copyrighted songs, I can’t publish them, unfortunately. And I guess a lot of other users have similar problems – how much sense makes a tweet about some unspectacular internal use of LilyPond? Greetlings, Hraban ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pondings
I don't think we should filter out anything below a Bärenreiter publication ;-) The point is to show what Lilypond is good and valuable for. So I'd say (but I'm not responsible for this): Anything that is in some way public (and possibly even linkable) qualifes immediately. Private use may also be useful for this purpose. If you can say: my church choir can sing better from LilyPond scores, it's a perfect advertisment for downloading lilypond, isn't it? And I'd estimate a statement like 'I use LilyPond for my analyzes because I can use style sheets to mark my results' also a valuable contribution. But as mentioned, I'm not responsible for this, so (all out there) get in touch with Mike ... Best Urs -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. Henning Hraban Ramm hra...@fiee.net schrieb: 2012/5/7 Urs Liska li...@ursliska.de: And I really stronly suggest, that - in addition to discussing the technical aspects - people think about submitting entries to Mike. I can't imagine that there aren't quite a few 'tweetable' projects out there. And I would consider it a very contraproductive 'statement' if it would remain a list of only two projects ... Would you tweet about a small LilyPond song score in a church magazine? That’s one of my regular uses, and I consider it too minor. My other main use are song sheets/booklets for my private pleasure, and since they contain mostly copyrighted songs, I can’t publish them, unfortunately. And I guess a lot of other users have similar problems – how much sense makes a tweet about some unspectacular internal use of LilyPond? Greetlings, Hraban _ 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
Glissando with artificial harmonics
Is it in any way possible to engrave a glissando with artificial harmonics? When I try the usual syntax for glissandi with the minimal example below, I get the following error: syntax error, unexpected ''', expecting or DRUM_PITCH or MUSIC_FUNCTION or NOTENAME_PITCH Tiny example: e! b!'\harmonic1 \glissando f! c!'\harmonic1 Many thanks! Jethro ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Glissando with artificial harmonics
Ah, nevermind. I should have read the error more clearly... Jethro Jethro Van Thuyne (06 May 2012 @ 18:21) Is it in any way possible to engrave a glissando with artificial harmonics? When I try the usual syntax for glissandi with the minimal example below, I get the following error: syntax error, unexpected ''', expecting or DRUM_PITCH or MUSIC_FUNCTION or NOTENAME_PITCH Tiny example: e! b!'\harmonic1 \glissando f! c!'\harmonic1 Many thanks! Jethro ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Different staff sizes
Hi everybody!
I'm new to this list, though I have been using and hugely appreciating
Lilypond for many years now. I am writing a book of little pieces for
violin beginners, free to use and copy of course :-) I'll set up a
website for it in the next months.
I am now blocked by what I consider a Lilypond limitation, but maybe I
just couldn't figure out how to do what I want. I'd like to have my
little pieces in one big pdf file. The problem is: I need different
staff sizes for different pieces and chapters of the book.
#(set-global-staff-size 14) does only work for books, but not for
\bookparts!
Using layout-set-staff-size makes only the font bigger (if I'm right),
but not the lines, so that following solution does not work:
\score{
\relative c' { c4 d e f g1 }
\layout {
#(layout-set-staff-size 15)
}
}
\score{
\relative c' { c4 d e f g1 }
\layout {
#(layout-set-staff-size 30)
}
}
According to Google, this seems to be a wide-known problem.
Is there any trick or tweak to scale the staves and lines to
layout-set-staff-size? Or any other way to have different staff sizes in
one document with Lilypond?
Does this bug report shows that there is no hope?
http://code.google.com/p/lilypond/issues/detail?id=216
Is an ugly trick excluded, a way to go around the problem?
Thank you for your time, greetings from Nürnberg, Germany,
Johannes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Swung eighths syntax?
Hi, I'm working on a project (github.com/mostawesomedude/lye) where one of the main formats is a strict subset of Lilypond syntax. I want to introduce swung eighths, but don't know what syntax Lilypond plans to adopt for it. What's the expected syntax going to look like? Should I just roll my own? ~ C. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Swung eighths syntax?
Corbin Simpson mostawesomed...@gmail.com writes: Hi, I'm working on a project (github.com/mostawesomedude/lye) where one of the main formats is a strict subset of Lilypond syntax. I want to introduce swung eighths, but don't know what syntax Lilypond plans to adopt for it. What's the expected syntax going to look like? Should I just roll my own? I don't think you should worry all too much: the expected syntax is most likely going to end up as a single music function call over a long music expression, so you are not likely to require doing much once it actually gets supported. If you intend on swinging manually yourself, you need to do something like converting every c8 c8 into c8*4/3 c8*2/3 (assuming the common 2+1 swinging pattern). That's not expected syntax but rather existing syntax, but of course doing that sort of thing for manual music entry is rather cumbersome. Since you are planning an automated export, you might consider doing it in this manner if you are in control of the generated rhythm anyway. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Different staff sizes
hi
you can override the staff-space of the staffsymbol like that:
\layout {
#(layout-set-staff-size 30)
\context {
\Staff
\override StaffSymbol #'staff-space = #(magstep 3)
}
}
hth
Eluze
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Swung eighths syntax?
On May 6, 2012, at 3:40 PM, Corbin Simpson wrote: Hi, I'm working on a project (github.com/mostawesomedude/lye) where one of the main formats is a strict subset of Lilypond syntax. I want to introduce swung eighths, but don't know what syntax Lilypond plans to adopt for it. What's the expected syntax going to look like? Should I just roll my own? The problem is that there is no accurate standard notation for the swing feel. There are various attempts to notate swing, such as alternating dotted 8ths and 16ths, but the swing groove is highly individual and is modified in context in the bandstand. My solution is to write straight 8s and note swing somewhere on the lead sheet (this may apply to the whole score or only to a section). ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Different staff sizes
In lilypond-user Digest, Vol 114, Issue 19, on 7 May 2012 Eluze wrote:
Message: 8
Date: Mon, 07 May 2012 15:54:57 +0200
From: Eluze elu...@gmail.com
Subject: Re: Different staff sizes
Message-ID: 4fa7d431.7040...@gmail.com
you can override the staff-space of the staffsymbol like that:
\layout {
#(layout-set-staff-size 30)
\context {
\Staff
\override StaffSymbol #'staff-space = #(magstep 3)
}
}
I find it difficult to find much documentation on this. What is a magstep?
and is the 3 just the layout-set-staff-size value divided by 10?
On 20 Apr 2012 in lilypond-user Digest, Vol 113, Issue 69, David Nalesnik wrote
to explain what the staff-space should be as follows:
On Fri, Apr 20, 2012 at 10:47 AM, Silvio ARDITO silvioard...@gmail.comwrote:
I need the following layout:
[image: Immagine in linea 2]
The result is a copy and paste from 2 .ly.
The little up-right staff uses: *#(set-global-staff-size 11)* ;
the rest uses: *#(set-global-staff-size 20)* .
The command: *#(layout-set-staff-size 11)*
in the \layout section gives a not valid result.
When you change the staff size like this, you also need to override the
distance between the lines:
\override Staff.StaffSymbol #'staff-space = #(/ 11 20)
no mention of magstep here
Also, take a look at this snippet:
http://lilypond.org/doc/v2.15/Documentation/snippets/staff-notation
and cited snippet contains code using magstep, again without much explanation
of how to calculate the value.
And finally, wouldn't it be nice to have all this explained in the Notation
Manual, say right after the following entry:
Known issues and warnings
layout-set-staff-size does not change the distance between the staff
lines.
but not as nice as having layout-set-staff-size actually set the staff-size
along with the elimination of the above Known issues and warnings?
The best explanation I have found of magstep is in section 4.3.3, Length and
thickness of objects, of the Learning Manual, although I find the explanation
at first reading to be a little opaque.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clickable table of contents
Federico Bruni wrote:
Il 04/05/2012 16:57, Álex R. Mosteo ha scritto:
I would also be interested on how to get automatically a ToC entry for
each song, I'm currently doing it like this:
\tocItem \markup Author - Song
\bookpart {
\header { title=Song subtitle=Author }
which causes some nagging duplication. But this is secondary anyway.
Now I see why your title is not clickable: you must put \tocItem inside
\bookpart:
markuplist \table-of-contents
\pageBreak
\bookpart {
\header { title=Song subtitle=Author }
\tocItem \markup Author - Song
\score { c'1 }
}
Thank you all for your answers and warnings. Indeed that was simple. That's
enough for my present purposes, even if I have to write two times the titles
(that was a minor nag).
This week-end I had settled on having a plain .tex file, and including the
PDF for each song (generated from separate .ly files). The package pdfpages
does it this way:
\includepdf[pages={-},addtotoc={1,section,1,Artist - Song,somelabel}]{file}
It's a bit more cumbersome (and still requires to duplicate the info). I'm
too newbie to know, but maybe there are cases with reasons to go fully LaTeX
and then this way would work (not that this is specific to lilypond,
anyway).
BTW, lilypond-book barfed on my .lytex when including my .ly (which compiled
fine with lilypond), but not when using inline snippets. I guess that is
necessarily a bug in lilypond-book?
Cheers,
Álex.
I don't know how to get automatically the ToC entry from the header.
You probably have to fiddle with \fromproperty #'header:title
If you have a look at ly/toc-init.ly you see:
\paper {
tocItemMarkup = \markup \fill-line {
\fromproperty #'toc:text
\fromproperty #'toc:page
}
}
You should find a way to tell lilypond to replace the content of
#'toc:text This content is defined inside \tocitem \markup { here }
But this doesn't print anything:
\markuplist \table-of-contents
\pageBreak
\bookpart {
\header { title=Song subtitle=Author }
\tocItem \markup \fill-line {
\fromproperty #'header:title
\fromproperty #'header:subtitle
}
\score { c'1 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
tremolo issues
using 2.12.3 (as packaged with Debian stable), I get the following issues:
tremolo marks touch the half-note stems, and I would like them to stop short
(giving an appearance similar to the tremelo marks for the whole note in the
included file)
I get the warning message weird stem size, check for narrow beams for the whole note
tremolo. If the note is lower on the staff, the message goes away. Is there some fix that will
either take care of the underlying narrow beam issue on the whole note if it is a valid
issue, or make the warning message go away?
following is a snippet that shows the behavior I am talking about:
\version 2.12.3
vi = { g!2:32
% beams are too wide on the tremolo here, should not touch the stems
\repeat tremolo 8 { f!32 e! } |
% these overrides are make the marks line up with the notes,
% they do not affect the weird stem size / narrow beams warning
\once \override Beam #'gap = #1.5
\once \override Beam #'extra-offset = #'(-0.5 . -1)
% narrow beams bug here
\repeat tremolo 16 { f!32 e!32 } | }
\score {
\new StaffGroup
\new Staff \relative c''' \vi
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Different staff sizes
I agree - I seem to remember having seen it in earlier documentations - now I found it in http://lilypond.org/doc/v2.15/Documentation/snippets/staff-notation#staff-notation-changing-the-staff-size why has it been moved? Eluze ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tremolo issues
hi
I don't know which is the newest available release on Debian but there
are significant changes!
Eluze
Am 07.05.2012 21:55, schrieb Justin Glenn Smith:
using 2.12.3 (as packaged with Debian stable), I get the following
issues:
tremolo marks touch the half-note stems, and I would like them to stop
short (giving an appearance similar to the tremelo marks for the whole
note in the included file)
I get the warning message weird stem size, check for narrow beams
for the whole note tremolo. If the note is lower on the staff, the
message goes away. Is there some fix that will either take care of the
underlying narrow beam issue on the whole note if it is a valid
issue, or make the warning message go away?
following is a snippet that shows the behavior I am talking about:
\version 2.12.3
vi = { g!2:32
% beams are too wide on the tremolo here, should not touch the stems
\repeat tremolo 8 { f!32 e! } |
% these overrides are make the marks line up with the notes,
% they do not affect the weird stem size / narrow beams warning
\once \override Beam #'gap = #1.5
\once \override Beam #'extra-offset = #'(-0.5 . -1)
% narrow beams bug here
\repeat tremolo 16 { f!32 e!32 } | }
\score {
\new StaffGroup
\new Staff \relative c''' \vi
}
___
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: tremolo issues
Justin Glenn Smith noisesmith at gmail.com writes: using 2.12.3 (as packaged with Debian stable), I get the following issues: tremolo marks touch the half-note stems, and I would like them to stop short There is a separate setting 'gap-count' for how many tremolo beams get a gap. http://lilypond.org/doc/v2.14/Documentation/snippets/rhythms.html#engraving- tremolos-with-floating-beams I get the warning message weird stem size, check for narrow beams for the whole note tremolo. The more recent version 2.14 gives no warning on your example. I don't know a way to quiet the warning with version 2.12 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
