Beaming question
For a long "cadenza" passage I want to beam all notes together, but
do not succeed: there is the a subdivision before last 16th note, and
this note has a small beam in the wrong direction.
code:
--
\version "2.9.9"
#(ly:set-option 'point-and-click #f)
\score {
\relative c'' {
\key a \major
\cadenzaOn
a64[ gis b32 a gis fis e! dis! cis b ais! b bis cis16 b a gis b a8
fis gis]
\cadenzaOff
\bar "|"
\break
}
}
--
LilyPond 2.9.9
Windows XP
Der folgende Teil dieser Nachricht enthält einen Anhang im
sogenannten Internet MIME Nachrichtenformat.
Wenn Sie Pegasus Mail oder ein beliebiges anderes MIME-kompatibles
Email-System verwenden, sollte Sie den Anhang mit Ihrem Email-System
speichern oder anzeigen können. Anderenfalls fragen Sie Ihren Administrator.
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any another MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
Datei Information/File information ---
Datei/File: beam299.png
Datum/Date: 20 Jun 2006, 10:26
Größe/Size: 10257 bytes.
Typ/Type:Unbekannt
beam299.png
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Export from Lilypond
How other score formats i can create from my lily scores. It should be openable in other score editors (finale or capella). It is possible ? I can't see it in docs. Regards Tomasz ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: music definition change in 2.9.9 or thereabouts?
Erik Sandberg schreef:
I'm not quite sure what the proper solution is. The attached patch solves the
problem by renaming EVENT_IDENTIFIER to ARTICULATION_IDENTIFIER. The solution
is easy and it works AFAICT, but it relies on music-classes, whose fate is
uncertain. I did consider the following solutions as well:
1. Extend identifier-smob with type information (typically corresponding to
the return value of try_special_idetifiers). I think this will only move the
problem, because expressions like foo = #... must still be assigned a type
correctly.
2. unify MUSIC_IDENTIFIER with EVENT_IDENTIFIER. This has one problem: someone
will try
foo = -.
{ c2\foo d2 }
which (AFAICT) will put the dot above the d2
3. Whenever a variable is assigned music, wrap it in a dummy sequential_music.
Unclean.
Isn't it much easier to remove event from 'types for KeyChangeEvent (and
rename to KeyChange ?). KeyChange remains an odd event; it should really
be a property set for keySignature.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pronunciation of the author's names
Shamus schreef: Meeting Han-Wen last time I asked him how the name `Nieuwenhuizen' actually does sound. To make it short: I'll stay with `Jan' and `Han-Wen'. I'll take a stab at it, though I'm no expert at this kind of thing (the words nine, when, and zen are the American English pronunciations): :-) Nienhuys --> nine - hyoos Nieuwenhuizen --> nee - oo - when - hoo - zen Note that there are no accent marks given; my best guess is that they would fall on the second to last syllable in each case. This is also most likely the wrong pronunciation in any case. So how did I do? Did I get anywhere close? :-) close but not quite: nienhuys = 'neen huh-iss nieuwenhuizen = 'nee wunn huh-izz zunn (where huh-i is a monosyllabic dipthong, so slide from uh to ih smoothly.) -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: music definition change in 2.9.9 or thereabouts?
On Tuesday 20 June 2006 12:59, Han-Wen Nienhuys wrote:
> Erik Sandberg schreef:
> > I'm not quite sure what the proper solution is. The attached patch solves
> > the problem by renaming EVENT_IDENTIFIER to ARTICULATION_IDENTIFIER. The
> > solution is easy and it works AFAICT, but it relies on music-classes,
> > whose fate is uncertain. I did consider the following solutions as well:
> > 1. Extend identifier-smob with type information (typically corresponding
> > to the return value of try_special_idetifiers). I think this will only
> > move the problem, because expressions like foo = #... must still be
> > assigned a type correctly.
> > 2. unify MUSIC_IDENTIFIER with EVENT_IDENTIFIER. This has one problem:
> > someone will try
> > foo = -.
> > { c2\foo d2 }
> > which (AFAICT) will put the dot above the d2
> > 3. Whenever a variable is assigned music, wrap it in a dummy
> > sequential_music. Unclean.
>
> Isn't it much easier to remove event from 'types for KeyChangeEvent (and
> rename to KeyChange ?). KeyChange remains an odd event; it should really
> be a property set for keySignature.
No. The underlying problem is that we now allow events that aren't wrapped in
event-chords. So the following:
foo = c4
could make foo contain a NoteEvent directly. (I think it currently wraps the
note in an EventChord, but I plan to change that). The problem is that
variables that contain events directly, can currently only be used as
articulations.
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book questions
At Mon, 19 Jun 2006 21:21:07 -0700,
Graham Percival <[EMAIL PROTECTED]> wrote:
> > How can I superscript text, like footnotemarkers, in lyrics mode?
> > Footnotemarkers are part of Unicode, but they should be superscripted
> > to improve the output. Alternatively, I guess one can use the
> > superscripted numbers in Unicode, but that is not the same, and is not
> > generic either. This illustrates the gap that has opened without TeX
> > backend.
>
> There are \super and IIRC \sub commands in \markup{} mode now. See
> "Overview of text markup commands".
Do you mean that \markup is useful in lyrics mode? I am under the
impression it's for in-staff annotations.
Thanks,
Marcus
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
shape notes
Dear Lilypond users, Somehow the SacredHarpHeads have gotten very small in 2.8. The regular notehead (the one called #f in property-init.ly) is normally sized, of course, so one can't simply globally adjust notehead size or one ends up with big fat "sol" noteheads. Is there a way to get the shaped heads to normal size while leaving the standard #f head as it is? BTW, the sequence of shapes for the Sacred Harp four-shape system is still wrong in property-init.ly. In property-init.ly it goes : (#f #f mi #f fa la #f) But it *should* go (fa #f la fa #f la mi). That's the Sacred Harp system. What lilypond has goes "sol sol mi sol fa la sol." Very funny scale, that. Muchas Gracias. Fr. P ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
DYI \chordcombine
I've been wanting something like \chordcombine, i.e. combine multiple voices into chords if they occur at the same time and same duration (possible edge cases not taken into account right now)How hard would it be to put together something like that myself, (a person knowing close to nothing about scheme, but programmer by profession). That is, is it feasible, or should I just forget it right away?regards,Simon ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: shape notes
Monk Panteleimon wrote: Dear Lilypond users, Somehow the SacredHarpHeads have gotten very small in 2.8. The regular notehead (the one called #f in property-init.ly) is normally sized, of course, so one can't simply globally adjust notehead size or one ends up with big fat "sol" noteheads. Is there a way to get the shaped heads to normal size while leaving the standard #f head as it is? BTW, the sequence of shapes for the Sacred Harp four-shape system is still wrong in property-init.ly. In property-init.ly it goes : (#f #f mi #f fa la #f) But it *should* go (fa #f la fa #f la mi). That's the Sacred Harp system. What lilypond has goes "sol sol mi sol fa la sol." Very funny scale, that. Muchas Gracias. Fr. P I compile Lilypond instead of using GUB, and I apply the attached patch to make shape-notes wider. They are a bit narrower than 2.7, but considerably wider than 2.8. It would be nice if the width of the shaped heads could be tuned within a .ly file, but right now I don't have any disposable cash to make that happen. Both 4-shape and 8-shape scales have noteheads exactly as wide as the round noteheads in all published sources I can find. I can send scans if you like. An online example can be found here: http://www.ccel.org/s/southern_harmony/sharm/sharm/hymn/t=New+Britain.html --d diff -Naur lilypond-2.9.9/mf/feta-bolletjes.mf lilypond-2.9.9/mf/feta-bolletjes.mf --- lilypond-2.9.9/mf/feta-bolletjes.mf 2006-05-17 10:36:37.0 -0700 +++ lilypond-2.9.9/mf/feta-bolletjes.mf 2006-05-17 10:38:04.0 -0700 @@ -910,9 +910,9 @@ save solfa_base_notewidth; solfa_base_notewidth# := black_notehead_width#; -solfa_whole_width := whole_notehead_width# / black_notehead_width#; -solfa_half_width := half_notehead_width# / black_notehead_width#; -solfa_quarter_width := 1.0; +solfa_whole_width := 1.7; +solfa_half_width := 1.45; +solfa_quarter_width := 1.55; def draw_do_head (expr width_factor, dir) = save p_in, p_out; ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: shape notes
Great! This topic was brought up right in time. I was about to post one similar. In the past I had sent the attachment (shapednotesnew.pdf) to Han-Wen, and I would like to request some changes to the shaped notes design: -> The half-notes (minims) in many shaped notes songbooks have one or more sides that are thicker in order to match more with the style of the normal half note. -> I'd like to see the whole note (semibreve) the same size as the half note, like a stemless half note. This style is common in many songbooks, even in Southern Harmony. The normal semibreve in feta font has sizes that are too thick to be matched with the other shapes. So my suggestion would be to make it just like the normal half-note. This change should only happen, of course, when the score is in shaped notes, otherwise the semibreve should have the same (beautiful) design as usual. I'd like to sponsor these changes, if I can afford them, and if nobody is against it. Here's a link to an old shaped-note songbook page. Notice that the size of the semibreves (whole-notes) are just the same as the minims (half-note): http://digital.lib.msu.edu/collections/index.cfm?action=view&TitleID=607&Format=jpg&PageNum=45 And here is another link about shaped-notes that offer a True Type font with shaped notes. The design of the half notes are like the one I'm proposing: http://www.paperlesshymnal.com/shapnote/shaped.htm Regards, Eduardo - Original Message - From: "Daniel Johnson" <[EMAIL PROTECTED]> To: "Monk Panteleimon" <[EMAIL PROTECTED]> Cc: Sent: Tuesday, June 20, 2006 4:17 PM Subject: Re: shape notes > Monk Panteleimon wrote: >> Dear Lilypond users, >> >> Somehow the SacredHarpHeads have gotten very small in 2.8. The regular >> notehead (the one called #f in property-init.ly) is normally sized, of >> course, so one can't simply globally adjust notehead size or one ends up >> with big fat "sol" noteheads. Is there a way to get the shaped heads to >> normal size while leaving the standard #f head as it is? >> >> BTW, the sequence of shapes for the Sacred Harp four-shape system is still >> wrong in property-init.ly. In property-init.ly it goes : (#f #f mi #f fa la >> #f) >> But it *should* go (fa #f la fa #f la mi). That's the Sacred Harp system. >> What lilypond has goes "sol sol mi sol fa la sol." Very funny scale, that. >> >> Muchas Gracias. >> Fr. P >> > I compile Lilypond instead of using GUB, and I apply the attached patch > to make shape-notes wider. They are a bit narrower than 2.7, but > considerably wider than 2.8. It would be nice if the width of the > shaped heads could be tuned within a .ly file, but right now I don't > have any disposable cash to make that happen. > > Both 4-shape and 8-shape scales have noteheads exactly as wide as the > round noteheads in all published sources I can find. I can send scans > if you like. An online example can be found here: > http://www.ccel.org/s/southern_harmony/sharm/sharm/hymn/t=New+Britain.html > > --d > shapenotesnew.pdf Description: Arquivo anexado pelo iGmail ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: DYI \chordcombine
Simon Dahlbacka wrote: > How hard would it be to put together something like that myself, (a person > knowing close to nothing about scheme, but programmer by profession). > That is, is it feasible, or should I just forget it right away? It depends. If you can grok the functional programming paradigm of LISP and its variants (of which Scheme is one), then you shouldn't have too much difficulty figuring out what you need to do. :-) -- Shamus ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
