[EMAIL PROTECTED] writes:
> Many thanks for the suggestion. This is s close it loses the
> 'rehearsal mark' font for the "23" and the "*N" (it comes out the same as
> normal lyrics text.) My next attempt was
>
> \mark #'(lines (mark "23") (mark "*N") (music "scripts-segno"))
>
> but tha
[EMAIL PROTECTED] writes:
> Is it possible to pass two music expressions to a scheme function
> as arguments?
>
no, but you can use
\apply #func { arg1 arg2 }
this passes a sequential music with 2 elts to func.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
Hello,
Is there a way to print the chord names _under_ the volta bars ?
I saw some stuff in the archives but doesn't quite work
(at least not on 1.6.7).
BTW while searching the archives I saw that several people were
interested in reducing the font size for chords. This is what I
managed to come
In message <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
> Graham Percival wrote:
> >
> > Hmm. Unfortunately Mutopia is down right now, so I can't check, but
> > what version is that lilypond source?
> > Near the top of the/a file(s), there should be a line something like
> > this:
> >
Mats,
thanks for the update ... glad to know I'm *not* going crazy ... I did
wonder for a while.
Just starting to get into it ... printed out my first score today,
WoHoo! Looks Great!
Cheers.
Jonathan.
On Mon, 24 Feb 2003 11:26:06 +0100, you wrote:
>It seems that noone else who answered bother
I'm using Lilypond (1.6.6-1, installed from RPM binaries to Red Hat 7.3) primarily for
my barbershop quartet music, and I'm having a little trouble finding the right way to
show lyrics.
In a typical quartet piece, all four parts sing the same words *most of the time*, but
there are spots where
First off, thanks very much to those who responded to my question about
partial scores.
I notice that the emacs info documentation comes with this in the top-level
file (lilypond.info):
START-INFO-DIR-ENTRY
* GNU LilyPond: (lilypond).The GNU music typesetter.
* ly2dvi: (lilyp
On Monday 24 February 2003 11:04 am, Mats Bengtsson wrote:
> David Raleigh Arnold wrote:
> > I think that lilypond contributes its own version of config,ps,
> > in order to print with a4 paper. TeTeX TeX and LaTeX
> > have lettersize as the default, (I hope. An European
> > maintainer might chang
Many thanks for the suggestion. This is s close it loses the
'rehearsal mark' font for the "23" and the "*N" (it comes out the same as
normal lyrics text.) My next attempt was
\mark #'(lines (mark "23") (mark "*N") (music "scripts-segno"))
but that did not change to the rehearsal mark f
On Mon, Feb 24, 2003 at 04:52:49PM +0100, Mats Bengtsson wrote:
> There are probably simpler methods to achieve what you want to do.
> Take a look at the two collections of examples at the web page,
> Go to lilypond.org, click on Documentation:Index and then on
> "tips-and-tricks" and "Regression T
How about (untested)
\mark #'(lines "23" "*N" (music "scripts-segno"))
/Mats
Hans Forbrich wrote:
The source for the current score I'm working has multiple 'marks' on the
same bar - the bar I'm looking at has a 'rehearsal mark (circled bar
number)', a 'segno' and a 'narrator's mark ("*N")' st
The source for the current score I'm working has multiple 'marks' on the
same bar - the bar I'm looking at has a 'rehearsal mark (circled bar
number)', a 'segno' and a 'narrator's mark ("*N")' stacked at the same
spot.
If I use multiple \mark indicators [\mark "23" \mark "*N", \mark
#'(music "scri
David Raleigh Arnold wrote:
I think that lilypond contributes its own version of config,ps,
in order to print with a4 paper. TeTeX TeX and LaTeX
have lettersize as the default, (I hope. An European
maintainer might change it.)
which is why you can delete the lines instead
of changing them.
This i
On Monday 24 February 2003 05:20 am, Mats Bengtsson wrote:
> That's really weird. I notice you have a brand new version of
> Ghostscript, could it be a bug in that? BeginPaperSize should
> be a standard construct as far as I know. I'd look for more
> information at www.ghostscript.com.
>
> Anyway,
There are probably simpler methods to achieve what you want to do.
Take a look at the two collections of examples at the web page,
Go to lilypond.org, click on Documentation:Index and then on
"tips-and-tricks" and "Regression Tests" respectively.
The Regression tests document contains an example on
Take a look at some of the lyrics examples in the tips-and-tricks
document (third time today that I refer to the same document on
the mailing list!). Go to lilypond.org, click on Documentation:Index
and then on tips-and-tricks and search for "lyrics".
/Mats
Christ van Willegen wrote:
Mats Beng
On Sunday 23 February 2003 06:04 am, Michael Vanier wrote:
> Quick question: is there a way to force lilypond to make all the bars
> on a single line equally wide? I realize that this isn't usually the
> right thing to do for a finished score, but I'm using it to write
> partial scores that I will
After I set up guile-1.4 (RH7.3 ships with guile-1.3.4)
lilypond-1.6.7 configure ends with:
) WARNING: Please consider installing optional programs: pktrace mftrace
)
) See INSTALL.txt for more information on how to build LilyPond
) Remove config.cache before rerunning ./configure
)
) Type:
)
Graham Percival wrote:
>
> Hmm. Unfortunately Mutopia is down right now, so I can't check, but
> what version is that lilypond source?
> Near the top of the/a file(s), there should be a line something like
> this:
> \version "1.2.14"
Fur Elise is old enough it doesn't even _have_ a version ID :-
This, and tons of other features, can be found in the
"tips-and-tricks" document. Just go to lilypond.org,
click on Documentation:Index and then on tips-and-tricks.
The example you should look at is partial-blank.ly
/Mats
Michael Vanier wrote:
Quick question: is there a way to force lilypond to
I agree with you, and I would be sad I you should think I critic
lilypond or the people who work on it. The project is impressive and
thanks to it, I've be able to produce beautiful sheet music since 99.
I don't think I will use so much a graphical music program, as I don't
use word processor b
Never mind -- it turns out that the error was happening in the next line.
An off-by-one error in the line count, I guess, or else emacs' line
numbering doesn't match lilypond's.
Mike
> Date: Mon, 24 Feb 2003 03:16:47 -0800
> From: Michael Vanier <[EMAIL PROTECTED]>
>
> I'm getting strange warni
I'm getting strange warning messages in a lilypond file that are unrelated
to the contents of the line being warned about:
foo.ly:147:6: warning: unbound spanner `Beam':
s1
foo.ly:147:6: warning: beam has less than two visible stems:
s1
foo.ly:147:6: warning: Beam has less than tw
On Sun, 23 Feb 2003 03:04:18 -0800
Michael Vanier <[EMAIL PROTECTED]> wrote:
> Quick question: is there a way to force lilypond to make all the bars on a
> single line equally wide? I realize that this isn't usually the right
> thing to do for a finished score, but I'm using it to write partial sc
On Sun, 23 Feb 2003 10:51:57 +0100
Alexandre Beneteau <[EMAIL PROTECTED]> wrote:
> Would you agree if I would say lilypond's error messages are sometimes
> confusing ?
I'll agree that some programs have more useful error messages. However,
I don't intend that statement to be a criticism of the wo
On Sun, 23 Feb 2003 21:58:38 -0800
[EMAIL PROTECTED] wrote:
> I have a copy of Fur Elise that I downloaded from mutopia, then
> hacked^H^H^H^H^H^Harranged for Flute and Viola, that I need to
> make some edits on. But I can't for the life of me get a version
> of lilypond that reads it, or for that
It's really hard to give any advice without more information.
Please send us the output of
ly2dvi -V whateverfile.ly
which will give some more printouts on what might have gone
wrong.
When you built the program, did you have to install anything
extra efter you first issued configure? In that case,
Pete Young wrote:
...
That allowed me to fix a few 'syntax' errors in lilypond-book.py,
the 'import lilypond as ly' one I reported earlier and use of the
' += ' operator - maybe this is a consequence of me having python 1.5
rather than python 2?
Note that the fix you suggested in an earlier emai
It seems that noone else who answered bothered to actually take a
look at the file you refer to. The PS and PDF versions of the
manual for the stable Lilypond version are indeed broken.
The underlying problem is an error in the font setup for the
Type1 versions of the musical fonts. For the moment,
That's really weird. I notice you have a brand new version of
Ghostscript, could it be a bug in that? BeginPaperSize should
be a standard construct as far as I know. I'd look for more
information at www.ghostscript.com.
Anyway, the problem is not at all related to Lilypond. The lines
are generated
Also, there a bug in the latest stable versions 1.6.x. If you
try to use the Type1 (vectorized) fonts instead of the default
Type3 (bitmapped) fonts, the wrong fonts will be shown in the
Postscript or PDF. I think that's what happened to you.
The simple solution, if you just want a PS file to view
31 matches
Mail list logo