Re: Article in German LinuxUser magazine
Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander Kobel: > today at the train station I stumbled across the German LinuxUser > magazine, featuring an article about music engraving. I found myself > surprised and happy, seeing LilyPond mentioned in the first place Thanks for mentioning this. I found it can be downloaded from http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf Any volunteers for adding this to web/publications? > Alas, then comes the summary: It's even worse, it starts out with Fazit Auch im Jahr 18 seit dem Kernel 0.1 bleibt es dabei: Die Open- Source-Welt hat noch immer Schwierigkeiten, ein derartiges Nischenprodukt wie ein Noten- satzprogramm zu entwickeln. Die Ergebnisse von Lilypond samt seinem Frontend Frescobal- di mögen äußerst professionell anmuten, doch eine neue Mark up-Sprache zu erlernen und in dieser grafische Vorstellungskraft zu entwickeln ist nicht jeder- manns Sache. "Even in the 18th year since kernel 0.1 it remains: the open source world has still difficulties developing a niche-product like a music typesetter." > I'm more than willing to write a letter to the editor. Great. It looks friendly and informative, I hope they print your suggestions next time. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Png image files are always 859x1111
Hi Everyone
I've been experimenting with Lilypond to see how I might project music with an
overhead projector for sing-alongs. While playing with the png format option I
noticed that the png image is always cropped to be 859x pixels (which
corresponds the "Letter" size, I believe). I say "cropped" because I can make
the standard lilypond footer line move around by changing paper sizes, but the
image size never changes.
I am running version 2.12.2 of Lilypond on a Windows XP machine with ample
resources. This is the lilypond file I played with (a snippet I found on the
website):
#(set-default-paper-size "a5" 'landscape)
\paper {
#(set-paper-size "a5")
}
\relative c'' {
a1 a a
% move to right position
-\tweak #'extra-offset #'(-2 . -4.5)
% place in bottom layer
-\tweak #'layer #-1
^\markup {
% specify color
\with-color #(rgb-color 1 0.5 0.5)
% specify size
\filled-box #'(0 . 8) #'(0 . 4) #0
}
a
}
I played with various combinations of 'set-default-paper-size' and
'set-paper-size'. I found that the pdf output format takes the paper size into
account, but never the png one. I even created a new output form size and
edited paper.scm as suggested elsewhere - still with no effect on png (although
it worked with pdf).
Is there something else I need to take into account with png? Some other
property or setting I need to change, perhaps?
I would like to get it to work with png format as that opens up other
possibilities for me which won't be available with pdf or ps formats.
Kind regards,
Johan Hoogenboezem
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 22 Sep 2009, at 01:09, Joseph Wakeling wrote: Currently Lilypond's transposition is tonal only, with the 'smart transpose' snippet providing a Scheme function to minimise accidental use. Unfortunately this function is incompatible with quarter-tone notation. Discussing with Graham Breed, I got the impression that LilyPond does it correctly, only that it insists on substituted values for the intervals. When transposing, roughly, one transposes intervals and scale degrees separately. The scale degrees may be identified with the pitch values of the staff. Then, on top of that, one may impose enharmonic equivalents with respect to some tuning system. (E12 is a favorite.) The attached snippet shows the problem. A quarter-tone chromatic scale is displayed, first untransposed; then untransposed and run through the naturalizeMusic function; then transposed a quarter- tone up; then transposed up and run through naturalizeMusic; and finally, run through naturalizeMusic and then transposed. So here you transpose a quarter-tone and a scale degree zero. All note heads should remain in the same position in the staff; only accidentals change. What you see is that (i) without naturalizeMusic, transposition fails: transposition alone leaves the final pitch being 'g+5/4' which has no accidental I think is just a bug. Somehow the sharp drops out. (ii) naturalizeMusic saves the transposition, but alters accidentals which don't need to be altered -- e.g. g-3/4 is transformed to f+1/4. Here, the most obvious thing for a machine to do, is to merely impose E12 enharmonic equivalents in order to minimize the number of accidentals. So the problem is to figure out a rule for the changes. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
Hans Aberg wrote: >> What you see is that >> >> (i) without naturalizeMusic, transposition fails: transposition alone >> leaves the final pitch being 'g+5/4' which has no accidental > > I think is just a bug. Somehow the sharp drops out. It's not so much a bug as a notational impossibility. Think of pitch as being staff position s plus alteration a. The latter is used to determine the accidental. So in this case we're dealing with a base pitch of g+1, which is displayed as g-double-sharp. Now you transpose it up a quarter-tone, so all pitches are altered by +1/4. Your pitch is now g+5/4 and there is no accidental for +5/4 so of course one can't be displayed. So, if there _is_ a bug, it's that Lilypond doesn't recognise that an alteration of >1 should change the staff position. > Here, the most obvious thing for a machine to do, is to merely impose E12 > enharmonic equivalents in order to minimize the number of accidentals. So the > problem is to figure out a rule for the changes. Yup. It's a not-entirely-trivial problem. For example, you want to preserve things like the notated g-three-quarters-flat which naturalizeMusic destroys, but you want to avoid ridiculous notations like E-three-quarters-sharp or C-three-quarters-flat. But anyway, THAT I think I can do. The question is, how to incorporate a well-defined chromatic transposition rule as an option in Lilypond as opposed to a function à la naturalizeMusic? Thanks & best wishes, -- Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 22 Sep 2009, at 11:16, Joseph Wakeling wrote: Hans Aberg wrote: What you see is that (i) without naturalizeMusic, transposition fails: transposition alone leaves the final pitch being 'g+5/4' which has no accidental I think is just a bug. Somehow the sharp drops out. It's not so much a bug as a notational impossibility. Think of pitch as being staff position s plus alteration a. The latter is used to determine the accidental. So in this case we're dealing with a base pitch of g+1, which is displayed as g-double-sharp. Now you transpose it up a quarter-tone, so all pitches are altered by +1/4. Your pitch is now g+5/4 and there is no accidental for +5/4 so of course one can't be displayed. The correct accidental is a # plus a !/4. It then does not change the scale degree. This will also be correct in if the sharp and microtonal accents are relative a tuning system other than E12. So, if there _is_ a bug, it's that Lilypond doesn't recognise that an alteration of >1 should change the staff position. In this case, staff position only changes if enharmonic equivalents are applied. This is how it should be. The question is, how to incorporate a well-defined chromatic transposition rule as an option in Lilypond as opposed to a function à la naturalizeMusic? The staff system is what I call diatonic. It cannot be changed, because that is how it was designed around year 1600. I made a description of it using minor, major and neutral seconds. I can think of generalizations, where the staff indicates an arbitrary choice pitches, but I do not think that musicians could read it. So you want is a mixture if the traditional system and enharmonic equivalents. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Jan Nieuwenhuizen wrote: Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander Kobel: today at the train station I stumbled across the German LinuxUser magazine, featuring an article about music engraving. I found myself surprised and happy, seeing LilyPond mentioned in the first place Thanks for mentioning this. I found it can be downloaded from http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf Any volunteers for adding this to web/publications? The article about lilypond is not there. It should be at page 46, but this pdf is only 34 pages.. This is the correct link (I think): http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
Hans Aberg wrote: > The correct accidental is a # plus a !/4. It then does not change the > scale degree. This will also be correct in if the sharp and microtonal > accents are relative a tuning system other than E12. No, it's a DOUBLE-sharp plus a 1/4, which quite obviously does not exist. > In this case, staff position only changes if enharmonic equivalents are > applied. This is how it should be. That's why I stress I want this as an _option_ for transposition, not default functionality. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
On Tue, Sep 22, 2009 at 09:40:59AM +0200, Jan Nieuwenhuizen wrote: > Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander > Kobel: > > > today at the train station I stumbled across the German LinuxUser > > magazine, featuring an article about music engraving. I found myself > > surprised and happy, seeing LilyPond mentioned in the first place > > Thanks for mentioning this. I found it can be downloaded from > > http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf > > Any volunteers for adding this to web/publications? Added to Documentation/general/community.itexi, Publications section. I'm not going to bother with oldweb. (will push the commit in a few hours) Not being able to read German, I made it a neutral announcement about the article's existance. If anybody feels like adding something like "we disagree with their `Fargle Zein Buutstrapp' comment", go ahead. OTOH, maybe we should wait a few weeks until we can say "a letter publishined in _this other article_ contains a few clarifications to this article". Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
2009/9/22 Federico Bruni : >> http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf >> > > The article about lilypond is not there. > It should be at page 46, but this pdf is only 34 pages.. It is, just search for "LilyPond", page 46 is at page "17 of 24" of the PDF > This is the correct link (I think): > http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel Yes, for an html version of the article. -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
On Tue, Sep 22, 2009 at 11:46:32AM +0200, Federico Bruni wrote: > Jan Nieuwenhuizen wrote: >> Thanks for mentioning this. I found it can be downloaded from >> >> http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf >> >> Any volunteers for adding this to web/publications? >> > > The article about lilypond is not there. > It should be at page 46, but this pdf is only 34 pages.. > > This is the correct link (I think): > http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel Thanks, fixed due to the magic of git rebase -i. :) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Op dinsdag 22-09-2009 om 11:46 uur [tijdzone +0200], schreef Federico Bruni: > Jan Nieuwenhuizen wrote: > > Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander > > Kobel: > > > > Thanks for mentioning this. I found it can be downloaded from > > > > http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf > > > > Any volunteers for adding this to web/publications? > > > > The article about lilypond is not there. Yes it is, it is at page 46. > It should be at page 46, but this pdf is only 34 pages.. No it isn't. > This is the correct link (I think): > http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel That may be nicer to link to on our pub page, though. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Francisco Vila wrote: 2009/9/22 Federico Bruni : � � http://www.linux-user.de/Downloads/LUCE/2009/lu-ce_2009-10.pdf The article about lilypond is not there. It should be at page 46, but this pdf is only 34 pages.. It is, just search for "LilyPond", page 46 is at page "17 of 24" of the PDF Oh, you are right! Well.. my error forced me to find the html version, so it's better so ;-) This is the correct link (I think): http://www.linux-community.de/Internal/Artikel/Print-Artikel/LinuxUser/2009/10/Digitaler-Notenschluessel Yes, for an html version of the article. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Op dinsdag 22-09-2009 om 11:12 uur [tijdzone +0100], schreef Graham Percival: > On Tue, Sep 22, 2009 at 09:40:59AM +0200, Jan Nieuwenhuizen wrote: > > Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander > > Kobel: > > Added to Documentation/general/community.itexi Thanks! > Not being able to read German, I made it a neutral announcement > about the article's existance. I think it's unwise either way to bicker or complain when people are writing about you :-) Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
2009/9/21 Alexander Kobel : > Und für "das täglich Brot" eines Chor- oder Orchesterleiters - > einfache, vierstimmige Chorsätze und Stimmenauszüge für einzelne > Instrumente - ist LilyPond schon für Fast-Neueinsteiger das schnellste > Programm, dass ich bisher gesehen habe. Kein Griff zur Maus ist > notwendig, die Ausgabe kann sofort für die Musiker vervielfältigt > werden. Alternativ läßt sich auch eine MIDI-Eingabe einrichten. Und > wer mit musikalischer Notation vertraut ist, für den sind die > Notennamen auch buchstabiert bald ganz natürlich - dank \include > "german.ly" sogar mit h statt b. > > > [Es wird erwähnt, dass LilyPond den englischen > (bzw. alles-außer-deutschen) Bezeichner für das "h" verwendet - mit > genausoviel Text hätte man allerdings auch das \include "german.ly" > erklären können.] Thank you for the effort! The letter looks good, but I'd leave out the MIDI input (even if someone's working on midi2ly again), and at least in my installation of 1.13 there's no german.ly (must investigate further...) For the chords \germanChords is working. Greetlings, Hraban ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 22 Sep 2009, at 11:49, Joseph Wakeling wrote: The correct accidental is a # plus a !/4. It then does not change the scale degree. This will also be correct in if the sharp and microtonal accents are relative a tuning system other than E12. No, it's a DOUBLE-sharp plus a 1/4, ... Yes, sorry for the typo. ...which quite obviously does not exist. I think LilyPond, once it has found the correct scale degree, computes the interval offset. As there is none for this particular offset, it typesets nothing. It should report at least a warning, though. The value stored inside should though be correct. So I think you need to add a choice of glyph. LilyPond is too primitive to treat # and b and other accidentals as operators acting on all intervals. In this case, staff position only changes if enharmonic equivalents are applied. This is how it should be. That's why I stress I want this as an _option_ for transposition, not default functionality. I think one needs to think through carefully how one wants to enharmonic equivalences be applied. It may vary with context. On most instruments, it can be used to simplify key signatures. On a harp, it may have to be applied note-by-note, as double sharps and flats are not available. If the tuning is other than E12, it implies a small slip in pitch. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander Kobel: > Spätestens beim Schlusswort des Autors befiel mich jedoch das kalte > Grausen ob der Recherche: "wenn [...] Sie einzelne Stimmen > transponieren wollen, ist hier Neuschreiben angesagt[.]" Mitnichten! > \transpose c d etwa verlegt den folgenden Ausdruck einen Ganzton nach > oben. Rereading the article, I believe the author says * frescobaldi + LilyPond looks professional, but * writing .ly is not for everyone and * frescobaldi does not offer transposing or quoting with the mouse So, pointing to \transpose is fine, but that does not help the gui-only user... -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter Avatar®: http://AvatarAcademy.nl| http://lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Henning Hraban Ramm wrote: and at least in my installation of 1.13 there's no german.ly (must investigate further...) No, but there is a deutch.ly, so \include "deutch.ly" is probably what Alexander had in mind. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Henning Hraban Ramm schrieb: > and at least in my installation of 1.13 there's no german.ly (must > investigate further...) Try "deutsch.ly" :-) Ole ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
Hans Aberg wrote: > I think LilyPond, once it has found the correct scale degree, computes > the interval offset. As there is none for this particular offset, it > typesets nothing. It should report at least a warning, though. The value > stored inside should though be correct. Yes, I think this is exactly what it does -- and it does report a warning. > So I think you need to add a choice of glyph. LilyPond is too primitive > to treat # and b and other accidentals as operators acting on all > intervals. Well, the point is that a glyph for 5/4 sharp is nonsensical. A contemporary music player would be pissed off enough at seeing a double-sharp in non-tonal music, to say nothing of a 5/4-sharp symbol. >>> In this case, staff position only changes if enharmonic equivalents are >>> applied. This is how it should be. >> >> That's why I stress I want this as an _option_ for transposition, not >> default functionality. > > I think one needs to think through carefully how one wants to enharmonic > equivalences be applied. It may vary with context. On most instruments, > it can be used to simplify key signatures. On a harp, it may have to be > applied note-by-note, as double sharps and flats are not available. If > the tuning is other than E12, it implies a small slip in pitch. Yes, that's a good point I hadn't considered. The naturalizeMusic function serves the harp's needs well, where 3/4-sharps and flats are not possible. (Was that the motivation for this function?) So basically we are talking about a 'modulo effect', i.e. to constrain every accidental to 'modulo a' where a is an alteration: for the harp, to modulo 1/2, for standard chromatic transposition, to modulo 1. That might actually be the best way of looking at it -- relative to a maximum acceptable size of alteration. (Tricky would be less-than-or-equal-to versus less-than.) Best wishes, -- Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Henning Hraban Ramm wrote: Thank you for the effort! The letter looks good, but I'd leave out the MIDI input (even if someone's working on midi2ly again), Hm. Good point. It's not quite in the core... and at least in my installation of 1.13 there's no german.ly (must investigate further...) For the chords \germanChords is working. Uh-oh. See how often I use it, even as a German? It's called "deutsch.ly". And you're clever guys out there to look for an online version of the article... Kudos! Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
> > > Henning Hraban Ramm wrote: > > and at least in my installation > > of 1.13 there's no german.ly (must investigate further...) > > > No, but there is a deutch.ly, so > \include "deutch.ly" > is probably what Alexander had in mind. > > /Mats should be "deutsch.ly" Thomas > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Article in German LinuxUser magazine
Jan Nieuwenhuizen wrote: Op maandag 21-09-2009 om 22:47 uur [tijdzone +0200], schreef Alexander Kobel: Spätestens beim Schlusswort des Autors befiel mich jedoch das kalte Grausen ob der Recherche: "wenn [...] Sie einzelne Stimmen transponieren wollen, ist hier Neuschreiben angesagt[.]" Mitnichten! \transpose c d etwa verlegt den folgenden Ausdruck einen Ganzton nach oben. Rereading the article, I believe the author says * frescobaldi + LilyPond looks professional, but * writing .ly is not for everyone and * frescobaldi does not offer transposing or quoting with the mouse So, pointing to \transpose is fine, but that does not help the gui-only user... Actually, I think he's right in those basics. It _looks_ professional, and writing .ly probably _is_ not for everyone, but that's no excuse for poor investigation or writing about it. IMHO, it's nearly the same thing for LaTeX and LilyPond. I'd never bother to run LaTeX for a letter to Aunt Elsbeth, but as soon as you do larger projects, it starts to be worth the practising of the syntax. _Nearly_ the same thing, because I found LilyPond to be quicker even for the most basic musical works, but also this does probably not apply if you just want to type the chorals for your church wedding once in life. To be fair, regarding \transpose: I did not consider that he may have written only about language features actually offered by Frescobaldi - which may not be too bad at the first glance. On the other hand, I just recognised there is a menu option to switch to german note input (which, by the way, correctly includes "deutsch.ly", not "german.ly")... Cheers, Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 22 Sep 2009, at 13:44, Joseph Wakeling wrote: So I think you need to add a choice of glyph. LilyPond is too primitive to treat # and b and other accidentals as operators acting on all intervals. Well, the point is that a glyph for 5/4 sharp is nonsensical. A contemporary music player would be pissed off enough at seeing a double-sharp in non-tonal music, to say nothing of a 5/4-sharp symbol. The original staff system is generated by pure fifths and octaves. It can be recomputed in terms of major M and minor m seconds, which add one to the scale degree. The sharps and flats alter by the interval M - m, and do not change the scale degree. The original staff system is algebraic, and does not subsume any particular tuning. If one substitutes values for the intervals, then one has to be careful with that algebraic structure, because it is still there, but may be hidden by the explicit values. So you originally had two sharps and transposed up an intermediate interval, and so that is what you get. The sharp only get the value 1 in E12. But E12 does not respect the scale degrees of the original staff system. I think one needs to think through carefully how one wants to enharmonic equivalences be applied. It may vary with context. On most instruments, it can be used to simplify key signatures. On a harp, it may have to be applied note-by-note, as double sharps and flats are not available. If the tuning is other than E12, it implies a small slip in pitch. Yes, that's a good point I hadn't considered. The naturalizeMusic function serves the harp's needs well, where 3/4-sharps and flats are not possible. (Was that the motivation for this function?) So basically we are talking about a 'modulo effect', i.e. to constrain every accidental to 'modulo a' where a is an alteration: for the harp, to modulo 1/2, for standard chromatic transposition, to modulo 1. That might actually be the best way of looking at it -- relative to a maximum acceptable size of alteration. (Tricky would be less-than-or-equal-to versus less-than.) I think that the intervals, at least in E12 are computed internally so that an octave is 6. Thine if an offset is more than 1, you want to reduce it, and add 1 to the scale degree. So you should perhaps tweak the naturalizeMusic to do that instead. Then first transpose and apply this once afterwards. Just a guess. Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 9/21/09 5:09 PM, "Joseph Wakeling" wrote: > As I mentioned a little while back, I'm working on a specialist notation > section on contemporary music for the Notation Reference. And, as I > also mentioned, I'm going to be trying to implement and/or motivate some > feature development to support this. > > [...] > > > Now, I think that with a little time to get used to Scheme I could > rewrite naturalizeMusic to remove those undesirable features. The > bigger question is whether and how such functionality can be > incorporated into core Lilypond. > > What I'd like to see is to have transposition style defined as an aspect > of Score, StaffGroup/PianoStaff, Staff and Voice, that can change as the > piece progresses; so, one would be able to issue a command, > > \override Staff #'transposition = #'chromatic > > and later, switch back with > > \override Staff #'transposition = #'tonal > > ... with tonal being the default. > > So, the question is -- assuming I can define a _really_ smart transpose > with Scheme -- how feasible is it to incorporate it into Lilypond in > this fashion, and what should I be looking at/know in order to do it? > It will be not difficult to implement this in core LilyPond. Presumably there will be some sort of normalize-pitches function, which will take a staff position with with alterations and, based upon the key signature, turn it into a different staff position and alteration that represents the same pitch. Different normalize-pitches functions can be written for different behavior. A property representing the normalize-pitch function can tell the code which function to call. It will be necessary to add a property (easily done), and add the property to an interface (also easily done). If you get the chromatic transposition working properly, I'll commit to helping you get it embedded in LilyPond. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Contemporary music required feature #1: chromatic transposition
On 22 Sep 2009, at 15:00, Carl Sorensen wrote: If you get the chromatic transposition working properly, I'll commit to helping you get it embedded in LilyPond. My impression is that this works properly, only that LilyPond does not have the capacity to treat # and b as operators that can be iterated. Right now, I think, it just looks up the offset, and reports an error if no glyph is found for that offset. The missing glyph problem could be fixed by LilyPond then continuing and, if the offset is positive, subtracting a #, and then makes a new glyph lookup; and so on, until the offset becomes negative, and first then reports an error. Otherwise, print the number of #'s and the accidental. It will be not difficult to implement this in core LilyPond. Presumably there will be some sort of normalize-pitches function, which will take a staff position with with alterations and, based upon the key signature, turn it into a different staff position and alteration that represents the same pitch. Different normalize-pitches functions can be written for different behavior. A property representing the normalize-pitch function can tell the code which function to call. It will be necessary to add a property (easily done), and add the property to an interface (also easily done). For this, I think he just wants a version of the naturalizeMusic that applies E12 enharmonic equivalence if the offset is greater that two sharps, so one does not have to display a doublesharp plus a microtonal raising accidental. Though there is the case of say E#+ - should that be replaced by F+? Hans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Png image files are always 859x1111
Hello,
I typeset music weekly for display using Powerpoint. I'm attaching the
template I use. Once I have all the page breaks set the way I want, I
run lilypond in terminal (Linux) to generate the final png images.
lilypond -fpng -dresolution=300 filename.ly
The resolution doesn't need to be so high since display resolution is
only around 90 pixels per inch. But the higher resolution seems to work
better for whatever reason.
After generating my png images, I typically open them with Gimp and
convert the white background to alpha (Colors | Color to Alpha) before
loading them into Powerpoint. This allows you to use a color or texture
background to your music, which sometimes makes for a nicer display.
The template I use...
\version "2.12.0"
#(set-global-staff-size 40)
\header {
title = ""
subtitle = ""
composer = ""
tagline = ""
}
% The defined paper sizes are based on pixel to point conversion
% 1024 X 768 pixels (typical screen size) is equivalent to 768 X 576 points
% The line width of 748 allows for 10 points of white space on either
side of the image
\paper {
#(define paper-width ( * 768 pt))
#(define line-width ( * 748 pt))
#(define page-height ( * 576 pt))
print-page-number= ##f
between-system-space = 3.5\cm
between-system-padding = #4
ragged-bottom=##t
ragged-last-bottom=##t
%system-count = 18
%annotate-spacing = ##t
}
\relative c' {
\override Score.PaperColumn #'keep-inside-line = ##t
\override Score.NonMusicalPaperColumn #'keep-inside-line = ##t
\override Score.BarNumber #'transparent = ##t
\override Staff.TimeSignature #'style = #'()
\time 4/4
\key c \major
}
\addlyrics {
}
\layout {
indent = 0.0 \cm
}
These settings are sometimes used to help tweak the final results,
though I generally keep them commented out:
%system-count = 18
%annotate-spacing = ##t
Regards,
Stephen Corey
Roseville, California
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Png image files are always 859x1111
Stephen Corey wrote:
Hello,
I typeset music weekly for display using Powerpoint. I'm attaching the
template I use. Once I have all the page breaks set the way I want, I
run lilypond in terminal (Linux) to generate the final png images.
lilypond -fpng -dresolution=300 filename.ly
The resolution doesn't need to be so high since display resolution is
only around 90 pixels per inch. But the higher resolution seems to work
better for whatever reason.
After generating my png images, I typically open them with Gimp and
convert the white background to alpha (Colors | Color to Alpha) before
loading them into Powerpoint. This allows you to use a color or texture
background to your music, which sometimes makes for a nicer display.
The template I use...
\version "2.12.0"
#(set-global-staff-size 40)
\header {
title = ""
subtitle = ""
composer = ""
tagline = ""
}
% The defined paper sizes are based on pixel to point conversion
% 1024 X 768 pixels (typical screen size) is equivalent to 768 X 576 points
% The line width of 748 allows for 10 points of white space on either
side of the image
\paper {
#(define paper-width ( * 768 pt))
#(define line-width ( * 748 pt))
#(define page-height ( * 576 pt))
print-page-number= ##f
between-system-space = 3.5\cm
between-system-padding = #4
ragged-bottom=##t
ragged-last-bottom=##t
%system-count = 18
%annotate-spacing = ##t
}
\relative c' {
\override Score.PaperColumn #'keep-inside-line = ##t
\override Score.NonMusicalPaperColumn #'keep-inside-line = ##t
\override Score.BarNumber #'transparent = ##t
\override Staff.TimeSignature #'style = #'()
\time 4/4
\key c \major
}
\addlyrics {
}
\layout {
indent = 0.0 \cm
}
These settings are sometimes used to help tweak the final results,
though I generally keep them commented out:
%system-count = 18
%annotate-spacing = ##t
Regards,
Stephen Corey
Roseville, California
Forgot to mention that the page height setting
(#(define page-height ( * 576 pt))
doesn't actually work for png files. You'll have to use Gimp or another
software to manually crop the height at 576 points. After a couple
tries, you'll get a feel for where to break your pages. I can usually
get 3-4 staves per page with these settings. You can get a different
scale by changing
#(set-global-staff-size 40)
to whatever size works best for you.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Png image files are always 859x1111
2009/9/22 Stephen Corey : > You can get a different > scale by changing > > #(set-global-staff-size 40) > > to whatever size works best for you. For various reasons, this does not give the same appearance as an enlarged size of 20. I'd use always a big resolution instead, if necessary. -- Francisco Vila. Badajoz (Spain) www.paconet.org www.csmbadajoz.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
\RemoveEmptyStaffContext and cross-staff beams
Hello,
In the following code, the beam goes between the staves when
\RemoveEmptyStaffContext is commented out but goes above the top
staff when it's used.
This means you have to explicitly state all the stem directions to
get the beam to go in the middle of the staves when using
\RemoveEmptyStaffContext.
Is this a bug?
-Jonathan
Snippet below:
\version "2.13.3"
staffPiano = \new PianoStaff {
<<
\new Staff = "rh" { \relative c' {
c8[ c c c \change Staff = "lh" g, g g g]
}
}
\new Staff = "lh" { \relative c {
\clef bass
c1
}
}
>>
}
\score {
\staffPiano
}
\layout {
\context {
\RemoveEmptyStaffContext
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Png image files are always 859x1111
Hi Stephen Thanks a lot for your prompt and detailed reply. Your example certainly makes it look better. The dimensions are now 2550x3300 instead of 859x. Should it have been 1024x768? Thanks again Johan Hoogenboezem Gauteng, South Africa ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
