Re: InstrumentNames alignment
Sorry for the stupid question. I forgot that I can use \markup \right-align. Must have been a blackout. :-) Thomas ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
convert-ly
I came across a problem with convert-ly. I was trying to convert some 1.4 input files. Lilypond 1.4 obviously wasn't able to recongnize ties in the process of lyrics assignment, so you had to add one more _ in case of tied notes. Convert-ly is not able to address this issue, so the result is, one has to tediously search for such places and remove excess underscores. Is there any chance, this could be solved somehow in the future? Thanks Jan Janovcik __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: convert-ly
The easiest solution for you is probably to tell your current version of
LilyPond to also ignore ties when assigning lyrics to notes
(assuming that you use version 2.4.x now, always tell what version
you use to get a relevant answer):
\score{
...
\layout{
...
\context{
\Score
melismaBusyProperties = #'(melismaBusy slurMelismaBusy beamMelismaBusy)
}
}
}
The default definition can be found at
http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond-internals/Score.html
and some explanations can be found at
http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond-internals/Melisma_005ftranslator.html
/Mats
Jan Janovcik wrote:
I came across a problem with convert-ly. I was trying
to convert some 1.4 input files. Lilypond 1.4
obviously wasn't able to recongnize ties in the
process of lyrics assignment, so you had to add one
more _ in case of tied notes.
Convert-ly is not able to address this issue, so the
result is, one has to tediously search for such places
and remove excess underscores.
Is there any chance, this could be solved somehow in
the future?
Thanks
Jan Janovcik
__
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beams across repeat signs
Seems like a bug to me!
Example:
\version 2.4.2
\relative c' {
\repeat volta 2 {c d e16 f } e f g4 |
}
/Mats
Erik Ronström wrote:
According to the regression tests, LilyPond does not typeset beams
across manual repeat signs. That is true. However, it does place beams
across repeat-voltas, if the repeat sign is mid-bar. Is there a way to
avoid that without using manual beaming?
I use LilyPond 2.2.4.
I tried so search the list archives, but as someone already pointed
out, the search function doesn't appear to be working for the moment.
Regards
Erik Ronström
___
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 26, Issue 23
Just for the record, why do you prevent your xml file from being validated against the DTD ? Cheers, D. Joshua Koo wrote: Try http://www.recordare.com/dtds/partwise.html I still can access the server. Also after i installed the musicXml for finale plugin, a directory C:\MusicXML is created with lots of dtd and xsl. However, when I'm running xml2ly, i usually remove the doctype line eg. !DOCTYPE score-partwise PUBLIC -//Recordare//DTD MusicXML 0.6a Partwise//EN //D:/Program Files/MusicXML/partwise.dtd to prevent the xsl parser from validating the xml file. Joshua Date: Wed, 12 Jan 2005 13:37:41 +0100 From: [EMAIL PROTECTED] Subject: Music XML DTD or Schema To: lilypond-user@gnu.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=windows-1252 I decided I'd have a look at an improved MusicXML - Lilypond converter, but recordare's site seems to be down, no way for me to get the DTD or even better an XML Schema for MusicXML... Can anyone help ? Cheers, D. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson
[EMAIL PROTECTED] wrote:
I don't remember from the top of my head what version of LilyPond
you use. In version 2.2, it was possible to set the input and
font encoding using
\header{
fontencoding=...
inputencoding=...
}
That _was_ nice :), and let me do some tricks with latex intermediate
file, after willingly crashing lilypond by not defining the encoding and
using non-latin1 characters inside the piece :)
If you use version 2.4, don't spend too much energy on solving these
problems since a new solution is already (almost) implemented in
the latest development versions and it seems that the release of
the next stable version 2.6 is not in the very far future.
I found my solution (involving sed) after some struggle, and to avoid
that struggle
I proposed adding something to the docs, like an example
of what strange glyphs different people use in their own languages.
You may be sure that I will be one of the first people to try 2.6 utf
features :).
Of course if 2.6 is due in something like 1 month,
we can leave it, but if it's 6 months I would consider adding some hints or
expanding embedded TeX example.
to have a more generous example on TeX encoding for the use of
non-fully-latin alphabet
users ? And a clear remark, that one should probably not try to write
his/her
national characters normally (like latin2 encoding), or preprocess
the file to produce TeX
equivalents before running lilypond.
That's the part I feel is missing in 2.4 documentation - that if you really
want something in e.g. latin2 - use TeX encoding. I really have spent
lots of time getting my test files processed with no errors,
and seeing completely messy output afterwards, regardless
of defining
\header{
fontencoding=...
inputencoding=...
}
This applies to section 7.4.1 of the 2.4 documentation -
trying both cp1250 and latin2 for the inputencoding (Linux and Windows
install) , T1 for
fontencoding, general \encoding latin2 gave me only completely messy output,
the only usable encoding being TeX and writing the Polish glyphs
by \k{a}, \\'c and so on.
In my private mail I keep a discussion with two other Polih guys, who
hadn't ever managed
to get fontencoding and inputencoding working for version 2.4 and in
the same time
reporting that it works within 2.2.
For version 2.4 example of getting Polish glyphs follows:
---
\encoding TeX
\header{
title = \k{a}\\'c\k{e}\l\\'n\\'o\\'s\.z\\'zi
composer = \k{A}\\'C\k{E}\L\\'N\\'O\\'S\.Z\\'ZI
}
\transpose c c' {
{c d e f g a b c' cis' c d e f g a b c' cis' }
\addlyrics { \k{a} \\'c \k{e} \l \\'n \\'o \\'s \.z \\'z
\k{A} \\'C \k{E} \L \\'N \\'O \\'S \.Z \\'Z
}
}
-
This lets us use all the needed glyphs (and many others), but is far
from comfortable,
version 2.2 example with :
\header{
inputencoding = cp1250
fontencoding = T1
}
was reported to work perfectly, and used the encoding natural for windows
(latin2 for linux I suppose) .
In version 2.4.2
---
\header{
nputencoding = cp1250
fontencoding = T1
}
\transpose c c' {
{c}
\addlyrics { }
}
yields the following .log
---
This is TeXk, Version 3.14159 (Web2C 7.4.5) (format=latex 2005.1.13)
13 JAN 2005 11:40
%-line parsing enabled.
**\nonstopmode \input test.tex
(./test.tex (/usr/share/lilypond/2.4.2/tex/lilyponddefs.tex
\lytempdim=\dimen102
\outputscale=\dimen103
(/usr/share/lilypond/2.4.2/tex/lily-ps-defs.tex))
(/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 2001/04/21 v1.4e Standard LaTeX document class
(/usr/share/texmf/tex/latex/base/size10.clo
File: size10.clo 2001/04/21 v1.4e Standard LaTeX file (size option)
)
(...)
(/usr/share/texmf/tex/latex/base/inputenc.sty
Package: inputenc 2001/07/10 v0.99a Input encoding file
(/usr/share/texmf/tex/latex/base/latin1.def
File: latin1.def 2001/07/10 v0.99a Input encoding file
))
so it clearly tries to use latin1 encoding, where it shouldn't.
Shall we have an update like Non latin1 (or maybe just latin2) inputencodings
are deprecated in version 2.4, use TeX encoding and type the TeX
equivalents of your
national characters. If you do not feel comfortable with
TeX equivalents please do some preprocessing replacing the needed characters
by their TeX prefix represantation. in section 7.4.1 ?
Best regards, and thanks for Graham and Mats for their infinite will
of help.
Michal
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond pieces already entered
Hi!
Anybody have Bach's Little G-Minor? I think it's BWV# 1075 or something
like that . It would begin:
{
g'4 d'' bes'4. a'4 \bar |
g'8 bes' a' g' fis' a' d'4 \bar |
g'8 d' a' d' bes' a'16 g' a'8 d' \bar |
}
. . . etc.
If so,I would hope it could be compiled with 2.2.2, which is what I have.
Thanks
Gordon Gilbert
+=+
| Angels' Roost Farm |
| Rev. Dn. Gordon Gilbert Susan Gilbert |
| 705-549-5056 |
|[EMAIL PROTECTED] |
|[EMAIL PROTECTED] |
+=+
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
Micha Dwunik wrote:
On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson
[EMAIL PROTECTED] wrote:
I don't remember from the top of my head what version of LilyPond
you use. In version 2.2, it was possible to set the input and
font encoding using
\header{
fontencoding=...
inputencoding=...
}
That _was_ nice :), and let me do some tricks with latex intermediate
file, after willingly crashing lilypond by not defining the encoding and
using non-latin1 characters inside the piece :)
Did you see
http://lists.gnu.org/archive/html/lilypond-user/2003-08/msg00061.html
which shows how to specify the font that LilyPond uses for lyrics
(or other textual annotations) using the font-name property?
Again, this is something that works up to version 2.2 but probably
not longer.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Comment marks
Is it possible to comment out whole sections of your file? For example in
the process of trying something, would it work to comment out a whole
section of music or chords, or words like this?
%{
a b c d
d e f g
}
Would that whole thing not be processed as it is? or would it just choke
at the unmatched braces?
Gordon Gilbert
+=+
| Angels' Roost Farm |
| Rev. Dn. Gordon Gilbert Susan Gilbert |
| 705-549-5056 |
|[EMAIL PROTECTED] |
|[EMAIL PROTECTED] |
+=+
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Non-latin1 characters (was: Lyricsto skips notes with melisma's in 2.2)
On Thu, 13 Jan 2005 12:35:07 +0100, Mats Bengtsson
[EMAIL PROTECTED] wrote:
Micha Dwunik wrote:
On Wed, 12 Jan 2005 14:42:37 +0100, Mats Bengtsson
[EMAIL PROTECTED] wrote:
I don't remember from the top of my head what version of LilyPond
you use. In version 2.2, it was possible to set the input and
font encoding using
\header{
fontencoding=...
inputencoding=...
}
That _was_ nice :), and let me do some tricks with latex intermediate
file, after willingly crashing lilypond by not defining the encoding and
using non-latin1 characters inside the piece :)
Did you see
http://lists.gnu.org/archive/html/lilypond-user/2003-08/msg00061.html
which shows how to specify the font that LilyPond uses for lyrics
(or other textual annotations) using the font-name property?
Again, this is something that works up to version 2.2 but probably
not longer.
Yes. Instead of the hacks done by you for version from this thread
I invented something else, which included adding proper
inputencoding and fontencoding to the header of intermediate file,
together with font-substitution packages
like qtimes (that let me avoid looking into the font directory, which is not
my favourite, and in the same time utilize my, maybe small but existing, LaTeX
experience.
The output was very nice, but the way of dealing with the files was not so,
that's why I tried to move to version 2.4 and do +/- the same. I find
2.4 much more
comfortable with the small annoyance described before. Both 2.2 way and 2.4 way
is not something I would recommend to a fellow composer, but I hope
to be able to do so when 2.6 appears.
I admit, that I shouldn't pay to much attention to that and wait for 2.6,
but in the same time I would really like to avoid having to wait for 2.8,
because some working mechanism was discarded. (Please do not treat
it as doubting in lilypond developers, it's just a bitter experience from
some other GNU projects hunting for the ultimate solution, which is
always to come
in the next version).
Thanks for your help
Micha
PS:I feel like I'm saying the same thing for the n-th time, apologies
for the bored
PS2: We _want_ national characters, and if someone needs an example -
the difference between doing a favor and, err.. having oral intercourse
is only l or \l in TeX code
PS3:
http://www.lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Integrating-LaTeX-and-music.html
shows that even for 2.5 different encodings are usable, but very far from the
quality of the engraving itself, and that would be a pity to have perfect notes
with badly aligned text with shifts.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Comment marks
Search for comment in the Unified Index of the manual.
/Mats
Gordon Gilbert wrote:
Is it possible to comment out whole sections of your file? For example
in the process of trying something, would it work to comment out a whole
section of music or chords, or words like this?
%{
a b c d
d e f g
}
Would that whole thing not be processed as it is? or would it just
choke at the unmatched braces?
Gordon Gilbert
+=+
| Angels' Roost Farm |
| Rev. Dn. Gordon Gilbert Susan Gilbert |
| 705-549-5056 |
|[EMAIL PROTECTED] |
|[EMAIL PROTECTED] |
+=+
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Comment marks
On Thursday 13 January 2005 07:15 am, Gordon Gilbert wrote:
Is it possible to comment out whole sections of your file? For example in
the process of trying something, would it work to comment out a whole
section of music or chords, or words like this?
%{
a b c d
d e f g
}
Comment marks are this: %{ %}
not this: %{ }
LilyPond ignores the whole thing. It isn't there. Of course
a brace within the marks will leave a brace outside
them unmatched. In your example though, if you typed
% a b c d
% d e f g
you would type two characters instead of four, so unless
you are using slyce and/or sly you would find two main
uses for long comments: to write a long comment at the
beginning or end of your file or to temporarily remove
a large portion as you are doing. daveA
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Comment marks
Gordon Gilbert wrote:
Is it possible to comment out whole sections of your file? For example
in the process of trying something, would it work to comment out a whole
section of music or chords, or words like this?
%{
a b c d
d e f g
}
Would that whole thing not be processed as it is? or would it just
choke at the unmatched braces?
Gordon Gilbert
+=+
| Angels' Roost Farm |
| Rev. Dn. Gordon Gilbert Susan Gilbert |
| 705-549-5056 |
|[EMAIL PROTECTED] |
|[EMAIL PROTECTED] |
+=+
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Of course it is possible, and you was near to get the right solution!
Simply enclose the part to comment between %{ and %}, i.e.
%{
a b c d
d e f g
%}
will ignore the two lines a b c d and d e f g.
Maurizio.
--
Maurizio Tomasi
Via Newton, 6
24126 Bergamo (Italy)
Tel. +39-02-23699308
http://www.geocities.com/zio_tom78/
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
No .ps for me?
Buoyed by my recent success in polyphonic typesetting, I tried to install LilyPond on my home PC. These are the versions I have: lilypond 2.4.2 ec-fonts-mftraced 1.0.9 mftrace 1.1.2 tetex 2.0.2 Now, LilyPond creates the .dvi file perfectly, but neither .ps or .pdf files. It turns out that the dvips call dvips -t a4 -u+ec-mftrace.map -u+lilypond.map -Ppdf music fails with `dvips: ! Couldn't find header file ecrm10' Sure enough, I don't have a file `ecrm10' anywhere. Now, someone on the list reported that problem and said that the solution was to replace `ecrm10' by `ecrm10.pfa', etc., in ec-mftrace.map. But if I do this, I get no text in the .ps file, and mktexpk says: kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 --dpi 8000 ecrm10 mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. mktexpk: Can't guess mode for 8000 dpi devices. mktexpk: Use a config file, or update me. So lilypond appears to demanding 8000 dpi fonts for everything, but I would need 600 dpi. How do I change this? (On my office machine I have lilypond 2.4.2 ec-fonts-mftraced 1.0.7 mftrace 1.0.34 tetex 2.0.2c-3 and the same input works perfectly.) -- Kilian FothPhone +49 40 42883-2518 AB NATS, FB Informatik Fax +49 40 42883-2515 Universität Hamburg Vogt-Kölln-Str. 30 22527 Hamburg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \skip in lyricmode
Mats Bengtsson [EMAIL PROTECTED] schrieb am 12.01.05 10:09:54: If you use \lyricsto or \addlyrics, than the durations of each lyrics syllable is completely determined by the rhythm of the music voice that you have attached the lyrics to, so in that situation a \skip X will just denote a space with the same duration as the corresponding note, just as you have observed. However, if you don't use \lyricsto or \addlyrics and explicitly specify the durations for each syllable, then \skip 1 will work exactly as you expected. So, if you use \lyricsto, the character _ (underline) is much more convenient and stands for one syllable, too. Best wishes Michael ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Intelligently joining multiple songs?
Hi, I created some pieces based on the satb.ly template (started with 2.2.5 and converted to 2.4.2). Now I'm searching for an intelligent way to join them in one big file. Optimally I'd like to select only one voice from all input files. I did not find any \input command or such. Does anybody have a solution to that? Bye Michael ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar lines
\time 4/4 r4 R4*3 | This fails reproduceably in 2.4.2 (or am I coding nonsense here)? Unless I'm mistaken, R (capital R) is only for multi-measure rests, which means: to be used when one or more measures are completely empty except for the pause sign. Best, Gilles ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Intelligently joining multiple songs?
It's described in the Tutorial! /Mats Michael Kallas wrote: Hi, I created some pieces based on the satb.ly template (started with 2.2.5 and converted to 2.4.2). Now I'm searching for an intelligent way to join them in one big file. Optimally I'd like to select only one voice from all input files. I did not find any \input command or such. Does anybody have a solution to that? Bye Michael ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Bar lines. Was: Lilypond pieces already entered
Michael Kallas wrote: Barcheck is really great, yes, but I've found some times it fails when it shouldn't. Try for example: \time 4/4 r4 R4*3 | This fails reproduceably in 2.4.2 (or am I coding nonsense here)? As has already been pointed out by others, your example doesn't really make sense, since R gives you a full bar rest (or more of them). Still, the bar check should work, so I send a copy to the bug reporting mailing list. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
How to go back in time
I'm trying to regenerate some old stuff with lilypond 1.9.5. I have a .deb package, that warns me that I'm regressing, but seems to replace the 2.0 version of lilypond that I've been using fine. When I run lilypond everything looks as I expect. But when I run lilypond-book, I get terrible font problems. (noteheads as punctuation, clefs as bars, etc.) Is lilypond-book maybe getting its fonts from somewhere wierd where I have 2.0 fonts that haven't been removed? Does anyone have any other ideas for what to try? -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Fret Diagram height
Lilypond Version 2.4.2 on Cygwin...
Is there a similar method of adjusting the positioning of Fret Diagrams?
I've tried both \override Fret #'minimum-spacing = #5 and \override
FretDiagram #'minimum-spacing = #5, but neither seem to affect the
resulting PDF. The intent is to have all Fret Diagrams a constant height
above the staff.
Thanks,
Nick
--
Message: 2
Date: Mon, 3 Jan 2005 22:09:05 +0100
From: Sven Axelsson [EMAIL PROTECTED]
Subject: RE: Volta brackets on different heights
To: lilypond-user@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
That seems to do the trick. Thanks.
-- P/S Sven Axelsson, The Murray Pipes Drums of Gothenburg
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: den 3 januari 2005 12:59
To: Sven Axelsson
Cc: lilypond-user@gnu.org
Subject: Re: Volta brackets on different heights
To quote an old answer I sent to the mailing list:
The trick is to increase the minimum-space property, which
determines the default minimum spacing between the bracket
and the stave. The default value is 5, so try something like
\override Score.VoltaBracket #'minimum-space = #7
/Mats
Sven Axelsson wrote:
Hello List.
This question is for Lilypond 2.4.2.
I've recently started to use Lilypond for typesetting music
for the Highland
Bagpipe, having used MusicTeX for many years before. The
bagpipe specific
stuff is working fine - I started out with Andrew McNabb's
definitions and
changed a lot of stuff to better suit my previous work.
One thing I'm encountering all the time now is that the
volta brackets for
adjacent alternatives are put on different height. I would
like to *always*
put the brackets at the same height by some magic in the
\layout section I am
including in my bagpipe.ly file. I have tried this:
\layout {
\context {
\Score
\override VoltaBracket #'padding = #3.0
}
}
with different numbers for the padding, but it has zero effect.
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Help for OSX setup.
Hi, Does anyone know if there exists any 'simple' step-by-step instructions for installing and running Lilypond on Mac OS X? I am not familiar with UNIX applications and need some really basic step-by-step help. Thanks! Mark. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
transparent measures
Hi there,
during my adventure with lilypond I came across a problem of invisible
measures. I need to have some of bars in some staves quite transparent.
To do so I moved the Staff_system_engraver form Staff context to Voice
(in addition this manipulation causes barlines to disappear, but
nevertheless...). Then I tried to make a bar (put in separate voice
context) in one staff transparent by changing its transparent
property, but it didn't work. But -- the same operation worked refering
to thickness property. I don't know if my way of thinking is going in
right way, but if someone has any idea, I would be greatful :)
And some code illustrating the problem:
\version 2.4.2
%this doesn't seem to change anything
%staOFF = { \override Staff.StaffSymbol #'transparent = ##t }
%staON = { \revert Staff.StaffSymbol #'transparent }
%this does its work.
staOFF = { \override StaffSymbol #'thickness = 2 }
staON = { \revert StaffSymbol #'thickess }
vnTwo = \relative c' {
\context Voice =Vn { r1 | c4 r4 r2 }
\context Voice =Vnt { \staOFF s1 }
\context Voice =Vn { | c4 }
}
vn = \relative c' {
r1
| c4 d e f |
}
\layout {
\context {
\Staff
\remove Staff_symbol_engraver
}
\context {
\Voice
\consists Staff_symbol_engraver
}
}
\score {
\context StaffGroup = violiniI
\context Staff =vnI \vn
\context Staff =vnII \vn
\context Staff =vnIII \vnWithGap
\context Staff =vnIV \vn
\context Staff =vnV \vn
%here come other instrumental groups
}
Sincerly yours,
Andrew
PS. I'm working on linux Gentoo (x86), but this should be of no
importance, shouldn't it?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to go back in time
It could happen that you have generated font files left over in some directory. To find out where, try to run the following commands and see what directory the file paths point at: kpsewhich feta20.pk kpsewhich feta20.pfa if any of these paths point to a directory in /tmp/ or /var/ or something like that, you can safely remove all the files in that directory. Afterwards, you can run the command 'texhash' to update the TeX file name database. Regards /Mats Laura Conrad wrote: I'm trying to regenerate some old stuff with lilypond 1.9.5. I have a .deb package, that warns me that I'm regressing, but seems to replace the 2.0 version of lilypond that I've been using fine. When I run lilypond everything looks as I expect. But when I run lilypond-book, I get terrible font problems. (noteheads as punctuation, clefs as bars, etc.) Is lilypond-book maybe getting its fonts from somewhere wierd where I have 2.0 fonts that haven't been removed? Does anyone have any other ideas for what to try? -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fret Diagram height
Hi Nick, you could try something like \set Staff.minimumVerticalExtent = #'(-9 . 12) Thomas Lilypond Version 2.4.2 on Cygwin... Is there a similar method of adjusting the positioning of Fret Diagrams? I've tried both \override Fret #'minimum-spacing = #5 and \override FretDiagram #'minimum-spacing = #5, but neither seem to affect the resulting PDF. The intent is to have all Fret Diagrams a constant height above the staff. Thanks, Nick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fret Diagram height
Hi Nick, you could try somethinh like \set Staff.minimumVerticalExtent = #'(-9 . 12) Thomas Lilypond Version 2.4.2 on Cygwin... Is there a similar method of adjusting the positioning of Fret Diagrams? I've tried both \override Fret #'minimum-spacing = #5 and \override FretDiagram #'minimum-spacing = #5, but neither seem to affect the resulting PDF. The intent is to have all Fret Diagrams a constant height above the staff. Thanks, Nick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to go back in time
MB == Mats Bengtsson [EMAIL PROTECTED] writes: MB It could happen that you have generated font files left over MB in some directory. I think I've fixed it -- I had some environment variables set to point wrong. Thanks. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \skip in lyricmode
So--if I understand this correctly--the number after \skip is still
required in \lyricsto but doesn't do anything.
Realted to this, I have an introduction to a song that has a pickup text
(discussed in an earlier post). The text useed to appear on the and of
four in m.3. I added phrase marks and staccati to the introduction and
now the text won't appear. Using \skip, there is a point where the text
disappears.
I am using 2.4.2 under cygwin:
\version 2.4.2
#(set-default-paper-size letter)
%#(set-global-staff-size 25)
\header {
title = Casting Spells
poet = C J Ver Burg
composer = Charles Gran
tagline =
}
melody = {
\set Staff.extraNatural = ##f
\clef treble
\key f \minor
\time 2/2
%\tempo 2=60
{ f' aes'8-. f' aes'-. f' g' 4 f' aes'8-. f' aes'-. f'
g' 4 } \\ { c'4( b8) f-( c'4) b8 f-( }
{ c'' e''8-( b' d'' a' c'' c'' ees''~ c'' ees''4) r8
fes' aes'-( } \\ { aes2) aes c' ees'8-. aes c' ees'-. aes bes
d'4 }
{ aes' ces''8 ges' bes' f' aes') d' f'-( e' c''4.) c'8 }
\\ { aes ees'4 bes bes d'8-. bes d'-. c g bes4 }
}
pickup = \lyricmode {
\skip 8 \skip 8 \skip 8 \skip 8 \skip 8 \skip 8
\skip 8 \skip 8 \skip 8 \skip 8 \skip 8
\skip 8 \skip 8 \skip 8 \skip 8 \skip 8
It's
}
harmonies = \chordmode {
r1 r1 r1
}
\score {
\context ChordNames {
\set chordChanges = ##t
\harmonies
}
\context Voice = one {
\melody
}
\lyricsto 1 \new Lyrics \pickup
\layout { }
\midi { \tempo 2=60 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Accidentals
Hi From: Paul Scott [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: J L [EMAIL PROTECTED] CC: lilypond-user@gnu.org Subject: Re: Accidentals Date: Mon, 06 Dec 2004 23:15:39 -0700 A similar thing happened with a key signature change. i.e. G major to A major resulted in F-natural + F-sharp C-sharp G-sharp It would be good if there was a way to prohibit this. \set Staff.printKeyCancellation = ##f does that. Maybe I didn't give a good example. By setting key cancellation to none, ALL key cancellations are not printed. A major to E major in LilyPond would normally be F-natural + C-natural + G-natural + F-sharp + C-sharp + G-sharp + D-sharp. While normally, only F-sharp + C-sharp + G-sharp + D-sharp would be printed. what about the other way around E major to A major in LilyPond would normally be F-natural + C-natural + G-natural + D-natural + F-sharp + C-sharp + G-sharp. Normally, just F-sharp + C-sharp + G-sharp + D-natural would be printed. Any ideas anyone? Aligorith _ Surf the net and talk on the phone with Xtra JetStream @ http://xtra.co.nz/jetstream ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
