I've been trying to compile lilypond 2.0 on a FreeBSD machine. Configure
completed with a "warning". However, I tried to compile anyway. It seems
that the warning and the compile error are independent of each other. I
was wondering if there was a work-around or an update?
Thanks,
Chris.
# W
A 06/10/03 13:25:15
Mats Bengtsson <[EMAIL PROTECTED]> escribió:
>
> It seems that the correct handling is only implemented for texi
> documents, not for LaTeX documents. However, there's a simple
> workaround, just add the line
> \newcommand{\lilypondbook}{}
> somewhere before \begin{document}.
> > 1) All the text should be in the same line. But the text breaks
> > after the lilypond code.
> > Some notes used \lilypond[11pt]{c' e' g'} inline.
>
> It seems that the correct handling is only implemented for texi
> documents, not for LaTeX documents. However, there's a simple
> workaround, j
By default, LilyPond uses a new MIDI channel for each stave.
If you want to squeeze in more parts in the available 16
MIDI channels, I guess it's easiest to define a separate
\score{} context for the MIDI version of your music.
As long as you have used identifiers for all the different
parts, it's
Jonathan Levi MD wrote:
Dear LilyPond Team,
Thank you very much for LilyPond!
I'm attaching a two-file tarball of what appears to be a bug in
association with single-stem tremolos (they cause LilyPond to crash when
I attempt to combine them with another tremolo).
Additionally, may I note a s
José Luis Cruz wrote:
Hi list,
there are two things that doesn't goes, when including lilypond code into latex. And
according to the documentation, they are supported. I give 2 examples.
I should be very much obliged if anybody could bring some light about this. My lilypond \version
= "2.0.0"
Why are rehearsal marks placed to the left of the clef symbol? I don't
see this in other printed music or in Finale's output. Placing
rehearsal marks to the right of the clef symbol would solve one of my
problems and make it look like other printed music.
Maybe, this is a bug. I noticed in scm
