Still: Beaming
On Thu, 18 Mar 2004, Jan Nieuwenhuizen wrote: > Joerg Anders writes: > > > Or perhaps a pointer into the LilyPond C code ? > First of all: Thank you all who answered this question. > LilyPond uses rule based autobeaming, but it's far from perfect. It's > one of those things we'll have to Get Right (TM) some time. The rules > are listed in > >scm/auto-beam.scm > > and use time signature, position in measure and shortest note in beam. Very interesting! What happens if 2 rules match ? For instance in scm/auto-beam.scm: ((end * * 4 4) . ,(ly:make-moment 1 2)) ... ((end 1 16 4 4) . ,(ly:make-moment 1 4)) I made an attempt: The time signature is 4/4. I placed 16 16ths in 1st measure and and 8 8ths in 2nd measure. The 16ths are grouped: |--|--|--||--|--|--||--|--|--||--|--|--| |--|--|--||--|--|--||--|--|--||--|--|--| | | | || | | || | | || | | | | | | || | | || | | || | | | / / / // / / // / / // / / / i.e. according to 2nd rule (If I comprehended all right) The 8th are grouped: |---|---|---| |---|---|---| | | | | | | | | | | | | | | | | / / / / / / / / i.e. according to 1st rule (If I comprehended all right) Ok here is no problem because the 2nd rule does not match. But if I apply the 1st rule to 1st measure the result could be: |--|--|--|--|--|--|--| |--|--|--|--|--|--|--| |--|--|--|--|--|--|--| |--|--|--|--|--|--|--| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | / / / / / / / / / / / / / / / / What's the rule over rules ? a.) The last matching rules is applied ? b.) The most precise rule is applied ? -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED]) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Still: Beaming
Joerg Anders writes: > What happens if 2 rules match ? > > For instance in scm/auto-beam.scm: > > ((end * * 4 4) . ,(ly:make-moment 1 2)) > ... > ((end 1 16 4 4) . ,(ly:make-moment 1 4)) The most specific wins, in this case 1 16 4 4) > What's the rule over rules ? > > a.) The last matching rules is applied ? > > b.) The most precise rule is applied ? b.) Btw, if you find something better, you'll let us know, right? Jan. see lily/auto-beam-engraver.cc: /* Determine end moment for auto beaming (or begin moment, but mostly 0==anywhere) In order of increasing priority: i. begin anywhere, end at every beat ii. end * iii. end iv. end * * * v. end* * Rationale: [to be defined in config file] i. easy catch-all rule ii. exceptions for time signature iii. exceptions for time signature, for specific duration type [user override] iv. generic override v. override for specific duration type */ -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
augmentation dot
Hello list, I need to move an augmentation dot horizontally or vertically in a polyphonic situation to avoid collision with a notehead in another voice, but cannot find the appropriate command(s). \dotsUp does not help. Something like: \override Dot #'positions = #'(0.5 . 0.5) ? Thomas cygwin 2.1.28 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Still just a bit stumped.
Thanks for the assistance with my chart thus far; now I have two questions
remaining.
1. How can I increase the legibility of the chart by expanding staff sizes,
etc., especially the chord names? Jazz players would no doubt appreciate
much thicker chord symbols.
2. I'm still getting a funny "tail" on slash noteheads. How do I fix?
Source code follows:
\header {
title = "Monkeystump, the Drifter"
composer = "S L Raymond"
pagenumber = "no"
tagline = " "
}
changes = \chords {r1 c:7 r r r bes:7 r r a:9+ g:7 f:7 es:7}
\score {
\notes <<
\context ChordNames {
\property ChordNames.chordChanges = ##t
\transpose c d \changes
}
\context Staff = one \relative d'' {
\property Staff.instrument = #"Tenor Sax"
\key d \major
\time 4/4
\clef treble
\skip 2
a8 c e d
\repeat volta 2 {
r1
r2 r4 b'4
c8 dis,8 e g b a r8 fis
r8 g,4. bes4 d8 c~
c1
r2 r8 e8 g a
bes a g f e d r8 g~
g4 r4 d8 c b a
r8
\property Voice.TextScript\override #'padding = #1
a_\markup "Last Time: repeat final 4 bars" b c cis a'
aes g~
g2 b,8 d g f~
f1~
f1
}
}
\new ChordNames {
\property ChordNames.chordChanges = ##t
\changes
}
\new Staff {
\property Staff.instrument = #"Bass"
\key c \major
\clef bass
\skip 2
r2
r8 c8^\accent~ c4 ~ c2~
c1~
c1~
c2 r2
r4. bes,8^\accent~ bes,2~
bes,1~
bes,1
a,2
\property Voice.NoteHead \override #'style = #'slash
\property Voice.Stem \override #'length = #0 d4 d
d d d d
d d d d
d d d d
d d d d
\property Voice.NoteHead \revert #'style
\property Voice.Stem \revert #'length
}
>>
\paper{ }
\midi{ }
}
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Ack: Beaming
On Fri, 19 Mar 2004, Jan Nieuwenhuizen wrote: > > Btw, if you find something better, you'll let us know, right? I'm very sorry about I cannot make any contributions! I really wanted to learn something from LilyPond. I want better beaming in NoteEdit but I never was at music school. And I've seen in other mailing lists: Beaming is a big topic and also a matter of controversy. And I also got some critical mails about the situation in NoteEdit. Thank you again! BTW: I'm afraid I cannot implement such a modular mechanism as LilyPond has, because I have stronger timing restrictions. -- J.Anders, Chemnitz, GERMANY ([EMAIL PROTECTED]) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Still just a bit stumped.
> "Lyle" == Lyle Raymond <[EMAIL PROTECTED]> writes:
Lyle> Thanks for the assistance with my chart thus far; now I have
Lyle> two questions remaining.
Lyle> 1. How can I increase the legibility of the chart by
Lyle> expanding staff sizes, etc., especially the chord names? Jazz
Lyle> players would no doubt appreciate much thicker chord symbols.
I use this wth lily 1.6:
\paper {
\translator {
\ChordNamesContext
ChordName \override #'style = #'jazz
ChordName \override #'word-space = #2
ChordName \override #'font-series = #'bold
ChordName \override #'font-family = #'roman
}
}
--
Laurent MartelliJB Arban's trumpet method online
[EMAIL PROTECTED] `--> http://arban.bearteam.org/
Jazz tunes > http://partoches.bearteam.org/#jazz
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Lilypond-book and different versions of Lilypond
I'm writing something like a book of cello exercises, with a lot of short music fragments and some text. I find a combination of LaTeX and Lilypond-book a perfect tool for my work, at least in theory. However, there are some problems in practice. Using Lilypond version 2.0.1 with Fedora Core 1 Linux, I have produced more than 200 pages of output so far. It looks quite nice, but not perfect, as you can see from this sample: http://razor.arnes.si/~bkuzma1/lily/romberg-fedora2-0-1.ps . Beside the fact that the default staff size is a bit small, there are two very bothering things: - unacceptable collision among fingering marks and slurs - wrong font for fingering marks in smaller staffs. I knew 2.1.x versions improved Lilypond's output in several ways, but as my files might be incompatible, I hesitated to update my Lily at first. Now I've installed the latest Lilypond 2.1.28 Cygwin package in Windows, keeping the untouched 2.0.1 version running in Linux. Of course, when I tried to process my files with the new version, there were many problems. For instance, lilypond-book send many compatibility warnings and even stopped in the middle of processing longer files (was this a cygwin or a lilypond problem?). Finally I've isolated the same sample page as before. After succesful lily-book processing, I ignored some errors at latex processing to get this:http://razor.arnes.si/~bkuzma1/lily/romberg-cygwin2-2-28.ps. You can see in the new sample: - the default staff size is bigger (and actualy looks much better), - fingering marks have proper font in all staves (which is also good), - some linebreaks got lost (which is bad, but can probably be easily repaired), - width of fragments is totally wrong (why?), - the collision among fingering marks and slurs isn't any better as before, The questions I have are the following: - Was the "wrong font for fingering in small staff sizes" just a 2.0.1 bug, which is now fixed? - Is there a way to avoid the collision among fingering marks and slurs? Does it depend on version I use? - I know it is possible to tell lilypond to process .ly files as version 2.0.1. Can I also tell lilypond-book to process everything in a file as 2.0.1 version, and get the same output as before? - Were the errors in latex processing caused because of incompatibility of Linux and Cygwin TeTeX packages, or is something wrong with lilypond-book? If anyone wants to play around with the input file to suggest me some other improvements, here is http://razor.arnes.si/~bkuzma1/lily/romberg.tex . With regards from Slovenia, Bostjan Kuzman ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Move augmentation dot
Hello list, I need to move an augmentation dot horizontally or vertically in a polyphonic situation to avoid collision with a notehead in another voice, but cannot find the appropriate command(s). \dotsUp does not help. Something like: \override Dot #'positions = #'(0.5 . 0.5) ? Thomas cygwin 2.1.28 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book and different versions of Lilypond
Have you seen lilypond --help? It says you can use this: lilypond-book --filter="convert-ly --no-version --from=2.0.0 -" BOOK Do you not need this? Bert ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book and different versions of Lilypond
[EMAIL PROTECTED] writes: > Have you seen lilypond --help? > > It says you can use this: > >lilypond-book --filter="convert-ly --no-version --from=2.0.0 -" BOOK > > Do you not need this? That actually doesn't work due to some refactoring of the code. You can simply use convert-ly -n --from=2.0.0 --to=2.1.30 BOOK -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: \acciaccatura creates nonsense
On Thursday 18 March 2004 22:38, you wrote:
> As a follow-up to my previous post, you can fix it with this:
>
>
> lower = \new Voice \notes\relative f'' {
> \clef treble \key b \major \time 4/4
> 2 2 | etc.
>
> lower = \new Voice \notes\relative f'' {
> \clef treble \key b \major \time 4/4
> \grace s4 %% this is the fix
> 2 2 | etc.
>
> The line \grace s4 puts a spacer in the lower staff to line up the
> timings.
>
> -David
Many thanks, this works for me.
But this solution seems quite "hackish" to me, are there chances that the bug
will be fixed soon?
I work with Lilypond 2.0, but the bug message still is in the documentation of
2.1.
~michael
--
"Mailand oder Madrid - Hauptsache Italien!"
-Andreas Möller
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book and different versions of Lilypond
After some tweaking I've found that in 2.1.28:
- to add line breaks between fragments, I just add 2 empty lines in
input file,
- to avoid some latex-processing errors, all I had to do was to replace
the old "11pt" option in \begin[11pt]{lilypond} with "staffwidth=11".
This is quite weird, because now also my national characters print well
and I don't see how this can be connected.
- to get a natural fragment width, I have to use
\begin[raggedright]{lilypond} or drop out \score{ }.
However, longer fragments are not splitted in several lines automaticaly
anymore (as in 2.0.1) unless I specify "linewidth=160". How can I fix
this?
Also, how can I force lilypond (2.1.28) to use page width as linewidth
with shorter fragments without specifying the exact width?
- Regarding documentation: I think there is a mistake in the manual
(v2.1) at "6.4. Music fragment options".
Lilypond-book fails to process the file if I use "indent=\\10mm" (as in
example) or "indent=10\\mm" (as in explanation) option, while
"indent=10" goes through, making indent of 10mm. Also, I dont really
understand what "fragment/nofragment" options are used for. I can't
notice any change using either or none.
- For the next version of lilypond-book, I would also suggest some other
fragment options like "nobars", "nobarnumbers", "no key" or "plain" (no
time, key and barlines).
Bostjan.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book and different versions of Lilypond
Thanks, this will come handy. However, this conversion doesn't replace
"11pt" option with "staffwidth=11".
If I keep "11pt" in the code, I get several warnings from lilypond-book
and on running latex I get this:
LaTeX error: missing \begin{document}
l.1 ^^ef
^^bf^^\documentclass[a4paper]{article}
If I ignore this error, the file is then processed with music printed
correctly, but I get an empty page at the begining of my document.
Weird, but not a big problem though, as I can easily replace "11pt".
Bostjan.
-Original Message-
From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 5:08 PM
To: Bertalan Fodor
Cc: 'Bostjan Kuzman'; [EMAIL PROTECTED]
Subject: RE: Lilypond-book and different versions of Lilypond
[EMAIL PROTECTED] writes:
> Have you seen lilypond --help?
>
> It says you can use this:
>
>lilypond-book --filter="convert-ly --no-version --from=2.0.0 -"
> BOOK
>
> Do you not need this?
That actually doesn't work due to some refactoring of the code. You can
simply use
convert-ly -n --from=2.0.0 --to=2.1.30 BOOK
--
Han-Wen Nienhuys | [EMAIL PROTECTED] |
http://www.xs4all.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: EasyNotation in german
Hello list, hello Paul, You wrote > Roland Goretzki wrote: > >>>In which file could I change the names for the easy-notation-note-names? > >>in lily/note-head.cc! > >This file is not to find on my machine. > > > He was joking. That's why he said "seriously" below. That is one of > the source files for Lilypond. He meant you would have to modify > Lilypond to fix this which he has already done in the next version. Okay, thank You. That's really not what I want to ... ;-) At this point I use the time to say, how great I find this program lilypond, and how much I admire the work of the lilypond-programmers. My congratulation! :-) > Yes, you will have to get the latest version as soon as it's ready. > It should be version 2.1.32. Thank You. > This page should tell when your Mac version is ready unless it gets > announced here first: > http://lilypond.org/web/download/#2.1 Oh, on my machine is running debian (unstable). But I hope the version number will be the same and to get under: http://www.pedrokroeger.net/lilypond/ Is this correct? RegardsRoland ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Anomolies in 2.1.31.hwn1
I'm getting some strange results with v2.1.31.hwn1. Some short ties are showing rather more "arcing" than before. This appears to be affecting short ties between down stem notes but not up stem notes. Also, in one case, I have a tie between two down stem notes across a bar line where the tie is nearly flat, but it *slightly* bowed DOWNWARD. The opposite direction it should be. These things are happening in a score. In one "extracted" part I'm getting displaced elements. There are measure rest numbers set way off to one side. In another case there is a half or whole rest floating between systems (there is no short staff line attached to it). I tried 'clean-fonts' thinking it was a font update problem. Same results. I have not yet been able to reproduce this with a small file or I would have included one. I'll try to do so. I did get this at the end of the run just before the output: programming error: Stencil::move_to_edge: adding empty stencil. (Continuing; crossing fingers) programming error: Improbable offset for translation: setting to zero (Continuing; crossing fingers) -David ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Lilypond-book with Cygwin & Jedit
1) How can I configure JEdit to run lilypond-book => latex => dvips with a single click? 2) I noticed 2 minor mistakes in score setup wizard: - in "strings" section there are two violas named and no cello. - the wizard creates "\property" instead of "\set" Thank you for your great tool. Bostjan ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: augmentation dot
Hello list, hello Thomas, You wrote: > \dotsUp does not help. > Something like: > > \override Dot #'positions = #'(0.5 . 0.5) > > ? I was immediately interested, and with a little bit playing I found this solution: \override Staff.Dots #'extra-offset = #'(0.5 . 0.5) Hope it will help. ;-) Regards Roland ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Warning - Virus detected in email
Our viruschecker detected a virus in your email sent to [SMTP:[EMAIL PROTECTED] The email was cleaned. Please check your system for viruses. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book with Cygwin & Jedit
I don't have much time to work on lily4jedit in these days, but I can tell
you that many new features can be achieved by using just jEdit's features.
> 1 ) How can I configure JEdit to run lilypond-book => latex => dvips with
a single click?
That's a good question :-)
It's not so hard, but not so easy.
If you download the Console plugin, it enables you to edit commando files,
which then can be used to run commands. (Details are in its documentation)
Now I wrote a commando file that should do the trick I think (it's not one
click - but not so much). It is assumed that the extension of your file is
lytex. (Which is a quite good convention I think.)
lilypond-book.xml (put this in c:\Documents and
Settings\YOURNAME\.jedit\console\commando and use the
Plugins->Console->lilypond-book (after rescanning))
buf = new StringBuffer("C:\\cygwin\\bin\\bash.exe --login -c \"cd
`cygpath -au ");
String fileNoExt=filePath.replaceAll(".lytex$","");
fileNoExt=fileNoExt.replaceAll("","/");
buf.append(buffer.getDirectory().replaceAll("","/"));
buf.append(" ` ; lilypond-book ` cygpath -au ");
buf.append(filePath.replaceAll("","/"));
buf.append(" ` ; latex `cygpath -au ");
buf.append(fileNoExt+".tex");
buf.append(" ` ; dvips -ta4 -Ppdf -u +lilypond.map `cygpath -au ");
buf.append(fileNoExt+".dvi");
buf.append(" `\"");
buf;
> 2) I noticed 2 minor mistakes in score setup wizard:
> - in "strings" section there are two violas named and no cello.
Thanks, I will fix this.
> - the wizard creates "\property" instead of "\set"
That's true, because the wizard creates 2.1.11 code. After the wizard run
Document->Convert to current version.
Regards,
Bert
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: EasyNotation in german
Roland Goretzki wrote: This page should tell when your Mac version is ready unless it gets announced here first: http://lilypond.org/web/download/#2.1 Oh, on my machine is running debian (unstable). I just saw Mac in one of your earlier posts. I also run Debian unstable. But I hope the version number will be the same and to get under: http://www.pedrokroeger.net/lilypond/ Is this correct? Yes and Ferenc Wagner's packages work just as well on unstable. I go back and forth depending which one finishes the packages first and on little packaging problems that sometimes happen. Paul ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: Lilypond-book with Cygwin & Jedit - update
I modified it a bit (to not assume anything about extension).
And it seems that if you click on View PS, you can view the book as well :-)
So long time was I waiting for this commando file :-) Thank you for your
suggestion!
buf = new StringBuffer("C:\\cygwin\\bin\\bash.exe --login -c \"cd
`cygpath -au ");
String fileNoExt=MiscUtilities.getFileNameNoExtension(filePath);
fileNoExt=fileNoExt.replaceAll("","/");
buf.append(buffer.getDirectory().replaceAll("","/"));
buf.append(" ` ; lilypond-book ` cygpath -au ");
buf.append(filePath.replaceAll("","/"));
buf.append(" ` ; latex `cygpath -au ");
buf.append(fileNoExt+".tex");
buf.append(" ` ; dvips -ta4 -Ppdf -u +lilypond.map `cygpath -au ");
buf.append(fileNoExt+".dvi");
buf.append(" `\"");
buf;
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Anomolies in 2.1.31.hwn1
[EMAIL PROTECTED] writes: > I'm getting some strange results with v2.1.31.hwn1. > > Some short ties are showing rather more "arcing" than before. This > appears to be affecting short ties between down stem notes but not up > stem notes. Also, in one case, I have a tie between two down stem notes > across a bar line where the tie is nearly flat, but it *slightly* bowed > DOWNWARD. The opposite direction it should be. These things are > happening in a score. In one "extracted" part I'm getting displaced > elements. There are measure rest numbers set way off to one side. In > another case there is a half or whole rest floating between systems > (there is no short staff line attached to it). I tried 'clean-fonts' > thinking it was a font update problem. Same results. I have not yet > been able to reproduce this with a small file or I would have included > one. I'll try to do so. Jan has been doing some heavy stuff, but everything should be working again now. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Chord Names set at different heights?
On 3/19/04 1:15 AM, "Edward Sanford Sutton, III" <[EMAIL PROTECTED]> wrote: > On Thursday March 18 2004 20:57, Walter Hofmeister wrote: >> On 3/18/04 11:23 AM, "Bertalan Fodor" <[EMAIL PROTECTED]> wrote: >>> I think the question is to achieve something like this: >>> >>> >>> G >>> C F -o- -o- C >>> >>> o-o--o-- >>> --o- >>> o-o- >>> >>> >>> If you have a high note (or some lyrics for only some notes above the >>> staff) the whole line of chords is shifted up to be in one line, like >>> this: >>> >>> C F G C >>> hel-lo >>>-o- -o- >>> >>> o-o--o-- >>> --o- >>> o-o- >>> >> >> Actually, I want them all in a line like example 2. If the notes are above >> the staff, more clearance is required so that the chord names do not >> collide with the notes. To accomplish this it is necessary to increase the >> height of the chord names. But if on another line the notes are not so high >> on the staff, the higher chord names will look odd because now there is a >> lot of clearance between the staff and the chord names. >> >> >> >> C F G C >> -o- -o- >> --- >> --o-o-- >> --o-o-- >> --o-o-- >> --- >> >> This is OK. >> >> C F G C >> >> >> --- >> -o- >> -o-oo-- >> ---o---o--o---o >> -o--o-- >> >> This looks odd. >> >> My question is: is there a way so that the first example can get the extra >> clearance needed but also can the chord names in the second example be set >> lower or closer to the staff? I am assuming that both these settings are in >> the same .ly file. >> > > Staff.minimumVerticalExtent (as Mats Bengtsson stated) should be the > adjustment that you care to play with. LilyPond by default does the following > like you want; Staff.minimumVerticalExtent lets you control how much space it > makes for the chords to begin with. > > Hi Edward, I have played with Staff.minimumVerticalExtent and it seems to change the height of the chord names for the whole file. Even when I have several places in the source file where I set \set Staff.minimumVerticalExtent = #'(-6 . 6) or other settings, the largest amount of space is always the one that gets used. If you or anyone else are aware of a way to set this to different amounts for different systems I would be interested in knowing how. Walter ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Chord Names set at different heights?
On 3/19/04 10:13 PM, "Walter Hofmeister" <[EMAIL PROTECTED]> wrote: > On 3/19/04 1:15 AM, "Edward Sanford Sutton, III" <[EMAIL PROTECTED]> wrote: > >> On Thursday March 18 2004 20:57, Walter Hofmeister wrote: >>> On 3/18/04 11:23 AM, "Bertalan Fodor" <[EMAIL PROTECTED]> wrote: I think the question is to achieve something like this: G C F -o- -o- C o-o--o-- --o- o-o- If you have a high note (or some lyrics for only some notes above the staff) the whole line of chords is shifted up to be in one line, like this: C F G C hel-lo -o- -o- o-o--o-- --o- o-o- >>> >>> Actually, I want them all in a line like example 2. If the notes are above >>> the staff, more clearance is required so that the chord names do not >>> collide with the notes. To accomplish this it is necessary to increase the >>> height of the chord names. But if on another line the notes are not so high >>> on the staff, the higher chord names will look odd because now there is a >>> lot of clearance between the staff and the chord names. >>> >>> >>> >>> C F G C >>> -o- -o- >>> --- >>> --o-o-- >>> --o-o-- >>> --o-o-- >>> --- >>> >>> This is OK. >>> >>> C F G C >>> >>> >>> --- >>> -o- >>> -o-oo-- >>> ---o---o--o---o >>> -o--o-- >>> >>> This looks odd. >>> >>> My question is: is there a way so that the first example can get the extra >>> clearance needed but also can the chord names in the second example be set >>> lower or closer to the staff? I am assuming that both these settings are in >>> the same .ly file. >>> >> >> Staff.minimumVerticalExtent (as Mats Bengtsson stated) should be the >> adjustment that you care to play with. LilyPond by default does the following >> like you want; Staff.minimumVerticalExtent lets you control how much space it >> makes for the chords to begin with. >> >> > Hi Edward, > I have played with Staff.minimumVerticalExtent and it seems to change > the height of the chord names for the whole file. Even when I have several > places in the source file where I set \set Staff.minimumVerticalExtent = > #'(-6 . 6) or other settings, the largest amount of space is always the one > that gets used. If you or anyone else are aware of a way to set this to > different amounts for different systems I would be interested in knowing > how. > > Walter > I checked my output again and it appears that the chord name heights do vary. Sorry for the trouble. It does seem that in my example the top voice on the staff has the stems pointing up and when there is a beam, the chord names do almost touch the beams. Please see my original post as this did contain the .ly file pasted into it. walter ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Lilypond 2.1.31 packaged for cygwin
Cygwin binary packages of LilyPond 2.1.31 are available from my homepage. The package can be installed by adding and selecting my homepage as mirror: http://www.inf.bme.hu/~berti/lilypond Greetings, Bert ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
