Re: Even and odd page-margins
Hi Han-Wen, Gianluca,I don't know if anybody else is going to help sponsoring the mirrored-margins feature, but you can add me to the list for EUR 15.Best regards,Bart Kummel, Hilversum, The Netherlands On 5/26/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Gianluca D. schreef:> Hi everybody!> I'd like to ask if anyone knows a way to set different margins for odd and> even pages with Lilypond. I've tried to find some information from the manual> of boh 2.8 and 2.9 version, but I couldn't find anything.> I wouldn't like to use lilypond-book to achieve my goal, because I think it> would be a waste of resources to use two different programs to obtain a> simple thing like this. > I'd be also interested in sponsoring this feature, eventually.Hello!I can add this for 65 EUR.> Another feature I'd like to see in lilypond is a set of properties for the> first page of a score, or the page with title- something like > "first-page-between-system-space" or "first-page-top-margin"; actually, the> first page usually needs specific tuning, which are often not suitable for> the rest of the score- so I've thought it would be pretty nice to have > specific settings for the "title-page". I would be interested in sponsoring> this feature too.I can add code to override all relevant page dimensions for the firstpage only, for 130 EUR. Cheers,--Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwenLilyPond Software Design -- Code for Music Notationhttp://www.lilypond-design.com___lilypond-user mailing list lilypond-user@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: More Figured Bass Improvements... (potential sponsorship)
- Original Message -
From: "Han-Wen Nienhuys" <[EMAIL PROTECTED]>
To: "Trent Johnston" <[EMAIL PROTECTED]>
Cc:
Sent: Saturday, May 27, 2006 3:30 AM
Subject: Re: More Figured Bass Improvements... (potential sponsorship)
| Trent Johnston schreef:
| > Hi Han-Wen and Lilyponders,
| >
| > I am looking at the potential to sponsor more changes to the figured
bass
| > system. While the figured bass system is comphrehensive and looks good
it's
| > placement within a score that needs adjusting. There is often a wide a
gap
| > between the staff and the figures when using the current system (the
case
| > whether the figures are placed below or above the staff). I guess this
is
| > the mixture of both the minimum-Y-extent of the bass staff and the
figured
| > bass line.
| >
| > What I'm looking at sponsoring is changing the figured bass system so
that
| > the figures are closer to the notes. That instead of placing the figures
in
| > one line aligned above the highest note or lowest note that the figures
will
| > change height according to the notes in the score. i.e. figures are
placed
| > closer to the bass part and their heights change on a note by note
basis. I
| > know Nicholas Sceaux has an alternative figured-bass scheme that
positions a
| > figure in relation to the note that it is associated with. While this is
a
| > good alternative it doesn't have the extender lines of the new system.
| >
| > Could the two system be possibly put together?
| >
| > Or maybe way where the figures are placed close to the top line or
bottom
| > line depending on which way there user wants and the user can define
padding
| > for the individual or groups of figures that need to changed?
| >
| > Ideally the second option would be good as this would give the user more
| > control over the system.
|
| Hello,
|
| I think I know a good solution to this: I can make another engraver,
| which positions a consecutive range of figured bass numbers (created by
| the current engraver) above or below a staff. By putting it in the
| Staff context, the vertical alignment can react to individual notes.
|
| The syntax for this would be similar to
|
|
|theFigures = \figuremode { }
|\new Staff \with {
| \consists Figured_bass_side_engraver
|} <<
| \new Voice \with {
| \consists Figured_bass_engraver
| } <<
| \theBassMelody
| \theFigures
| >>
|>>
|
| where theFigures and theBassMelody contain the figures and the bass line
| respectively.
|
| I can do this for 130 EUR.
|
| > Also I was looking at making the numbers 10 / 11 / 12 as one symbol.
This
| > would make the numbers as in:
|
| > 10
| > 5
| > 3
| >
| > centred in the group rather than left aligned.
|
| I can add a property which specifies the alignment of individual
| figures, I can do this for 20 EUR. For completeness, I need to know how
| you want those numbers aligned when there are alterations.
|
| (Or, if you're clever with markups and Scheme, you can have a try
| yourself, see format-bass-figure in translation-functions.scm)
|
| --
|
| Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
|
| LilyPond Software Design
| -- Code for Music Notation
| http://www.lilypond-design.com
|
Hi Han-Wen,
That sounds great. I would love to sponsor both features: the figured bass
as well as the alignment of individual figures.
I'm assuming that the figures 10 / 11 / 12 etc would be centered instead of
left alined like the other figures.
Could we also put a blank figure in... this would be good to help with using
extenders etc.
I've included two diagrams one "01Figures" shows a possibility if there is
no blank figure. The figure is just above the line because the bass note is
within the staff but when the continuation lines end there is a f above the
line which could possibily mean that the lines would run through the f.
"02Figure" shows the ideal is that the figures are raised because the
continuation line ends on the f.
so a coding of <__ 5 6> <__ 5 6> 'double underscore' as a blank figure or
possibly <__ __ 5 6> <__ __ 5 6> so raise the figures higher.
Or could this be done automatically?
Anyway I leave it up to you as to what is easier and more effective.
Thanks,
Trent
02Figures.PNG
Description: PNG image
01Figures.PNG
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dotted phrasing slurs
Hi Fr. P,
Try this for the dotted phrasing slurs:
{
\slurDashed
c4( d e f)
\slurDotted
g4( a b c)
}
Can't help you on the slurs between lyrics, sorry.
Best,
Sean
___
Sean Reed
Hamburg, Germany
www.seanreed.de
On 26.05.2006, at 19:09, Monk Panteleimon wrote:
Dear friends,
How can I make a dotted phrasing slur? I have tried
\phrasingSlurDotted and
also several wild guesses beginning with \once \override Slur...
Using \slurDotted before a phrasing slur makes the next non-
phrasing slur to
be dotted. I looked in the user archive, but encountered only opacity.
Also, is it possible to have dotted slurs between lyrics (in order to
persuade people not to breath between specific words)?
Many thanks
Fr. P
___
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: dotted phrasing slurs
Hi again Fr. P. Sorry about that. Didn't help, did it? After fiddling with it a bit more, I see what you mean. Best, Sean ___ Sean Reed Hamburg, Germany www.seanreed.de On 26.05.2006, at 19:09, Monk Panteleimon wrote: Dear friends, How can I make a dotted phrasing slur? I have tried \phrasingSlurDotted and also several wild guesses beginning with \once \override Slur... Using \slurDotted before a phrasing slur makes the next non- phrasing slur to be dotted. I looked in the user archive, but encountered only opacity. Also, is it possible to have dotted slurs between lyrics (in order to persuade people not to breath between specific words)? Many thanks Fr. P ___ 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
Compiling lilypond files from Mutopia
Dear list, I would like to compile a Lilypond file downloaded from Mutopia. It needs an include file (paper-20.ly). Where can I get this? And does that define all the 'extra' syntax the .ly file seems to contain? Thanks, Peter C ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Windows font problem?
I am a new user to Lilypond, and can't get the titles or footers to appear correctly in the PDF output. Instead, it displays a series of "r"s and "p"s and commas. Even the Lilypond tagline at the bottom appears this way. I am using Windows. Did I install some font file incorrectly? Thanks for the help. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mixed questions
At 19:00 26-5-2006, Stephen wrote: The double bar-line followed by a repeat bar-line is significant for many. Every 32-bar song form of the Twentieth Century needs a double bar-line after the 4-bar intro and/or a double bar-line after the 16-bar verse, followed by a 32-bar chorus with repeats and an alternative. The slur on the repeat alternative is similiarly required for every poplular song. Someone must have solved this already. I have to say that this new example is nicely simplified. Stephen Well, yes, take any Nat King Cole/Cole Porter/Frank Sinatra/Gershwin etc. songbook, and you'll find abundant examples of that principle. As these songs are not yet to be found at Mutopia (for obvious reasons), there is a dearth of Lilypond-coded examples. I will be very grateful for any pointers. Matthijs ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Compiling lilypond files from Mutopia
On May 27, 2006, at 8:17 AM, Peter Clarke wrote: Dear list, I would like to compile a Lilypond file downloaded from Mutopia. It needs an include file (paper-20.ly). Where can I get this? And does that define all the 'extra' syntax the .ly file seems to contain? Thanks, Peter C Unfortunately, there is no simple way for the Mutopia maintainer (Chris Sawer) to update all the files with each new Lilypond version. I would suggest using the latest stable Lilypond version's convert-ly to update the file. If you can download one of the compiled binary Lilypond versions, use the "convert" function. Depending on how old is the Lilypond version of the Mutopia file, you may have to do some further editing. Regards, Stan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: dotted phrasing slurs
I think this would work for dotted phrasing-slurs if I knew what to put in
the blanks:
\once \override Slur #'(name of property) = #(name of variable)
That has worked with #'thickness on phrasing slur.
So can anyone fill in the blanks?
As for the slurs on lyrics, I read somewhere (by a 3rd party) that one can
insitute engravers in contexts where they don't belong by default. If I
understand correctly, that means I could put something in \layout{ \context{
\Lyrics } that would allow me to put a slur on lyrics.
Maybe I'll try putting them *under barlines (invisible if necessary).
XB,
Fr. P
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Automatic beaming
Hi,
I'm trying to get automatic beaming to do some work
for me... see attached example.
In bar 1 & 2, I've manually beamed the quavers
to how I'd like them.
I tried using the statement
#(override-auto-beam-setting '(end * * * *) 1 4) to do this automatically, but
it's not working.
Thanks,
Stewart
\version "2.8.0"
#(set-default-paper-size "a4" )
#(set-global-staff-size 20 )
\header
{
%Mutopia headers
mutopiatitle = "Recuerdos de la Alhambra"
mutopiacomposer = "F. Tárrega (1852-1909)"
mutopiainstrument = "Guitar"
source = "Orfeo Tracio Edition"
style = "Romantic"
copyright = "Public Domain"
maintainer = "Stewart Holmes"
lastupdated = "2006/May/26"
dedication = "Hommage á l'eminent artiste Alfred Cottin"
title = "Recuerdos de la Alhambra"
composer = "Francisco Tárrega (1852-1909)"
arranger = "Fingerings revised by Stewart Holmes"
copyright = "Public Domain"
}
top = \relative c
{
a32 e'' e e e, e' e e c e e e e, e' e e b d d d e, d' d d a,
c' c c e, c' c c |
% 2
a c c c e, c' c c b d d d e, d' d d a, e'' e e e, e' e e c
e e e e, e' e e |
% 3
c e e e e, e' e e a,, e'' e e e, e' e e c e e e e, e' e e d
f f f g, f' f f |
% 4
c, g'' g g g, g' g g e g g g e, g' g g d f f f g, f' f f c,
e' e e g, e' e e |
% 5
c e e e g, e' e e d f f f g, f' f f c, g'' g g g, g' g g e
g g g g, g' g g |
% 6
e g g g g, g' g g c,, g'' g g g, g' g g e g g g g, g' g g e
g g g g, g' g g |
% 7
f, c'' c c c, c' c c a c c c c, c' c c g b b b c, b' b b f,
a' a a c, a' a a |
% 8
f a a a c, a' a a d,, b'' b b f b b b e,,, a'' a a b, a' a4*21/256
b a4*22/256 e32 gis gis gis b, gis' gis gis |
% 9
e gis gis gis b, gis' gis gis e,, gis'' gis gis d gis gis gis
e gis gis gis d gis gis gis e gis gis gis d gis gis gis |
% 10
a,, ais'' ais ais cis, ais' ais ais e ais ais ais cis, ais'
ais ais e a a a cis, a' a a cis,, g'' g g a, g' g g |
% 11
e g g g a, g' g g f a a a a, a' a a d,, g' g g e g g4*21/256
a g4*22/256 d32 f f f a, f' f f |
% 12
d f f f a, f' f f d, f' f f a, f' f f d f f f a, f' f f d f
f f a, f' f f |
% 13
d, e' e e a, e' e e b e e e a, e' e e b d d d a d d d f,, c''
c c dis, c' c c |
% 14
a c c c dis, c' c c a d d d dis, d' d d e,, c'' c c e, c' c4*21/256
d c4*22/256 gis32 b b b e, b' b b |
% 15
gis b b b e, b' b b e,, b'' b b e, b' b b gis b b b e, b' b
b gis b b b e, b' b b |
% 16
a, e'' e e e, e' e e c e e e e, e' e e b d d d e, d' d d a,
c' c c e, c' c c |
% 17
a c c c e, c' c c b d d d e, d' d d a, e'' e e e, e' e e c
e e e e, e' e e |
% 18
c e e e e, e' e e a,, e'' e e e, e' e e c e e e e, e' e e d
f f f g, f' f f |
% 19
c, g'' g g g, g' g g e g g g e, g' g g d f f f g, f' f f c,
e' e e g, e' e e |
% 20
c e e e g, e' e e d f f f g, f' f f c, g'' g g g, g' g g e
g g g g, g' g g |
% 21
e g g g g, g' g g c,, g'' g g g, g' g g e g g g g, g' g g e
g g g g, g' g g |
% 22
f, c'' c c c, c' c c a c c c c, c' c c g b b b c, b' b b f,
a' a a c, a' a a |
% 23
f a a a c, a' a a d,, b'' b b f b b b e,,, a'' a a b, a' a4*21/256
b a4*22/256 e32 gis gis gis b, gis' gis gis |
% 24
e gis gis gis b, gis' gis gis e,, gis'' gis gis d gis gis gis
e gis gis gis d gis gis gis e gis gis gis d gis gis gis |
% 25
a,, ais'' ais ais cis, ais' ais ais e ais ais ais cis, ais'
ais ais e a a a cis, a' a a cis,, g'' g g a, g' g g |
% 26
e g g g a, g' g g f a a a a, a' a a d,, g' g g e g g4*21/256
a g4*22/256 d32 f f f a, f' f f |
% 27
d f f f a, f' f f d, f' f f a, f' f f d f f f a, f' f f d f
f f a, f' f f |
% 28
d, e' e e a, e' e e b e e e a, e' e e b d d d a d d d f,, c''
c c dis, c' c c |
% 29
a c c c dis, c' c c a d d d dis, d' d d e,, c'' c c e, c' c4*21/256
d c4*22/256 gis32 b b b e, b' b b |
% 30
gis b b b e, b' b b e,, b'' b b e, b' b b gis b b b e, b' b
b gis b b b e, b' b b |
% 31
a, e'' e e e, e' e e cis e e e e, e' e e b d d d e, d' d d
a, cis' cis cis e, cis' cis cis |
% 32
a cis cis cis e, cis' cis cis b d d d e, d' d d a, e'' e e
e, e' e e cis e e e e, e' e e |
% 33
cis e e e e, e' e e a,, e'' e e e, e' e e cis e e e e, e' e
e cis e e e e, e' e e |
% 34
a,, fis'' fis fis fis, fis' fis fis d fis fis fis fis, fis'
fis fis d fis fis fis fis, fis' fis fis a,, d'' d d d, d' d d |
% 35
b d d d d, d' d d d, fis fis fis fis, fis' fis fis a,, fis''
fis fis d fis fis4*21/256 gis fis4*22/256 cis32 e e e e, e' e
e |
% 36
cis e e e e, e' e e a,, e'' e e e, e' e e cis e e e e, e' e
e cis e e e e, e' e e |
% 37
fis,, a'' a a fis, a' a a a, a' a a cis, a' a a a, a' a a fis,
a' a a gis,, gis'' gis gis gis, gis' gis gis |
% 38
c, gis' gis gis dis gis gis gis c, dis dis dis gis, dis' dis
dis cis, fis' fis fis gis, fis' fis fis cis e e e gis, e' e e |
% 39
cis e e e gis, e' e e cis, e' e e gis, e' e e cis e e e gis,
e' e e cis e e e gis, e' e e |
% 40
b, d' d d f,
Re: lilypond-book fragment with ties/slurs continuing over the end of the fragment
Graham, thanks for your reply... I thought it was a trivial thing to do and that I overlooked something since it is a natural feature to expect for fragment-typesetting. Do you recommend turning over to the devel list? Lilypond is able to produce preview of the first system only using the -p (--preview) option, but I don't see how to use it with LaTeX and lilypond-book. It should be easy to implement, only using that interface, but the "python" code of lilypond-book scared me. Will post to devel, then. Regards, Vaclav Smilauer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automatic beaming
Hello list, hello Stewart,
convert-ly and the documentation say, that You can get what You want
with
\set Staff.beatLength = #(ly:make-moment 1 4)
instead of
#(override-auto-beam-setting '(end * * * *) 1 4)
But this doesn't seem to work, whereas the following does work:
\set Staff.beatLength = #(ly:make-moment 1 2)
You can try ... but You don't need ...
I'm quite sure this is a bug, and I wrote over this two times the last
week, but nobody seems to know an answer. So I was just thinking about
to send en e-mail again, as I saw Your question. :-)
The example You give is very long, so I put my ly-file with six differnt
very short examples (showing, what works, and what not works) in the
attachment.
Best Regards Roland
\version "2.8.2"
\layout { ragged-right = ##t }
% manual setting, this works:
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
\times 2/3 {
\repeat unfold 4 { f16 [ g a bes a g ] }
}
}
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
% not manual, setting the same to quarters doesn't work:
\set Voice.beatLength = #(ly:make-moment 1 4)
\times 2/3 {
\repeat unfold 4 { f16 g a bes a g }
}
}
\relative c' {
\set tupletSpannerDuration = #(ly:make-moment 1 8)
% not manual, setting the same to eight's does work:
\set Voice.beatLength = #(ly:make-moment 1 8)
\times 2/3 {
\repeat unfold 4 { f16 g a bes a g }
}
}
\relative c' {
% normal sixteenths do work for quarters:
\set Voice.beatLength = #(ly:make-moment 1 4)
\repeat unfold 4 { f16 g a bes }
}
\relative c' {
% normal 32's don't work for quarters:
\set Voice.beatLength = #(ly:make-moment 1 4)
\repeat unfold 4 { f32 g a bes }
}
% normal 32's do work for halfs:
\relative c' {
\set Voice.beatLength = #(ly:make-moment 1 2)
\repeat unfold 4 { f32 g a bes f g a bes }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Automatic beaming
Hmm... I think I may have misunderstood the documentation originally. If I use #(override-auto-beam-setting '(end * * * *) 1 4 'Staff) #(override-auto-beam-setting '(end * * * *) 1 2 'Staff) #(override-auto-beam-setting '(end * * * *) 3 4 'Staff) it works. The trick must be to define each point in the bar at which you want the beams to break. Stewart - Original Message - From: "Roland Goretzki" <[EMAIL PROTECTED]> To: Sent: Saturday, May 27, 2006 8:39 PM Subject: Re: Automatic beaming Hello list, hello Stewart, convert-ly and the documentation say, that You can get what You want with \set Staff.beatLength = #(ly:make-moment 1 4) instead of #(override-auto-beam-setting '(end * * * *) 1 4) But this doesn't seem to work, whereas the following does work: \set Staff.beatLength = #(ly:make-moment 1 2) You can try ... but You don't need ... I'm quite sure this is a bug, and I wrote over this two times the last week, but nobody seems to know an answer. So I was just thinking about to send en e-mail again, as I saw Your question. :-) The example You give is very long, so I put my ly-file with six differnt very short examples (showing, what works, and what not works) in the attachment. Best Regards Roland ___ 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
A new tie-bug?
Hi,
using 2.8.2 I found a bad looking tie-end after using \tieDown for
octaves in the bass (needed par example for the left hand in the first
Chopin study Op. 10, No. 1, because of many notes for the right hand have
to appear in the bass.
Attached a short example with comments.
Best Regards Roland
\version "2.8.2"
\layout { }
\relative c {
\clef bass
\tieDown
1 ~ \break
% The upper f at the beginning of the following line has a very bad
% tie-end:
~ \break
% The upper g at the beginning of the following line has a nice
% tie-end:
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: dotted phrasing slurs
On Sat, 2006-05-27 at 09:32 -0400, Monk Panteleimon wrote:
> I think this would work for dotted phrasing-slurs if I knew what to put in
> the blanks:
> \once \override Slur #'(name of property) = #(name of variable)
> That has worked with #'thickness on phrasing slur.
> So can anyone fill in the blanks?
There are two ways you can find this out (btw you want PhrasingSlur
instead of Slur). If you go to the top documentation page, then
-> Program Reference
-> Backend
-> All layout objects (this is a very useful page, you can look up all
your overrides from here)
-> PhrasingSlur
At the bottom of the page is a list of all the interfaces supported by
PhrasingSlur. In this case, the properties (you need 2 of them) you are
looking for are in slur-interface, so click on that link.
Then look in the list of User-settable properties.
The other way to find this out is to work out what slurDotted is defined
to be. The definition is in ly/property-init.ly in your lilypond
installation directory. You can then use the same definition, but with
PhrasingSlur instead of Slur.
>
> As for the slurs on lyrics, I read somewhere (by a 3rd party) that one can
> insitute engravers in contexts where they don't belong by default. If I
> understand correctly, that means I could put something in \layout{ \context{
> \Lyrics } that would allow me to put a slur on lyrics.
> Maybe I'll try putting them *under barlines (invisible if necessary).
>
> XB,
> Fr. P
>
>
>
> ___
> 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
